PipeLine Directory in XI

Hello All,
I have small doubt relating to XI pipeline directory which is an Interview question
1>What is meant by XI Pipeline Directory ?
2>What is the basic usage of this directory and importance of it ?
Best Regards
Rakesh

Hi,
>>What is meant by XI Pipeline Directory ?
>>What is the basic usage of this directory and importance of it
Pipeline is the term used to refer to all steps that are performed during the processing of an XML message.
A pipeline represent a fixed processing run for particular XML messages and differs from other pipelines depending on the configuration of the Integration Engine. There are pipelines for a local Integration Engine in the sender or receiver system, or for a central Integration Engine that is configured as the Integration Server, for example.
The individual processing steps are called pipeline services and are defined in pipelines.
There are also special pipelines for processing acknowledgment messages (BACK pipelines) and for messages sent or received by a business system using the Web service protocol (WS_SENDER or WS_RECEIVER).
Regards,
sangeetha

Similar Messages

Developer studio does not update pipeline

Hi
I created my first Endeca app, called testapp2.
The app seems correctly provisioned, then I created a project in developer studio with the same name of the app.
I issue "set instance configuration" and it seems sto work , but in /app/oracle/product/endeca/apps/testapp2/config/pipeline the file ar not updated.
The strange things is that if I make a change in the project, the I revert back by issuing "get instance configuration" the previous configuration is correctly loaded in the project. This gives me the idea that configuration are strored somewhere but not where I am looking to.
Any Idea?
Regards
Giuseppe

That isn't what set instance configuration does, that is why it doesn't work - you are using a utility to update a completely separate piece of software called Merchandising Workbench.
If you want to apply changes to the configuration to a different server you would copy the changed pipeline directory there. I.e. if you are editing the pipeline on your local PC, say in C:\Endeca\applications\testapp2\config\pipeilne, you would change things in Developer Studio, click the Save button, then open up whatever you use for file copies and copy the contents of C:\Endeca\applications\testapp2\config\pipeline\* to /app/oracle/product/endeca/apps/testapp2/config/pipeline. Then you would run a baseline via /app/oracle/product/endeca/apps/testapp2/control/baseline_update.sh.
Michael

Unable to connect multiple MAF components in a WPF host application

I'm trying to connect my MAF component parts for the addin extensibility to work, however I'm getting certain errors while trying to build my add in store.
string path = @"...\MyProject\Extensibility\Output";
string[] errorList = AddInStore.Rebuild(path);
that's the pipeline path, which looks like according to documentation:
Extensibility\
Output\
AddIns
AddInSideAdapters
AddInViews
Contracts
HostSideAdapters
My WPF host app DLL file is located under this directory:
MyProject\WPFApp\bin\debug
So, I'm unsure where to build my HostView. Currently the output is the pipeline root directory (Extensibility\Output)
I have 4 errors in my errorList:
While examining an assembly for pipeline segments, got a ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information. File Name: ...MyProject\Extensibility\Output\AddInSideAdapters\AddInSideAdapters.dll
2:
Could not connect up a part in a pipeline to its neighbors: Contract Name: "IAddInContract" Location: "Contracts\Contracts.dll".
3:
Could not connect up a part in a pipeline to its neighbors: AddInBase Name: "AddInView" Location: "AddInViews\AddInViews.dll".
4:
Could not connect 2 valid add-in model parts.
And the code of addin side adapter, contact and addin view respectively:
[AddInAdapter]
public class AddInSideAdapter : ContractBase, IAddInContract
private AddInView view;
public AddInSideAdapter(AddInView view)
this.view = view;
public void Initialize(IPluginHandler handler)
view.Initialize(handler);
public INativeHandleContract GetCustomUI()
return FrameworkElementAdapters.ViewToContractAdapter(view.GetCustomUI());
[AddInContract]
public interface IAddInContract: IContract
void Initialize(IPluginHandler handler);
INativeHandleContract GetCustomUI();
[AddInBase]
public abstract class AddInView
public abstract void Initialize(IPluginHandler handler);
public abstract FrameworkElement GetCustomUI();
They're output directories are ok, all building into the corresponding pipeline segments. I really cannot understand what's failing. Pipeline structure is ok, build paths of segments are ok (just not sure about the HostView and the host app). The path variable
is ok, i just omitted the entire path for brevity

Hi Mefhisto,
>>”So, I'm unsure where to build my
HostView. Currently the output is the pipeline root directory”
I found some information about your problem in “Pipeline Development Requirements”,It said “The host application and the host view are typically deployed
in the same directory. The pipeline directory can be in any location but is typically in the same directory as the host application.”This is the link of the document :
https://msdn.microsoft.com/en-us/library/bb384240(v=vs.90).aspx. And there are several samples,you can refer to it for reference.
http://clraddins.codeplex.com/wikipage?title=Samples&referringTitle=Home

Issue in workbench integration with Dev studio on unix machine

Hi,
I am trying to integrate my workbench on unix machine with dev studio on windows machine. To do so, I did the following:
1. created a new application in dev studio
2. In dev studio - Tools - Workbench settings I gave the host and port of my unix workbench. It was able to connect properly.
3. Then through Tools - Workbench - Set Instance Configuration, I sent these configurations of my application on dev studio to that of workbench(which I had selected earlier in step #2)
4. Then in my unix machine, I replaced the wine data with my new data feed
5. Ran initialize services, load baseline update and baseline update scripts.
5. My baseline update script Failed at Forge with the following error:
FATAL     03/07/13 12:21:30.718 UTC (1362658890718)
+FORGE     {config}: Could not open "/app/ENDECA/endeca/endeca/apps/Test/data/processing/wine_data.txt.gz": No such file or directory     +
+ERROR     03/07/13 12:21:30.719 UTC (1362658890719)     FORGE     {config}: Forge failed with 1 error and 0 warnings.+
I am not able to figure out why it is still looking for wine data. Any suggestions on this are highly welcome!
Thanks,
Vineet

Vineet,
Using a text editor, search for "wine.data.txt.gz" in your ./Test/config/pipeline/pipeline.epx. If you find it, note the record adapter's name trying to read it and then remove it in DEV Studio and reupload your pipeline project. If you don't find it, check the same file in the ./Test/data/processing/pipeline.epx directory. If you find it there, you may have an issue with your baseline update script as defined in your ./Test/config/script/AppConfig.xml file. Make sure that your Forge.getConfig(); command is successfully copying contents from the ./Test/config/pipeline directory to the ./Test/data/processing directory (you may want to clear out the processing directory before your next run to make sure of it).
HTH,
Dan
http://branchbird.com

How to create Dimension group in ATG-endeca ecommerce application

We have requirement where we have to specify dimensions and their schema from BCC in ATG. Now the problem is we want to dimension groups and we don't see anywhere in documents to create it. Since this dimensions are created through FCM so we are not able to see in /config/pipeline directory but we see only in processing directory. So we don't see any means to create dimension group through dev studio too. Please tell us how we can do it.

we have to do it through EP interface through BP TMS.
1. connect EP to SAP system
2. Configure all the iviews of TMS business package so it can communicate with SAP system (change only SAP system name for all iviews)
3. Assign the roles to user of EP
4. run application using TMS

How it is possible to reflect workbench changes on clustered environment

Hi All,
I am running endeca on MachineA and MachineB with separate MDEX engine.
Cluster dgraph is implemented on MachineA with MachineB, thus data will updated on machineB when i run baseline update on MachineA.
I have installed Experience Manager on MachineA and created some pages using Workbench.
The rules are getting fired for MachineA without baseline update, but i noticed that same are not working for MachineB even though both machines are in cluster.
When i run baseline update on MachineA rules are working with MachineB.
How it is possible to reflect workbench changes on both clustered MDEX engine without running baseline update.
Please share your suggestion.
Thanks in Advance,
SunilN

Hi Guys,
I have tried to both approaches which you have suggested me.
But still the rules are not fired for MachineB.
I have tested it endeca_jspref on MachineB it the rules are not getting reflected for MachineB.
Below is my MachineA AppConfig.xml file :
<?xml version="1.0" encoding="UTF-8"?>

<spr:beans xmlns:spr="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:tx="http://www.springframework.org/schema/tx"
xmlns:aop="http://www.springframework.org/schema/aop"
xmlns="http://www.endeca.com/schema/eacToolkit"
xsi:schemaLocation="
http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.0.xsd
http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.0.xsd
http://www.endeca.com/schema/eacToolkit http://www.endeca.com/schema/eacToolkit/eacToolkit.xsd">
<app appName="WineStore" eacHost="MachineA" eacPort="8888"
dataPrefix="WineStore" sslEnabled="false" lockManager="LockManager">
<working-dir>${ENDECA_PROJECT_DIR}</working-dir>
<log-dir>./logs</log-dir>
</app>
<host id="ITLHost" hostName="MachineA" port="8888" />
<host id="MDEXHost" hostName="MachineA" port="8888" />
<host id="MDEXHost2" hostName="MachineB" port="8888" />
<host id="webstudio" hostName="MachineA" port="8888" >
<directories>
<directory name="webstudio-report-dir">./reports</directory>
</directories>
</host>
<lock-manager id="LockManager" releaseLocksOnFailure="true" />
<script id="InitialSetup">
<bean-shell-script>
<![CDATA[
    if (ConfigManager.isWebStudioEnabled()) {
      log.info("Updating Oracle Endeca Workbench configuration...");
      ConfigManager.updateWsConfig();
      log.info("Finished updating Oracle Endeca Workbench.");
]]>
</bean-shell-script>
</script>
<script id="BaselineUpdate">
<log-dir>./logs/provisioned_scripts</log-dir>
<provisioned-script-command>./control/baseline_update.bat</provisioned-script-command>
<bean-shell-script>
<![CDATA[
    log.info("Starting baseline update script.");
    // obtain lock
    if (LockManager.acquireLock("update_lock")) {
      // test if data is ready for processing
      if (Forge.isDataReady()) {
        if (ConfigManager.isWebStudioEnabled()) {
          // get Web Studio config, merge with Dev Studio config
          ConfigManager.downloadWsConfig();
          ConfigManager.fetchMergedConfig();
        } else {
ConfigManager.fetchDsConfig();
// clean directories
Forge.cleanDirs();
PartialForge.cleanCumulativePartials();
Dgidx.cleanDirs();
// fetch extracted data files to forge input
Forge.getIncomingData();
LockManager.removeFlag("baseline_data_ready");
// fetch config files to forge input
Forge.getConfig();
// archive logs and run ITL
Forge.archiveLogDir();
Forge.run();
Dgidx.archiveLogDir();
Dgidx.run();
// distributed index, update Dgraphs
DistributeIndexAndApply.run();
// if Web Studio is integrated, update Web Studio with latest
// dimension values
if (ConfigManager.isWebStudioEnabled()) {
ConfigManager.cleanDirs();
Forge.getPostForgeDimensions();
ConfigManager.updateWsDimensions();
// archive state files, index
Forge.archiveState();
Dgidx.archiveIndex();
// (start or) cycle the LogServer
LogServer.cycle();
} else {
log.warning("Baseline data not ready for processing.");
// release lock
LockManager.releaseLock("update_lock");
log.info("Baseline update script finished.");
} else {
log.warning("Failed to obtain lock.");
]]>
</bean-shell-script>
</script>
<script id="DistributeIndexAndApply">
<bean-shell-script>
<![CDATA[
    DgraphCluster.cleanDirs();
    DgraphCluster.copyIndexToDgraphServers();
    DgraphCluster.applyIndex();
      ]]>
</bean-shell-script>
</script>
<script id="LoadXQueryModules">
<bean-shell-script>
<![CDATA[
    DgraphCluster.cleanLocalXQueryDirs();
    DgraphCluster.copyXQueryToDgraphServers();
    DgraphCluster.reloadXqueryModules();
      ]]>
</bean-shell-script>
</script>
<script id="ConfigUpdate">
<log-dir>./logs/provisioned_scripts</log-dir>
<provisioned-script-command>./control/runcommand.bat ConfigUpdate run</provisioned-script-command>
<bean-shell-script>
<![CDATA[
    log.info("Starting dgraph config update script.");
    if (ConfigManager.isWebStudioEnabled()) {
      ConfigManager.downloadWsDgraphConfig();
      DgraphCluster.cleanLocalDgraphConfigDirs();
      DgraphCluster.copyDgraphConfigToDgraphServers();
      DgraphCluster.applyConfigUpdate();
    } else {
log.warning("Web Studio integration is disabled. No action will be taken.");
log.info("Finished updating dgraph config.");
]]>
</bean-shell-script>
</script>
<custom-component id="ConfigManager" host-id="ITLHost" class="com.endeca.soleng.eac.toolkit.component.ConfigManagerComponent">
<properties>
<property name="webStudioEnabled" value="true" />
<property name="webStudioHost" value="MachineA" />
<property name="webStudioPort" value="8006" />
<property name="webStudioMaintainedFile1" value="thesaurus.xml" />
<property name="webStudioMaintainedFile2" value="merch_rule_group_default.xml" />
<property name="webStudioMaintainedFile3" value="merch_rule_group_default_redirects.xml" />
     <property name="webStudioMaintainedFile4" value="merch_rule_group_MobilePages.xml"/>
     <property name="webStudioMaintainedFile5" value="merch_rule_group_NavigationPages.xml"/>
     <property name="webStudioMaintainedFile6" value="merch_rule_group_SearchPages.xml"/>
</properties>
<directories>
<directory name="devStudioConfigDir">./config/pipeline</directory>
<directory name="webStudioConfigDir">./data/web_studio/config</directory>
<directory name="webStudioDgraphConfigDir">./data/web_studio/dgraph_config</directory>
<directory name="mergedConfigDir">./data/complete_index_config</directory>
<directory name="webStudioTempDir">./data/web_studio/temp</directory>
</directories>
</custom-component>
<forge id="Forge" host-id="ITLHost">
<properties>
<property name="numStateBackups" value="10" />
<property name="numLogBackups" value="10" />
</properties>
<directories>
<directory name="incomingDataDir">./data/incoming</directory>
<directory name="configDir">./data/complete_index_config</directory>
<directory name="wsTempDir">./data/web_studio/temp</directory>
</directories>
<args>
<arg>-vw</arg>
</args>
<log-dir>./logs/forges/Forge</log-dir>
<input-dir>./data/processing</input-dir>
<output-dir>./data/forge_output</output-dir>
<state-dir>./data/state</state-dir>
<temp-dir>./data/temp</temp-dir>
<num-partitions>1</num-partitions>
<pipeline-file>./data/processing/pipeline.epx</pipeline-file>
</forge>
<dgidx id="Dgidx" host-id="ITLHost">
<properties>
<property name="numLogBackups" value="10" />
<property name="numIndexBackups" value="3" />
</properties>
<args>
<arg>-v</arg>
</args>
<log-dir>./logs/dgidxs/Dgidx</log-dir>
<input-dir>./data/forge_output</input-dir>
<output-dir>./data/dgidx_output</output-dir>
<temp-dir>./data/temp</temp-dir>
<run-aspell>true</run-aspell>
</dgidx>
<dgraph-cluster id="DgraphCluster" getDataInParallel="true">
<dgraph ref="Dgraph1" />
<dgraph ref="Dgraph2" />
     <dgraph ref="Dgraph3" />
</dgraph-cluster>
<dgraph-defaults>
<properties>
<property name="srcIndexDir" value="./data/dgidx_output" />
<property name="srcIndexHostId" value="ITLHost" />
<property name="srcPartialsDir" value="./data/partials/forge_output" />
<property name="srcPartialsHostId" value="ITLHost" />
<property name="srcCumulativePartialsDir" value="./data/partials/cumulative_partials" />
<property name="srcCumulativePartialsHostId" value="ITLHost" />
<property name="srcDgraphConfigDir" value="./data/web_studio/dgraph_config" />
<property name="srcDgraphConfigHostId" value="ITLHost" />
<property name="srcXQueryHostId" value="ITLHost" />
<property name="srcXQueryDir" value="./config/lib/xquery" />
<property name="numLogBackups" value="10" />
<property name="shutdownTimeout" value="30" />
<property name="numIdleSecondsAfterStop" value="0" />
</properties>
<directories>
<directory name="localIndexDir">./data/dgraphs/local_dgraph_input</directory>
<directory name="localCumulativePartialsDir">./data/dgraphs/local_cumulative_partials</directory>
<directory name="localDgraphConfigDir">./data/dgraphs/local_dgraph_config</directory>
<directory name="localXQueryDir">./data/dgraphs/local_xquery</directory>
</directories>
<args>
<arg>--threads</arg>
<arg>2</arg>
<arg>--spl</arg>
<arg>--dym</arg>
<arg>--xquery_path</arg>
<arg>./data/dgraphs/local_xquery</arg>
</args>
<startup-timeout>120</startup-timeout>
</dgraph-defaults>
<dgraph id="Dgraph1" host-id="MDEXHost" port="15000">
<properties>
<property name="restartGroup" value="A" />
<property name="updateGroup" value="a" />
</properties>
<log-dir>./logs/dgraphs/Dgraph1</log-dir>
<input-dir>./data/dgraphs/Dgraph1/dgraph_input</input-dir>
<update-dir>./data/dgraphs/Dgraph1/dgraph_input/updates</update-dir>
</dgraph>
<dgraph id="Dgraph2" host-id="MDEXHost" port="15001">
<properties>
<property name="restartGroup" value="B" />
<property name="updateGroup" value="a" />
</properties>
<log-dir>./logs/dgraphs/Dgraph2</log-dir>
<input-dir>./data/dgraphs/Dgraph2/dgraph_input</input-dir>
<update-dir>./data/dgraphs/Dgraph2/dgraph_input/updates</update-dir>
</dgraph>
<dgraph id="Dgraph3" host-id="MDEXHost2" port="15000">
<properties>
<property name="restartGroup" value="B" />
<property name="updateGroup" value="a" />
</properties>
<log-dir>./logs/dgraphs/Dgraph3</log-dir>
<input-dir>./data/dgraphs/Dgraph3/dgraph_input</input-dir>
<update-dir>./data/dgraphs/Dgraph3/dgraph_input/updates</update-dir>
</dgraph>
</spr:beans>
Do i need to change any things else.
Please suggest me.
Thanks
SunilN

ASMA Directory

Hi Guys,
Could someone please guide me with a problem that I am having using the file adapter's ASMA?
I am trying to pick-up a file using the file adapter and then place the file in a different directory also using the file adapter. I have selected the Directory ASMA in both adapters. I am also keeping the same filename. This part is working fine.
I am using a UDF to specify the target directory. The UDF contains that following code:
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
DynamicConfigurationKey key1 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","Directory");
String filename = conf.get(key);
conf.put(key, filename);
String directory = conf.get(key1);
directory = "/Central/Branches/70018/";
conf.put(key1, directory);
return a;
The problem that I am experiencing is that the file is placed back into the source folder, thus causing a loop. It appears that the UDF is not changing the target directory.
Thanks very much,
Miguel

Hi Bhavesh,
I have reactivated the message mapping and done a full cache refresh...
I cannot find the section of the trace that you have mentioned.
This is the trace that I get:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"><Trace level="1" type="T">Party normalization: sender </Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external = </Trace>
<Trace level="1" type="T">Sender party normalized = </Trace>
<Trace level="1" type="T">Party normalization: receiver </Trace>
<Trace level="1" type="T">Receiver scheme external = </Trace>
<Trace level="1" type="T">Receiver agency external = </Trace>
<Trace level="1" type="T">Receiver party external = </Trace>
<Trace level="1" type="T">Receiver party normalized = </Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST"></Trace>
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
<Trace level="2" type="T">Host = pgsap45.sap.pg.co.za:8001</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
<Trace level="2" type="T">Remote address = 172.16.1.108</Trace>
<Trace level="1" type="T">COMMIT is done by XMB ! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace>
<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB... </Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE">
</Trace>
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found </Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK. </Trace>
</Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="T">*                                                  * </Trace>
<Trace level="1" type="T">*                                                  * </Trace>
<Trace level="1" type="T">XMB entry processing </Trace>
<Trace level="3" type="T">system-ID = XIQ</Trace>
<Trace level="3" type="T">client = 300</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2007-08-28T13:57:48Z CAT </Trace>
<Trace level="1" type="T">*                                                  * </Trace>
<Trace level="1" type="T">*                                                  * </Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE"></Trace>
<Trace level="1" type="T">Message-GUID = 8489A912556E11DC9A030014220DCB99</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC"></Trace>
<Trace level="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = 8489A912556E11DC9A030014220DCB99</Trace>
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="3" type="T">Generate prefixed queue name </Trace>
<Trace level="1" type="T">Queue name : XBTI0002</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0002</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment </Trace>
<Trace level="3" type="T">Setup qRFC Scheduler </Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK! </Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = 8489A912556E11DC9A030014220DCB99</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">OK. </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message </Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking </Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST </Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC </Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye ! </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="3" type="T">Version number = 000</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace>
<Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK. </Trace>
<Trace level="3" type="T">Message was read from persist layer. OK. </Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK. </Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read </Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC"></Trace>
<Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = XIQ</Trace>
<Trace level="3" type="T">client = 300</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline attributes </Trace>
<Trace level="3" type="T">PID        = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE     = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE    = A</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline elements </Trace>
<Trace level="3" type="T">ELEMPOS    = 0001</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0002</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0003</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0004</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0007</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0008</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0009</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS    = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG     = </Trace>
<Trace level="3" type="T">FL_DUMMY   = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N </Trace>
<Trace level="1" type="T"> Cache Content is up to date </Trace>
<Trace level="2" type="T">Start without given receiver </Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules. </Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1 </Trace>
<Trace level="3" type="T">...create rule engine </Trace>
<Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET_SYSTEM(MSG=&_MSG&;SYSFIELD="FileName";SYSNSP="http://sap.com/xi/XI/System/File")% [*] 6* </Trace>
<Trace level="2" type="T">......attachment XI_Context not found </Trace>
<Trace level="3" type="T">......extracting from attachment: FileName = 70018_SendMSG_Payment_0_709_20070807052913.xml </Trace>
<Trace level="2" type="T">......extracting values found: 1 </Trace>
<Trace level="2" type="T">...invalid Receiver: - IP_Digicall_BranchPayment </Trace>
<Trace level="2" type="T">Check conditions for rule line no. 2 </Trace>
<Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET_SYSTEM(MSG=&_MSG&;SYSFIELD="FileName";SYSNSP="http://sap.com/xi/XI/System/File")% [*] 7* </Trace>
<Trace level="2" type="T">......attachment XI_Context not found </Trace>
<Trace level="3" type="T">......extracting from attachment: FileName = 70018_SendMSG_Payment_0_709_20070807052913.xml </Trace>
<Trace level="2" type="T">......extracting values found: 1 </Trace>
<Trace level="2" type="T">...valid Receiver with Condition: - SBO_DRP_SERVER </Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0 </Trace>
<Trace level="2" type="T">Number of Receivers:1 </Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">No persisting of message after plsrv call, because of config </Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS    = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG     = </Trace>
<Trace level="3" type="T">FL_DUMMY   = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N </Trace>
<Trace level="1" type="T"> Cache Content is up to date </Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) SBO_DRP_SERVER MI_Digicall_BranchPayment </Trace>
<Trace level="2" type="T">...valid InbIf without Condition: MI_Digicall_BranchPayment </Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1 </Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">No persisting of message after plsrv call, because of config </Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT"></Trace>
<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS    = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
<Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG     = </Trace>
<Trace level="3" type="T">FL_DUMMY   = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV"></Trace>
<Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="2" type="T">got property produced by receiver determination </Trace>
<Trace level="1" type="T">number of receivers: 1 </Trace>
<Trace level="1" type="T">Single-receiver split case </Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTO0___0000</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling </Trace>
<Trace level="1" type="T"> </Trace>
<Trace level="1" type="T">Going to persist message + call qRFC now... </Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking </Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST </Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye ! </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace>
<Trace level="3" type="T">Persisting message Status = 012</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK. </Trace>
<Trace level="3" type="T">Message was read from persist layer. OK. </Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK. </Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read </Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC"></Trace>
<Trace level="3" type="T">message version successfully read from persist version= 001</Trace>
<Trace level="2" type="T">Increment log sequence to 002</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = XIQ</Trace>
<Trace level="3" type="T">client = 300</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace>
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline attributes </Trace>
<Trace level="3" type="T">PID        = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE     = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE    = A</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline elements </Trace>
<Trace level="3" type="T">ELEMPOS    = 0001</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0002</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0003</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0004</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0007</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0008</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0009</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
<Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS    = CL_MAPPING_XMS_PLSRV3</Trace>
<Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG     = </Trace>
<Trace level="3" type="T">FL_DUMMY   = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="2" type="T">......attachment XI_Context not found </Trace>
<Trace level="3" type="T">Append context with name =Directory and value =/Ibolt/Transactions/Out </Trace>
<Trace level="3" type="T">Append context with name =FileName and value =70018_SendMSG_Payment_0_709_20070807052913.xml </Trace>
<Trace level="3" type="T">Mapping is already determined in the interface determination </Trace>
<Trace level="1" type="T">No mapping required </Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">No persisting of message after plsrv call, because of config </Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS    = CL_XMS_PLSRV_OUTBINDING</Trace>
<Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG     = </Trace>
<Trace level="3" type="T">FL_DUMMY   = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="2" type="T">O U T B O U N D - B I N D I N G </Trace>
<Trace level="2" type="T"> Cache Content is up to date </Trace>
<Trace level="2" type="T">determine OUTBOUND BINDING for: </Trace>
<Trace level="2" type="T">-IBOLTSERVER </Trace>
<Trace level="2" type="T">-SBO_DRP_SERVER </Trace>
<Trace level="2" type="T">http://ibolt.com/PGSAP/TransactionalData.MI_Digicall_BranchPayment </Trace>
<Trace level="2" type="T">Channel found: - SBO_DRP_SERVER - FTP_Digicall_Franchisee_Payment </Trace>
<Trace level="2" type="T">no header mapping defined </Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">No persisting of message after plsrv call, because of config </Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"></Trace>
<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS    = </Trace>
<Trace level="3" type="T">P_IFNAME   = </Trace>
<Trace level="3" type="T">P_METHOD   = </Trace>
<Trace level="3" type="T">FL_LOG     = </Trace>
<Trace level="3" type="T">FL_DUMMY   = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Unknown channel type: File</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = AENGINE</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS    = CL_XMS_PLSRV_IE_ADAPTER</Trace>
<Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG     = </Trace>
<Trace level="3" type="T">FL_DUMMY   = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace>
<Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="3" type="T">Channel for adapter engine: File</Trace>
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="2" type="T">return fresh values from cache </Trace>
<Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET): </Trace>
<Trace level="3" type="T">URL = http://pgsap45:50100/MessagingSystem/receive/AFW/XI</Trace>
<Trace level="3" type="T">User = XIISUSER</Trace>
<Trace level="3" type="T">Cached = X</Trace>
<Trace level="3" type="T">Creating HTTP-client </Trace>
<Trace level="3" type="T">HTTP-client: creation finished</Trace>
<Trace level="3" type="T">Security: Basic authentication </Trace>
<Trace level="3" type="T">Serializing message object... </Trace>
<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
<Trace level="3" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
<Trace level="3" type="T">HTTP-client: response received</Trace>
<Trace level="3" type="T">HTTP-client: checking status code...</Trace>
<Trace level="3" type="T">HTTP-client: status code = 200 </Trace>
<Trace level="3" type="T">Deserializing message object... </Trace>
<Trace level="3" type="T">HTTP-client: closing...</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-08-28T13:57:53Z CAT End of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">No persisting of message after plsrv call, because of config </Trace>
</Trace>
<Trace level="3" type="T">Async processing: skip mapping of response </Trace>
</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Async processing completed OK. </Trace>
<Trace level="3" type="T">system-ID = XIQ</Trace>
<Trace level="3" type="T">client = 300</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2007-08-28T13:57:53Z CAT </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace>
<Trace level="3" type="T">Persisting message Status = 003</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
Thanks,
Miguel

Unable to Receive the File into Target Directory Using FTP

Hi All,
Here I Did Simple File-File Scenario With FTP.
Iam Able to Pick the File From the FTP Location And File has been Deleted From Source Location ( Set the Processing Mode as Delete ).
Unable to See the Pipeline Steps in Moni, But Able to Se the Success Message With the Inbound Payload only.
Also chked with the comm. channel of sender and receiver, where the sender shows the message process details but not the receiver comm. channel.
Regards
Giri

You Did the right thing in communication channel that u selected the IS.
Hi
Just check out if you sending the correct parameters and also check out the payload you sending and check out in SXMB_MONI for you message that after success wat is the payload and match with your input.
Rather, for input check, In IR, get the XML data from ur Message Mapping and then save it to your inbox that is input directory.
Also check out the permission of Output directory and also check the configuration of sender and reciver communication channel.
Regards
Aashish Sinha
PS : reward points if helpful

No service for system SAPNID, client 800 in Integration Directory

Hi All,
I am getting No service for system SAPNID, client 800 in Integration Directory in tRFC monitor (SM58).
My scenario is IDOC to File.
I did following step in R3.
1.     Created RFC destination pointing to XI systems (name:XID)
2.     Created IDOC port (name: SAPNID) and use above (XID) RFC in RFC destination.
3.     Create Partner Type LI (Partner No. 3000) and add message type ORDERS, set the receiver port (SAPNID) created above.
XI Side.
1.     Create Technical System (Name : XID)
2.     Business Systems (Name: R3XID)
3.     In Integration Repository.
     Created Data Type
     Import IDOC ORDERS.ORDERS04
     Created Message Interface
     Created Message Type
     In Mapping Object created Message Mapping and Interface Mapping.
4.     In Integration Directory
     Created the Scenario (name : FILE_FROM_IDOC)
     Assign Business Systems as R3XID
     Create communication channel(name: FILE_ORDERS_COM_CHNL)
     Create Receiver Determination
     Interface Determination
     Receiver Agreement.
IDOC is triggered correctly but in tRFC monitor I am getting following error
No service for system SAPNID, client 800 in Integration Directory
With regards
Sunil

Hi Udo/Renjith and Rakesh,
Thanks for quick reply and appreciate you help.
Now I can say that there is some problem with my Technical Systems or Business Systems, let me give you details regarding my Technical/Business systems.
During post-Installation i created Technical/Business System, following are the details regarding these systems.
<u><b>Technical Systems.Detail</b></u>
System Name: XID
System Home: crmides
Installation Number: INITIAL Change...
Release: 640
Description:
Administrative Contact:
TMS Domain:
TMS Transport Group Name:
Clients: 100 800 Add...
Message Server: XID crmides
Central Application Server: crmides_XID_00
Secondary Application Servers: Add...
Internet Transaction Servers: Add...
Installed Products: SAP EXCHANGE INFRASTRUCTURE, SAP EXCHANGEINFRASTRUCTURE 3.0 XID
SAP R/3, 4.5B XID on crmides
SAP R/3, 4.6C XID on crmides
Add...
Installed Software Components
Business Systems:
1. R3XID
2. SAPNID
Earlier I have only one Client (100) and One Busines Systems (R3XID)
My XI Systems is XID Host : crmides Client : 100 System Number : 00
My R3 Systems is NID Host : netbw Client : 800 Systems Number : 02
<u><b>Business Systems Detail</b></u>
Name: R3XID
Description:
Administrative Contact:
Business System Role: Integration ServerApplication System
Pipeline URL:http://crmides:8000/sap/xi/engine?type=entry
Integrated Business Systems: SAPNID
Group:   (No Group Assigned)Edit Groups...
Transport Targets:
Technical System: XID on crmides Change...
Client: <b>100 of XID</b>
Logical System Name: SAPNID
Installed Products: SAP R/3, 4.5B XID on crmides
SAP R/3, 4.6C XID on crmides
SAP EXCHANGE INFRASTRUCTURE, SAP EXCHANGEINFRASTRUCTURE 3.0 XID
Software Components: ABC, 1.0 of knack
R/3 CORE 4.5B
SAP ABA 4.6C
SAP ABA 640
SAP APPL 4.6C
SAP BASIC JAVA LIBS 6.30
SAP BASIS 4.6C
SAP BASIS 6.40
SAP GUI FOR WINDOWS 4.5B
SAP GUI FOR WINDOWS 4.6C
SAP GUI FOR WINDOWS 6.20
SAP HR 4.5B
SAP HR 4.6C
SAP ITS 4.6B
SAP ITS 4.6C
SAP J2EE ENGINE 6.30
SAP J2EE ENGINE CORE 6.30
SAP JAVA TECH SERVICES 6.30
SAP JCO 6.30
SAP SOFTW. DELIV. MANAGER 6.30
XI ADAPTER FRAMEWORK 3.0
XI CONNECTIVITY SE 3.0
XI TOOLS 3.0
During Post Installation I had one Technical Systems (XID) and one Business Systems (R3XID), after that I created one more Business Systems (SAPNID).
<u><b>SAPNID Business Systems Detail</b></u>
Name: SAPNID
Description:
Administrative Contact:
Business System Role: Application System
Related Integration Server: R3XID
Group: (No Group Assigned)
Transport Targets:
Technical System: XID on crmides Change...
Client: <b>800 of XID</b>
Logical System Name: SAPNID
Installed Products: SAP R/3, 4.5B XID on crmides
SAP R/3, 4.6C XID on crmides
SAP EXCHANGE INFRASTRUCTURE, SAP EXCHANGEINFRASTRUCTURE 3.0 XID
Software Components: ABC, 1.0 of knack
R/3 CORE 4.5B
SAP ABA 4.6C
SAP ABA 640
SAP APPL 4.6C
SAP BASIC JAVA LIBS 6.30
SAP BASIS 4.6C
SAP BASIS 6.40
SAP GUI FOR WINDOWS 4.5B
SAP GUI FOR WINDOWS 4.6C
SAP GUI FOR WINDOWS 6.20
SAP HR 4.5B
SAP HR 4.6C
SAP ITS 4.6B
SAP ITS 4.6C
SAP J2EE ENGINE 6.30
SAP J2EE ENGINE CORE 6.30
SAP JAVA TECH SERVICES 6.30
SAP JCO 6.30
SAP SOFTW. DELIV. MANAGER 6.30
XI ADAPTER FRAMEWORK 3.0
XI CONNECTIVITY SE 3.0
XI TOOLS 3.0
I do not know whether SAPNID is required or not, earlier I used R3XID as Business Systems at the time of configuration now I changed it to SAPNID. I am getting the same error in both the case.

PI Pipeline Doubt : Pipeline Steps in ABAP stack and JAVA stack

Hello
Can anyone please assist me with which stages steps of the PI Pipeline are executed on the Java or the ABAP stack.
Receiver Determination
Interface Determination
Message Split
Message Mapping
Technical routing
Call Adapter
Also can anyone please provide links relating to the PI architecture diagram describing it from ABAP and Java Stack Perspective and not from the Components perspective i.e. Integration Repository and Directory.
Thanks.
Kiran

Hi
Tha ABAP stack consists of the Integration Server which in turn contains your Integration Engine and Business Process Engine.
The J2EE stack contains the Adapter Engine and your IR and ID run on the J2EE engine.
Most of XI pipelines happens in the ABAP stack.
All messsages picked by the Adapter Framework running on the J2EE engine are passed to the Integration Engine, which does the routing. The mapping program again gets executed on the Java stack and the rest of the pipeline servies are executed again on the ABAP stack and so on.
Message, Java & XSLT (under Imported Archives) mappings are executed at Java stack;
ABAP & XSLT (in ABAP stack) mappings are executed at ABAP stack.
PI Architecture look threads
Architecture
/message/5802842#5802842 [original link is broken]

Transmitting message to entry pipeline failed !!

Hi all,
We have configured a <b>file adapter</b> to poll a specific directory. Now the adapter polls the file , deletes it after reading it , however it fails to deliver the message to entry pipeline.
We are getting an error msg that reads:
<b>Transmitting the message to endpoint http://itcxi1:53000/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 404..</b>
We have already gone through the link:
<b>Transmitting message to entry pipeline failed !!
Accordingly we have checked but we have <b>not used any business system</b>.
There are <b>two business service</b>(one sender and the other reciever).
We have checked sxmb_adm and httpport in the exchange profile but all of them are filled with the respective values:
com.sap.aii.connect.integrationserver.r3.httpport = <b>8030</b>.
com.sap.aii.connect.integrationserver.httpport = <b>53000</b>.
in sxmb_adm we have given url as http://10.119.4.33:8030/sap/xi/engine?type=entry
But still in the error msg the url reads as:
http://itcxi1:53000/sap/xi/engine?type=entry
<b>The entire audit log shown is</b>:
2006-05-24 12:59:10 Success
Channel SenderChannel: Send binary file "D:\usr\sap\trans\tmp\sender\xi_input.xml". Size 363 with QoS EO
2006-05-24 12:59:10 Success
Application attempting to send an XI message asynchronously using connection AFW.
2006-05-24 12:59:10 Success
Trying to put the message into the send queue.
2006-05-24 12:59:10 Success
Message successfully put into the queue.
2006-05-24 12:59:10 Success
The application sent the message asynchronously using connection AFW. Returning to application.
2006-05-24 12:59:11 Success
The message was successfully retrieved from the send queue.
2006-05-24 12:59:11 Success File "D:\usr\sap\trans\tmp\sender\xi_input.xml" deleted after processing
2006-05-24 12:59:11 Success
The message status set to DLNG.
2006-05-24 12:59:11 Error
Transmitting the message to endpoint http://itcxi1:53000/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 404..
2006-05-24 12:59:11 Success
The asynchronous message was successfully scheduled to be delivered at Wed May 24 13:04:11 GMT+05:30 2006.
2006-05-24 12:59:11 Success
The message status set to WAIT.
2006-05-24 13:04:11
Success Retrying to send message. Retry: 1
This same process is repeated 4 times.
Pls suggest what else do i need to check.
Regards
Neetu

Hi Michal,
Thanks for ur prompt response.
Actually in this scenario i am not using any business system.
As mentioned before i have two business services one of which acts as the sender service and the other one acts as the receiver service.
Each one of them have their corresponding communication channels.
So where do i change the url.
My sld has a business system for xi in which i changed the url, putting the port as 8XXX.
Next i imported this system to my scenario and tried sending a message again but got the same error.
What should i do next?
Regards
Neetu

File to Idoc Scenario -- No Pipeline steps in Moni

Hi,
I have created a File2Idoc scenario. I have done all the configurations & finally dropped the file in source directory. File got picked up and deleted from source directory, But I could see in Moni only for the Inbound message but not able to see the message mapping and Receiver determination pipeline steps in Moni.
Also viewed the communication channel for sender and it is working perfectly and it shows the logs with the details of File deleted.
Note: The XI server is newly installed and configured and this is the first scenario being executed in the server. So should there be any other installation configuration to be done, to process the file in IS.
Because as per our assumption, the file has not reached the IS and it still stays in the queue with only the Inbound message.
Regards,
Nithiyanandam

Hi Nithiyanandam,
as u described your problem i want to guide u through foll steps:
1. in xi monitor on pipeline window their is only one msg for inbound,
check out the color of the icon if it is green( i think it must be green) then go to
T-code SXMB_ADM which is under Admin node in xi server window
--- > Select manage queues then activate queues under action node.
2. Also clear cache by going to t-code SXI_CACHE under configration node
---> Go to XI Runtime Cache menu option and select "delta cache refresh" and " complete cache refresh"
3. if inbound msg icon is red then do accordingly. in this case of red icon there is possibility if bug also
thanks
mandeep virk
**reward if helpful and also update ur status

Get filename and directory name during runtime

Hi guys,
I am developing a file to file interface without content conversion, just a simple file transfer from one ftp server to another. I have to read the same filename (invent.txt) from multiple folders (mstransfer/M01/IN1, mstransfer/M02/IN1, mstransfer/M03/IN1....) that represent different stores and transfer it as it is with the same name to exactly the same directory name in the target ftp location.
My problem is found inside a dummy mapping that I have created in order to specify the target directory and the name of the file. I am doing the following:
A) A Java UDF to specify the filename
trace = container.getTrace();
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
String filename = conf.get(key);
trace.addWarning("filename = "+filename);
conf.put(key, filename);
return "";
//return filename;
B) A Java UDF to specify the directory name
//write your code here
trace = container.getTrace();
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","Directory");
String directory = conf.get(key);
trace.addWarning("directory before = "+directory);
directory = "/usr/sap/trans"+directory;
trace.addWarning("directory after = "+directory);
conf.put(key, directory);
return "";
//return "/usr/sap/trans"+directory;
In receiver file adapter I do not specify neither a filename nor a target directory.
When I am testing it, I always get a mapping runtime error.
Any ideas?
--Evaggelos

Guys,
First of all, I am doing an end to end testing, i.e. I let the FTP adapter pick the file up and another FTP adapter delivers the file to target folder. I am definitely not testing the mapping in mapping editor.
I get the error in Request message mapping (pipeline step, which I can see in SXMB_MONI transaction) which is a dummy mapping between two message types that I have created and are based on two data types with two fields each.
The UDF's that I have created go in-between the source and target fileds of the message types/data types.
The error that I see in the trace section of the XML message in SXMB_MONI is the following:
"<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_MM_G_SRS_FileTransfer_MNS_</Trace>
<Trace level="1" type="T">java.lang.NullPointerException at com.sap.aii.mappingtool.tf3.AMappingProgram.exceptionCaught$(AMappingProgram.java:59) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:182) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:149) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at"
I have included some trace.addWarning() lines in Java code to help me debug my code, but I cannot see them anywhere inside the trace to be getting executed.
I will try Bhavesh's idea and I will write the code in the Java Section of my message mapping ( either Intialization or Destrcution ) section.

Waitnig status in a pipeline step

Hi guys...
I've a scenario JDBC --> XI --> JDBC, I checked the objects in the Integration Repository and are activated, I configure twice the object in the Integration Directory and when the scenario is running, some message are stuck in the pipeline step "Message Branch According to Receiver List". I look for the trace in the message step and it show the following information:
<Trace level="1" type="T">start CHECK_INTERFACE</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface mi_oa_rclTec_DMS*</Trace>
<Trace level="1" type="T">select interface namespace urn:dms-grt:DMS_GRT_01</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--<b>no sender or receiver interface definition found</b></Trace>
But the problem is not persistent, sometimes its works, but sometimes dont, that is, get stuck in that step.
Any ideas???
Hector

Hi Hector -
Is this all you see? What's the message status - any error? This part of the trace is not indicative of what the problem is. For example, on a standard successful message that processes all the way through, I can see exactly what you posted - it's just part of the preliminary processing. You mentioned the message reached the pipeline step "pipeline step "Message Branch According to Receiver List". So it was able to perform Receiver and Interface Determination up to this point.
Maybe you can raise the trace level to 3 to see if you get any more info - SXMB_ADM then Integration Engine Configuration->Change Specific Configuration, then:
RUNTIME (Category), TRACE_LEVEL (Parameter), 3 (Current Value)
Regards,
Jin

Very urgent, please help. Pipeline classpath

I am working on a compony portal project. I have 4 jar'd pipeline components. No
matter what I did, the system could not find them. I always got error "Class must
be in classpath".
I define them in beaApps\portalApp\META-INF\application.xml like this:
<module>
<ejb>myPipeline.jar</ejb>
</module>
Since they are not enterprise java bean, I also reference them in the classpath
of pipeline.jar's manifest. The system has no problem seeing the input porcessor
classes, but right after that it should go to my pipeline component, but it did
not. I always got error "Class must be in classpath".

You should be able to do one of the following two things..
1) just delare you jar in the pipelie.jar manifest's classpath and make sure
the pipeline jar is registered in the application.xml file (not myPipelie.jar)
2) As long as you are running 8.1, just put the jar in the APP-INF/lib directory.
I assume the class it is complainng about is one of yours?
"Crystal" <[email protected]> wrote:
>
I am working on a compony portal project. I have 4 jar'd pipeline components.
No
matter what I did, the system could not find them. I always got error
"Class must
be in classpath".
I define them in beaApps\portalApp\META-INF\application.xml like this:
<module>
<ejb>myPipeline.jar</ejb>
</module>
Since they are not enterprise java bean, I also reference them in the
classpath
of pipeline.jar's manifest. The system has no problem seeing the input
porcessor
classes, but right after that it should go to my pipeline component,
but it did
not. I always got error "Class must be in classpath".

PipeLine Directory in XI

Similar Messages

Maybe you are looking for