XI3.1 Sizing Documentation

Hi Ingo,
I have followed the links to the XI 3.1 sizing recommendations and it opens the XIR2 Sizing Documentation.
Is there an actual 3.1 document that lists all of the new server types?
George

Hi Pascal, as Ingo has stated, the sizing for XIR2 is still valid for XI3.1. We have just upgraded from XIR2 to XI3.1 and we did not change any hardware configuration. You can find the sizing guide for XIR2 at:
http://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/e01588cd-c73e-2b10-018c-fe083bc6e05e
Please note that the sizing guide is merely a general guideline only. In reality, sizing really varies from company to company. There is no cookie-cutter formula. Very often, it is a trial-n-error process. The good news is that the XI platform is highly-scalable. You can always scale-out when needed.
Hope this helps.
If you are using the BusinessObjects tool, you should join [ASUG|www.asug.com]

Similar Messages

Sizing documentation for Oracle OSM production

Hi,
Does anyone have documentation explaining the software & hardware requirements to install Oracle OSM 7.0.1 in a Production Enviroment in Clustering?
Thanks

Hi,
We have an internal (to Oracle) tool, which we use for H/W sizing Please send me an private message, with your requirements (Number of orders processed per hour, work hours/day, type of order, size of typical order, lines/order etc) and customer name. We will be happy to assist you.
Thanks,
Deepankar (Deep) Dey
OSM Product Management

Virus Scan Server Sizing

Dear colleagues
Where can I Find sizing documentation of virus scan servers?
How many servers I should install? Does it depend on number of uploads and number of connected ABA/JAVA instances?
Regards
Vladimir

Hi Vladimir,
This url might be helpful to you http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/aa783f181b0866e10000000a114084/frameset.htm
-Pinkle

New Performance Section Added to the UWL/UWL Sizing Guide

Hi Everyone,
Happy New Year! I just wanted to inform you of some new documentation. On the main UWL WIKI with the help of our development support colleagues, have added a Performance section in this WIKI. It's worth taking a look.
[Universal Worklist Wiki|http://wiki.sdn.sap.com/wiki/x/ehU]
Also, our colleagues in development support put together a handy sizing guide for UWL. You can find the document under this path: [Sizing documentation|www.service.sap.com/sizing] --> sizing guidelines --> Solutions and Platforms New Structure --> SAP NetWeaver --> scroll down to find Universal Worklist. Here you will find the new sizing guideline for working with the Universal Worklist.
Beth Maben
EP - Senior Support Consultant II
SAP Active Global Support
Global Support Centre Ireland
**SDN Forum Moderator:
SAP Enterprise Portal: Application Integration
**SDN Universal Worklist Wiki:
http://wiki.sdn.sap.com/wiki/x/ehU

Hi r rajyalakshmi
it may be wrong forum for this question. but you can follow the below link for some idea.
http://wiki.sdn.sap.com/wiki/display/BPX/UWL+FAQ
hope it helps.
Deep

WAS inlcusion in FrontEnd BI 4.0

Hi,
I would like to ask a question about the BI 4.0 sizing documentation - WAS inclusion in the total FrontEnd SAPS for BI applications.
From the BI 4.0 sizing PowerPoint presentation u2013 it says that the WAS is included in the FrontEnd unless stated otherwise in the guides.
Than inside the Companion guide for all BI applications (OLAP analysis, WebI, Cystal, etc.) it says "The Web/App Server SAPS rating is the same as the SAP BusinessObjects machine SAPS rating". Does it mean that the WAS is not included in the sizing? Meaning that in case the sizing documentation recommends FrontEnd tier to be M size = 8440 SAPS, based on the statement above do I have to add another 8440 SAPS only for the WAS? - seems to be quite high.
It is a bit confusing but crucial for proper sizing.
Thanks!
Erik.

Hi all,
SAP has recommended to use the quicksizer tool for BI 4.0 to verify/asses the requirements on the application tier. It is now available for BI 4.0 as well. Closing the thread.
Erik.

CCMS implementation performance impact

Dears
I'm looking for information on the impact on performance of a CCMS implementation.
Impact on Solution Manager, impact on managed SAP systems. I opened a customer message but SAP comes back with there is no sizing documentation for ccms.
The purpose is to add a lot of managed SAP system into SAP Solution Manager and enable CCMS + IT Performance Reporting. I would like to know how much impact the RFC access causes.
If anyone has done a study on this or has information on this please share.
Kind regards
Tom

@Mauricio Yes I do understand the principal behind it. From a logical point of view it should improve performance but then again tests should have been run to prove the point.
For example: I'm involved in the pilot program for SAPJVM 4.1 and while SAP sais the performance should be the same or better but we all know SAP doesn't have every combination of OSDBSAP system running. It's the same principal, from a logical point of view it should be the same or better but one should do some performance tests to verify if it's the case.
@Augusto No problem on the misunderstanding, it shows my question wasn't that great and I should have provided more information
The point is that we have a lot of managed SAP systems to add and apparently SAP doesn't have that many customers that have a big number of managed SAP systems in the Solution Manager. The performance impact of CCMS implementation is neglictible if you only have some managed SAP systems. What is a 3% CPU rise in that case, shouldn't be a problem but now imagine you put in thirty times as much SAP systems then it can be become a problem if you don't foresee additional server resources.
A lot of those scenario's seem to have been tested with only a few managed SAP systems, doing a full landscape fetch through transaction SMSY takes a long time for example. I do know in Solution Manager 7.1 there is another component in between the SLD and SMSY which can synchronize content faster to avoid long runtime.
Another example was the landscape verification tool 1.0 which I reviewed in a blog. It didn't have a possibility to refresh single systems (I haven't checked latest version) but that is a problem if you have many managed SAP systems and you want to just check one. In the video demo's it flashes and it's very fast because there are only five managed SAP systems.
I'm looking forward to Solution Manager 7.1 but these kind of performance impacts should be known really. Doing a small implementation is no problem but customers are really interested in application lifecycle management and so on and are starting to generate demand for a lot of different scenario's. Sizing it is not that hard in small environment but once the environments become larger and a lot of managed SAP systems are involved the issue I see with CCMS for example rises and it becomes very hard to size properly. Perhaps it could be integrated into the quick sizer (number of managed SAP systems and enablement/use of certain scenarios).
I do know for some scenarios there is sizing documentation available, diagnostics being one of those.

Shrink MGMT_TABLESPACE - EMREP

Hi,
We are using EM Cloud Control 12c, and the EMREP database is growing up. So... do you know an oficial procedure to shrink the MGMT_TABLESPACE?
Thanks.

Please refer to the Sizing documentation - http://docs.oracle.com/cd/E24628_01/install.121/e24089/sizing.htm#BCGCFHHE for details on recommended space requirements for EM. Based on your # of targets and agents, yours would be considered a small environment. The size also depends on what you're using EM for. Are you using patching, provisioning, lots of jobs, templates, customizations, additional metrics, policies, reports, etc. This can all add to the size of the tablespace. My lab box has 2 agents, and uses 5gb. 10gb for 33 agents does not seem large at all. It also depends on how long your system has been running. It will continue to grow for a year, at that point all the purge jobs will kick in and it will stabilize.

Documentation about server sizing

Hi,
I know it's not an Abap question, but, if you have some idea where to find a documentation about how to make a sizing of a new installation of SAP ?
Rgd
Frédéric

Yes this a good link: https://websmp202.sap-ag.de/quicksizing
From server sizing prospective, as you can download complete PDF about it . I used this in last project. Its worth reading and using.
Thanks
Message was edited by: Saquib Khan

Sizing guidline documentation

Hi
we are planning for the upgrade our current Peoplesoft application to PT 8.52 , CRM 9.1 (old version PT 8.48 , CRM 8.9) and want to build the new hardware, Just want to make sure we have good hardware resources in place before starting the upgrade process. any documentation or sizing guideline to support Co current users up to 1000 ? - Small configuration for example
CPU & Memory requirement for application server/web server /data base server ? Current system we have Operating system window 2008 R2 and we use SQL 2008. I open the case with oracle tech. support , they refer me to Hardware /software requirement documentation which was not big help.
Thank you

You could look at this info provided by Nicolas in a recent Post. Guidelines on Hardware requirements/sizing for PeopleSoft 9.1
I would read the performance tuning guide he mentions.
Some food for thought. In these days of commodity hardware, the cost of equipment usually pales in comparison to the cost of rest of the project. I would get the best you can get. Scrutinizing hardware with a fine tooth comb only to pay consultants to sit around and suffer on slow hardware for months only costs you further. Better hardware is cheaper than consultant fees a lot of the time (granted every situation is different). Consider options for both scaling horizontally and vertically. It's not just the hardware but also how you implement that hardware.

Oracle EBS 12.1.3 and SOA 10g hardware sizing

Hi All,
To give you the background, we have integration requirements where in one of the interface about 20000 sales orders come in the system everyday and they have about 3-5 lines per sales order. Most of these orders come between 3-6 PM. We have 50 other interfaces along with this but this is a major one. Client is concerned about performance and so we have to give right design and right hardware sizing so that the system is able to handle all the load without causing performance issues. We are planing to use Oracle EBS 12.1.3 and SOA Suite 10.1.3.5 (10g)
Any processes, documentation on how to go about hardware sizing, tools will be helpful
Thanks,
Rahul

Any Updates??

Can I get more sizing information in scripted JPEG exports?

Exporting to JPEG from script seems to give less size/resolution information than exporting from AI itself.
This manifests itself when opening in Microsoft Word, when the 'from AI' JPEG appears correctly sized, whereas the 'from script' JPEG just fills whatever page size you've specified.
Does the 'from AI' JPEG have more metadata compared to the 'from script' JPEG? This is what it looks like when I look at the files using Exiftool.
Does 'from AI' have EXIF data, maybe as well as JFIF? Does 'from script' only have JFIF? And Word is only looking at the EXIF data?
Can I get EXIF into the exports?
Thanks

I recommend looking at the Javascript Documentation.
under ExportOptionsJPEG.
your quality issues may just be the script is using the default quality setting
qualitySetting
number (long)
The quality of the exported image. Range: 0 to 100. Default: 30
not so sure about the scaling issue
but I believe EXIF comes from your camera where as JFIF is the standard from most software.
I could be wrong in this.

ESS Who's Who photo re-sizing?

Hello all -
we're implementing ESS using ECC6, EP7. The employee photos are appearing against the employee records in Who's Who, but the sizing and aspect of the standard (170x200) is not the same as the corporate standard (150x200), so the photos are distorted.
Does anyone have any experience with changing the sizing of the photo displayed in Who's Who?
thanks in advance,
Sonya

Hi Sonya
Is there any documentation which mentions that the standard size is 170*200?
I found a link on SAP Help when mentions that the size should be 130*100
http://help.sap.com/saphelp_nw70/helpdata/en/cf/95f6409daddb12e10000000a155106/frameset.htm
Please help sort this confusion out.
Thanks

XI3 Jdbc Adapter

Hello,
we try to get access to a database like hsqlDB.
If we want to use the Jdbc Adapter we get the folling error message:
(com.sap.aii.af.ra.ms.api.DeliveryException: java.lang.Exception:
database connection )
We configurated the channel prober and deployed at the SDM the hsql driver jar exactly like it is recommended at the Xi3 documentation.
Our database works fine so it must be a problem with the jdbc deployment.
Some help would be nice!
Here is the full Monitoring error::
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-
wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000"
SOAP:mustUnderstand="1" wsu:Id="wsuid-main-
92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>SystemError</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>DAF75920-28E7-11D9-A5A9-000EA6B4552F</SAP:MessageId>
<SAP:RefToMessageId>8F008041-83D0-D52F-E100-
0000C0A88572</SAP:RefToMessageId>
<SAP:TimeSent>2004-10-28T13:47:06Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>COM_PLBPRODUCTDB_T</SAP:Service>
<SAP:Interface namespace="http://plecto.com/com/xibank/plb-
products_db">insert_inb</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
<SAP:Service>COM_PLBPRODUCTDB_T</SAP:Service>
<SAP:Interface namespace="http://plecto.com/com/xibank/plb-
products_db">http_put</SAP:Interface>
</SAP:Receiver>
<SAP:Interface namespace="http://plecto.com/com/xibank/plb-
products_db">insert_inb</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
SystemErrorAckRequested="true" SOAP:mustUnderstand="1">
<SAP:QualityOfService>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="PARSING">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException:
java.lang.Exception: database connection missing</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2004-10-28T13:46:58Z" wasRead="false">
<SAP:Engine type="IS">is.00.sapxi3</SAP:Engine>
<SAP:Adapter
namespace="http://sap.com/xi/XI/System">HTTP</SAP:Adapter>
<SAP:MessageId>8F008041-83D0-D52F-E100-0000C0A88572</SAP:MessageId>
<SAP:Info>host:192.168.133.114:8000::remote-
addr:192.168.133.72</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2004-10-28T13:46:58Z" wasRead="false">
<SAP:Engine type="IS">is.00.sapxi3</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>8F008041-83D0-D52F-E100-0000C0A88572</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
</SAP:HopList>
- <SAP:Ack xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
SOAP:mustUnderstand="1">
<SAP:Status>Error</SAP:Status>
<SAP:Category>permanent</SAP:Category>
</SAP:Ack>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20041028</SAP:Date>
<SAP:Time>154658</SAP:Time>
<SAP:Host>sapxi3</SAP:Host>
<SAP:SystemId>XI3</SAP:SystemId>
<SAP:SystemNr>00</SAP:SystemNr>
<SAP:OS>Linux</SAP:OS>
<SAP:DB>ADABAS D</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>000</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>WSC</SAP:User>
<SAP:TraceLevel>3</SAP:TraceLevel>
<SAP:Logging>1</SAP:Logging>
<SAP:LogSeqNbr>000</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineEle
mentId>
<SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>
<SAP:QIdInternal />
<SAP:CommitActor>A</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="100">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID" />
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>138</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>0</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>138</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>336</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>PLAINHTTP</SAP:AdapterInbound>
<SAP:AdapterOutbound>AENGINE</SAP:AdapterOutbound>
<SAP:RandomNumber>54</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin"
host="sapxi3">20041028134658.554363</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end"
host="sapxi3">20041028134658.574832</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin"
host="sapxi3">20041028134658.658371</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end"
host="sapxi3">20041028134658.675398</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin"
host="sapxi3">20041028134658.695891</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end"
host="sapxi3">20041028134658.713369</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin"
host="sapxi3">20041028134658.751765</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end"
host="sapxi3">20041028134658.7664</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="begin"
host="sapxi3">20041028134658.788744</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="end"
host="sapxi3">20041028134704.21443</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="begin"
host="sapxi3">20041028134704.253736</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="end"
host="sapxi3">20041028134704.278098</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
<SAP:Timestamp type="begin"
host="sapxi3">20041028134704.303583</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
<SAP:Timestamp type="end"
host="sapxi3">20041028134706.126445</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SAP:OutboundBindingEntry version="30">
<SAP:OutboundBindingObjectId>A486A55969723803BA4C52A896A8BF83</SAP:Outbo
undBindingObjectId>
<SAP:FromPartyName />
<SAP:FromServiceName>COM_PLBPRODUCTDB_T</SAP:FromServiceName>
<SAP:ToPartyName />
<SAP:ToServiceName>COM_PLBPRODUCTDB_T</SAP:ToServiceName>
<SAP:ToInterfaceName>insert_inb</SAP:ToInterfaceName>
<SAP:ToInterfaceNamespace>http://plecto.com/com/xibank/plb-
products_db</SAP:ToInterfaceNamespace>
- <SAP:OutboundBindingAttributes>
<SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:OutboundBindingAttributes>
- <SAP:HeaderMapping>
<SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:HeaderMapping>
- <SAP:ChannelEntry version="30">
<SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ServiceName
xmlns:SAP="http://sap.com/xi/XI/Message/30">COM_PLBPRODUCTDB_T</SAP:Serv
iceName>
<SAP:ChannelName
xmlns:SAP="http://sap.com/xi/XI/Message/30">jdbc2</SAP:ChannelName>
<SAP:AdapterName
xmlns:SAP="http://sap.com/xi/XI/Message/30">JDBC</SAP:AdapterName>
<SAP:AdapterNamespace
xmlns:SAP="http://sap.com/xi/XI/Message/30">http://sap.com/xi/XI/System<
/SAP:AdapterNamespace>
<SAP:AdapterSWCV
xmlns:SAP="http://sap.com/xi/XI/Message/30">3B787A8035C111D6BBE0EFE50A11
45A5</SAP:AdapterSWCV>
<SAP:AdapterEngineType
xmlns:SAP="http://sap.com/xi/XI/Message/30">AE</SAP:AdapterEngineType>
<SAP:AdapterEngineName
xmlns:SAP="http://sap.com/xi/XI/Message/30">af.xi3.sapxi3</SAP:AdapterEn
gineName>
<SAP:MessageProtocol
xmlns:SAP="http://sap.com/xi/XI/Message/30">XML_SQL</SAP:MessageProtocol
>
<SAP:MessageProtocolVersion
xmlns:SAP="http://sap.com/xi/XI/Message/30">3.0.0527</SAP:MessageProtoco
lVersion>
<SAP:TransportProtocol
xmlns:SAP="http://sap.com/xi/XI/Message/30">JDBC</SAP:TransportProtocol>
<SAP:TransportProtocolVersion
xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ChannelDirection
xmlns:SAP="http://sap.com/xi/XI/Message/30">O</SAP:ChannelDirection>
<SAP:FromPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
- <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:ChannelAttributes>
</SAP:ChannelEntry>
</SAP:OutboundBindingEntry>
</SAP:OutboundBinding>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <Trace level="1" type="B" name="CL_HTTP_PLAIN_INBOUND">
<Trace level="1" type="T">server-protocol HTTP/1.1</Trace>
<Trace level="1" type="T">user-agent Java/1.4.2_04</Trace>
<Trace level="1" type="T">host 192.168.133.114:8000</Trace>
<Trace level="1" type="T">content-type application/x-www-form-
urlencoded</Trace>
<Trace level="1" type="T">content-length 138</Trace>
<Trace level="1" type="T">remote-addr 192.168.133.72</Trace>
</Trace>
<Trace level="1" type="T">COMMIT is expected by application !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<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 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 = XI3</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = WSC</Trace>
<Trace level="1" type="Timestamp">2004-10-28T13:46:58Z CET</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 level="1" type="T">Message-GUID =
8F00804183D0D52FE1000000C0A88572</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = BE</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 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 level="3" type="T" />
<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 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 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 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 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 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 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 level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-
WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="2" type="T">Persisting original message</Trace>
<Trace level="3" type="T">Message-Version = 000</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="Timestamp">2004-10-28T13:46:58Z CET Begin of
pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2004-10-28T13:46:58Z CET 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 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>
<Tracelevel="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 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">Check conditions for rule line no.
1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: -
COM_PLBPRODUCTDB_T</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2004-10-28T13:46:58Z CET 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">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2004-10-28T13:46:58Z CET 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 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 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 ER 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)
COM_PLBPRODUCTDB_T insert_inb</Trace>
<Trace level="2" type="T">...valid InbIf without Condition:
insert_inb</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2004-10-28T13:46:58Z CET 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">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT">
<Trace level="1" type="Timestamp">2004-10-28T13:46:58Z CET 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 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 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 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>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2004-10-28T13:46:58Z CET End of
pipeline service processing PLSRVID=
PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-
WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 003</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
<Trace level="1" type="Timestamp">2004-10-28T13:46:58Z CET 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 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 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="1" type="T">Interface Mapping
http://plecto.com/com/xibank/plb-products_db http_to_productdb</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping
F90D4E058EFD371E806F0C9E0307E1CE</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping
6E2DC920107611D98FEAE42AC0A88572</Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA
com/sap/xi/tf/_http_to_jdbc_</Trace>
<Trace level="2" type="T">Mode 0</Trace>
<Trace level="3" type="T">Creating Java mapping
com/sap/xi/tf/_http_to_jdbc_.</Trace>
<Trace level="3" type="T">Load 6e2dc920-1076-11d9-8fea-e42ac0a88572,
http://plecto.com/com/xibank/plb-products_db, -1,
com/sap/xi/tf/_http_to_jdbc_.class.</Trace>
<Trace level="3" type="T">Search com/sap/xi/tf/_http_to_jdbc_.class
(http://plecto.com/com/xibank/plb-products_db, -1) in swcv 6e2dc920-
1076-11d9-8fea-e42ac0a88572.</Trace>
<Trace level="3" type="T">Loaded class
com.sap.xi.tf._http_to_jdbc_</Trace>
<Trace level="2" type="T">Call method execute of the application Java
mapping com.sap.xi.tf._http_to_jdbc_</Trace>
<Trace level="1" type="T">*** START APPLICATION TRACE ***</Trace>
<Trace level="3" type="T">Document start</Trace>
<Trace level="3" type="T">Start tag [ns9:sql_insert]</Trace>
<Trace level="3" type="T">Add raw attribute [
xmlns:ns9="http://plecto.com/com/xibank/plb-products_db"]</Trace>
<Trace level="3" type="T">Start tag [Statement1]</Trace>
<Trace level="3" type="T">Start tag [PRODUCTTABLE]</Trace>
<Trace level="3" type="T">Add attribute: [action]=[update]</Trace>
<Trace level="3" type="T">Start tag [table]</Trace>
<Trace level="3" type="T">Put value [productdb:PRODUCTTABLE]</Trace>
<Trace level="3"type="T">Close tag [table]</Trace>
<Trace level="3" type="T">Start tag [access]</Trace>
<Trace level="3" type="T">Start tag [productCategoryId]</Trace>
<Trace level="3" type="T">Put value [4444]</Trace>
<Trace level="3" type="T">Close tag [productCategoryId]</Trace>
<Trace level="3" type="T">Close tag [access]</Trace>
<Trace level="3" type="T">Start tag [key]</Trace>
<Trace level="3" type="T">Start tag [productid]</Trace>
<Trace level="3" type="T">Put value [000001]</Trace>
<Trace level="3" type="T">Close tag [productid]</Trace>
<Trace level="3" type="T">Close tag [key]</Trace>
<Trace level="3" type="T">Close tag [PRODUCTTABLE]</Trace>
<Trace level="3" type="T">Close tag [Statement1]</Trace>
<Trace level="3" type="T">Close tag [ns9:sql_insert]</Trace>
<Trace level="3" type="T">Document end</Trace>
<Trace level="1" type="T">*** END APPLICATION TRACE ***</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_http_to_jdbc_
completed. (executeStep() of com.sap.xi.tf._http_to_jdbc_</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2004-10-28T13:47:04Z CET 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">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 004</Trace>
<Trace level="3" type="T">Message version 004</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
<Trace level="1" type="Timestamp">2004-10-28T13:47:04Z CET 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 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 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="1" type="T">processing the outbound binding</Trace>
<Trace level="1" type="T">search outbound bindings</Trace>
<Trace level="2" type="T">search outbound binding for:</Trace>
<Trace level="2" type="T">... sender party =</Trace>
<Trace level="2" type="T">... sender service =
COM_PLBPRODUCTDB_T</Trace>
<Trace level="2" type="T">... receiver party =</Trace>
<Trace level="2" type="T">... receiver service =
COM_PLBPRODUCTDB_T</Trace>
<Trace level="2" type="T">... receiver interface namespace =
http://plecto.com/com/xibank/plb-products_db</Trace>
<Trace level="2" type="T">... receiver interface name =
insert_inb</Trace>
<Trace level="2" type="T">outbound binding found</Trace>
<Trace level="2" type="T">outbound channel is:</Trace>
<Trace level="2" type="T">... party =</Trace>
<Trace level="2" type="T">... service = COM_PLBPRODUCTDB_T</Trace>
<Trace level="2" type="T">... name = jdbc2</Trace>
<Trace level="2" type="T">no header mapping defined</Trace>
<Trace level="1" type="T">outbound bindings found</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2004-10-28T13:47:04Z CET End of
pipelineservice 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">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 005</Trace>
<Trace level="3" type="T">Message version 005</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
<Trace level="1" type="Timestamp">2004-10-28T13:47:04Z CET Start of
pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<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 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 level="3" type="T">Unknown channel type: JDBC</Trace>
<Trace level="3" type="T" />
<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 level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="3" type="T">Channel for adapter engine: JDBC</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="2" type="T">Get logon data for adapter engine
(SAI_AE_DETAILS_GET): af.xi3.sapxi3</Trace>
<Trace level="3" type="T">URL =
http://sapxi3:50000/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">2004-10-28T13:47:06Z CET 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">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 006</Trace>
<Trace level="3" type="T">Message version 006</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-
WRITE_MESSAGE_LOG_TO_PERSIST" />
- 
<Trace level="2" type="T">Persisting original message</Trace>
<Trace level="3" type="T">Message-Version = 000</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
<SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-
wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-
5CABE13F5C59AB7FE10000000A1551F7" />
</SOAP:Body>
</SOAP:Envelope>

Hi werner,
You will have to check the jar file deployment and see if its deployed properly ...By the way which XI document did u refer too..
-admin

Oracle 10g server sizing information

We are planning to implement WEBMTHODS and METAMATRIX tool. These apps require Oracle database. We are planning 3 HP rp4410 servers running HP-UX 11i. One foe WEBMETHODS APP, ONE FOR METAMATRIX. BOTH APPS are using one ORACLE DB server.
I am looking some type of ORACLE 10g server sizing information to support ny hardware configuration. Can someone help me where to find this information?
Thanks.

Hi
What is AFAIK? As Far As I Know
Can you send the contact info?Unless you're not living in the same country (please see my profile), I don't think it would make any sense. I do know that hp.at offers sizing information.
If you are refering to Just HP support I did contact
them. They asked me to contact Oracle. I am looking
for some guideline documentation.So thing are a bit different in your country ...
C.

Sun hardware sizing guidelines

I am looking for server sizing guidelines for running Oracle apps 11i on Sun hardware. Is there any documentation available for this?
Thanks

Hi,
I believe this information is not published to end-users. However, your Sun or Oracle representative can contact Sun-Oracle Applications Technology Center where this information can be obtained.
MilosM

XI3.1 Sizing Documentation

Similar Messages

Maybe you are looking for