Adapter Engine--ports

Hi
How and where to know whether AE is listening to certain port or not?

Hi
u need to configure port for AE that is for XI...normally AE doesn't listen to port..
The system on which AE is configured(J2EE engine)listens to the port...
we need to configure ports and those can be done from R/3 using transactions IDX1,IDX2.

Similar Messages

Default port for J2SE Adapter Engine?

Hello all,
what is the default port for J2SE Adapter Engine? How do I restart this adapter engine?
Regards,
N.S

Swamy,
8200 is the default port. Also go through this help of how to start and stop the J2SE Adapter Engine:
http://help.sap.com/saphelp_nw04/helpdata/en/12/5dd23aaad7b3408dde3c1577fda5b3/frameset.htm
---Satish

HTTPS port not activated on non-central Advanced Adapter Engine

Hello,
we have upgraded our non-central adapter engine from XI 3.0 to 7.1 EHP1.
Before, we were using port 58201 (5<InstanceID>01) for HTTPS and it was working fine. On the new system, the port 58201 isn't active, which I've checked with 'telnet <host> 58201'.
On XI 3.0, the port could be configured in the Visual Admin -> SSL Provider, but I don't find the corresponding setting in NWA.
I've already checked miscellaneous SAP notes (856597, 891877,...), HowTo-Guides and Blogs, but didn't find any hint...
Any idea, where I could edit the HTTPS port in NWA of the non-central adapter engine?
Thanks,
Juergen

Hello,
I didn't get access to ExchangeProfile over URL http://<host>:<port>/exchangeProfile and didn't find the settings in NWA.
Reason was the missing CryptoLibrary as discribed on http://help.sap.com/saphelp_nwpi711/helpdata/en/f1/2de3be0382df45a398d3f9fb86a36a/frameset.htm
Regards,
Juergen

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

Why I can see this messages only in the integration server?
>>>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

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

How to delete / cancel messages in PI adapter engine

Hello expert,
we have a scenario File (EOIO) --> PI --> ABAP. Today the file we received is big (>100mb), apparently PI can't handle it, and we got error
Transmitting the message to endpoint http://host:port/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException:
Error transmitting the message over HTTP. Reason: java.io.IOException: Error writing to server.
seems like PI adapter engine got problem while delivering the huge message to ABAP integration engine. In RWB message monitoring, the message is set to Error. Unfortunately the file has been picked up many times, thus the huge message is stuck in adpater engine. In RWB message monitoring, I can see the message listed many times and status is HOLDING because the previous message can not be delivered to Intergration engine. I want to delete/cancel all the messages, I tried in RWB message monitoring to cancell the messages, however after cancelling one message, it crashed the PI system and cause a reboot.
My question is; Is there some place in NWA (net weaver admin) to force all the messages to be deleted? (Because deleting/cancel in RWB message monitoring does not work because it causes system crash).
Thanks
Jayson

Hi Team,
I couldn't able to delete old message's from one of Q system, Persistence layer is 584 % filled, after triggering delete job(RSXMB_DELETE_MESSAGES) and Persistence layer has come to 384% and further I couldn't able to delete old messages.I executed program "
                                                                                                      RSXMB_CHECK_MSG_QUEUE" and manage to delete few entries.Could you please suggest how to reduce fill level to below 100%
Switch Procedure (for Persistence Tables) Deactivated
Number of Table Entries
3.185.992
Maximum Number of Table Entries
830.000
Current Fill Level in %
384
Threshold value for fill level for executing a switch run in %
60
Number of Logically Deleted Table Entries
0
Decline of Fill Level in % Following Deletion
384
Delete or archive processed XML messages
Job log overview for job:    SAP_BC_XMB_DELETE_001 / 06302000
Date       Time     Message text                                                                               Message class Message no. Message
13.03.2013 06:39:55 Job started                                                                                     00           516          S
13.03.2013 06:39:55 Step 001 started (program RSXMB_DELETE_MESSAGES, variant &0000000000034, user ID SAPBATCH)      00           550          S
13.03.2013 06:39:55 Value for parameters DELETION-RELATED_OBJECTS-ASYNC: 1                                        XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-RELATED_OBJECTS-ROWS: 100                                       XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-RELATED_OBJECTS-IDX5_DELAYED: 0                                 XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-ROWS_PER_LOOP-DELETE: 100                                       XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION-ASYNC: 007                                     XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION-SYNC: 007                                      XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_ERROR-SYNC: 007                                XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION-IDX5: 007                                      XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_UNIT-ASYNC: D                                  XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_UNIT-SYNC: D                                   XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_ERROR_UNIT-SYNC: D                             XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_UNIT-IDX5: D                                   XMS_ADM        375          S
13.03.2013 07:27:58 0 XML messages deleted                                                                        XMS_ADM        351          I
13.03.2013 07:27:59 Step 002 started (program RSXMB_TABLE_SWITCH, variant &0000000000034, user ID SAPBATCH)         00           550          S
13.03.2013 07:28:00 Job finished                                                                                    00           517          S

CPALookupException while sending a Test message to Adapter engine

Hello Experts,
I am getting following exception while sending a test message to Adapter engine through Runtime Workbench.
Error while sending message: com.sap.engine.interfaces.messaging.api.exception.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve outbound binding for the given P/S/A values: FP=<Configured Party>;TP=;FS=<Configured Communication component>;TS=;AN=<Configured Outbound Interface>;ANS=<Configured Namespace>
This scenario works fine when I submits the message through Integration engine. So ID configuration is perfect. Also cache contents are upto date.
Thanks in advance.
Regards
Rajeev

Error is clearly saying that it is unable to find receiver agreement for that particular interface.
Please check your receiver agreement for the interface.
If your receiver agreement is fine then do CPA cache refresh using following URL:-
http://<host>:<port>/CPACache/refresh?mode=full

Cache Refresh for Adapter Engine is not working

Hi,
our adaper engine is not working. At RTW no there are no channels visible and the button "Test Cache Connectivity" leads to a yellow icon for the adapter engine with the error text: "Attempt to fetch cache data from Integration Directory not yet started or still in process".
The error reason is at http://<j2ee host>:<port>/CPACache/history.jsp available: com.sap.aii.af.service.cpa.impl.exception.CPADirectoryCacheException: Couldn't open Directory URL (http://pixd1.digoff.no:55200/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.xd1.dat-dof-xi), due to: HTTP 403: Forbidden
The cache refreh request from adapter engine to directory gets an 403 error. What is strange: No problem, to execute that request in a browser, i get the right message, no fault.
I searched for notes or other threads, i could find only <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_xi/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d373531383536%7d">SAP note 751856</a> , but it is valid for XI 3.0; we are on PI 7.0.
I checked out:
- no user blocked
- all system users have standard authorisations
- reimport of SAP BASIS SWC
- SICF services for XI active
- destination INTEGRATION_DIRECTORY_HMI working
Any idea, how i can get the adapter engine working?
Regards,
Udo

Hi,
There are two ways to display the content of the CPA cache refresh.
1. The Cache-Update Content-XML
Document can be stored in the Adapter Framework database (J2EE schema) for further analysis. Here you have to set the property in the J2EE Visual Administrator tool.
To do so, proceed as follows:
=>J2EE-service SAP XI AF CPA Cache
=> set property trackCacheUpdateXML= true
=> You can now display the cache update XML with the alias CPACache
=> View Cache Update History
=> View Cache Update XML
2. The content of the cache refresh from the Integration Directory intothe CPA cache can be written to an XML file: Here you have to set the property inthe J2EE Visual Administrator tool:
=>J2EE-service SAP XI AF CPA Cache
=> set property J2EE service SAP XI AF CPA Cache cacheUpdateDebugFile = true
=> the CPA cache refresh XML file will be in the server(0) directory search for the following file names:
=> value of the property cacheUpdateDebugFile.deltaif you intend to see the delta refresh accordingly and the value of the property cacheUpdateDebugFile.full if
you intend to see the full cache refresh content
Note: After your analysis, do not forget to reset the properties value to false.
You can delete the XML cache-
refresh table: alias CPACache
=> View Cache Update History
=> Delete History
Also check out the user and its permission.
regards
Aashish Sinha
PS : Reward points if Helpful

Getting error in the adapter engine when sending a message

Hi,
I'm always getting this error in the adapter engine: Message processing failed. Cause: com.sap.aii.messaging.util.URI$MalformedURIException: no scheme
The comm channel ends up in error because of messages having the above error.
Could someone please help?
Thanks.
Mike

Mike.
Please check this links.
Check your adapter and restarted.
com.sap.aii.messaging.util.URI$MalformedURIException: invalid port number
Re: Prerequisites to setup configure mail scenario.
error in communication channel
Error :Receiver File Channel not Initialized

Non-central adapter engine not visable in integration builder

ls,
I have a pi system and a separate non-central adapter engine. After installing i did all the post actions including the following part:
5.13 Clearing the SLD Data Cache after Installing a Non-central Advanced Adapter Engine
When you have installed a non-central Advanced Adapter Engine, you need to manually clear the SLD Data Cache in the Integration Builder to make it visible and selectable in the communication channels.
Procedure
1.
After SAPinst has finished, open the Integration Builder of your PI system at http://<host>:<port>/dir/start/index.jspIntegration Directory and logon as a user with the ABAP role SAP_XI_CONFIGURATOR assigned.
2.
In the Integration Builder, choose Environment.
3.
From the drop-down list, choose Clear SLD Data Cache.
(as described in: Installation GuideAdapter Engine (Java EE) 7.1 Including Enhancement Package 1 on Windows: MS SQL ServerTarget)
However when creating a communication channel in the integration builder there is only the central adapter engine to choose in parameter tab screen.
I was hoping maybe some-one knows what else need to be done to make de non-central known as adapter engine.
thanks in advance
Peter

HI,
with user PIDIRUSER i was indeed able to refresh the af cache. Unfortunately without a positive
Under the runtime workbench (http://<host>:<port>0/rwb/index.jsp) tab sld registration i don't see the ae neither under non-central components. If i try to register i get:
Registration of Adapter Framework with SLD was successful
Registration of fix AF adapter services with the SLD was successful
Registration of dynamic CPA cache based AF adatper services with SLD was successful
but no AAE...although it is visible in the SLD under technical systems...

Shutdown of XI 3.0 Plain J2SE Adapter Engine.

How do I shutdown the XI 3.0 Plain J2SE Adapter Engine? Where should I go to do this?
Regards,
N.S

Hi N.S. -
If I recall correctly, you open a browser to http://<host>:8200 . 8200 is the default port. If not using the default port, you may need to investigate what that port is. Delivered initial user/pwd is sap/init.
There's a Shutdown Adapter Engine option once you get in. Of course, the j2se adapter engine must be running in order for you to do this.
Regards,
Jin

HTTP/S POST from J2SE adapter engine (NO SOAP)

Hi there,
We have a scenario at work where we have XI sending messages to the "lightweight" J2SE adapter engine in the DMZ....and from there the message is sent out to an HTTPS site that is obvioulsy outside of our network.
Currently I can see that the J2SE adapter engine support SOAP over HTTP/S......but how can I do a normal POST of the message NOT using SOAP to an external HTTP/S address?
I do not see any straight HTTP adapter in the J2SE adapter engine. I have a small java file that can connect and POST the message to the external website.
My question is how can I use this code easily in the J2SE adapter engine? I just want a simple HTTP
POST ...no SOAP.....
Is there some sort of EXIT or dispatcher that I can hook onto?
Any help or push in the right direction will be greatly appreciated
Regards
Lynton

Hi there,
You can see in the config file below that we did put it into the adapter config. It does not complain about the parameter BUT it still has the SOAP envelope / headers in the result message. Any ideas how we can get around this?
Thanks for the help
Lynton
# Bubble adapter java class
classname=com.sap.aii.messaging.adapter.ModuleBubble
# Sets the bubble module helper that can instantiate your bubble bag
Bubble.Helper=com.sap.aii.messaging.adapter.ModuleBubbleHelperXMBWSImpl
#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
# Below this line are the parameters specific to the ModuleBubbleHelperXMBWSImpl
#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
# The configuration of this helper class is divided in three parts. The first part,
# Part 0, specifies the common parameters. The second part, Part 1, specifies the
# adapter configuraton for Web-Service clients communicating with an XMB server.
# The third part, Part 2, specifies the configuration for XMB clients
# communicating with a WebService server. For sender or inbound adapters, Part 0
# and Part 1 must be configured. For receiver or outbound adapters, Part 0 and
# Part 2 must be configured.
# This is a sample configuration file for a SOAP Outbound/Receiver Adapter
###### Part 0 (FromWS and ToWS) : common part ######
# Keeps the XMB headers in web service messages
XMBWS.KeepHeaders=false
# Keeps the attachments in web service messages
XMBWS.KeepAttachments=false
# Encodes the xmb headers into a special HTTP header string x-xmb_ws_encoded
XMBWS.UseEncoded=false
# Encodes the value of x-xmb_ws_encoded (see UseEncoded) in the request query string
XMBWS.UseQueryString=false
# Uses the specified xml encoding for the soap envelope encoding
#XMBWS.XMLEncoding=iso-8859-1
*XMBWS.NOSOAP=true*
###### Part 1 (FromWS) : WS clients to XMB server ######
# This part is configured for SOAP Sender or SOAP Inbound-Adapter)
# It is left empty in this configuraton file.
###### Part 2 (ToWS): XMB clients to WS server ######
# This part is configured for SOAP Receiver or SOAP Outbound-Adapter.
# The target URL for the web service, to which the adapter sends web service messages.
XMBWS.TargetURL=https://localhost:443
# The port and path where the adapter waits for XMB messages from clients.
XMBWS.XMBPort=8015
XMBWS.XMBPath=/bt
XMBWS.SSLcertificate=somecert.p12
XMBWS.SSLcertificatePassword=hello
XMBWS.SSLauthentication=true
# The default SOAPAction HTTP request header to the web Service server
XMBWS.DefaultSOAPAction=xmbws
# END

Receiver File Adapter J2SE Adapter Engine

Hi,
We have configured a receiver file adapter on a J2SE adapter engine through the administrator page of the J2SE adapter.
XI.httpPort=8222
XI.httpService=/file/Receive
and the rest of the adapter parameters.
I have configured a channel in ID as XI receiver adapter.
host: "hostname"
Service: 8222
Path Prefix: /file/Receive
The messages in sxmb_moni fail to be delivered with "HTTP error 404 Resource not found."
Through a browser I am also not able to make a connection to this url:
"host":8222/file/Receive
Getting Http error "501".
Please can someone shed some light on this problem.
Regards
Willie Hugo

>Through a browser I am also not able to make a connection to this url:
>"host":8222/file/Receive
>Getting Http error "501".
This is ok. Since get method not implemeted for this service.
Since from XI you are getting this error "HTTP error 404 Resource not found", can you logon to XI server at OS level and do a telnet test to check if the port is working.
cmd> telnet
telnet> open <J2SEAdpaterEngineHostName (or) IPAddress> 8222

Problem: Plain J2SE Adapter Engine

Hello,
I have installed the Plain J2SE Adapter Engine.
On the Adpater Engine running a SOAP Adapter.
When i try to test the Adapter i become following error Message:
java.net.ConnectException: Connection refused: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(Unknown Source)
 at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
 at java.net.PlainSocketImpl.connect(Unknown Source)
 at java.net.Socket.connect(Unknown Source)
 at java.net.Socket.connect(Unknown Source)
 at java.net.Socket.<init>(Unknown Source)
 at java.net.Socket.<init>(Unknown Source)
 at com.sap.aii.messaging.net.ClientHttpImpl.call(ClientHttpImpl.java:146)
 at com.sap.aii.messaging.adapter.SinglePayloadClient.doPost(SinglePayloadClient.java:222)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.aii.messaging.adapter.Zone.service(ModuleGUIBrowserEngine.java:1073)
 at com.sap.aii.messaging.adapter.HTTPRequest.run(ModuleGUIBrowserEngine.java:371)
any idea?
Regards,
Robin

Hi Stefan,
SOAP Adapter module settings:
Bubble adapter java class
classname=com.sap.aii.messaging.adapter.ModuleBubble
This adapter instantiates a bubble bag for supporting
a xmb web service gateway. A bubble bag is a collection of Bubble
instances that form some processing chain of message objects.
Below parameter Bubble.Helper specifies the helper class that implements
the ModuleBubbleHelper interface. This class is used to instantiate
a bubble bag for this adapter.
Sets the bubble module helper that can instantiate your bubble bag
Bubble.Helper=com.sap.aii.messaging.adapter.ModuleBubbleHelperXMBWSImpl
#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
Below this line are the parameters specific to the ModuleBubbleHelperXMBWSImpl
#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
The configuration of this helper class is divided in two parts. The first part
specifies the adapter configuraton for Web-Service clients communicating with an
XMB server. The second part specifies the configuration for XMB clients
communicating with a WebService server. Either one or both parts can be configured
in a single configuration file.
Part 0 (FromWS and ToWS) : common part ######
Keeps the XMB headers in web service messages
XMBWS.KeepHeaders=true
Keeps the attachments in web service messages
XMBWS.KeepAttachments=false
Encodes the xmb headers into a special HTTP header string x-xmb_ws_encoded
XMBWS.UseEncoded=false
Part 1 (FromWS) : WS clients to XMB server ######
The target URL of XMB broker, to which the adapter sends XMB messages.
XMB.TargetURL=http://netweaver:8000/sap/xi/engine?type=entry
The port and path where the adapter waits for web service messages from clients.
XMBWS.WSPort=4444
XMBWS.WSPath=/soap/start
The following XMB attributes are used to fill default XMB messages.
XMB.SenderBusinessSystem=MOS_BS
XMB.SenderInterfaceNamespace=ns:moskau
XMB.SenderInterfaceName=MOSOut
XMB.QualityOfService=BE
now i have an other error message.
com.sap.aii.messaging.net.TransportException: HTTP 500 Internal Server Error
http-Response:
content-type: text/xml
content-length: 349
content-id: <[email protected]>
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Body><SOAP:Fault><faultcode>SOAP:Server</faultcode><faultstring>com.sap.aii.messaging.srt.BubbleException: Can't call the endpoint; Exception raised by com.sap.aii.messaging.net.TransportException: Content-Type not set</faultstring></SOAP:Fault></SOAP:Body></SOAP:Envelope>
 at com.sap.aii.messaging.net.ClientHttpImpl.call(ClientHttpImpl.java:337)
 at com.sap.aii.messaging.adapter.XMBTestClient.doPost(XMBTestClient.java:236)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.aii.messaging.adapter.Zone.service(ModuleGUIBrowserEngine.java:1073)
 at com.sap.aii.messaging.adapter.HTTPRequest.run(ModuleGUIBrowserEngine.java:371)

J2SE Adapter Engine Error

Hi everyone,
I am facing couple of issues with J2SE adapter engine.
1. First Issue
Config in SLDaccessor -
file adapter java class
classname=com.sap.aii.messaging.adapter.ModuleSLDaccessor
SLD.host=<HOST>
SLD.port=50xxx
SLD.user=user
SLD.password=pass
SLD.adapterEngineName=AdapterEngine
Config in Sender File Channel
file adapter java class
classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
version=30
mode=FILE2XMBWITHROWCONVERSION
XI.SLDConfiguration=SLDaccessor
#XI.TargetURL=http://<HOST>:<50xxx>/sap/xi/engine/?type=entry
XI.TargetURL=<fromSLD>
XI.QualityOfService=EO
XI.Client=001
<Other parameters like InterfaceName / FCC>
If I use XI.SLDConfiguration=SLDaccessor and XI.TargetURL=<fromSLD>, I get an error of HTTP 401 unauthorized.
If I ignore the SLDaccessor, the message is processed successfully.
Am I missing anything in the above configuration?
The user id user is having the roles of SAP_SLD_CONFIGURATOR and SAP_XI_APPL_SERV_USER.
2. Second Issue
In RWB -> Component Monitoring -> J2SE Adapter Engine, there is an error coming up - Unable to establish connection to "https://<LocalHost>:50001/rtc"
The port is wrong ... it should be 8200. My question is, from where to fix this?
Any help will be highly appreciated.
Thanks,
Neetesh

Hi Neetesh,
After copying tech_adapter on your local machine douple click on run_adapter.bat and then open internet explorer and enter http://l<ocalmachine_ip_address>:8200/adapter.html
After doing this you will get logon popup, enter user & password and configure the adapters.
Secondly you can see the port in SLDAPICUST if I am not mistaken. (not very sure)
Compare your configuration with below one
file adapter java class
classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
version=30
mode=FILE2XMB
Integration Engine address and document settings (example, see docu)
XI.TargetURL=http://<host>:8000/sap/xi/engine?type=entry
XI.User=testuser
XI.Password=pass123
XI.QualityOfService=EO
#XI.SenderParty=
XI.SenderService=LocalSystem
#XI.ReceiverParty=
XI.ReceiverService=LocalSystem
XI.Interface=IM_J2SE
XI.InterfaceNamespace=http://abc.com/j2se/test
##File Adapter specific parameters (example, see docu)
file.type=BIN
#file.type=TXT
file.encoding=UTF-8
file.sourceDir=c:/sender
file.sourceFilename=sender1.xml
#file.processingMode=test
file.processingMode=delete
#file.processingMode=archiveWithTimeStamp
#file.archiveDir=./temp_archive
#file.retryInterval=20
file.pollInterval=30
Regards,
Sarvesh

Adapter Engine--ports

Similar Messages

Maybe you are looking for