Jar for the package com.sap.engine.interfaces.messaging.api

Dear All,
I am writing a UDF where we want to use the Payload class of package com.sap.engine.interfaces.messaging.api. We are not getting the corresponding jar file.
Please suggest what should be the jar file.
Thanks and Regards,
Rana Brata De

this you can not use at mapping runtime. You can use this API only in Adapter modules.
What is your requirement?
Edited by: Praveen Gujjeti on Feb 27, 2012 4:38 PM

Similar Messages

Com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax

Hello,
Please explain me the error :
com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.ejb.EJBException: nested exception is: java.lang.RuntimeException: java.lang.NoClassDefFoundError: com/primavera/integration/server/ServerFacade : cannot initialize class because prior initialization attempt failed
Where should I find the issue and how to correct it.
Regards

Hi,
This seems to be related to some deployed components on J2EE-engine being corrupt. Try re-deploy the primavera-component to fix the error. I'm guessing this component is some 3rd party or custom developed component?
Also make sure this component compiles correctly if it's a custom development component.
Br,
Kenneth

Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found

In my 2006 biztalk application I have exposed web service to receive SAP input. It was working fine. After I have modified something in orchestration in that application . I am getting following error while SAP try to consume my web service. Can anyone please
help me.
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found

In my 2006 biztalk application I have exposed web service to receive SAP input. It was working fine. After I have modified something in orchestration in that application . I am getting following error while SAP try to consume my web service.
HI Arivazhagan K,
Could you give some explanation about what you modified? according the to error message, this is "resource is not found issue".
Best regards,
Angie
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException in sap pi

Hi all,
I am working on SAP PI 7.3.1 SP09. Currently we have interfaces which uses 50200 port. I have created a http destination from nwa pointing to https://....url. So all of a sudden all the interfaces went to error state. After debugging i found that the port 50200 is replaced with 50201which is https port. After changing the port to initial value ie., 50200 all interfaces are working fine except the one which were pointing to https url and they are showing the following error description.
<SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The entire trace is as follows:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="3" type="T">Sender scheme external =</Trace>
<Trace level="3" type="T">Sender agency external =</Trace>
<Trace level="3" type="T">Sender party external =</Trace>
<Trace level="3" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Determining the sender agreement</Trace>
<Trace level="3" type="T">##### DG: 3</Trace>
<Trace level="3" type="T">##### TO: 3</Trace>
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine/?type=entry HTTP/1.0</Trace>
<Trace level="2" type="T">Host = 10.66.14.150:50200</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.0</Trace>
<Trace level="1" type="T">Remote address = 10.66.10.160</Trace>
<Trace level="1" type="T">User = SFUSER</Trace>
<Trace level="1" type="T">Process ID: 760</Trace>
<Trace level="1" type="T">Work Process ID: 10</Trace>
<Trace level="1" type="T">Message ID = 53BEFE7146893BD5E10000000A420AA0</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="3" type="T">##### DG: 3</Trace>
<Trace level="3" type="T">##### TO: 3</Trace>
<Trace level="1" type="T">Hop engine name = is.02.devpipd1</Trace>
<Trace level="1" type="T">Hop engine type = IS</Trace>
<Trace level="1" type="T">Hop adapter name = XI</Trace>
<Trace level="1" type="T">Hop adapter namespace = http://sap.com/xi/XI/System</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="3" type="T">system-ID = PD1</Trace>
<Trace level="3" type="T">client = 001</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = SFUSER</Trace>
<Trace level="1" type="Timestamp">2014-07-10T08:56:37Z INDIA</Trace>
<Trace level="1" type="T">ACL Check is performed</Trace>
<Trace level="1" type="T">XML validation is executed</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<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">>>>PID delete old pid determination coding</Trace>
<Trace level="3" type="T">Pipeline-Elements for pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T">0001 PLSRV_XML_VALIDATION_RQ_INB</Trace>
<Trace level="3" type="T">0002 PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">0003 PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">0004 PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">0005 PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">0006 PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">0007 PLSRV_VIRUS_SCAN_RQ_OUT</Trace>
<Trace level="3" type="T">0008 PLSRV_XML_VALIDATION_RQ_OUT</Trace>
<Trace level="3" type="T">0009 PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">0010 PLSRV_VIRUS_SCAN_RS_INB</Trace>
<Trace level="3" type="T">0011 PLSRV_XML_VALIDATION_RS_INB</Trace>
<Trace level="3" type="T">0012 PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">0013 PLSRV_VIRUS_SCAN_RS_OUT</Trace>
<Trace level="3" type="T">0014 PLSRV_XML_VALIDATION_RS_OUT</Trace>
<Trace level="3" type="T">system-ID = PD1</Trace>
<Trace level="3" type="T">client = 001</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = SFUSER</Trace>
- <Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-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">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB">
<Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Start of pipeline service processing PLSRVID= PLSRV_XML_VALIDATION_RQ_INB</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_XML_VALIDATION_RQ_INB</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</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_VALIDATION</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" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV">
<Trace level="3" type="T">Pipeline Service = PLSRV_XML_VALIDATION_RQ_INB</Trace>
<Trace level="3" type="T">Skip Inbound Validation =</Trace>
<Trace level="3" type="T">Skip Outbound Validation =</Trace>
<Trace level="3" type="T">Area = XML_VALIDATION_INB</Trace>
<Trace level="1" type="T">Reading sender agreement</Trace>
<Trace level="1" type="T">Message does not contain a sender agreement</Trace>
<Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA End of pipeline service processing PLSRVID= PLSRV_XML_VALIDATION_RQ_INB</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-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">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA 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

HI,
Thank you for your hint. Maybe I just forgot to mention one important fact. We have second SAP Netweaver PI 7.1 which is completely our system. The first one I mentioned in first message is the customer's one. The one we have extra is also connected to MAXIMO and GIS. Settings of this interface is completely same among one thing:
Patch level of XIAF:
1. customers SAP PI level is
Adapter Common Library Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:29:47+0000)
Adapter Application Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:30:00+0000)
2. our SAP PI level is
Adapter Common Library Version: 1.7.1008.20100215155230.0000, NW07_08_REL (2010-02-15T17:19:21+0000)
Adapter Application Version: 1.7.1008.20100215155230.0000, NW07_08_REL (2010-02-15T17:19:31+0000)
Both of them has Axis Version: Apache Axis version: 1.4 Built on Apr 22, 2006 (06:55:48 PDT)
Also important to mention is fact that same problem happened in our SAP PI, but we implemented last patch of XIAF and it has suddenly started to work. I have suspicion it is somehow connected to this patch. Btw. this patch contains a lot of notes regarding AXIS framework (i.e. 1435998, 1150375, 1048268), so obviously some bugs of the AXIS adapter has been resolved by this patch.
What do you think ?
Thanks

SOAP Sender Error - com.sap.engine.interfaces.messaging.api.exception

Hi,
I am testing a SOAP Sender Channel using a SOAP Client and getting the following error. I have read almost all the posts related to errors in SOAP Channel and also have checked my URL which is correct. AS mentioned in many of the posts, my url goes like
https://<host>:<port>/XISOAPAdapter/MessageServlet?channel=:DEMO:SOAP_s_GETLIST&version=3.0&SenderService=DEMO&interface=si_os_GETLIST&interfaceNamespace=<namespace>
This is the error that I get when sending a message to the interface
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>Server Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context>XIAdapter</context>
               <code>ADAPTER.JAVA_EXCEPTION</code>
<text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIProxy:PARSE_APPLICATION_DATA:
     at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1041)
     at sun.reflect.GeneratedMethodAccessor1044_10001.invoke(Unknown Source)*
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
Has Anybody got this problem before? Is it any problem with the SOAP Adapter itself or with the data that is going in the message? If so, What is the possible solution for this?
Thanks,
Rashmi.

Hi Rashmi,
I also think your problem is data related.
Check the response in your SAP PI message monitor (SXMB_MONI) when you trigger a request using SoapUI. It sometimes provides a bit more detail. You design (data types, message types, service interfaces etc.) was done in SAP PI 7 then an Abap Proxy was generated from the service interface?
Sometimes there is an issue between the XSD data type declaration in SAP PI and the conversion to Abap data types that takes place when a proxy is generated from a PI Service Interface.
Check the data that you pass in your request, especially those like datetime fields. Maybe even change some of the data type definitions (like datetime) to a string (request & response) & then test through SoapUI & see if you still get the error. Then you can work out how to best resolve it.
Best Regards, Trevor

Integrated Configurations com.sap.engine.interfaces.messaging.api.exception

Hi guys,
we are using PI 7.11.
With this release local processing on the advanced adapter engine is possible, when using integrated configurations.
This works fine.
Lately I faced an error situation in an RFC to JDBC scenario, when one field doesn´t meet the conditions of the database.
I tried to dig deeper to identify the incorrect value by switch on the trace in the receiver JDBC channel, as I did several times before.
Afterwards I treied to restart the message.
Following error occurs.
com.sap.engine.interfaces.messaging.api.exception.ConfigException: Unable to retrieve interface determination with object ID ab1bf720bf2711dea7d2020000000030 from CPA cache.
I made some test with integrated configurations (FTP to FTP) and come to the result that errors, which require changes on the communication channel e.g. wrong password etc. result in an new object in the CPA cache
trying restart the failed message ends up in the error specified aboce.
Anyone faced the same issue already?
Kind regards
Jochen

HI Jochen,
I feel that you should once go for a CPA Cache refresh from Adapter Engine and try executing your failed messages once again in the adapter engine.
To do a CPA Cache Refresh from the Adapter Engine:
To trigger a cache refresh from the individual Adapter Framework, open a browser window and enter the following URL:
http://<host>:<port>/CPACache/refresh?mode=delta|full
The Monitoring url is like this:
http://<host>:<port>/CPACache
Check this How-to Guide on Cache, it will be useful:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01be34&overridelayout=true
Thanks
Dhwani

Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all

Hello,
I have an issue configuring a simple File Adapter Content Conversion, it will be great to give me some support as I'am new in the PO Environment.
Iam reading a flat file and trying to write into an XML in the same FTP server
I have a 1 to 1 Mapping as follows
And my Content Conversion at Sender side Looks like this
After running the configuration Iam getting following error message
Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all
My System is the SAP Netweaver Process Intgration 7.4 single Java stack
Do you have any idea how to fix this issue?
Many thanks in advance
Khadim

Hi evrybody
I have enabled the tracing of ICO and have seen that my payload for the message mapping is ok,.
<ns:hartgeldbest_ERP_KT xmlns:ns="http://xxxxxx.de">
<Recordset>
<header>
     <gesellschaft>03</gesellschaft>
     <filiale>000</filiale>
     <satzart>11</satzart>
     <datum>00000000</datum>
     <kennzeichen>1</kennzeichen>
</header>
</Recordset>
</ns:hartgeldbest_ERP_KT>
The issue is on detrmining the RECEIVER in the Main-XML
<sap:Main xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sap="http://sap.com/xi/XI/Message/30" versionMajor="3"versionMinor="1" SOAP:mustUnderstand="1">
<sap:MessageClass>ApplicationMessage</sap:MessageClass>
<sap:ProcessingMode>asynchronous</sap:ProcessingMode>
<sap:MessageId>ae41678e-da87-11e3-cd0f-0000006831a2</sap:MessageId>
<sap:TimeSent>2014-05-13T10:16:43Z</sap:TimeSent>
<sap:Sender>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty"/>
<sap:Service>CC_Hartgeldbest_File2Idoc</sap:Service>
</sap:Sender>
<sap:Receiver>
<sap:Party agency="" scheme=""/>
<sap:Service/>
</sap:Receiver>
<sap:Interface namespace="http://xxxxx.de">hartgeldbest_KT_async_out</sap:Interface>
</sap:Main>
Is it possible that the receiver is overwritten due to the Content Conversion? Because if I set my Message Protocol to "File" the receiver determination will work.
Any idea?
Thx
Khadim

File to RFC Error com.sap.engine.interfaces.messaging.api.exception.Messagi

Hi ,
I am doing File to RFC Scenario.
My file get picked and I able to view the audit log under RWB message monitoring.
Here I am getting the error
u201CTransmitting the message to endpoint dest://XI_INTEGRATION_SERVER using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message using HTTPTransmitter. Reason: java.net.MalformedURLException: unknown protocol: dest.
Can any one tell me what is the reason.
Regards, Navneet

Hi Prakasu,
I am using PI 7.1 version .
When I opened SMICM there I am finding the HTTP Port as 52000.and the BS at SLD are also using the same Port in URL..
And when i verified with the Basis they confirmed that Exchange profile is set correctly.
But My file adapter is still not able to send the data to IS.
Than I configured a scenario file to file without IR object and in this case data is coming to IS and it is succesfull also.
what is the reason that in this case file adapter not able to push the data to IS.
I used File adapter with NFS protocol.
regards,
navneet

Com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException

Hi All,
PI 7.1 is sending the following error:
2009-12-10 15:55:00     Information     Trying to put the message into the send queue.
2009-12-10 15:55:00     Error     Putting message into send queue failed, due to: com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id ee6b5d0d-25a6-4aec-0fec-f1099b5335ce(OUTBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: DB2 SQL error: SQLCODE: -803, SQLSTATE: 23505, SQLERRMC: 1;SAPPIDDB.BC_MSG_DUP_CHECK.
2009-12-10 15:55:00     Error     Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id ee6b5d0d-25a6-4aec-0fec-f1099b5335ce(OUTBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: DB2 SQL error: SQLCODE: -803, SQLSTATE: 23505, SQLERRMC: 1;SAPPIDDB.BC_MSG_DUP_CHECK
2009-12-10 15:55:00     Error     MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id ee6b5d0d-25a6-4aec-0fec-f1099b5335ce(OUTBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: DB2 SQL error: SQLCODE: -803, SQLSTATE: 23505, SQLERRMC: 1;SAPPIDDB.BC_MSG_DUP_CHECK
I didn't find anything into OSS... =(   Does anybody can help me?
I really appreciate your help
Regards,
Gilberto Martínez

Hi Suman,
Which PI version you are using? Is it double stack?
We also faced a similar problem few days back.
We have tried a below approach and succeeded.
Can you please check with T-code SXMB_MONI if there are any queues are stopped (Red circle symbol written STOP on it).
Go to t-code SMQ1/SMQ2 and click on the line items, it will open another session which will display the details of message status (Green flag-scheduled).
Click on the Resend button on the tool bar, it will show a pop-up there click on Retain button.
This will help you to restart a stucked EOIO/EO messages.
P.S: You have to determine that how many such kind of queues are stopped and so you have to manually restart those scheduled messages.
Also refer to this thread Queue stopped in sxmb_moni
Try this if it helps.
Regards,
Dipen.

Com.sap.engine.interfaces.webservices.runtime.RuntimeProcessException

I get the below error in Develope trace and see all the process are in status :"Inprogress" from many days and the task's related to them are inactive.How can i rectify?
process()
[EXCEPTION]
com.sap.engine.interfaces.webservices.runtime.RuntimeProcessException: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Connection IO Exception. Check nested exception for details. (Invalid char #0x0 (:main:, row:328, col:0)).
at com.sap.engine.services.webservices.espbase.server.additions.StreamEngine.deserializeJEE(StreamEngine.java:386)

Hi,
You get this error when null value is passed when the webservice is triggerred. Check for null values and pass any default value when triggering the webservice. This will solve. At the end of the error trace the exact cause for the exception will be mentioned.
Regards,
Shilpa

Com.sap.engine jars

Hi all,
Witch jar contains this packages:
com.sap.engine.interfaces.security.auth.AbstractLoginModule;
com.sap.engine.lib.security.http.HttpGetterCallback;
com.sap.engine.lib.security.http.HttpCallback;
com.sap.engine.lib.security.LoginExceptionDetails;
com.sap.engine.lib.security.Principal;
Best Regards,

Hello,
AbstractLoginModule class can be found in security_api.jar package....
which can be found at <j2ee_install>\j2ee\cluster\server0\bin\interfaces\security
For rest of the classes .can be found in util.jar package...
Regards,
Madhu

Unable to login to IB - again com.sap.engine.services.rmi_p4.P4IOException

We have installed a new PI 7.1 system and at he moment I have the problem that I can't login into the IB tools. I found a lot of threads with this problem but I can't find a solution for my specific problem. Have a look at the well known error log:
com.sap.aii.utilxi.misc.api.ReconnectRuntimeException: Cannot connect to server using message server: ms://MYHOST:8100/P4
     at com.sap.aii.ib.clsif.login.EJBHomeFactory.getInitialContext(EJBHomeFactory.java:668)
     at com.sap.aii.ib.clsif.login.EJBHomeFactory.connect(EJBHomeFactory.java:461)
     at com.sap.aii.ib.clsif.login.EJBHomeFactory.initRemoteFactory(EJBHomeFactory.java:133)
     at com.sap.aii.ib.clsif.login.LoginServiceImpl.login(LoginServiceImpl.java:176)
     at com.sap.aii.ib.clsif.login.LoginServiceImpl.login(LoginServiceImpl.java:121)
     at com.sap.aii.ib.clsif.login.LoginServiceImpl.login(LoginServiceImpl.java:109)
     at com.sap.aii.ib.gui.login.SplashLoginFrame$LoginController.doTrial(SplashLoginFrame.java:960)
     at com.sap.aii.ib.gui.login.SplashLoginFrame$LoginAction$1.run(SplashLoginFrame.java:832)
     at java.awt.event.InvocationEvent.dispatch(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor.dispatchEvent(Guitilities.java:319)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext.
     at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:488)
     at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
     at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
     at javax.naming.InitialContext.init(Unknown Source)
     at javax.naming.InitialContext.<init>(Unknown Source)
     at com.sap.aii.ib.clsif.login.EJBHomeFactory.getInitialContext(EJBHomeFactory.java:653)
     ... 15 more
Caused by: com.sap.engine.interfaces.cross.EXTstinationException: cannot establish connection with any of the available instances:
MYHOST.DOMAIN.EXT:50104 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 172.24.205.193 and port: 50104
     at com.sap.engine.interfaces.cross.EXTstination.getNextAvailableBroker(Destination.java:59)
     at com.sap.engine.interfaces.cross.EXTstination.getRemoteBroker(Destination.java:35)
     at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:352)
     ... 20 more
As you can see I call the IB via a pure hostname "MYHOST". But in the last step you can see the the FQDN "MYHOST.DOMAIN.EXT"was used. That brings me into trouble because these are different IP's. I can't reach the MYHOST.DOMAIN.EXT IP and that's why I can't login into the IB.
If I add an entry in my local host file for MYHOST.DOMAIN.EXT with the IP address I can reach all works fine but this solution is unacceptable.
The key question is why the IB uses this FQDN. I can't find any setting where this FQDN is used. I have checked the complete exchange profile, the sld and and and u2026. I always find only the pure hostname MYHOST.
Additionally I have to say that we have already a PI 7.1 system (DEV) whre I can use all tools. But this is a migrated system (from 3.0). I have only problems with that new installed empty system.

Thanks Barry. I've checked all connections. They all use the short name and all work.
Thanks Joel, but I think you get me wrong. That's why I will explain it a little bit better.
I can use the IB if I manipulate my own hosts file but this is in my eyes not the right way. As I have written I can use my PI dev system without that kind of manipulation.
My new PI system is at our computer centre. The PI machine has two network interface and I can use only one of these two. As you can see at the error log the full name points to 172.24.205.193 but I only can reach the 172.20.02.193 address. For this second IP we have an entry at our DNS server. The other one (FQDN) comes from the computer center DNS server. Of course I can overwrite it with an entry in my local hosts file but I think that isn't a good solution.
The key question is: Why the full qualified domain name "MYHOST.DOMAIN.EXT" is used instead of the short name.
I call the IB via the web page
http://MYHOST:50100/dir/start/index.jsp
And as you can se at the log the first call goes to this address. But then a second call goes to MYHOST.DOMAIN.EXT:50104. And I can find any setting (exchange profile and so on) where this full qualified domain name is specified.

Sda with com/sap/aii/utilxi/misc/api/BaseRuntimeException jar?

Hi,
does anybody know the location and name of the sda file which contains the class com/sap/aii/utilxi/misc/api/BaseRuntimeException?
Kind regards and thank you in advance,
Heiko

Hi Gopinath
Check this thread
An invalid XML character (Unicode: 0x1d) was found in the element
Kind regards
Javi

Com.sap.esi.uddi.sr.api.exceptions.SRExceptionerror code: null detail messa

Dear All,
When we try to publish a Web Service using Service Registry, following error appears, even though my user has the roles UDDI_Admin and SERVICE_REGISTRY_READ_WRITE
com.sap.esi.uddi.sr.api.exceptions.SRExceptionerror code: null detail message: com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.UDDIServerRemoteException: <Localization failed: ResourceBundle='com.sap.engine.services.webservices.wscm.validation.accessors.validation', ID='DISPOSITION_REPORT_UDDI_SERVER', Arguments: ['http://host:port/uddi/api/inquiry/', 'http://host:port/uddi/api/publish/', 'Fatal: A serious technical error has occurred while processing the request. ']> : Can't find bundle for base name com.sap.engine.services.webservices.wscm.validation.accessors.validation, locale en->com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.UDDIServerRemoteException: <Localization failed: ResourceBundle='com.sap.engine.services.webservices.wscm.validation.accessors.validation', ID='DISPOSITION_REPORT_UDDI_SERVER', Arguments: ['http://host:port/uddi/api/inquiry/', 'http://host:port/uddi/api/publish/', 'Fatal: A serious technical error has occurred while processing the request. ']> : Can't find bundle for base name com.sap.engine.services.webservices.wscm.validation.accessors.validation, locale en->com.sap.esi.uddi.server.proxy.depl.v3.DispositionReport
Note: We have also configured the UDDI destination as described in sap help @ http://help.sap.com/saphelp_nwpi71/helpdata/en/45/c1ea61a1194432e10000000a155369/frameset.htm
Thanks in Advance,
Immy.

Hi Rajesh,
Many thanks for your prompt reply, however this note 1267817 was already applied before posting message.
B/W I have observed that in spite of the error the service published multiple times in the registry (perhaps each try to publish resulted a entry in SR).
Really crazy error, any other suggestion??
Regards, Immy.

SAPinst error:- The java class is not found: com.sap.engine.offline.Offlin

Hi,
I am in the midst of Installing SOLMAN on RHEL5-ORACLE
Have installed IBM JDK version 1.4.2_10
During the CREATE SECURE STORE PHASE I am getting the following error:
sapinst_dev log file O/P
WARNING[E] 2008-06-09 18:04:43.225
           CJSlibModule::writeError_impl()
CJS-30050 Cannot create the secure store. SOLUTION: See output of log file SecureStoreCreate.log:
The java class is not found: com.sap.engine.offline.OfflineToolStart.
TRACE      2008-06-09 18:04:43.225 [iaxxejsbas.hpp:483]
           EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.
TRACE      2008-06-09 18:04:43.243 [syuxctask.cpp:1382]
           CSyTaskImpl::start(bool)
A child process has been started. Pid = 2529
TRACE      2008-06-09 18:04:43.281 [syuxctask.cpp:1382]
           CSyTaskImpl::start(bool)
A child process has been started. Pid = 2530
ERROR      2008-06-09 18:04:43.310 [sixxcstepexecute.cpp:951]
FCO-00011 The step createSecureStore with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_SecureStore|ind|ind|ind|ind|8|0|createSecureStore was executed with status ERROR .
TRACE      2008-06-09 18:04:43.317 [iaxxgenimp.cpp:752]
            CGuiEngineImp::showMessageBox
<html> <head> </head> <body> <p> An error occurred while processing service SAP Solution Manager 4.0 Support Release 4 > SAP Systems > Oracle > Central System > Central System. You may now </p> <ul> <li> choose <i>Retry</i> to repeat the current step. </li> <li> choose <i>View Log</i> to get more information about the error. </li> <li> stop the task and continue with it later. </li> </ul> <p> Log files are written to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS. </p> </body></html>
TRACE      2008-06-09 18:04:43.317 [iaxxgenimp.cpp:1255]
           CGuiEngineImp::acceptAnswerForBlockingRequest
Waiting for an answer from GUI
SAPINST.LOG file O/P
WARNING 2008-06-09 18:04:43.224
Execution of the command "/opt/IBMJava2-amd64-142/bin/java -classpath /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/launcher.jar -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.security.core.server.secstorefs.SecStoreFS /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/lib:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/exception.jar:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/logging.jar:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/tc_sec_secstorefs.jar create -s SMD -f /sapmnt/SMD/global/security/data/SecStore.properties -k /sapmnt/SMD/global/security/data/SecStore.key -enc -p XXXXXX" finished with return code 1. Output:
The java class is not found: com.sap.engine.offline.OfflineToolStart
WARNING[E] 2008-06-09 18:04:43.225
CJS-30050 Cannot create the secure store. SOLUTION: See output of log file SecureStoreCreate.log:
The java class is not found: com.sap.engine.offline.OfflineToolStart.
ERROR 2008-06-09 18:04:43.310
FCO-00011 The step createSecureStore with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_SecureStore|ind|ind|ind|ind|8|0|createSecureStore was executed with status ERROR .
SecurStoreCreate log O/P
The java class is not found: com.sap.engine.offline.OfflineToolStart
Pls suggest how to resolve this issue
Pls help to resolve this issue
Rgds,
Abhijeet

Hi All,
I Found the Solution.
The SAPinst tool was somehow not able to extracte the
J2EEINSTALL.SAR files from the JAVA Components DVD.
So I manually extracted the the file in the temporary install folder which the SAPinst creates in the /tmp filesystem (on LINUX by deafult) during the installation process.
The following command is used (I used this on Red Hat LINUX 5.2) to extract the J2EEINSTALL.SAR file:-
/sapmnt/SMD/exe/SAPCAR
-xvf /dump/SR4_Java_Components/D51033521/DATA_UNITS/JAVA_J2EE_OSINDEP_J2EE_INST/J2EEINSTALL.SAR
/sapmnt/SMD/exe/SAPCAR -->source directory of the file SAPCAR which is used to extarct CAR / SAR files on UNIX
/dump/SR4_Java_Components/D51033521/DATA_UNITS/JAVA_J2EE_OSINDEP_J2EE_INST/J2EEINSTALL.SAR--> destination dir. where the SAPinst tool will read and execute the file.
Rgds,
Abhijeet K

Jar for the package com.sap.engine.interfaces.messaging.api

Similar Messages

Maybe you are looking for