Installation and then Configuration of Plain J2se Adapter Engine

[Former Member]

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

[Former Member]

Hi Amol,

I want to see the AdapterEngine Screen. But the AdapterEngine URL is not working. What could be the reason behind that? Moreover how and where do we set the class path for JMS Adapter?

Regards

[Former Member]

If you want to see the Adapter engine screen for the plain J2SE adapter engine, then

http://<hostname>:8200/

is the url for it. The default user and password available after installation is

User : <b>SAP</b>

Password : <b>init</b>

Secondly, you can set the CLASSPATH variable at the OS level or for a perticular JVM instance.So if you are working on Windows, open System Properties>Advanced Tab>Environment variables and append the CLASSPATH variable with entries for Jar files for your JMS provider. on unix offcourse <b>export</b> and set the values or put it in the user profile.

[Former Member]

Hi Amol,

Thanks for quick response.When we type this URL, we are getting an error message that "page cannot be displayed".Can u guide us on why this is happening and what we need to do?

Regd. the class path,

what should be the variable name?Can u send me the exact path?

Regards

[Former Member]

have you started the adapterengine?

in the <b>tech_adapter</b> directory you will find script <b>run_adapter</b>. you will need to start the adapter engine with this.

Regd. the class path,-->

The variable name is

<b>CLASSPATH</b>

for classpath setting examples check

http://java.sun.com/j2se/1.3/docs/tooldocs/win32/classpath.html

[Former Member]

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

<b>"ERROR CALLING THE RESTART ADAPTER"</b>

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

1. JMS-Adapter Configurarion

#

1. This Configuration is a sample for a JMS sender channel (inbound, sends to XI IS)

#

1. *************************************************************************************************************

2. Set XI message protocol version. This sample is designed for XI 3.0

version=30

#

1. JMS message receiver class

classname=com.sap.aii.messaging.adapter.ModuleJMS2Transport

#

1. set if a transacted JMS Session should be used (default: true)

#JMSSession.sessionTransacted=false

#

1. 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

#

1. set the Message Formats you want to process (Formats only needed if they can not be evaluated at runtime)

#

1. 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

1. *************************************************************************************************************

3. uncomment and adjust parameters for Transformation Type (Binding of JMS-Transport Message),

4. insert your class here for an individual binding between JMS and Transport Message

#

1. uncomment the following line for using Bindings that belong to Tunneling

#transformClass=com.sap.aii.messaging.adapter.trans.JMSTunneling

1. uncomment the following line for using Bindings that belong to Single Payload Binding

transformClass=com.sap.aii.messaging.adapter.trans.JMSSinglePayloadBinding

1. *************************************************************************************************************

#

1. ID Garbage Collector: For EO(IO) handling XI adapters store the JMS/XI message ID's in the ID logger

2. Uncomment the following lines and change the default values if you recognized "out of memory" problems due to

3. very large ..\tech_adapter\Data\*_ID.dat files which will be kept in the memory as well

4. eoExpirationAfterDays is the period of keeping the message ID in days. Afterwards the message ID might be used again

5. garbageCollectorInterval is the period in milliseconds when the ID garbage collector is started. It will however only

6. be started if messages are exchanged otherwise ID logs won't be created anyway

7. eoExpirationAfterDays=365

8. garbageCollectorInterval=86400000

#

1. *************************************************************************************************************

<b>#

1. the following parameters are used in some Bindings that belong to Single Payload Binding needing XMBHeader Information

2. uncomment and adjust parameters according your requirements. Please note, that the party identfier needs not to be

3. 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

#</b> *************************************************************************************************************

<b>#

1. 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

#</b> *************************************************************************************************************

#

1. URL of file adapter if a loopback JMS to File should be configured

2. XI.TargetURL=//localhost:8210/file/receiver

1. *************************************************************************************************************

<b># uncomment the following settings if needed (independent on JMS provider)

JMS.QueueConnectionFactoryImpl.user=xisuper

JMS.QueueConnectionFactoryImpl.password=xxx

#</b>

1. uncomment and adjust parameters for loading JMS administrated objects via JNDI

#

1. 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

1. set the Lookup Names

#JMS.JNDILookupNameQueueConnectionFactory=jmsfactory/default/joetest

#JMS.JNDILookupNameQueue=jmsQueues/default/sapDemoQueue

1. *************************************************************************************************************

#

1. uncomment and adjust parameters for loading JMS administrated objects from filesystem ***

#JMS.FileNameQueueConnectionFactory=SAPQueueConnectionFactory.ser

#JMS.FileNameQueue=SAPQueue.ser

1. *************************************************************************************************************

3. 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

1. *************************************************************************************************************

<b># 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}

#</b> *************************************************************************************************************

#

1. 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,

[stefan_grube]

Hi Sathia,

The XI parameters should be:

XI.TargetURL=http://bwxi:<b>8000</b>/sap/xi/engine?type=entry

XI.User=XIAF

XI.Password=XIPASS

XI.Client=<XIClient>

Is the user XIAF available?

Regards

Stefan

[Former Member]

Hi Stefan,

Thanks a lot. We dont have XIAF user. Where do i need to enter these parameters?Is this for refreshing the cache in Integration server?

Regards

Sathya

[stefan_grube]

These parameters are used for send the XI message from the adapter to the Integration Server.

You can use XIAPPLUSER or XIAFUSER for this purpose.

Regards

Stefan

[Former Member]

1. Have you taken care of the steps specifically mentioned in the section <b>"Additionally for the JMS adapter"</b> before installing the JMS adapter?

2. Did you check the status of the adapter if it is configured / installed correctly at the URL

http://hostname:8200/. It clearly shows a red / green light indicating the status of the adapter.

Regards,

Amol