Troubleshooting Tips for Your TREX Implementation in Internet Sales
- by Gil Magana, Principal Consultant, Intelligroup
- April 15, 2007
Learn how you can install Text Retrieval and Information Extraction for Internet Sales to augment your E-Commerce functionality. Although the Basis team usually works with the CRM team on the implementation, the roles are often not clearly defined, which can lead to redundancy. These tips help the CRM team avoid this overlap by explaining how to complete the installation without relying on the Basis team.
Text Retrieval and Information Extraction (TREX) is a search and classification engine that SAP offers as an extension to many of its systems, including E-Commerce. It offers services for searching, classifying, and mining of data either in documents or business objects. You can install TREX as a standalone engine and use it in many SAP applications, including SAP CRM. A part of the search integration capabilities in SAP NetWeaver, TREX supports the search technology and functions for Search Engine Service for structured or unstructured searches.
Using Text Retrieval and Information Extraction (TREX) with Internet Sales (ISA), also known as E-Commerce, can help you improve your system’s performance, enhance product searches, and retrieve documents. It offers enhanced search capabilities not delivered as part of the standard E- Commerce platform. TREX also offers an ABAP- or Java-based design, which provides enhanced content and increased flexibility. This allows for product searches with multiple languages and fuzzy logic, document and image cataloging, and load balancing for a scalable architecture.
I recently worked with a client to troubleshoot its TREX implementation in ISA. As with any SAP component, installing TREX has no defined hand-off when it comes to task assignments of who does what. Basis resources usually tell you they are only responsible for installing the component. As such, the installation of TREX involves not only installing the component, but configuring it as well. This requires two or even three separate resources to work collectively to get the job done. If the CRM functional resource can handle these tasks, you can avoid redundancy.
I’ll show you how you can use TREX to take on what is typically a Basis task so you can perform most of the core tasks (installation, configuration, and troubleshooting techniques) on your own. In addition, I include examples with supporting references to streamline this process to minimize downtime incurred in troubleshooting errors and decrease installation time. My example illustrates the installation of a TREX 6.1 instance with an ISA 4.0 (ERP edition) implementation and an R/3 4.6C back- end system.
I describe the lessons learned in two different TREX projects — uninstalling a current TREX instance and installing a fresh instance of TREX. The steps noted here take into consideration the use of SAP Best Practices documentation, such as “Search and Classification (TREX) 6.1,” which you can find on SAP Service Marketplace. Note that you are not required to perform both procedures — either you have an issue with your current TREX component that requires you to perform an uninstall or you are installing TREX for the first time.
Would you like to see this full item?