Xi Clarifications

[Former Member]

Hi,

Can you please explain these stuffs. Belive it is part of BASIS, but are these necessary to be taken care as part of Go-Live.

u2022 Check Logs of import/deployment

u2022 Setup indexing for TREX

u2022 Add new Channels to Communications Channel Inventory List

u2022 Add Interfaces to XI Message Archiving

u2022 Check EOIO settings

[Former Member]

HI

TREX

TREX is a product from SAP for searching and classifying large collections of documents. TREX stands for SAP NetWeaver Search and Classification (TREX) finds information in both structured and unstructured data.

TREX is a like a search engine which provides SAP applications to search structured and unstructured data.And it can read the images for the searching query.

TREX is based on a client/server architecture. The client component is integrated into the application that uses the TREX functions, and allows communication with the TREX servers.

The server component processes the requests; it indexes and classifies documents and answers search queries.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/78df2a46-0a01-0010-ef81-a6be60cc....

TREX provides several client options:

Java client for communication via HTTP/XML in SAP EP

ABAP client for communication via RFC or ICM in SAP landscape

C++ and Python clients for internal calls and development

Inside TREX there are four main services:

Name server: manages TREX landscape, allocates TREX services

Index server: indexing and retrieval

Text-mining engine for classification and similarity search

Text search engine for search and indexing unstructured text Attribute/BIA engine for searching and indexing structured data

Queue server: manages asynchronous indexing

Preprocessor: document retrieval, filtering, linguistic processing

TREX Queue Server

􀂄 Collects indexing requests

u2013 Sends them to the index server

􀂄 Enables asynchronous indexing

u2013 Scheduled

u2013 Event triggered

􀂄 Includes scheduler for replication

u2013 Replication runs on index server

􀂄 Stores snapshots for replication

TREX Preprocessor

􀂄 Delivers documents that the engines can use directly

􀂄 Supports almost any data type

􀂄 Gets documents via HTTP from source

􀂄 Converts documents to HTML

􀂄 Keeps the document structure

􀂄 Extracts attributes

u2013 Metadata from DOC, PDF, ...

u2013 Names from a lexicon

u2013 Application-specific attributes

􀂄 Performs linguistic processing

u2013 Tokenization

u2013 Stemming

u2013 Tagging

(using third party products)

The TREX administration tool is the place to:

􀂄 Set up and configure a distributed landscape

􀂄 Monitor and administer services, indexes, queues, replication, ...

􀂄 Show trace files, configuration files, version info, ...

There are three flavors:

􀂄 Standalone

u2013 Richest feature set

u2013 Requires full access to TREX host

􀂄 ABAP

u2013 Restricted feature set

u2013 Easy access on customer systems

􀂄 Java

u2013 Highly restricted feature set

cheers

reward points if found useful

Edited by: vemuganti naga phalguna on May 28, 2008 12:07 PM

[Former Member]

Hi,

TREX

*******

Its external search engine for SAP, we can buy this and install in the XI server.

ex : Suppose we have an order number, we don't no in which scenario it is used then we give this number to the TREX

then it searches and gives that scenarion name.

TREX is based on a client/server architecture. The client component is integrated into the

application that uses the TREX functions, and allows communication with the TREX servers.

The server component processes the requests; it indexes and classifies documents and answers

search queries.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/78df2a46-0a01-0010-ef81-a6be60cc...

[GabrielSagaya]

Are you using XI >> SP 19 ???

please check it

https://websmp208.sap-ag.de/~sapidb/011000358700006308412006E.xls

TREX

******

TREX normally queries content snippets or "Did you mean" terms every time you execute a search. If you do not display content snippets or "Did you mean" terms in your search iView, you can deactivate this query. This can significantly improve search performance.

XI Message Archiving

**************************

In XI All the data are transferred in form of messages and it may necessary to Archive data for future references .When we do the Archiving all the processed messages will be out of system and also it improves the performance. In General Rule the messages are multiplied into 10 times when compared to data which is sent

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/402fae48-0601-0010-3088-85c46a23...

http://help.sap.com/saphelp_nw04/helpdata/en/fc/e6173d3215cc40e10000000a114084/frameset.htm

EOIO settings

****************

the queue ID was used for serialization in the Adapter Engine.

http://help.sap.com/saphelp_nw04/helpdata/en/45/0ff940964e04a8e10000000a155369/content.htm