Where to find J2se Adapter

Hi Friends,
I guess the J2se adapter has to be installed or configured locally.Please correct me if iam wrong. Can anybody here tell me where i could find this software so that i could download it and use?..
Thanks in advance.
Regards,
Tamilarasan.

Hi Tamilarasan,
I think you can find it here:
https://websmp106.sap-ag.de/swdc
then this path:
- Support Packages and Patches
- - SAP NetWeaver
- - - SAP NETWEAVER
- - - - SAP NETWEAVER 04
- - - - Entry by Component
- - - - - XI Adapter Engine J2SE
- - - - - - XI CONNECTIVITY SE 3.0
- - - - - - - OS independent
Regards,
michal

Similar Messages

Where to find Power Adapter for iBook - 65W Model A1021?

Does anyone know where I can find a new power adapter for an older iBook?
Details:
Apple 65W
Portable Power Adapter
Model No. A1021
Cord seems to be fine, just need the brick.
Thank you!!
Teresa

The '12 PowerBook G4 1.5 GHz now uses the same power adapter as your iBook G4 does. The '12 PowerBook G4s originally shipped with the 45 power adapter brick Model A1022 but they started catching fire so Apple immediately recalled them. Just tell who you talk you on Apple's Support hotline that you want the power adapter that the '12 PowerBook G4 or iBook G4 uses.
Their Tech Support phone number is 1-800-274-2273.

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

Where to find a power adapter for PB G3 Wallstreet?

Hi,
could you please give me an idea where to find a power adapter for my PB G3 Wallstreet?
Location: Bangkok, Thailand or Munich, Germany.
Thanks in advance!
Greetings
bierstein

eBay is probably your best bet.
http://www.ebay.com/sch/sis.html?_kw=Apple+Powerbook+G3+Pismo+Wallstreet+Lombard +yo-Yo+power+cord+adapter+Model+M7332

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

"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,

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

How to get J2SE Adapter?

Hi all,
I am planning to use J2SE adapter with NW2004s 7.0. Where do I get the adapter?
Thanks,
Prabhu.

Download the latest patch from service.sap.com/patches
Deploy this on your XI with SDM.
Add the libraries servlet.jar and jms.jar to the folder tech_adapter (created during deployment).
That is all.
Stefan

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 / JMS Adapter

We need to connect to MQ Series 5.3 (Websphere MQ) from the XI (3.0 SP16) box.
1)Is J2SE adapter engine needs to be enabled/configured in order to use JMS Adapter? Cant we use J2EE JMSAdapter instead of J2SE JMS Adapter?
2) Where can I download the JMS Adapter libraries, for installation?
Ours is unix-based installation.
I have gone thru the thread
Installation and then Configuration of Plain J2se Adapter Engine
and the SAP Note: 747601 that talks about J2EE JMSAdapter MQSeries libraries.
TIA,
Steve

Hi Steve,
Check these ~
http://help.sap.com/saphelp_nw04/helpdata/en/6f/246b3de666930fe10000000a114084/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/03fd85cc-0201-0010-8ca4-a32a119a582d
J2Se adapter
Installation and then Configuration of Plain J2se Adapter Engine
Hope this helps,
Regards,
Moorthy

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

Where to find out with serial number to verify whether my dslr is genuine or not?

where to find out with serial number to verify whether my dslr is genuine or not?

Hey guys!
The following information can be found at https://www.usa.canon.com/cusa/consumer/standard_display/gray_market
Information on Parallel or "Gray Market" Products
Canon sells and supports Canon-brand consumer and professional products in the U.S. through Canon U.S.A., which distributes these products through its authorized dealers and distributors. Canon U.S.A. is the only authorized importer of these products in the U.S., and provides industry-leading customer service and support for them. Products distributed by Canon U.S.A. are "localized" to meet the needs of customers in the U.S. market and are engineered to comply with local safety regulations and governmental requirements. As such, these products come with different accessories, manuals, and warranties than the versions intended for sale in other global regions such as Asia. Any Canon-brand products which are imported and sold other than by this method are referred to as "parallel," or "Gray Market," products (collectively, "Gray Market Products").
Hazards and Difficulties Associated with "Gray Market" Products
Customers in the U.S. may find that Gray Market Products do not meet their expectations because they were not intended by Canon for sale in the U.S. In some cases, sellers of Gray Market Products may attempt to localize the products themselves by adding, changing or removing certain accessories from the products, which may result in the following:
including in product packaging illegal or counterfeit accessories, such as batteries, chargers, and ink tanks, which can cause injury and seriously damage your Canon product;
an incorrect power cord or adapter which was not provided, or quality checked, by Canon;
incorrect software or illegal copies of software which may not function;
poor photocopies of the original manual;
a fake Canon U.S. warranty, a warranty provided by a third party, or no warranty at all; and
a device with a serial number which cannot be registered with Canon in the U.S.
Customers should also be aware that Gray Market Products may not be eligible for:
coverage under a U.S. warranty;
U.S. promotions, including mail-in and instant rebates; and
technical support
If you are in doubt about a seller, or whether the products it sells are intended for the U.S., please visit http://usa.canon.com/authorizeddealers for a list of Canon U.S.A.'s Authorized Dealers. New and genuine Canon products intended for sale in the U.S. can only be purchased from Canon Authorized Dealers in the U.S. or from Canon U.S.A. directly.
To learn more about counterfeit products, please visit http://usa.canon.com/aboutcounterfeits to view important information.

Find the adapter that triggers

I have to modify a code, all I know is the method that is triggering from logs
Eg: com.labtest.operation.ModifyOperation.addorremove:
But I am unable to find which adapter is the one which is using this method. I have like more than 200 adapters.
Can we find out exactly which adapter or process task or event handler is triggering this method?

There is a column in adp table containing the class details which is stored as BLOB.
This query works in OIM 10g. I did not try this in 11g
SELECT *
FROM adp
WHERE dbms_lob.instr(adp_class,utl_raw.cast_to_raw('com.labtest.operation.ModifyOperation'))>0
This will retrun the adapters which are using that particular class. Add till class name and put in this query to try any other class usage in adapter also.
Edited by: Durgaprasad on Apr 15, 2013 8:46 PM

Where to find J2se Adapter

Similar Messages

Maybe you are looking for