Monitoring status of OID Integration Server

Does anyone know anything about the best practices of monitoring the status of OID integration server. I'm writing a small plugin for Nagios and I was hoping to be able to pull a single attribute out of LDAP that tells me the status of Integration server. We have it running against iPlanet, and we need to make sure it's always in sync (and when it's not, notification is sent.)
Is this what the attribute orclodipinstancestatus does? Anyone have any info on the possible values of this (I presume 1 means everything is OK, although this may be the wrong attribute.)
I could just look at the odi/log/AGENTNAME.trc file, but if OID Manager can see the status (sync success or failure) I'm pretty sure it's some value in ldap... somewhere...

I'll answer my own question... I believe this should do the trick.
Using ldapsearch:
ldapsearch -h localhost -D "<SOME ADMIN USER>" -w <PASSWORD> -b "orclodipagentname=<AGENT NAME>, cn=subscriber profile,cn=changelog subscriber,cn=oracle internet directory" -s sub "objectclass=*"
A nice text attribute:
orclodipsynchronizationstatus=Synchronization Successful
reveals the status.

Similar Messages

"To Be Delivered" status in XI integration server

Hey Guys!
I have a question, right now we are trying to load Items into SRM; however, the records are being given the To Be Delivered status in the XI Integration Server. The records do not reach SRM. We have tried refreshing the XI Cache, as well as restarting the J2EE engine, all to no avail. Would anyone of you guys know how to address this issue? Thanks in advance!!
Best Regards,
Glenn

Hi,
Status: TO_BE_DELIVERED
Which means that the message was successfully delivered from Integration Server point of view and it states that the messages is initially handed over to the Messaging System.
TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue.
Solution:
This is done via the Messaging System receive servlet:
http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>
/<PROTOCOL>
Only if this was executed successfully the Messaging System returns HTTP 200 to the Integration Server and the Status TO_BE_DELIVERED moves to DELIVERING
1. Try logging into Sap GUI with two users: XIAPPLUSER & XIAFUSER
to see if they are blocked
2. We can check the messages:
AdapterFramework
com.sap.aii.adapterframework.serviceuser.language
com.sap.aii.adapterframework.serviceuser.name = XIAFUSER
com.sap.aii.adapterframework.serviceuser.pwd
ApplicationSystem
com.sap.aii.applicationsystem.serviceuser.language
com.sap.aii.applicationsystem.serviceuser.name = XIAPPLUSER
com.sap.aii.applicationsystem.serviceuser.pwd
in the exchange profile to make sure the right passwords
Regards
Agasthuri Doss

Monitoring PI Integration Server in Solution Manager

I am trying to set up monitoring the PI Integration Server in Solution Manager. The issue I am having is assigning the auto-reaction methond in solution manager. I am unable to assign as it is not modifiable in Solution Manager. I am able to change in PI system, but do not want to do it there. Has anyone done this and can you guide me to steps/documentation ?

Hi Alexey,
everything you need to know is in the "SAP Solution Manager operations"
document under
http://service.sap.com/solutionmanager
-> Media library
-> Documentation
if you have problems with the communication between the SLD and the SolMan
check document SAP Solution Manager Landscape Setup Guide
under http://service.sap.com/diagnostics
-> Media Library
and note 1148028 - Setup SLD in the scope of Solution Manager 7.0
If you are curious about the SLD architecture in general you can also have a look at
http://service.sap.com/sld
regards, Javier

Connection Integration Server failed. Status: HTTP/1.0 401 Unauthorized

Hello everybody,
I know, that this topic is discuss several times, but I couldn't find a satisfied solution. Sorry for the questions again.
Question:
Scenario: We have to realize a proxy connection between BW 3.5 and SAP XI 3.0. SLDCHECK works fine. But we have trouble with the http - Connection. We create a destionation via TA SM59:
. Target Host : Hostname SAP XI Integration Server
- Service No: <Port>
- Path Prefix: /sap/xi/engine?type=entry
- User: XIAPPLUSER
(this destionation works fine in another Sender systems)
If we try to test the connection. We get an Logon Prompt for the SAP XI Web Application Server back. Funny is, if we put the same User / Password from SM59 in, we get no error message back. But we couldn't put any logon / user information in the proxy area. What can we do ?
I did/checked follow:
- SAP XI: The User XIAPPLUSER, has the right password and authorizations,
- SAP BW: The Destionation is created and the System - Role (sxmb_adm) ist maintained.
- SAP BW: we compare the configuration with other Sender - Systems
- SAP BW: we create the Destionation with RFC - Typ H
Remark:
I created the same Destionation in other Sender-Systems: Works fine, we didn't get any logon promp, if we test the http Destination via SM59.
Thanks for your help
Regards
Stephan

Hello Sandro,
I execute the report, but the solution was in both systems the same:
Result:
In Exchange Profile: http:<hostname:Port>/rep
In Table SPROXSET : <blank>
Status: OK: Address maintained
I also tried follow reports:
SPROX_CHECK_IFR_CONNECTION
Result: Integration Builder server functioning correctly. Data unterstood
SPROX_CHECK_HTTP_COMMUNICATION
Result: HTTP communication functioning
SPROX_CHECK_IFR_RESPONSE
Result: I get a list of xml - entries back
Remark:
I thought the cache information was obsolete. I start a full cache refresh on SAP XI site, without success.
Remark 2:
I checked the system area, and I found out, that the Sender System with the problem is a non UNICODE and our SAP XI is a Unicode. Is this a reason, we have a http connection problem ? And when yes, what can we do.....
Thanks

Adapter Engine / Integration Server Problem

Hi,
I'm new to SAP and I have some questions regarding my new PI 7.0 SP10 setup.
Problem:
In Integration Directory, when I tried to define a communication channel, after specifying the "Adapter Type" (File in my case), I had to specify the "Adapter Engine" from a drop-down. But the dropdown list is empty!
What I've done & Observations:
1. I've recently imported the file "XI7_0_SAP_BASIS_7.00_06_00.tpz" (From the installation DVD). After importing, I've refreshed the SLD cache.
2. SLDCHECK reveals that the connection to SLD is successful.
3. RWB component monitoring shows:
    Integration Server - No light (Node cannot be expanded)
    Integration Engines - No light (Node cannot be expanded)
    Non-Central Adapter Engines -
        Adapter Engine ootspdbs02 (Red Light)
          - Self Test Failed - Details: Client 010 is not available in this system.
          - Cache Connectivity Test:
            Attempt to fetch cache data from Integration Directory failed; cache could not be updated
            [Fetch Data]: Unable to find an associated SLD element (source element: SAP_XIIntegrationServer, [CreationClassName, SAP_XIIntegrationServer, string, Name, is.01.ootspdbs02, string], target element type: SAP_BusinessSystem)
    J2SE Adapter - No light (Node cannot be expanded)
    Tools
        - System Landscape Directory ootspdbs02 (Green Light)
        - Integration Directory ootspdbs02 (Green Light)
        - Integration Repository ootspdbs02 (Green Light)
        - Runtime Workbench ootspdbs02 (Green Light)
4. In my SLD - I've defined a business system PI_BS_01
    Role: Integration Server
    Pipeline URL: http://OOTSPDBS02:8001/sap/xi/engine?type=entry
    Group - No Group Assigned.
    Client: 001 of PI1
    Technical System: PI1 on ootspdbs02 - Release 700
Given the above observations, can anyone please point out to me where I went wrong?
Any advise is greatly appreciated.
Thank you.
Best Regards,
Ron Lai

Hi Archana,
The configuration in SLD DataSupplier is:
Latest Send Activity
     2007/01/04 09:18:09:564
Used HTTP Parameters [http host:port] [user] [protocol]
     [ootspdbs02:50100] [SLDDSUSER] [http]
Sending Node [nodeID] [hostname]
     [11621750] [ootspdbs02]
Send Result
     Success
Next Automatic Send Timestamp
     2007/01/04 21:18:08:189
Send Type
     Automatic (Time Scheduled)
Configuration Status
     Valid
The hierarchy of this business system is:
Business System:
   BS_NAUTICUS_OOTS [Role = Application System, Related Integration Server = PI1_BS_01, Technical System = TS_NAUTICUS_OOTS]
Technical System:
   TS_NAUTICUS_OOTS [Type = Third Party, Software Component = SWC_NAUTICUS_OOTS, Product = Product_NAUTICUS_OOTS]
Basically I created product, software component, technical system, business system from scratch.
I did not put any dependencies to existing products/software components.
Regards,
Ron

Message monitoring Status Waiting for email receiver

Hi Guru,
Scenario: SAP ECC will call Error Handling interface class. The communication channel for the Error Handling interface is Email Adapter.
Below is CC setting:
Adapter Type: Mail (Receiver)
Transport Protocol: SMTP
Message Protocol: XIALL
Adapter Engine: Integration Server
URL: smtp://11.11.11.111/
Check - Configure User Authentication
User : user1
Password: password
Mail Attributes:
From: [email protected]
To : [email protected]
Subject : test
Content Encoding: base64
I encountered one problem where my email receiver status in message monitoring is always 'Waiting'. I do not know what went wrong in the setting? Does anyone know how to solve my problem ?
Thanks in advance.
Regards

XI tries 3 times before changing the status of the message to System Error. One can Manually resend the error messages by using the RESEND button in RWB. In scenarios where XI was trying to send the message to an end system that was down for maintenance, you would want XI to resubmit the message automatically without human intervention. What would be nice is to able to tune the retries like IS_Retry which is available for Integration engine.
We can achieve this by changing the retry count used by the Adapter Engine, by default its set to 3 times, 5 minutes apart. This count can be changed in Visual Admin->server->services-> SAP XI Adapter: XI.
Here change the number Retries parameter from 3 to 10 and change the retry retryInterval to around 10minutes. For these configuration changes to be picked up, restart SAP XI Adapter: XI.
please visit the blog
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically

Integration Server Coniguration

XI-Gurus!
We're trying to access the integration server using the file adapter. Polling the file from the source directory works fine but the file isn't transported to the integration server.
In the runtime workbench's message monitor I found an entry that we're using an "unsupported media type" in our message (HTTP code 415). The message has content-type "multipart/related).
Maybe we have a misconfigured integration engine?
I've looked up the configuration with TCODE "SICF". In the HTTP-Handler list there's only on entry "CL_XMS_HTTP_HANDLER".
Is it possible, that this handler doesn't support multipart messages?
Has anybody an idea about this error? Help is highly appreciated...
Regards,
Matthias

Anirban,
thanks for your quick answer! Your reffered document handles (in my opinion) with client access to the Integration Repository. In this trace file req_resp.trc only the requests for port 50000 are mentioned.
Our problem handles with sending HTTP-messages to the integration engine. The HTTP status code is only visible in the message log and not in a response page.
Thank you anyway, maybe you have another idea?
Cheers,
Matthias

How to change connection port between INTEGRATION SERVER and Adapter Engine

Hi,
I have scenario that in the productions server we are using SAP web dispatcher to connect to Adapter Engine for example the port is 60000.
So when we copy this server to DR environment the webdispatcher is not there. is that any way to change the all connection port between IS and Adapter from 60000 back to original port 50000 ?
Please advise ?
Thank You and Regards
Fernand

HI,
The waiting status is because of Message Queue is in wiating status. This may be because of overload of the messages, or may be your receiver systems is not ready etc.
SO go to SMQ2 and check the status of the queues.
Also have a look into this blog-
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
<i>
Why I can see this messages only in the integration server?</i>
>>>If message reachs the Adapter engine, you can see in the Adapter monitor. In your case, message is still there in the Integration Engine. Once the queues are cleared it will reach the Adapter engine, so you can monitor it in the adapter engine
Regards,
Moorthy

How to configure the Integration Server Settins?

Hi,
I am doing a scenario like Idoc 2 File, I am passing parameter of Adapter Engine is a Integration Server, and when we generate a Idoc and send to XI system using TC: WE19. XI System is not picked the Idoc, and when i am checking RWB the Adapter Framework. Please Guide me how to configure the Integration Server setting.
Regards
Mohan

Hi,
did you checked the ur IDOC outbound status?
also check IDX5, whether it has reached XI system.
plz do check all ur settings:
1. Create RFC destination to XI in SM59 transaction
2. Create a port in we21
3. Create partner profile we20
4. we05- Idocs monitoring
XI Settings:
1. Create RFC destination to XI in SM59 transaction
2. Idx1 Port maintenance
3. Idx2 - Metadata maintenance
4. Idx5 All Idoc inbound and outbound messages
regards
Message was edited by:
Vijaya Lakshmi MV

Message File Adapter - XI Integration Server not arriving

We have configured a file adapter to read a file. According to the audit log the file is successfully read and converted to XML; however, the message is never posted to XI. We have checked to make sure that no XI* users are locked and we have bounced the server.
The following error message is listed in the audit log:
Transmitting the message to endpoint http://kansbwul01:50000/sap/xi/engine/entry?action=execute using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: Error writing to server.
The following is the application log:
#1.5#0003BA54D61900190000000C000030E60003EEAAD1138641#1106842349700#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.stop()######3e38f290707e11d996610003ba54d619#SAPEngine_System_Thread[impl:5]_35##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Java###The running MCF with GUID will be stopped now#1#8fa37160707811d995b00003ba54d619#
#1.5#0003BA54D619001900000014000030E60003EEAAD16F4730#1106842355713#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.stop()######3e38f290707e11d996610003ba54d619#SAPEngine_System_Thread[impl:5]_35##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Java###MCF with GUID was stopped successfully.#1#8fa37160707811d995b00003ba54d619#
#1.5#0003BA54D619006000000009000030E60003EEAAD1A4DD9D#1106842359225#/Applications/ExchangeInfrastructure/AdapterFramework/ResourceAdapter/MessagingSystem/System/Clustering##com.sap.aii.af.ra.ms.runtime.MessagingSystem.reassignMessages(String, String[])#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_11##0#0#Error#1#com.sap.aii.af.ra.ms.runtime.MessagingSystem#Java###Could not redistribute messages due to #1#LockingManager must be initialized before usage.#
#1.5#0003BA54D6190040000000000000316A0003EEAAD9D40B8C#1106842496535#/Applications/ExchangeInfrastructure/AdapterFramework/Services/SecurityService##com.sap.aii.af.security.MessageSecurityServiceFrame.MessageSecurityServiceFrame.start()#######SAPEngine_System_Thread[impl:5]_24##0#0#Info#1#com.sap.aii.af.security.MessageSecurityServiceFrame#Java###QUEUE_CONNECTION_FACTORY: , ERROR_QUEUE: , QUEUE: , JARM_PREFIX: , JARM_USER: , JARM_ENABLED: .#6#jmsfactory/default/QueueConnectionFactory#jmsqueues/default/MessageSecurityErrorQueue#jmsqueues/default/MessageSecurityQueue#XI:Security:#XISecurityUser#false#
#1.5#0003BA54D619004A000000060000316A0003EEAADD1ABF82#1106842551500#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb60001]###9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#com.sap.aii.adapter.file.File2XI#Plain###Module Exception 'com.sap.aii.af.mp.module.ModuleException: senderChannel 'c5a6ccb89b113e8c92474a4aa0df5858': Catching exception calling messaging system' found, cause: com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available.#
#1.5#0003BA54D619004A000000080000316A0003EEAADD1AC8F6#1106842551503#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb60001]###9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#com.sap.aii.adapter.file.File2XI#Plain###Delivery Exception for guid'96f35561-707e-11d9-a16c-0003ba54d619' - non recoverable error, retry anyway#
#1.5#0003BA54D619004A0000000A0000316A0003EEAADD1ACE8D#1106842551504#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0####9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#com.sap.aii.adapter.file.File2XI#Plain###Channel CDWExtFile: Sending file failed with com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available. - continue processing#
#1.5#0003BA54D6190011000000FD0000316A0003EEAADF49F9C7#1106842588150#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.SpiManagedConnectionFactory()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Plain###This SPIManagedConnectionFactory has the GUID: cc6372c0-707e-11d9-ca96-0003ba54d619#
#1.5#0003BA54D6190011000001030000316A0003EEAADF4ADA00#1106842588207#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.start()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Java###MCF with GUID is started now. (,)#3#cc6372c0707e11d9ca960003ba54d619#com.sap.engine.services.deploy.server.ApplicationLoader@5293b95#cc6372c0707e11d9ca960003ba54d619#
#1.5#0003BA54D6190011000001090000316A0003EEAADF4AEA33#1106842588211#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.start()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Java###MCF with GUID was started successfully.#1#cc6372c0707e11d9ca960003ba54d619#
#1.5#0003BA54D6190051000000040000316A0003EEAAE1DFB940#1106842631518#/Applications/ExchangeInfrastructure/Repository#sap.com/com.sap.xi.repository#com.sap.aii.ib.core.applcomp.ApplicationComponent#J2EE_GUEST#0####e63e40d0707e11d9b8020003ba54d619#SAPEngine_Application_Thread[impl:3]_21##0#0#Info#1#com.sap.aii.ib.core.applcomp.ApplicationComponent#Plain###Startup of XI Application "REPOSITORY" ok.#
#1.5#0003BA54D6190054000000170000316A0003EEAAE4BA42E1#1106842679394#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector#J2EE_ADMIN#339####02bf9dd0707f11d9b9830003ba54d619#SAPEngine_Application_Thread[impl:3]_12##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
#1.5#0003BA54D619004C000000080000316A0003EEAAE692D9D6#1106842710366#/Applications/ExchangeInfrastructure/Directory#sap.com/com.sap.xi.directory#com.sap.aii.ib.core.applcomp.ApplicationComponent#J2EE_GUEST#0##kansbwul01.erc.ge.com_LB1_148575#Guest#d8164a70707e11d9a3490003ba54d619#SAPEngine_Application_Thread[impl:3]_26##0#0#Info#1#com.sap.aii.ib.core.applcomp.ApplicationComponent#Plain###Startup of XI Application "DIRECTORY" ok.#
#1.5#0003BA54D619004D000000040000316A0003EEAAEB3DF548#1106842788689#/Applications/ExchangeInfrastructure/Directory#sap.com/com.sap.xi.directory#com.sap.aii.ib.server.util.BasicJMSClient#WSHAUN#466#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb6000ffffff90]###43ec08c0707f11d99f8b0003ba54d619#SAPEngine_Application_Thread[impl:3]_32##0#0#Error#1#com.sap.aii.ib.server.util.BasicJMSClient#Plain###TopicConnectionFactory not found#
#1.5#0003BA54D619004D000000050000316A0003EEAAEB3E07B0#1106842788693#/Applications/ExchangeInfrastructure/Directory#sap.com/com.sap.xi.directory#com.sap.aii.ib.server.util.BasicJMSClient#WSHAUN#466#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb6000ffffff90]###43ec08c0707f11d99f8b0003ba54d619#SAPEngine_Application_Thread[impl:3]_32##0#0#Error#1#com.sap.aii.ib.server.util.BasicJMSClient#Plain###Exception during JMS startup for topic "SYNCHRONIZED_CACHE"
Thrown:
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at java:comp, the whole lookup name is java:comp/env/jms/topic/xi/TopicConnectionFactory.
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:258)
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:621)
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
     at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
     at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at com.sap.aii.ib.server.util.BasicJMSClient.initJmsResources(BasicJMSClient.java:77)
     at com.sap.aii.ib.server.util.BasicJMSClient.init(BasicJMSClient.java:54)
     at com.sap.aii.ib.server.util.BasicJMSClient.<init>(BasicJMSClient.java:48)
     at com.sap.aii.ib.server.util.ClusterSyncedCache.<init>(ClusterSyncedCache.java:41)
     at com.sap.aii.ib.server.cpa.AdapterMDCache.<clinit>(AdapterMDCache.java:27)
     at com.sap.aii.ib.sbeans.misc.MiscServicesBean.getAdapterMetadata(MiscServicesBean.java:226)
     at com.sap.aii.ib.sbeans.misc.MiscServicesRemoteObjectImpl10.getAdapterMetadata(MiscServicesRemoteObjectImpl10.java:2028)
     at com.sap.aii.ib.sbeans.misc.MiscServicesRemoteObjectImpl10p4_Skel.dispatch(MiscServicesRemoteObjectImpl10p4_Skel.java:284)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:291)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
#1.5#0003BA54D6190004000000060000316A0003EEAAED036F71#1106842818407#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
#1.5#0003BA54D6190004000000120000316A0003EEAAED1F56F6#1106842820236#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
#1.5#0003BA54D61900040000001E0000316A0003EEAAED2014BF#1106842820285#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
#1.5#0003BA54D61900040000002A0000316A0003EEAAED20EE43#1106842820341#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
#1.5#0003BA54D6190004000000360000316A0003EEAAED21A105#1106842820386#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
#1.5#0003BA54D6190004000000420000316A0003EEAAED2268E0#1106842820438#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
#1.5#0003BA54D61900040000004E0000316A0003EEAAED233205#1106842820489#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
#1.5#0003BA54D61900040000005A0000316A0003EEAAED23EDCB#1106842820537#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
#1.5#0003BA54D6190004000000660000316A0003EEAAED249350#1106842820580#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
#1.5#0003BA54D6190051000000090000316A0003EEAAF39F13CA#1106842929271#/Applications/ExchangeInfrastructure/IntegrationServer#sap.com/com.sap.xi.services#com.sap.aii.ib.core.applcomp.ApplicationComponent#XIDIRUSER#526####97b7c160707f11d9837b0003ba54d619#SAPEngine_Application_Thread[impl:3]_21##0#0#Info#1#com.sap.aii.ib.core.applcomp.ApplicationComponent#Plain###Startup of XI Application "RUNTIME" ok.#
#1.5#0003BA54D619003C0000000C0000316A0003EEAAFD1B729D#1106843088417#/Applications/ExchangeInfrastructure/AdapterFramework/ResourceAdapter/MessagingSystem/System/Queue##com.sap.aii.af.ra.ms.runtime.ListenerFinder.run()#J2EE_GUEST#0####b4a1c0b1707e11d98d600003ba54d619#SAPEngine_Application_Thread[impl:3]_19##0#0#Error#1#com.sap.aii.af.ra.ms.runtime.ListenerFinder#Java###Message listener could not be created for connection after attempts.#3#localejbs/TestListener#test#10#
#1.5#0003BA54D6190058000000050000316A0003EEAB27D41690#1106843805160#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector#J2EE_ADMIN#635####a1c95a40708111d9887c0003ba54d619#SAPEngine_Application_Thread[impl:3]_28##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
The following is the trace file:
#1.5#0003BA54D6190000000000140000316A0003EEAAD72107D8#1106842451248#com.sap.engine.core.service630.container.ReferenceResolver##com.sap.engine.core.service630.container.ReferenceResolver#######Thread[Thread-1,5,main]##0#0#Error##Plain###Component com.sap.aii.af.security has a hard reference to service com.sap.aii.af.service.cpa with manual startup mode.#
#1.5#0003BA54D6190036000000000000316A0003EEAAD94B1302#1106842487558#com.sap.engine.library.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###************************************************************#
#1.5#0003BA54D6190036000000010000316A0003EEAAD94C908B#1106842487656#com.sap.engine.library.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###**************     CCMS CONNECTOR (System)    **************#
#1.5#0003BA54D6190036000000020000316A0003EEAAD94C936D#1106842487657#com.sap.engine.library.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###************************************************************#
#1.5#0003BA54D6190036000000030000316A0003EEAAD94C9621#1106842487657#com.sap.engine.library.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###Tracelevel: 0#
#1.5#0003BA54D6190036000000040000316A0003EEAAD94E292D#1106842487760#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###************************************************************#
#1.5#0003BA54D6190036000000050000316A0003EEAAD94F65F2#1106842487842#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###*******     Java Monitoring API - Version      ********#1#1.8.8#
#1.5#0003BA54D6190036000000060000316A0003EEAAD9525DA5#1106842488036#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###************************************************************#
#1.5#0003BA54D6190036000000070000316A0003EEAAD9547512#1106842488173#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###Host: , OS: , JDK: .#3#kansbwul01.erc.ge.com#SunOS_sparcv9_5.9#1.4.2_06#
#1.5#0003BA54D6190036000000080000316A0003EEAAD95490A6#1106842488180#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###Calculated library path: /global/usr/sap/LB1/DVEBMGS00/j2ee/cluster/server0/bin/ext/com.sap.mona.api#
#1.5#0003BA54D6190036000000090000316A0003EEAAD954A29A#1106842488185#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###System.load [2] /global/usr/sap/LB1/DVEBMGS00/j2ee/os_libs/libjmon.so#
#1.5#0003BA54D61900360000000A0000316A0003EEAAD95617BA#1106842488280#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###Version of JNI library: .#1#3.12 Non-Unicode Version#
#1.5#0003BA54D61900360000000B0000316A0003EEAAD9562000#1106842488283#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###Java tracelevel set to .#1#Error#
#1.5#0003BA54D61900360000000C0000316A0003EEAAD9577C95#1106842488372#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###Connected () to segment (), , .#5#attach#0#read/write#system mode#40000000 bytes#
#1.5#0003BA54D6190009000000010000316A0003EEAAD97D6C04#1106842490858#com.sap.aii.af.ra.ms.impl.core.queue.Queue##com.sap.aii.af.ra.ms.impl.core.queue.Queue.run()#######SAPEngine_System_Thread[impl:5]_73##0#0#Error##Java###Failed to retrieve message from MessageStore for queue .#2#aef38c80-707d-11d9-a639-0003ba54d619(OUTBOUND)#AFWSend#
#1.5#0003BA54D6190014000000020000316A0003EEAAD988D5C9#1106842491606#com.sap.aii.af.ra.ms.impl.core.queue.Queue##com.sap.aii.af.ra.ms.impl.core.queue.Queue.run()#######SAPEngine_System_Thread[impl:5]_28##0#0#Error##Java###Failed to retrieve message from MessageStore for queue .#2#ea9f3be0-707c-11d9-834f-0003ba54d619(OUTBOUND)#AFWSend#
#1.5#0003BA54D619003F000000000000316A0003EEAAD9CFB274#1106842496250#com.sap.aii.af.service.cpa.impl.cache.CacheManager##com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(boolean)#######SAPEngine_System_Thread[impl:5]_65##0#0#Error##Java###CPA Cache not updated with directory data, due to: #1#Couldn't open Directory URL (http://kansbwul01:50000/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.lb1.kansbwul01), due to: HTTP 503: Service Unavailable#
#1.5#0003BA54D619003F000000010000316A0003EEAAD9D09295#1106842496307#com.sap.aii.af.service.cpa.impl.cache.CacheManager##com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(boolean)#######SAPEngine_System_Thread[impl:5]_65##0#0#Error##Java###Confirmation handling failed, due to: #1#Couldn't send confirmation, due to: Couldn't access Confirmation URL, due to: HTTP 503: Service Unavailable#
#1.5#0003BA54D6190046000000000000316A0003EEAAD9E5FAD6#1106842497710#com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext##com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext.setCurrentNodeID(int)#######SAPEngine_System_Thread[impl:5]_43##0#0#Info#1#/Version#Plain###Current node set to 1485750#
#1.5#0003BA54D6190046000000010000316A0003EEAAD9E62B77#1106842497723#com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext##com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext.setEnvironmentState(int)#######SAPEngine_System_Thread[impl:5]_43##0#0#Info#1#/Version#Plain###Environment state set to : ENV_INCOMPLETE#
#1.5#0003BA54D6190049000000000000316A0003EEAAD9F40CB0#1106842498632#com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry##com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry.getValue(boolean)#######SAPEngine_System_Thread[impl:5]_77##0#0#Error##Java###Decryption failed, due to .#1#<null>#
#1.5#0003BA54D6190049000000010000316A0003EEAAD9FB0888#1106842499090#com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry##com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry.getValue(boolean)#######SAPEngine_System_Thread[impl:5]_77##0#0#Error##Java###Decryption failed, due to .#1#<null>#
#1.5#0003BA54D6190049000000020000316A0003EEAAD9FB3838#1106842499102#com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry##com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry.getValue(boolean)#######SAPEngine_System_Thread[impl:5]_77##0#0#Error##Java###Decryption failed, due to .#1#<null>#
#1.5#0003BA54D6190049000000030000316A0003EEAAD9FB61D0#1106842499113#com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry##com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry.getValue(boolean)#######SAPEngine_System_Thread[impl:5]_77##0#0#Error##Java###Decryption failed, due to .#1#<null>#
#1.5#0003BA54D6190009000000020000316A0003EEAADA5386CF#1106842504889#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage)######9998abd0707e11d9cd270003ba54d619#SAPEngine_System_Thread[impl:5]_73##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: Error writing to server#http://kansbwul01:50000/sap/xi/engine/entry?action=execute#
#1.5#0003BA54D6190014000000030000316A0003EEAADA542AB7#1106842504931#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage)######99afb640707e11d9a86c0003ba54d619#SAPEngine_System_Thread[impl:5]_28##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: Error writing to server#http://kansbwul01:50000/sap/xi/engine/entry?action=execute#
#1.5#0003BA54D619004D000000000000316A0003EEAADAF321D0#1106842515349#com.sap.aii.proxy.xiruntime.web.TransportServlet#sap.com/com.sap.xi.proxyserver#com.sap.aii.proxy.xiruntime.web.TransportServlet.init(...)#J2EE_GUEST#0####a1006c50707e11d99ea30003ba54d619#SAPEngine_Application_Thread[impl:3]_32##0#0#Info##Plain###Initialized#
#1.5#0003BA54D619004D000000010000316A0003EEAADAF32B88#1106842515352#com.sap.aii.proxy.xiruntime.web.TransportServlet#sap.com/com.sap.xi.proxyserver#com.sap.aii.proxy.xiruntime.web.TransportServlet.init(...)#J2EE_GUEST#0####a1006c50707e11d99ea30003ba54d619#SAPEngine_Application_Thread[impl:3]_32##0#0#Info##Plain###Registered with Adapter Framework Monitor#
#1.5#0003BA54D6190055000000010000316A0003EEAADCAC81FD#1106842544275#com.sap.pmi.io.HttpPostThread##com.sap.pmi.io.HttpPostThread######b1f90ee0707e11d9c4300003ba54d619#Thread[Thread-42,5,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/System/Server#Plain###Error sending PMI records to http://kansbwul01:8000/sap/bc/sapi_gate, HTTP response: 404Not found. Please check the HTTP destination "pmistore".#
#1.5#0003BA54D619004A000000050000316A0003EEAADD1ABD1C#1106842551499#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb60001]###9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Module Exception 'com.sap.aii.af.mp.module.ModuleException: senderChannel 'c5a6ccb89b113e8c92474a4aa0df5858': Catching exception calling messaging system' found, cause: com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available.#
#1.5#0003BA54D619004A000000070000316A0003EEAADD1AC765#1106842551502#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb60001]###9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Delivery Exception for guid'96f35561-707e-11d9-a16c-0003ba54d619' - non recoverable error, retry anyway#
#1.5#0003BA54D619004A000000090000316A0003EEAADD1ACD22#1106842551504#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0####9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CDWExtFile: Sending file failed with com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available. - continue processing#
#1.5#0003BA54D619004A0000000C0000316A0003EEAADD1B3AEE#1106842551532#com.sap.engine.services.ts##com.sap.engine.services.ts#J2EE_GUEST#0####9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Server#Java#ts_0021##Thread is not associated with any transaction context.##
#1.5#0003BA54D619004A0000000D0000316A0003EEAADD1B41AE#1106842551533#com.sap.engine.services.ts##com.sap.engine.services.ts#J2EE_GUEST#0####9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ts.exceptions.BaseIllegalStateException: Thread is not associated with any transaction context.
     at com.sap.engine.services.ts.jta.impl.TransactionManagerImpl.rollback(TransactionManagerImpl.java:441)
     at com.sap.aii.adapter.file.File2XI.processFileList(File2XI.java:1756)
     at com.sap.aii.adapter.file.File2XI.run(File2XI.java:1007)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
#1.5#0003BA54D6190011000000790000316A0003EEAADDAE5C4B#1106842561174#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.xi.ibresources factory name: jms/topic/xi/TopicConnectionFactory loader does not exist: . Using default class loader!!!#
#1.5#0003BA54D61900110000007A0000316A0003EEAADDAFCE2B#1106842561269#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: jms/topic/xi/TopicConnectionFactory loader does not exist: . Using default class loader!!!#
#1.5#0003BA54D61900110000007C0000316A0003EEAADDAFE340#1106842561274#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.xi.ibresources factory name: jms/queue/xi/QueueConnectionFactory loader does not exist: . Using default class loader!!!#
#1.5#0003BA54D61900110000007D0000316A0003EEAADDB040CB#1106842561298#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: jms/queue/xi/QueueConnectionFactory loader does not exist: . Using default class loader!!!#
#1.5#0003BA54D6190011000000B20000316A0003EEAADE6877ED#1106842573371#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.aii.af.ispeak.app factory name: ISPXAConnectionFactory loader does not exist: . Using default class loader!!!#
#1.5#0003BA54D6190011000000B30000316A0003EEAADE68A1E8#1106842573382#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: ISPXAConnectionFactory loader does not exist: . Using default class loader!!!#
#1.5#0003BA54D6190011000000C10000316A0003EEAADE837B81#1106842575141#com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext##com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext.setEnvironmentState(int)######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#/Version#Plain###Environment state set to : ENV_COMPLETE#
#1.5#0003BA54D6190011000000C20000316A0003EEAADE83D50E#1106842575164#com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession##com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.initialize()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#/Version#Plain###Looked up factory : com.sap.engine.services.jmsconnector.cci.QueueConnectionFactoryImpl@6cbd9138#
#1.5#0003BA54D6190011000000C30000316A0003EEAADE83D78C#1106842575165#com.sap.aii.af.protocol.ispeak.j2ee.services.ISPStartupService##com.sap.aii.af.protocol.ispeak.j2ee.services.ISPStartupService.onAllAppStart()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#/Version#Plain###Calling onServerStart on ISPClusterContext...#
#1.5#0003BA54D6190011000000E60000316A0003EEAADF147D24#1106842584644#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.ip.me.insttool factory name: InstToolTopicFactoryCreateEmptyImage loader does not exist: . Using default class loader!!!#
#1.5#0003BA54D6190011000000E70000316A0003EEAADF14A82D#1106842584655#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: InstToolTopicFactoryCreateEmptyImage loader does not exist: . Using default class loader!!!#
#1.5#0003BA54D6190011000000E90000316A0003EEAADF14B7A3#1106842584659#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.ip.me.insttool factory name: InstToolTopicFactoryFinishImage loader does not exist: . Using default class loader!!!#
#1.5#0003BA54D6190011000000EA0000316A0003EEAADF14DC56#1106842584669#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: InstToolTopicFactoryFinishImage loader does not exist: . Using default class loader!!!#

The problem was the Pipeline URL for the integration server.
http://<server>:50000/sap/xi/engine/entry?action=execute
is the defective URL.
Once we logged into SLD and selected the business system for the integration server we change the pipeline URL to the following
http://<server>:8000/sap/xi/engine?type=entry
we then restarted the J2EE server and it worked fine.

ERROR REGARDING INTEGRATION SERVER

hai am k chandrakanth from bangalore a beginner in sap-xi,below am posting feew question s,kindly revert back with suitable answers with screen shots if possible(note: these are all the problems which am facing inmy PC)
1)during INTEGRATION SERVER CONFIGURATION thru SXMB_MONI
i got an error message "CORRRESPONDING INTEGRATION SERVER NOT MAINTAINED" on execution of the configuration.
2)When i select ROLE OF BUSINESS SYSTEM AS ->APPLICATION SYSTEM and
RELATED INTEGRATION SERVER -> (While assigning INTEGRATION SERVER)
i got an error :could not update the business system JAVA.LANG.NULLPOINTER EXCEPTIONS.
3)in SXI_CACHE t.code when i choose menu path ENVIRONMENT -> CACHE NOTIFICATIONS i got an error : UNABLE TO DETERMINE THE NAME OF THE CENTRAL ADAPTER ENGINE FROM THE SLD
4)during PERFORMANCE MONITORING
errors: A)APPLICATION ERRORS: INTEGRATION SERVER UNABLE TO FETCH DATA
B)ERROR CLASS:COM.SAP.AII.RWB.WEB.PERFORMANCEMONITORING.AGGREGATE.....
C) NO COMPONENTS AVAILABLE IN THE INTEGRATION SERVER...

Hi Chandra,
Have you done the XI - Post congiuration completely ?
Did you cross check and validate the XI Configuration?
Regards,
Prem

BPM Acknowledgement message reading the wrong integration server name

HI
I have a scenario where I have BPM which sends data to A MS SQL Server database and waits for a TRANSPORT Acknowledgement. The Mesage going to the Database is processed successfully but the acknowledgement messasge fails giving the following error when viewed in the message monitor.
IS_DETAILS_GET_ERROR
no_integration_server_found: Unable to find Integration Server is.XX.XXXXXXXX
Error while reading access data (URL, user, password) of Integration Server is.XX.XXXXXXXX
Actually the string "is.XX.XXXXXXXX" contains the name of the integration server.
Now my problem is the actual value contained in the above string is the name of the integration server . But this name is not correct , I mean it is not what the actual name should be. We are not able to find out from where this incorrect name is being picked up. Can anyone tell from where the actaul name and url of the integration server is read. Is it stored in different locations for inbound messages and acknowledgement msgs. Will refreshing any of the caches will help.
Please suggest.
regards
Nilesh Taunk.

Hi Nilesh,
your problem is very strange because your BPM is sending data correctly to SQL DB .....your db is processed.....but the ack msg when coming in bpm gives IS_DETAILS_GET_ERROR.
i think just see all the objects in IR and ID are activated.....after that by SXI_CACHE transaction do a cache refresh.........see the return code of BPM is zero or not......the retun code of BPM shuld be zero.......
again run your this scenario.......now please tell what happens......
Thanks,
Rajeev Gupta

SOAPFault from Integration Server because of attachment name

Hello everyone,
I'm currently building the attachment function into our adapter for IBM Lotus Notes and SAP XI.
In the Sender part, the adapter must add the attachment from Lotus Notes to the XI Message as a payload.
The following source code show how to do this:
/Create a payload from a XI Message/
Payload attachment = xiMessage.createPayLoad();
/Set the attachment name with the file name of the Notes attachment/
/I have problem with this method/
attachment.setName(notesAttachment.getFileName());
/Set the content (byte array) of the attachment/
attachment.setContent(notesAttachment.getBytesContents());
This works well unless no special file name like ("Ättachment") is entered in the method Payload.setName().
Errors will be shown in the Audit Log:
1. SOAPFault received from Integration Server. ErrorCode/Category: XIProtocol/SAP_CODEPAGE_CONVERSION_ERROR; Params: ; AdditionalText: ; ApplicationFaultMessage: ; ErrorStack: Error when converting the code page for character set UTF-8 (code page 4110): Cannot convert character sets for one or more characters.
2. Transmitting the message to endpoint http://kit-was:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during creation of multipart mime object.
and in the Logviewer:
1. enrichMessageData(): Error during retrieving the end-to-end-monitoring information
Thrown:com.sap.aii.rwb.endtoendmonitoring.util.Sxmb_Get_Pmi_Info_Fault_Exception: at sun.reflect.GeneratedConstructorAccessor553.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
But in the "Message content --> SOAP Document", the attachment name can be showed correctly:
- <sap:Payload xlink:type="simple" xlink:href="cid:[email protected]">
<sap:Name>Ättachment</sap:Name>
<sap:Description>üüüäää</sap:Description>
<sap:Type>ApplicationAttachment</sap:Type>
</sap:Payload>
I've no idea, what should I do. Apparently I did every correctly, but why SAP Integration Server didn't work?
The ABAP stack of the XI server should also support Unicode. Our XI server is 04 SP 19.
Please give me some help.
with regards
Xiang

Hi Stefan,
thanks for your reply.
The problem is that String is unicode in Java. The method from SAP is
void setName(java.lang.String name) .
In Java it is only necessary to define charset when create a string based on a bytes array.
String(byte[] bytes, String charsetName)
Constructs a new String by decoding the specified array of bytes using the specified charset.
I got the file name from Lotus Notes as a String and just gave it to the SAP method. Then the Integration Server gave an error message about the name.
Regards
Xiang

No destination for Integration Server found - XI 2.0

Hello,
I have developed a few java proxies and have had good luck using the jpf.properties file. Now, as we would like to set up more of a production scenario we are in need of moving over to the dbconnect.properties and technicalID.properties. The problem is when switching over to these files I received the "No destination for Integration Server found" error. So first off I would like to make sure we have the files configured correctly.
dbconnect.properties
hostname=xipsys
systemNumber=03
user=xiusr
password=xipswd
client=300
language=EN
... the dbconnect.properties file is correct I believe.
technicalID.properties
SAPTechnicalSystemIdentification=TS_MyTechnicalSystemName.SystemHome.MyPCName
... the TS_MyTechnicalSystemName is the technical system that I created in the SLD. MyPCName is my computer name as this is where I'm running the java proxies from.
First off, does it look like my files are configured properly?
Second, in the SLD I've configured my technical system and also a business system with similar names and specified the host as MyPCName. Is this correct?
I've also noticed that when I remove the files completely from my system I get the exact same error message however they are in the right location and have the correct names. Is there anyway to get a better error message out of the system? I know the files are in the right location cause if I use the jpf.properties in that location it works.
thx
XI 2.0

Well it's getting a lot closer. I'm getting a different error now and its showing up in tx SXMB_MONI. The error I get is...
ROUTING.NO_SENDER:Unable to find a sender
In the monitor it shows that there was a message pushed but it's red flagged and there is no sender/receiver information. Is there anything else I need to add to the java proxies?
The following is my latest configuration ....
dbconnect.properties looks like
hostname=myXIServer
systemNumber=03
user=XILDUSER
password=password
client=300
language=EN
technicalID.properties
SAPTechnicalSystemIdentification=TS_myTechSys.SystemHome.BS_myBizSys
In the SLD I have TS_myTechSys defined as a "SAP Standalone Java System" on myComputer.mydomain.com.
Also in the SLD, I have defined BS_myBizSys as a "Java System" and belongs to the TS_myTechSys Technical System.
In the exChange Profile under ApplicationSystem I have the following defined
com.sap.aii.applicationsystem.serviceuser.language
com.sap.aii.applicationsystem.serviceuser.name
com.sap.aii.applicationsystem.serviceuser.pwd
com.sap.aii.proxy.framework.connection.timeoutInMSec
com.sap.aii.proxy.framework.destination
com.sap.aii.proxy.framework.destination.client
In addition I also get the following error sometimes...
JPF loadProfileProperties() - Could not access Exchange Profile: java.lang.ExceptionInInitializerError: JCO.classInitialize(): Could not load middleware layer '
com.sap.mw.jco.rfc.MiddlewareRFC'
no sapjcorfc in java.library.path
I have this file as a dll in the same directory as all the jar's.
in addition XILDUSER is part of the following group
SAP_BC_AI_LANDSCAPE_DB_RFC
Should that user have more permission?
Any ideas?
XI 2.0
One more note, I am running my WebApp from an instance of Tomcat 4.1. This is where the Java Proxies are running and it works fine using the jpf.properties. Some of the documentation I've recently found has said that it needs to be running on a SAP J2EE engine which we will not be able to do in the end.
Message was edited by: Larry Chaput
Message was edited by: Larry Chaput

Error: Idoc name IDoc cannot find request IDoc in Integration Server

Hi,
I am getting an error while working on a scenario.
scenario is Idoc to file. when the Idoc is posted, i am getting the error "ALEAUDIT IDoc cannot find request IDoc in Integration Server" when i see the status in SXMB_MONI
I have tested the message mapping and configuration induvidually. They are working fine.
Kindly help me out in solving this issue.
please reply

Hi,
The AleAduit sent in the case of Idoc to File if the file is posted successfuly is not actually a App Ack, and that is why we get the info Ack not possible.
But, as the R3 might expect this Idoc, XI still sends it back to the Source R3 system.
Regards,
phani

Monitoring status of OID Integration Server

Similar Messages

Maybe you are looking for