Adapter engine on a J2EE dialog instance?

Can you install an adapter engine on a J2EE dialog instance, or by nature if you add DI's to the central adapter engine they already have adapters?
Thanks

hay Jeremy,
2 instances = 2 adapter engine.
(you can also look at engine adapter problem after I start dialog instance)
Happy trails,
Uri.

Similar Messages

Siteminder authentication on j2ee Dialog Instances only but not on C.I

I am doing an Siteminder external authentication implementation on SAP
Enterprise Portal 6.40 SP16.I have a configuration that want somehow to
validate.
The issue is that the J2EE Dialog Instances should be protected by SM
Agent (they are the load-balanced nodes with the Apache web agent) but
the Central Instance (which will run on a separate node) protected just
with the default basic authentication supported by SAP and not with the
SM Agent. The idea is to be able to access the CI without going through
the Front Web Instances for troubleshooting purposes.
Can we support them on this & in what form of configuration?
I appreciate your comments on this.
Thanks
Tagore

ok I will try to add BasicPasswordLoginModule and check it out .after that as you said when I access url http://server:50000/irj -> it should directly go to portal with default authentication (not siteminder).
I'm still wondering without customizing authscheme.xml how the siteminder is doing authentication as per your scenario explained in ur previous mail.
we have customized the in httpd.conf file in apache server like below..
<VirtualHost server:80>
 ServerName xxxxxx
Alias /siteminderagent/pwcgi/ /usr/netegrity/webagent/pw/
 <Directory /usr/netegrity/webagent/pw/>
 Options Indexes MultiViews ExecCGI
 AllowOverride None
 Order allow,deny
 Allow from all
 </Directory>
xxxxxx
xxxxx
 ProxyPass /irj/ http://server:50000/irj/
 ProxyPassReverse /irj/ http://server:50000/irj/
</VirtualHost>
APACHE deafult port 80 will listen ur portal url access http://server/irj -> pass this resource request to webagent and check if or not resource proteced in siteminder policy server and does authentication .Once its autheticatated sitmeinder provide user id in the form header to j2ee.
if you try to access the portal by giving following url http://server:50000/irj will not work .
could you tell me the
Note: in our scenario whe have installed both webserver (IBM HTTP APACHE 6.X)and web agent & ERP AGENT & PORTAL SERVER installed on same box.
Can you send me doc how you custmozed ur webserver for proxy & reverse proxy to my e-mail id :[email protected]
anyhow may I know your e-mail id ?
Thanks
Tagore

Uninstall J2ee Dialog instance on UNIX environment

HI Everyone,
I am trying to uninstall J2ee Engingine Dialog instance. I saw the procedure on the install document and it talks about deleting the files manually and also i have this not 871523 which says removing dialog instance from database after uninstallation.
I am searching for unistall tool. uninstsap script in Unix. Can someone guide me where i can find it. I am using Was 640 sp 12. Thanks for your help in advance.
Regards
Harish

You should have an Unix user for each version Why do you mean that?
You can have all oracle home with the same user.
$ id -Gn
dba ...
$ export ORACLE_HOME=/u01/app/oracle/product/7.3.4.0
$ export ORACLE_SID=DB1
$ svrmgrl
connect internal
startup$ export ORACLE_HOME=/u01/app/oracle/product/8-9-10
$ export ORACLE_SID=DB2
$ sqlplus "/ as sysdba"
startup$

Decentralized/Standalone XI Adapter Engine in same SID as Central AE

For reasons of splitting functionality, we want to setup separate XI adapter engines (AE) so that we can "pin" certain communication channels to specific AE.
On top of the "Central" AE (installed in /usr/sap/<SID>/DVEBMGS39), I have now installed a second ABAP/J2EE dialog instance (in /usr/sap/<SID>/D89).
All the Java components and services are visibile in VisualAdmin.
D89 shows up in SLD, and the J2EE SLD Data Supplier in D89 works.
However, there seems to be no "separation" of the 2 instances of the AE:
In RWB, component monitoring, there are no entries under "Non Central Adapter Engine" (although it is visible as a second node in Adapter Monitoring/MDT)
In IB/DIRECTORY, only the "Integration Server" is visible as an "Adapter Engine" in the communication channels
In the SLD, the class "HTTP Service Port: Basic URLs of Adapter Engine on <hostname>" only shows 1 URL (pointing to D89 and not to the "central" DVEBMGS39l).
To me it seems the 2 J2EE instances (within the same SID) behave as 1 (just like if we added another server1 to the same J2EE instance).
I think the main problem is within the data of the SLD. Does the separate "Adapter Engine" need to be registred manually (for example by creating an additionale instance of the CIM class "SAP_XIAdapterFramework" ?
System has been restarted many times.
Has anybody setup a separate adapter engine this way ?
Thanks for your help
Kind regards,
Jan Van Achte

Dear Jan
did you find a solution for your problem ? i got the same problem and did still not find a solution in sapnet.
regards peter

Architecture question on adapter engine?

What is the difference between running a decentral adapter engine and just having J2EE dialog instances?
Is using a decentral adapter engine a viable method of load balancing?
Does anyone have an SAP recommended architecture for load balancing with XI, or practical experience with this?
Thanks
Jeremy Baker

Jeremy,
J2EE dialog instances:
This is used for load balancing.
Decentral AE -load balancing:
I would say, Decentral AE is not for load balancing, please correct me if i'm wrong. Load balancing is the term if the server is down then the processes will be routed to the other servers in order to continue the process without interruption. Am I right, if yes Decentral AE is not for load balancing.
The min diff btw Central AE and Decentral AE is Central AE will be default once u installed XI. But Decentral AE is installed based on you landscape reqmt. So if you install Decentral AE , then you can route your messages to Central as well as Decentral AE.
To be much clear, see i'm confguring File-XI-File scenario , in the adapters I can choose either Central/Decentral AE. So that the work load on particular AE will be less. Hence in the above scenario if you chosse Central AE, if its down it will not take Decentral AE to process the message.
I hope it clears your doubt.
SAP XI Architecture & load balancing:https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/c3d9d710-0d01-0010-7486-9a51ab92b927
Best Regards,
raj.

Non Central adapter engine error

Hi All, Here is my Scenario: Trying implement /configure Non-central adapter engine hosted separate (J2EE) server. This will be connected to XI server(Integration engine and SLD) from where messages are sent/received. When I try to post message from XI to Non_central adapter engine following is the message u201CThe requested protocol u201CXIu201D is currently unavailableu201D Then I realized there is a problem in Non-central adapter engine configuration, which will be connected to SLD and Integration engine. I can see technical system and business system in SLD for Non-central adapter engine. Following is the findings in NWA of same host where non-central adapter engine. 1) I see all J2EE services are running 2) Application u201Ccom.sap.aii.adapter.soap.libu201D is no started and status is u201Cfailed to startu201D. Later I tried to restart and following are the 4 error messages in sequence from trace file. a) Message: Access to XI AF MS resource failed. Date: 2010-07-02 Time: 22:05:15:273 Category: com.sap.aii.adapter.soap.ra.SPIManagedConnectionFactory Location: com.sap.aii.adapter.soap.ra.SPIManagedConnectionFactory.SPIManagedConnectionFactory() Application: Thread: Deploy Start Application Thread Data Source: j2ee\cluster\server0\log\defaultTrace_00.trc B) [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/com.sap.aii.adapter.soap.lib]. [EXCEPTION] com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/com.sap.aii.adapter.soap.lib]. at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:619) at com.sap.engine.services.deploy.server.application.StartTransaction.rollbackPart(StartTransaction.java:653) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:506) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483) at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180) at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340) at com.sap.engine.frame.core.thread.Task.run(Task.java:73) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274) Caused by: com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";. at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122) at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502) ... 8 more Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound. at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375) C) Cannot bind "com.sap.aii.adapter.soap.lib";. [EXCEPTION] com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";. at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122) at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483) at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180) at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340) at com.sap.engine.frame.core.thread.Task.run(Task.java:73) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274) Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound. at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375) d) Global operation [startApp] over [application] [sap.com/com.sap.aii.adapter.soap.lib] finished with errors for [16]ms on server [4796750 >>> without warnings << >> Errors <<< 1). Cannot bind "com.sap.aii.adapter.soap.lib";. -> Object with name com.sap.aii.adapter.soap.lib is already bound. 2). com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";. at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122) at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483) at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180) at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340) at com.sap.engine.frame.core.thread.Task.run(Task.java:73) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274) Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound. at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375) Any of you have seen this kind of problem. Thanks Sam Edited by: sam robert on Jul 2, 2010 10:24 PM

Hi Sam,
1- What is your PI version?
2- Do you use a High Availability system?
3- Can you describe your scenario?
From the 503 error, here is a generic description:
The error message 503 Service unavailable Application stopped! is displayed.
Description:The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
Possible Tips: Because of J2EE application com.sap.aii.af.ms.app not active
u2022 Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine
u2022 The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
u2022 Refer SAP Note 803145,807000,791655
Regards,
Caio Cagnani

Polling adapters with additiona dialog instances?

Hi,
I have a question regarding the behavior of polling adapters, i.e. FTP adapter, when you install additional dialog instances for the central AE.
If the Central AE runs in two cluster nodes what is the behavior of a ftp sending adapter? I guess the adapter runs in both instances (RWB tells me that) but does both adapter instances poll the same ftp catalog for the same files at the same time? Is this a problem, i.e. is there a chance of picking up the same file in both instances?
//Johan

I encountered the same problem and found the following workaround:
1. Create a copy of the table without the collection type column.
2. Go through the Database Adapter Wizard and finish it normally.
3. Next, modify the created Dataabse Adapter but now select the original table with the collection type column.
4. You should now be able to finish the wizard without any problems.

J2EE Engine cannot be started. SAP CRM EHP1 Dialog Instance Installation

Hi All,
During Installation of a DI on a Linux host, I encounterd a problem. An error occured during " start dialog instance". The ABAP enginee is started successfully where as the JAVA Enginee cant be started. During investigation I found from the log directory
..j2ee/cluster/server0/log as stated below ..
#1.#0050569F663E001E0000000C0000054F0004803004D18B3F#1266843634469#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_64##0#0#Error#1#/System/Server#Java###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
[EXCEPTION]
#1#com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: null
 ume.db.connection_pool_type=SAP/BC_UME
 ume.db.connection_pool.j2ee.xatransactions_used=false
 ume.db.connection_pool.j2ee.is_unicode=false
 ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
 at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
 at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
 at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
 at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:83)
 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:109)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: null
 ume.db.connection_pool_type=SAP/BC_UME
 ume.db.connection_pool.j2ee.xatransactions_used=false
 ume.db.connection_pool.j2ee.is_unicode=false
 ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
 at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:887)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:440)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
 at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
 at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
 ... 6 more
#1.#0050569F663E001E0000000E0000054F0004803004D18C49#1266843634469#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_64##0#0#Fatal#1#/System/Server/Critical#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
I checked with the env variable and parameter, it all looks good. If anybody finds the same issue please suggest ....
Thanks in Advance.
Regards,
Shashi

There is a troubleshooting topic for this on the Help Portal.
See http://help.sap.com/saphelp_nw70ehp1/helpdata/en/20/361941edd5ef23e10000000a155106/frameset.htm.
-Michael

J2ee Adapter engine installation error

Hi All,
I am installing XI with NW07. I had an ERP2005 server here with ABAP only. I installed Java Add In to it with usage type PI.
Now I tried to install J2ee adapter engine. It showed if i want to run a new installation or continue the old one.
I tried to install installation of J2ee adapter engine from a new directory.
It is stuck in between. I choose it as a MCOD to existing DB.
I can see a new instance for this in MMC and it is up and running.
But the old java instance is not running. None of the Proceses of Old Java instance (dispatcher, server0 and SDM) are not running. Did I do something wrong?
My JVM_BOOTSTRAP.OUT says this:-
Exception occurred:
com.sap.engine.frame.core.configuration.NameNotFoundException: A configuration with the path "cluster_data/dispatcher/ID4065200" does not exist.
at com.sap.engine.core.configuration.impl.ConfigurationDataCacheAllImpl.getSubConfiguration(ConfigurationDataCacheAllImpl.java:107)
at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getSubConfiguration(ReadAccessConfiguration.java:715)
at com.sap.engine.bootstrap.Synchronizer.getConfiguration(Synchronizer.java:426)
at com.sap.engine.bootstrap.Synchronizer.getElementType(Synchronizer.java:72)
at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:420)
at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Exception occurred:
com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:422)
at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
== Caused by: ==----
com.sap.engine.bootstrap.SynchronizationException: No such Dialog Instance (ID4065200) in the database! Check database consistency or local Bootstrap properties!
at com.sap.engine.bootstrap.Synchronizer.getElementType(Synchronizer.java:75)
at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:420)
at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Bootstrap module> Problem occurred while performing synchronization.
My dev_jcontrol.b00 shows:-
JControlStartJLaunch: program = C:\usr\sap\IDE\DVEBMGS00\exe\jlaunch.exe
-> arg00 = C:\usr\sap\IDE\DVEBMGS00\exe\jlaunch.exe
-> arg01 = pf=C:\usr\sap\IDE\SYS\profile\IDE_DVEBMGS00_sapides
-> arg02 = -DSAPINFO=IDE_00_bootstrap
-> arg03 = -nodeId=-1
-> arg04 = -file=C:\usr\sap\IDE\DVEBMGS00\j2ee\cluster\instance.properties
-> arg05 = -syncSem=JSTARTUP_WAIT_ON_5284
-> arg06 = -nodeName=bootstrap
-> arg07 = -jvmOutFile=C:\usr\sap\IDE\DVEBMGS00\work\jvm_bootstrap.out
-> arg08 = -stdOutFile=C:\usr\sap\IDE\DVEBMGS00\work\std_bootstrap.out
-> arg09 = -locOutFile=C:\usr\sap\IDE\DVEBMGS00\work\dev_bootstrap
-> arg10 = -mode=BOOTSTRAP
-> arg11 = pf=C:\usr\sap\IDE\SYS\profile\IDE_DVEBMGS00_sapides
-> arg12 = -DSAPSTART=1
-> arg13 = -DCONNECT_PORT=4740
-> arg14 = -DSAPSYSTEM=00
-> arg15 = -DSAPSYSTEMNAME=IDE
-> arg16 = -DSAPMYNAME=sapides_IDE_00
-> arg17 = -DSAPPROFILE=C:\usr\sap\IDE\SYS\profile\IDE_DVEBMGS00_sapides
-> arg18 = -DFRFC_FALLBACK=ON
-> arg19 = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;F:\oracle\IDE\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_06\bin;C:\j2sdk1.4.2_06\lib;C:\usr\sap\IDE\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_09\bin;C:\usr\sap\IDE\DVEBMGS00\j2ee\os_libs;F:\oracle\IDE\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_06\bin;C:\j2sdk1.4.2_06\lib;C:\usr\sap\IDE\SYS\exe\uc\NTI386
Thr 4232 Tue Sep 16 17:48:04 2008
Thr 4232 *** ERROR => invalid return code of process bootstrap (exitcode = 66) http://jstartxx.c 1642
Thr 4232 JControlExecuteBootstrap: error executing bootstrap node bootstrap (rc = 66)
Thr 4232 JControlCloseProgram: started (exitcode = 66)
Thr 4232 JControlCloseProgram: good bye... (exitcode = 66)
My DEV_BOOTSTRAP.B00 shows:-
Thr 5984 Tue Sep 16 17:48:02 2008
Thr 5984 JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
Thr 5608 Tue Sep 16 17:48:04 2008
Thr 5608 JLaunchIExitJava: exit hook is called (rc = 66)
Thr 5608 **********************************************************************
u2022
o
 ERROR => The Java VM terminated with a non-zero exit code.
 Please see SAP Note 943602 , section 'J2EE Engine exit codes'
 for additional information and trouble shooting.
Thr 5608 JLaunchCloseProgram: good bye (exitcode = 66)
I ran the prerequisite checks before starting the installation.
It shows everything ok except it told me to have a environmental variable as CPIC_MAX_CONV with the value 200 at least. And I did that.
All the other checks were ok.
All are on SAME OS and same machine.
I have J2EE Adapter Engine installation guide, but there is nothing for this in that
In Instance properties file for the old instance it is showing the instance ID which it is not able to find.
In the configtool of both the instances, the instance ID is same under cluster_data and this is of the newer instance
How did the instance ID and data got replaced in the configtool of old instance. I mean the new instance has its new directory or folder.
What Could be the problem?
Did I do anything wrong here?
Kindly help

Hi,
Check out the SNote 997510, " Note 997510 - Troubleshooting
J2EE Engine 6.40/7.0 Bootstrap Issues ".
I hope it will help you to drill more in to the problem
Rgds
Radhakrishna D S

Decentral J2EE Adapter Engine

I am trying to install a Decentral J2EE Adapter Engine.
Please could someone tell me whether, when defining ABAP UME, should I define the same users as were defined on my Central PI instance for Admin & Guest, or should I use the suffix of the users as I receive in the default values on the screen ?

Hi Mark,
have you tried this presentation?
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/03fd85cc-0201-0010-8ca4-a32a119a582d
Regards,
Michal

Installation of J2EE Adapter Engine with DB on different host

Hello all,
I don't know if this is the right thread, but hopefully it is.
I have got following assignment:
I have to install NW70 PI/XI J2EE Adapter Engine. The trouble is, that due to a CI and DB hosts politics it's necessary to have database on different host than the central instance is.
But unfortunatelly the "SAPINST" program and its choice of J2EE Adapter Engine installation doesn't offer the possibility to install the product (J2EE AE) as a distributed system. SAPINST simply installs J2EE AE on one host including database. I've not succeeded the find a work-around.
I got two ideas, but I would like to confirm them:
1) Instal full SAP Java AS as a distributed system. After proper installation and patching I would use a SDM tool and deploy all necessary components to get a J2EE Adapter Engine "like" system. The only problem is that I don't know exact difference between normal SAP Java AS and SAP J2EE Adapter Engine and I'm not sure where could I get all necessary .SAR files.
2) Make a installation of SAP J2EE Adapter Engine as SAPINST allows. After installation and pathing, shutdown the system and move database to desired host, change all settings and start SAP J2EE AE as a distributed system. Only thing I'm not sure about is, if the J2EE AE would run in such a landscape.
Could anyone help me to get out of this deadend ?
Thank you for your comments in advance. Rewards points granted.
Tomas

Hi Jitendra,
thank you for your effort.
Maybe the question is more to Oracle forum part, because I don't think, that I would be able to do the installation as I described in point 1) (distributed JAVA AS and manuall deploying of AE components).
Probably the SAPINST is built up in this way, because in most cases it's needed to install J2EE AE on side of the other integrated system and there is one special machine dedicated to it.
If this is true and J2EE AE is really "normal JAVA AS" with some more functionality, I think the installation can be done as I described in point 2) - to install the J2EE AE locally, then shut it down and move the database to different host as required.
Anybody with different idea ?
Thank you
Regards
Tomas

Moving the database of SAP J2EE Adapter Engine on another host

Hello all,
I'd like to ask SAP/Oracle experts if there is any obstacle, why would not be able to move Oracle database of SAP J2EE Adapter Engine on other/different host after the installation.
As I describe int he thread [Installation of J2EE Adapter Engine with DB on different host|Installation of J2EE Adapter Engine with DB on different host;, the SAPINST program doesn't offer the possibility to install J2EE Adapter Engine with DB on other host than the central instance.
Only thing I'm not sure about is if this is done by any purpose for some database requirement, or it's simply not there.
SAP J2EE AE is normal JAVA AS with some more functionalities and is also installed within SAP PI/XI installation, which can run in "distributed model" system.
What do you think ?
Thank you for your opinion in advance.
Regards
Tomas

No opinion anyone ?
Tom

Guide for J2EE Adapter Engine on WAS 6.40 with XI 3.0

Hi all,
we are currently struggling with our AE. We are going to migrate from Xi 2.0 to XI 3.0, we run into problems while configuring our old J2SE AE (for which I have found a good PDF document on the SAP Service Marketplace).
Now we would like to test/configure the J2EE AE on XI 3.0.
But I cant find any guide for this on the SAP Service Marketplace. Does anyone know where to find this?
Thanks
Nesimi Buelbuel

Hi Nesimi,
There is a webinar replay of "Troubleshooting the J2EE Adapter Engine" at
https://www.sdn.sap.com/sdn/webinar.sdn?res=/irj/servlet/prt/portal/prtroot/com.sap.sdn.wcm.compound.docs//library/uuid/47a9a361-0301-0010-d39a-dd40d34b2e9d
Also make sure you check these links:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/events/webinars/configuring a local adapter engine.pdf
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/3.0/configuration guide - sap xi 3.0.pdf
Regards,
Sridhar

Error in Local J2EE Adapter Engine

Hi All,
We configured the J2ee Adapter engine and did the design and Configuration part also.but while testing the scenario it's giving error in SXMB_MONI as
*<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
*- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.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=;TP=;FS=BS_LAE;TS=BS_LAE;AN=MI_PPS_IB;ANS=urn:pps.com;</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can anyone suggest me?
Thanks,
Kalyan.

Hi kalyan,
If the error still says that, "Failed to determine a receiver agreement for the given message" - could you please compare the Sender/Receiver party/service determined in the XI message header and that in the Receiver Agreement in ID? Also please check the same for the Receiver Interface and Namespace. receiver agreement not found means any of these values doesn't match. If these look fine.............can you provide us with few more extra information...........like at which pipeline step in MONI you getting the error - the message hasn't yet reach Adapter Engine. So I don't think it's a problem in AE.
Regards,
Suddha

Installation of J2ee Adapter engine

Hi All,
As per my understanding in order to install J2ee Adapter engine, First we need to install Java System and later we install J2ee Adapter Engine.
Please correct me if am wrong.
Thanks,
Kalyan.

Hi Prateek,
Thanks for ur reply,
We ahve a J2ee engine in EP server. If i want to configure a Local J2ee engine in that.Do i need to install a separate J2ee adapter engine on already existed J2EE (EP)server. Or can i do directly Configuration in Visual Admin of the existed J2EE server to connect my PI system.
My doubt is J2ee adapter engine already exists in J2ee engine of the WAS or is that a separate installation i need to do even i have tha J2EE engine.
Please clarify my doubt.
Thanks,
Kalyan.

Adapter engine on a J2EE dialog instance?

Similar Messages

Maybe you are looking for