Decentralized J2se adapter issue

Dear Gems,
My J2se adapter is configured to pick a file and archive to a different folder.My current issue is
Adapter pics the file posts to Integration server and while archiving it creates 0kb file with the below error.
This is not happening all the time. can any one guess?
Log:
Oct 14, 2010 1:42:30 PM ...i.messaging.adapter.File2XMBProcessor [Thread[nterface,5,main]] Error: Confirmation failed: Moving sent file 'sample file path.xml' to archive failed
java.io.FileNotFoundException: Sample file path.xml (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:135) at com.sap.aii.messaging.adapter.File2XMBProcessor.archiveFile(ModuleFile2XMB.java:2123) at com.sap.aii.messaging.adapter.File2XMBProcessor.processFileAccess(ModuleFile2XMB.java:1928)at com.sap.aii.messaging.adapter.File2XMBProcessor.run(ModuleFile2XMB.java:1009) at java.lang.Thread.run(Thread.java:811)
Thanks
Prabhakar Teegavarapu

Hello Prabhakar,
This problem is solved in a patch.
Please read this SAP note:
1492379 - Archived file in FTP Sender Communication Channel is empty
This note may also be helpfull, even though the description of it doesn't match your issue.
SAP note 1225693.
Enjoy the weekend!
Jorge Eidelwein

Similar Messages

J2RE + Windows + J2SE Adapter Engine = Dump Xmx128m

Hi,
I want to use a decentralized J2SE Adapter Engine in order to data to XI.
When I install it on a Windows 2000 Professional, AE running is good and all are perfect... But when I install it on a Windows Server 2003, I have the following dump when I use the file "run_adapter.bat":
"-Xmx128m: illegal argument"
Here is the instruction when my tool uses for its running :
java -Xmx128m -classpath aii_msg_adapter.jar;aii_msg_runtime.jar;httpclient.jar;aii_af_trace.jar;aii_rfcadapter.jar;pmi.jar;exception.jar;jperflib.jar;guidgenerator.jar;aii_utilxi_misc.jar;aii_util_cimaccess.jar;sapxmltoolkit.jar;logging.jar;lcrclient.jar;tc_sec_core.jar;tc_sec_api.jar;jms.jar;servlet.jar;jarm.jar;%CLASSPATH%; com.sap.aii.messaging.adapter.AdapterImpl
Notes:
1. J2RE is j2re-1_4_2_06-windows-i586-p.exe)
2. I have replace 128 by 256 or 512, but it's the same issue.
So,
1. Anybody could explain why I have that with Windows Server 2003 ?
2. is it a problem with a Java Virtual Machine ?
3. Must I do something inside Windows : Environment variable, register key or other ?
Any helps are welcome.
Mickael

No. (neither PATH or JAVA_HOME, or J2EE_HOME)
What folder must I precise in this variable :
C:\Program Files\Java\j2re1.4.2_06\javaws ?
or
C:\Program Files\Java\j2re1.4.2_06\bin ?
Regards.
Mickael

J2SE adapter PI 7.1 issue with XML to flat conversion and namespace length

Dear reader,
We are facing an issue with J2SE Adapter PI7.1 for a number of flows.
The flow requirements:
[1] Namespace length for interfaces is up to 100 characters
[2] The XML message must be converted to Flat on the adapter channel
Our PI system is at patch level 7 and we implement J2SE adapter on patch level 7 as well.
We found that the J2SE adapter on patch level 7 does not support long namespaces [1] (as it should since this is an PI 7.1 j2SE adapter) but no issues where found with the XML to flat conversion [2].
Experimenting with J2SE adapter on patch level 6 we found the long namespaces [1] are supported however an issue is found with the XML to flat conversion [2] as stated in SAP note 1335527.
An SAP Customer Message is raised on this issue however your input is highly appricated!
With Kind Regards,
Harald Kastelijn
Edited by: Harald Kastelijn on Mar 6, 2010 9:17 AM
Edited by: Harald Kastelijn on Mar 6, 2010 9:19 AM

We found that the J2SE adapter on patch level 7 does not support long namespaces [1] (as it should since this is an PI 7.1
j2SE adapter) but no issues where found with the XML to flat conversion [2]
I think the restriction of namespace length still remains in design time (IR).....the same however has been extended in configuration and runtime...this SAP note has some information: https://service.sap.com/sap/support/notes/870809

Standalone (J2SE) adapter - axis SOAP adapter - issue duplicate messages

All,
Perhaps you can help me. I've setup a scenario where an standalone (J2SE) adapter sends a file to SAP XI channel, configured on the central adapter engine, of type SOAP configured to use Axis servlet.
The connection is setup and the standalone adapter channel logs thre response from the SOAP channel which reads HTTP error 500, indicating a duplicate message.
SAP has identified this problem and proposes in the FAQ for Axis (note 1039369) to set on the SOAP channel module CallSapAdapter property ignoreDuplicate to true in the module processor.
I've implemented this as suggested however found the problem persists. I'm still receiving an HTTP 500 error.
Your help is much appreciated solving this problem.
Thanks
Harald

As there was a bugfix recently, make sure that you have installed the latest patch.
If this does not work, open an OSS ticket for this issue.
Stefan

Filename in J2SE Adapter with Variable Substitution

Hello,
Within the J2EE receiver fileadapter (and ftp) from SP13 it is possible to compose the target filename and directory based on the payload of a message using variable substitution.
I wonder if it is also possible to use variable substitution with the J2SE fileadapter. For this it is not documented but i thougth that the same java libraries are used for the J2EE an J2SE file-adapters.
Aybody??
Really Nobody??
Message was edited by: Emile Hermans

Hello,
the J2SE Adapter does not support variable subsition. Therefore we created our own class which gets called from the main SAP XI class "XMB2FileProcessor.class" wich is in the jar "aii_msg_adapter.jar". In your own class you can do what ever you need to chane the file name. In the configuration you can set your own parameter to search the payload for a string you want to replace. We also had to come up with our own timestamp, e.g. file2005-11-10 which SAP does not let you do, only the full timestamp is possible.
One other nice thing is that you can develop our JAVA class local and test it with your local J2SE Adapter Engine on you PC before you deploy it.
Steps to do:
1. JAD the SAP class
2. Put a call in the SAP class
3. Compile the class
4. Put the class back in the archive
5. Create your own class
6. Create a jar file for it
7. Put the jar file in the tech_adapter directory
8. Change the run_adapter start cmd to include your jar file
It works great, the only issue is if you patch the J2SE engine you have to do step 1 to 4 again but that should it very easy to do.
Cheers
Stefan

How to go for Advance selction for source file in J2SE adapter

Hi all,
I am doing a file to file scenario using J2SE adapter.I have to pick file from two different directory we can easily achieve it in J2EE adapter using advance selection of source file but how to proceed in case of J2SE plain adapter.Please guide me with your knowledge.
Regards,
saurabh

This is not possible. You need different adapters, but you can use the same interface and namespace, so there should be no issue.
Regards
Stefan

"Performance" problems with the File adapter on Plain J2SE Adapter Engine

Hi,
At the moment I'm on a customer side to solve some XI issues for a few days. One of the issues is the performance of the Plain J2SE Adapter Engine, using the file adapter to transfer XML messages(already XI message format) from the legacy system to the Integration Engine. The File adapter has to deal with "large" XML messages(max at the moment is 65 Mb) and the engine fails with the following error when transferring the big XML file: "ERROR: Finished sending to Integration Engine with error "java.lang.OutOfMemoryError". Skip confirmation and quit this loop".
As far I got the information from the customer the memory use of the Plain adapter engine is set to 512Mb. This is maybe to low. But I don't know where to look for this, I only have the adapter web interface in front of me, no access to the OS it self via for example remote connection.
On the Integration Engine I know there is the ability to split large message with the file adapter(File Content Conversion), but I don't know this for the Plain Adapter Engine. Is there a possibility to do this also on the Plain Adapter Engine?
Thanks in advance for any input.
Greetings,
Patrick

Hi Sameer,
Thanks for your answers.
On the first solution, yes that is possible, we first decided to see if the legacy system can do the splitting, before starting developing a Java program.
On the second solution, as far as I know is this solution possible on the Integration Engine. But we are facing the problems on the Plain J2SE Adapter Engine. I went trough that documentation(link:
http://help.sap.com/saphelp_nw04/helpdata/en/6f/246b3de666930fe10000000a114084/frameset.htm ), to look for I similiar solution in the Plain Adapter Engine. So my question is, is this possible with the Plain Adapter? And if so, what kind of parameters I need to use to achieve this.
Regards,
Patrick

Installation and then Configuration of Plain J2se Adapter Engine

Hi All,
Actually we want to use JMS Adapter for that we had installed Plain J2SE Adapter Engine but after installing and following the initial steps of Adapter.pdf we are not able to access the Adapter Engine through URL.We are using the URL http://<hostname>:8200/MessagingSystem/receive/AFW/XI
this URL is there in our SLD but we are not able to access the page.
So Please can somebody help me to resolve this issue.
Thanks & Regards
Sathya

Hi Amol,
I am trying to send read data from MQSeries using JMS adapter. We are successful in opening the Adapter Engine and the GUI. We have cofigured the adpter as follows. But when we try to restart the adapter to get the changes get saved we are getting the following error
"ERROR CALLING THE RESTART ADAPTER"
Also status is shown is yellow and version is shown as not set.
Where ever I have changed the configuration data I have shown it in bold
JMS-Adapter Configurarion
This Configuration is a sample for a JMS sender channel (inbound, sends to XI IS)
Set XI message protocol version. This sample is designed for XI 3.0
version=30
JMS message receiver class
classname=com.sap.aii.messaging.adapter.ModuleJMS2Transport
set if a transacted JMS Session should be used (default: true)
#JMSSession.sessionTransacted=false
set delay in milliseconds before processing next message after an error (default: 0)
errorDelay=10000
#set delay in milliseconds before trying to reestablish the JMS Connection after a connection error (default: -1 (do not try to reconnect))
#reconnectDelay=10000
set the Message Formats you want to process (Formats only needed if they can not be evaluated at runtime)
TransportMessage Type can be set to TransportMessage of XMBMessage. It is used for sending and receiving Transport and XMBMessages
#TransportMessage.type=TransportMessage
TransportMessage.type=XMBMessage
uncomment and adjust parameters for Transformation Type (Binding of JMS-Transport Message),
insert your class here for an individual binding between JMS and Transport Message
uncomment the following line for using Bindings that belong to Tunneling
#transformClass=com.sap.aii.messaging.adapter.trans.JMSTunneling
uncomment the following line for using Bindings that belong to Single Payload Binding
transformClass=com.sap.aii.messaging.adapter.trans.JMSSinglePayloadBinding
ID Garbage Collector: For EO(IO) handling XI adapters store the JMS/XI message ID's in the ID logger
Uncomment the following lines and change the default values if you recognized "out of memory" problems due to
very large ..\tech_adapter\Data\*_ID.dat files which will be kept in the memory as well
eoExpirationAfterDays is the period of keeping the message ID in days. Afterwards the message ID might be used again
garbageCollectorInterval is the period in milliseconds when the ID garbage collector is started. It will however only
be started if messages are exchanged otherwise ID logs won't be created anyway
eoExpirationAfterDays=365
garbageCollectorInterval=86400000
#
the following parameters are used in some Bindings that belong to Single Payload Binding needing XMBHeader Information
uncomment and adjust parameters according your requirements. Please note, that the party identfier needs not to be
configured in case of A2A scenarios.
#XI.SenderParty=Sender
XI.SenderService=MQSeries
#XI.ReceiverParty=Receiver
XI.ReceiverService=MTX
XI.InterfaceNamespace=http://xitest
XI.Interface=MI_Out_File
XI.TraceLevel=1
XI.LoggingLevel=1
XI.QualityOfService=EO
XI.QueueId=ABCD
XI.ContentType=text/xml
# *************************************************************************************************************
#
URL of XI IS to send the messages to
XI.TargetURL=http://bwxi:50000/sap/xi/engine?type=entry
XI.User=XIAF
XI.Password=XIPASS
# *************************************************************************************************************
URL of file adapter if a loopback JMS to File should be configured
XI.TargetURL=//localhost:8210/file/receiver
# uncomment the following settings if needed (independent on JMS provider)
JMS.QueueConnectionFactoryImpl.user=xisuper
JMS.QueueConnectionFactoryImpl.password=xxx
#
uncomment and adjust parameters for loading JMS administrated objects via JNDI
uncomment and adjust parameters if not the default context should be used
#JNDI.InitialContext.property.1=java.lang.String {javax.naming.Context.INITIAL_CONTEXT_FACTORY}, java.lang.String com.sap.engine.services.jndi.InitialContextFactoryImpl
#JNDI.InitialContext.property.2=java.lang.String {javax.naming.Context.PROVIDER_URL}, java.lang.String localhost:50004
#JNDI.InitialContext.property.3=java.lang.String {javax.naming.Context.SECURITY_PRINCIPAL}, java.lang.String Administrator
#JNDI.InitialContext.property.4=java.lang.String {javax.naming.Context.SECURITY_CREDENTIALS}, java.lang.String sap
set the Lookup Names
#JMS.JNDILookupNameQueueConnectionFactory=jmsfactory/default/joetest
#JMS.JNDILookupNameQueue=jmsQueues/default/sapDemoQueue
uncomment and adjust parameters for loading JMS administrated objects from filesystem ***
#JMS.FileNameQueueConnectionFactory=SAPQueueConnectionFactory.ser
#JMS.FileNameQueue=SAPQueue.ser
uncomment and adjust parameters for creating SonicMQ JMS administrated objects ***
JMS.QueueConnectionFactoryImpl.classname=progress.message.jclient.QueueConnectionFactory
JMS.QueueConnectionFactoryImpl.constructor=java.lang.String localhost:2506
JMS.QueueImpl.classname= progress.message.jclient.Queue
JMS.QueueImpl.constructor=java.lang.String SampleQ1
# uncomment and adjust parameters for creating MQSeries JMS administrated objects ***
JMS.QueueConnectionFactoryImpl.classname=com.ibm.mq.jms.MQQueueConnectionFactory
JMS.QueueConnectionFactoryImpl.method.setHostName=java.lang.String BWXI
JMS.QueueConnectionFactoryImpl.method.setChannel=java.lang.String JAVA.CHANNEL
JMS.QueueConnectionFactoryImpl.method.setTransportType=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_TP_CLIENT_MQ_TCPIP}
JMS.QueueConnectionFactoryImpl.method.setQueueManager=java.lang.String QM_BWXI
JMS.QueueImpl.classname= com.ibm.mq.jms.MQQueue
JMS.QueueImpl.constructor=java.lang.String postcard
JMS.QueueImpl.method.setTargetClient=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_CLIENT_NONJMS_MQ}
# *************************************************************************************************************
uncomment and adjust parameters for using a dispatcher ***
#Dispatcher.class=com.sap.aii.messaging.adapter.ConversionDispatcher
#Dispatcher.namespace=namespace1
#namespace1.ConversionDispatcher.logPayload=true
#namespace1.Service.1=Plain2XMLService
#namespace1.Plain2XMLService.class=com.sap.aii.messaging.adapter.Conversion
#namespace1.Plain2XMLService.xml.conversionType=SimplePlain2XML
#namespace1.Plain2XMLService.xml.processFieldNames=fromConfiguration
#namespace1.Plain2XMLService.xml.fieldNames=a,b,c
#namespace1.Plain2XMLService.xml.fieldSeparator=;
#namespace1.Service.2=XSLTService
#namespace1.XSLTService.class=com.sap.aii.messaging.adapter.XSLTConversion
#namespace1.XSLTService.XSLTConversion.XSLTFileName=Data/DemoConversion.xsl
Can you please help me in resolving the error.
Regards,

J2SE adapter upgrade to PI 7.1

Hi,
is there anything special that needs to be changed
when moving those local (J2SE) adpaters from 7.0 to 7.1 ?
anyone already moved those pretty, little, file configuration based devils ?
Thank you,
Regards,
Michal Krawczyk
http://mypigenie.com XI/PI FAQ

Hi Michal,
Unfortunately I dont have a PI 7.1 server to test.
Michal are you facing any issue when working J2SE Adapters with PI 7.1?
@Rajesh:
>I read some of the documents that J2SE adapters aresupported only in XI 3.0 to support XI 2.0 implementation customers
Though the document says it works for XI 3.0, it still works with PI 7.0 since the concept lies in posting the message to XI PIPELINE while sending from J2SE Adapter
and on the way back from XI to J2SE Adapter Engine using one of the configured working servlet in J2SE Adapter Engine.
Thanks,
- Gujjeti.

J2SE adapter engine and SSL testing

Hi there,
We are currently doing a B2B scenario whereby SAP XI sends a message to the J2SE adapter engine in the DMZ and then that sends the message via HTTPS / SSL to the receiving service....
In order to test that the HTTPS / certificate etc worked I wrote a small Java application and dialled out of the network. I inserted the DER file into my CACERTS file on my local machine using the keytool as a "trusted certificate". The Java application worked 100% and did the SSL handshake fine and POSTED the data fine as well......
Now I am no expert in the J2SE adapter engine but decided to try testing the same SSL connection using the J2SE adapter engine from my LOCAL machine with me dialled out onto the Internet.
I logged into the J2SE adapter engine and imported the same DER file into the engine (actually inserted into the "truststore.jks" file). I them went into the "Test Environment" of the J2SE adapter and have been trying to test.....
I have a few questions:
1. Do I have to use a P12 or PFX file for this sort of communication? Reason I ask is that with the Java application all I needed was the DER file?
2. In the full blown scenario do I have to have SSL configured between XI and the J2SE adapter engine as well? Or can that stay as HTTP?
My basic config for the test is roughly:
WS.targetURL=https://someserver:4433/soap/someInbox
WS.SOAPAction=CustomSoapAction
SSLauthentication=true
Do I really need the following two?
SSLcertificate=somecert.p12
SSLcertificatePassword=somepassword
From my logic all I should need if the DER file loaded into the J2SE adapter which I have done......
Has anyone done successfull SSL / HTTPS testing from the J2SE adapter engine using the "Test Environment"?
Any advise would be greatly appreciated
Kind regards
Lynton

Hi
Not a answer to your question but why use the J2SE adapter engine in the DMZ and why not the J2EE Decentral Adapter Engine?
Regards
Bhavesh

J2SE Adapter Installation error

Hi
I'm getting the following error when i try and start the J2SE Adapter service from windows services -
Error opening the Java Virtual Machine (Path: E:\Java\jre6\bin\client)
Its been an issue before when i had spaces in the path, but since then its worked, however now with a fresh install i get this error.
Thanks!

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

J2SE Adapter + Remote connection by XI PROXY

Hi,
1. When you use a decentralized Adapter Engine (called also J2SE Adapter Engine), you use the following URL address in order to start the Graphical User Interface (GUI) associated to A.E: http://localhost:8200/adapter.html
2. You also have the possibility to use directly your own IP address instead of "localhost"... Thus you could use something like that: http://999.88.77.666:8200/adapter.html (remote URL)
3. If you use another IP address than yours, then you have the possibility to have a remote connection to another AE installed on another workstation... GREAT !
BUT it's seems this tips is limited by a firewall action: I could only call "Target AE " if this tool is on the same network than mine... (cf. point (0) )
 Firewall
 ||
<======= Network 1 ==========> || <======= Network 2 =======>
 ||
(0) "My PC" ---> "Target AE" ||
 ||
(1) "My PC" ----------------->|| "Target AE"
 || T
(2) XI <---------------------+
 ||
 ||
(3) "My PC" || "Target AE"
 | || T
 | || |
 +-------> XI ----------------------+
 PROXY ? ||
 ||
<======= Network 1 ==========> || <======= Network 2 =======>
 ||
 Firewall
>> Exactly, my problem is the following one:
- I have 2 networks separated by a firewall
- This firewall is only openned between XI and the Target AE (cf. point (2) )
- When I use directly my tips from "My PC" to "Target AE", I cannot reached it(according to me it's because of Firewall)... (cf. point (1) )
THUS I would like to use the "openned door" between XI and "Target AE", in order to a have a complete remote connection from "My PC" to "Target AE" by passing across XI... (cf. point (3) )
Not especially by using a scenario or a BPM, but directly by using HTTP address and / or a PROXY on XI. This Proxy will be used to call directly the "Target AE" by specifying an URL: http://999.88.77.666:8200/adapter.html
>> Is it possible to define a PROXY on XI in order to do such a connection between "My PC" and "Target AE"?
Any help and any idea are welcome!
Regards.
Mickael

Hi Mickael,
Your Problem is more an Network Problem than an xi problem.
With a ABAP Proxy and a HTTP Request it maybe works when you develop something like a browser. You must send a HTTP GET Request to the Target.
Maybe you develop a J2EE application that is able to show the site in a iframe. But this i think is a redirict and will also block form your firewall.
The easyiest way is to call your admin and he open ther ports for your Plain J2SE Adapter Engine
Regards,
Robin

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

J2SE adapter engine monitoring.

Hi,
I have setup GRMG monitoring for a J2SE adapter engine in our landscape. I have set up a HTTP RFC destination in SM59. In the HTTP RFC destination, type H, I have specified the "Target Host" (FQHN) the "Service No." (8200 default J2SE installation port) and a "Path Prefix" (/rtc). The security is set to Basic and I have used a PIRWBUSER that I have setup on the J2SE Adapter Engine with role Administator. In the GRMG template I insert the RFC destination.
I have also inserted the ID, ESR, RWB, SLD and the Central Adapter framework of the PI system in the GRMG template, then deployed the template on the monitoring server. I am able to successfully monitor the other components except for the J2SE adapter.
I have to concede that when I test the RFC destination to the J2SE adapter it does not work. I think the J2SE adapter is up, as I can connect to the administrator. Even when I put the url ("host:port/rtc") for the J2SE adapter in my browser, it then request to login. After I have logged in, it gives a error "The Page can not be found".
It would be most appreciated if someone can shed some light on this issue.
Regards
Willie Hugo

FTS SAP Basis,
Thanks for that advice. However once I have set the "Accept cookies" to "Yes", and once again I do a "Connection Test", the result I get "ICM_HTTP_CONNECTION_FAILED". Also remember when I try to connect to the URL "http://host:8200/rtc", it requests a login, but then display "The page can not be displayed".
Any other suggestions are welcome.
Regards
Willie Hugo

J2SE Adapter Registration

I've tried to get an answer for this question long time ago, but no one ever answered.
How to register J2SE adapter with XI ?
I tried using SLDAccess service on J2SE adapter with no luck (with this J2SE Adapter Engine is registered in the SLD). My J2SE adapter was never available in the configuration means, in the communication channel ex: file adapter, for the adapter engine drop down all I have is Integration Server, my J2SE adapter was never listed there.
thanks
SKM

Tony,
You do not need FTP server to use file adapter. I've installed and configured a J2SE Adapter Engine on my laptop.
I was able to use sender adapter but not the receiver adapter. I've followed all kinds of documentation, asked Qs in the forum but never got any feed back.
After you install plain J2SE AE on your laptop, you have to configure SLDAccess service. Once it is connected to SLD, you can see the adapter engine name in the XI technical systems.
Then you can configure FileAdapters by copying the existing one. Go through the Adapter documention in the installed directory.
Hope this helps.
Regards
SKM

Decentralized J2se adapter issue

Similar Messages

Maybe you are looking for