Local and central intergration Engine?

Hi Team
Please let me know the difference between local and central integration engine. what are the usages of the same with one example each. plesae clarify.
thanks
Raj

Hey,
When you install XI / PI default central adapter is installed For load balacing we install de-central adapter.
https://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/03fd85cc-0201-0010-8ca4-a32a119a582d&overridelayout=true
Cheers
Agasthuri

Similar Messages

Question about Local and Central Services Registry

Hi guru,
We are using CE7.2 and have deployed some BPM DC to it.
After deployment, we can see the web service (we made to start the process) from the local SR.
Now we want to build a central SR on aonther machine (AS Java + SLD + SR) and re-point the previous CE7.2's service reg to this central SR. We did it by running the configuration wizard.
I GUESS after the change, the web service in new BPM DC deployment will be automatically published to the CENTRAL SR, rather than the LOCAL, but it didn't happen, am I wrong ?
I'm wondering what kind of situation will cause automatically registration ?
Please shed some light
thanks

Tim,
They will be fully documented in the 11g XML DB Developer's guide.
The documentation is still covered by the beta NDA, so I can't show it to you.
I can describe them, though.
They will work through the HTTP server that is part of XML DB, similar to the way that you can currently access data as XML:
http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14259/xdb15dbu.htm#i1025534
Or the way you can call stored procedures through the PL/SQL geteway.
http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14251/adfns_web.htm#ADFNS015
If there is an 11g XE, I expect native web services would work because they don't depend on Java.
They applied for a patent on it:
http://www.freshpatents.com/Techniques-for-automatically-exposing-as-web-services-procedures-and-functions-stored-in-a-database-dt20060622ptan20060136351.php
Doug

Understanding Flexconnect - Local vs Central Switching, and WLC failover scenario ??

Hello Experts
We have one WLC 5508 in Building1, few 2700 Series AP in Building1, and one 1252AG in Building2. The LAN subnet is same for both Buildings connected via a dark fiber.
My requirement is to have Central Switching in Building1 since WLC is located locally, and Local Switching in Building2 to avoid inter-building traffic, for both Buildings we already one VLAN/IP Subnet. (Both Buildings access resources from a central Datacenter which hosts all the servers.)
Questions:
1. Is the above scenario possible using single SSID ? My understanding is that one WLAN+SSID can't have both Local and Central switching enabled.
2. In Flexconnect Central Switching mode, during WLC failure, does the switching change to Local switching automatically ?
3. When I choose Local Switching for a specific WLAN, does it Locally switch always , or does it Locally switch only when WLC is down ?
4. We want to use Microsoft PEAP using AD User Authentication. When Local Authentication is enabled on WLC, I understand that when WLC fails (and RADIUS Server is still reachable), can we still have the AP directly contact RADIUS server as a direct client and provide 802.1X Microsoft PEAP authentication. Guess this is Primary Backup Radius Server configuration. Is this understanding correct ?
Thanks.

Hi
The LAN subnet is same for both Buildings connected via a dark fiber.
If this is the case there is no need of FlexConnet, as you have enough bandwidth & same L2 extended in those two buildings. Typically FlexConnect is for branch deployment where WAN link bandwidth is a concern.
Anyway if you want to do this & here is the answer for your specific queries.
1. Is the above scenario possible using single SSID ? My understanding is that one WLAN+SSID can't have both Local and Central switching enabled.
You can have both local switching & central switching available for a given SSID. Only FlexConnect mode AP will do Local switching & all Local mode AP will do central switching, though both using the same SSID.
2. In Flexconnect Central Switching mode, during WLC failure, does the switching change to Local switching automatically ?
No, if it is central switching SSID, when WLC is not available client won't able to join this SSID. It is not fall back to Local switching.
3. When I choose Local Switching for a specific WLAN, does it Locally switch always , or does it Locally switch only when WLC is down ?
This is applicable only to FlexConnect mode APs & it always do local switching if that configured. If WLC is not reachable AP will go on "standalone mode" & still do local switching.
4. We want to use Microsoft PEAP using AD User Authentication. When Local Authentication is enabled on WLC, I understand that when WLC fails (and RADIUS Server is still reachable), can we still have the AP directly contact RADIUS server as a direct client and provide 802.1X Microsoft PEAP authentication. Guess this is Primary Backup Radius Server configuration. Is this understanding correct ?
Yes, when this option configured & WLC is not reachable (but RADIUS is reachable) then AP will act as Authenticator & pass radius messages to Auth Server directly.
This is a very good Ciscolive presentation you should see as it describe lots of these features & which WLC codes they introduced.
BRKEWN-2016 - Architecting Network for Branch Offices with Cisco Unified Wireless
HTH
Rasika
**** Pls rate all useful responses ****

Diffrence Between Local IE And Central IE

Hi All,
What is the difference between the local Integration Engine And the Central Integration Engine ???
Please Explain me
Regards
Vamsi

The systems on which SAP WAS is installed has Integration Engine as one of its components. Now for PI/XI also WAS is a must. Therefore PI/XI also has an Integration Engine called as Integration Server.
Now talking in terms of PI/XI, Integration Server has Adapter Engine, Integration engine (for pipeline steps) and Business Process Engine. This Integration Server is the central Integration Engine.
The Integration Engine of other systems is termed as local Integration Engine
Regards,
Prateek

Not Working-central web-authentication with a switch and Identity Service Engine

on the followup the document "Configuration example : central web-authentication with a switch and Identity Service Engine" by Nicolas Darchis, since the redirection on the switch is not working, i'm asking for your help...
I'm using ISE Version : 1.0.4.573 and WS-C2960-24PC-L w/software 12.2(55)SE1 and image C2960-LANBASEK9-M for the access.
The interface configuration looks like this:
interface FastEthernet0/24
switchport access vlan 6
switchport mode access
switchport voice vlan 20
ip access-group webauth in
authentication event fail action next-method
authentication event server dead action authorize
authentication event server alive action reinitialize
authentication order mab
authentication priority mab
authentication port-control auto
authentication periodic
authentication timer reauthenticate server
authentication violation restrict
mab
spanning-tree portfast
end
The ACL's
Extended IP access list webauth
    10 permit ip any any
Extended IP access list redirect
    10 deny ip any host 172.22.2.38
    20 permit tcp any any eq www
    30 permit tcp any any eq 443
The ISE side configuration I follow it step by step...
When I conect the XP client, e see the following Autenthication session...
swlx0x0x#show authentication sessions interface fastEthernet 0/24
           Interface: FastEthernet0/24
          MAC Address: 0015.c549.5c99
           IP Address: 172.22.3.184
            User-Name: 00-15-C5-49-5C-99
               Status: Authz Success
               Domain: DATA
       Oper host mode: single-host
     Oper control dir: both
        Authorized By: Authentication Server
           Vlan Group: N/A
     URL Redirect ACL: redirect
         URL Redirect: https://ISE-ip:8443/guestportal/gateway?sessionId=AC16011F000000510B44FBD2&action=cwa
      Session timeout: N/A
         Idle timeout: N/A
    Common Session ID: AC16011F000000490AC1A9E2
      Acct Session ID: 0x00000077
               Handle: 0xB7000049
Runnable methods list:
       Method   State
       mab      Authc Success
But there is no redirection, and I get the the following message on switch console:
756005: Mar 28 11:40:30: epm-redirect:IP=172.22.3.184: No redirection policy for this host
756006: Mar 28 11:40:30: epm-redirect:IDB=FastEthernet0/24: In epm_host_ingress_traffic_qualify ...
I have to mention I'm using an http proxy on port 8080...
Any Ideas on what is going wrong?
Regards
Nuno

OK, so I upgraded the IOS to version
SW Version: 12.2(55)SE5, SW Image: C2960-LANBASEK9-M
I tweak with ACL's to the following:
Extended IP access list redirect
    10 permit ip any any (13 matches)
and created a DACL that is downloaded along with the authentication
Extended IP access list xACSACLx-IP-redirect-4f743d58 (per-user)
    10 permit ip any any
I can see the epm session
swlx0x0x#show epm session ip 172.22.3.74
     Admission feature: DOT1X
     ACS ACL: xACSACLx-IP-redirect-4f743d58
     URL Redirect ACL: redirect
     URL Redirect: https://ISE-ip:8443/guestportal/gateway?sessionId=AC16011F000000510B44FBD2&action=cwa
And authentication
swlx0x0x#show authentication sessions interface fastEthernet 0/24
     Interface: FastEthernet0/24
     MAC Address: 0015.c549.5c99
     IP Address: 172.22.3.74
     User-Name: 00-15-C5-49-5C-99
     Status: Authz Success
     Domain: DATA
     Oper host mode: multi-auth
     Oper control dir: both
     Authorized By: Authentication Server
     Vlan Group: N/A
     ACS ACL: xACSACLx-IP-redirect-4f743d58
     URL Redirect ACL: redirect
     URL Redirect: https://ISE-ip:8443/guestportal/gateway?sessionId=AC16011F000000510B44FBD2&action=cwa
     Session timeout: N/A
     Idle timeout: N/A
     Common Session ID: AC16011F000000160042BD98
     Acct Session ID: 0x0000001B
     Handle: 0x90000016
     Runnable methods list:
     Method   State
     mab      Authc Success
on the logging, I get the following messages...
017857: Mar 29 11:27:04: epm-redirect:IDB=FastEthernet0/24: In epm_host_ingress_traffic_qualify ...
017858: Mar 29 11:27:04: epm-redirect:epm_redirect_cache_gen_hash: IP=172.22.3.74 Hash=271
017859: Mar 29 11:27:04: epm-redirect:IP=172.22.3.74: CacheEntryGet Success
017860: Mar 29 11:27:04: epm-redirect:IP=172.22.3.74: Ingress packet on [idb= FastEthernet0/24] matched with [acl=redirect]
017861: Mar 29 11:27:04: epm-redirect:IDB=FastEthernet0/24: Enqueue the packet with if_input=FastEthernet0/24
017862: Mar 29 11:27:04: epm-redirect:IDB=FastEthernet0/24: In epm_host_ingress_traffic_process ...
017863: Mar 29 11:27:04: epm-redirect:IDB=FastEthernet0/24: Not an HTTP(s) packet
What I'm I missing?

Same wlan both locally switched and centrally switched

Scenario:
1 virtual wireless controller
50 access points, some of them some local to the controller (same site), other on remote sites, all in flexconnect mode.
Is there a way for a wlan to be locally switched for a group of ap's, essentialy those local to the controller, and centrally switched for other groups of ap's, in fact those placed on remote sites?
I've tried configuring flexconnect groups, and ap groups, but no luck, I've found no way to override the globally configured flag "flexconnec local switching".
I've also tried to create two identical wlans, one locally switched and the second globally switched, but the wlc refuses to activate the second one since it has the same ssid of the first one.
Regards,
Massimo.

Since you have vWLC all AP needs to be in FlexConnect mode (If you got a normal WLC you can keep HQ AP in local mode & Remote AP in Flex mode to achieve this)
I think in your case you have to either choose "Central Switching" or "local switching" for your APs.
Regards
Rasika
**** Pls rate all useful responses ****

Unable to contact non-central adapter engine

Hi All
I install the local J2EE Adapter Engine, and configure the connection in exchange profile and set the SLD Data Supplier in Visual Admin
and i could see my local adapter engine in adapter configuration.
But in Runtime work bench ->component monitor->non-central adapter engine-> error:
Ping Status: status_image HTTP request failed. Error code: "401". Error message: "Unauthorized [http://host:port/AdapterFramework/rtc]"
how could i solve this?
thanks in advance

Hi , Lawrence
There was a solution to this problem?
Thanks
Leôncio

Problems with Non central Adapter Engine

Hi Friends,
We installed an non central Adapter engine. Then as per the documents we made entry for connection in exchange profile.Then in visual administrator in SLD data supplier i provided the required credentials for connecting to my XI server.
XILDUSER and XISUPER these users and passwords were provided for connection.
From visual admin we manually send the trigger to hit the SLD and make an entry there.It was successful in visual admin.
But after doing all this successfully we are not able to see the Local i.e non-central adapter in our XI SLD as well as in RWB.
can anyone throw some light on it.
Thanks,
yomesh

Hi Friends ,
I have solved this problem. The password provided for XILDUSER was wrong thats why it was not able to register in the SLD .also the differents user has to be created in Security provider service in visual administrator.
then it worked finr.
Yomesh

Missing central adapter engine??

Hello @all,
somehow in my xi(sp14) i only have a decentral adapter engine, but its not decentral. in the
http://server:port/mdt/amtServlet all adapter are correct and also working (tested some szenarios).
in the rwb component monitoring i would like to have my adapter listed as "central" and not as "decentral".
anyone with an idea?:-)
Thank you

Lasya,
For DeCentral Installation, only the Adapter Engine based on Adapter Framework is available.
Adapter Framework offers Messaging, Queuing etc.
BPE and Mapping Runtime will be avaibale in the Central Intergration Server. BPE is based on the ABAP Stack.
Integration Engine Pipeline services like mapping are available only for Integration Engines configured as Integration Servers.
Have your BASIS team to check how the installation was done.

SR1 De-Centralized Adapter Engine Install

Folks, I have installed Netweaver Developer Workplace SR1 sucessfully on a local machine XP Professional. When I attempt to install the De-Centralized Adapter Engine (also SR1) on the same machine it seems to corrupt the local AS Java server and it can no longer start correctly. I have tried this on two seperate machines with the same result. Has anyone completed this sucessfully? The Adapter Engine install guide is pretty thin and assumes that sapinst will complete with no errors.
Also the Adapter Engine does not seem to like XP, and wants to be installed on a Win Server2003, is this necessary?
I am beginning to wonder if the AS Java server that comes with Netweaver Developer Workplace is not a full install rendering the Adapter Engine install incompatible. Thoughts?

There really aren't any special requirements for NWDS7.0, other than WinXP and 2gb of RAM. They specify the most recent JDK, but other than that it is the same as the last version. Only it is a much larger memory hog over the last version. You definetly need 2gb of RAM.
Looking at the Adapter Engine install guide again, I don't believe that it is meant to be installed on a local pc for unit testing. If this is true it really stinks because you will not be able to test your Java proxies until the first Server in your landscape.

PI 7.11 Central Adapter Engine is not started

Hi Experts,
After active objects list, in the central adapter engine: ache update not yet started.
Looking for this error, is possible that is the RFC INTEGRATION_DIRECTORY_HMI because responde 403 forbidden,
Did you have any tips?
Thank you!
Bruno

Are you sure supplied credentials are valid for PIISUSER?
1) HTTP response does not contain a valid XML root tag or Error 'HTTP status code 400 Bad Request' while executing HTTP request (calling method 'get_status')
The error 'HTTP response does not contain a valid XML root tag' occurs when path prefix of the destination is '/dir/hmi_cache_refresh_service/ext'.
The error 'Error 'HTTP status code 400 Bad Request' while executing HTTP request (calling method 'get_status')' when path prefix is '/dir/CacheRefresh'.
Solution: Go to transaction sm59 and open destination of type 'H' INTEGRATION_DIRECTORY_HMI. Select "Connection Test". The connection test should return HTTP response 200.
Now go to "Logon & Security" tab and ensure that username and password are stored in the system. Fixing credentials should fix the problem.
Note: Credentials cannot be tested via "Connection Test" tool. If used credentials are wrong, the server simply returns login html page (using HTTP response code 200). As the login html page is not a valid cache refresh xml document, an error is shown in sxi_cache.

Help!Cache status of object for Central Adapter Engine is incorrect

this problem cconfused me several days!
version:PI 7.1
after i activate the communication channel, the cache not update for central adapter engine
problem: in cache status overview, the update for central adapter engine not yet started, but notification is ok.
the update for integration server and mapping run time are all correct.
then when i display wsdl for sender agreement(SOAP sender), show message:Cache status of object abcd123 for Central Adapter Engine is incorrect
if i ignore this message, error message popup:dapter Engine af.xid.sapittest for communication channel abcd123 not registered in SLD
who can help me solve this problem.
thank you in advance.

Hi cheng,
Kindly check if you have set theparameter 'com.sap.aii.connect.integrationserver.sld.name' in your
Exchange Profile, since it's not set by default. Open note #1278563 and follow the procedures.
And you may check the following notes:
#1031321 - Self-Registration of Adapter Engine and RWB fails
#1334053 - No automatic PI 7.10 SLD Registration (Here you'll see the note 764176 which you have already applied and also the note #1117249).
In RWB, is the adapter Engine "red light"? If yes, what is the specific error?
Regards,
Caio Cagnani

Non-central adapter engine not visable in integration builder

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

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

Configuration of JMS Adapter in Central Adapter Engine

Hi all,
I have configured Sender JMS Adapter in Central Adapter Engine with the following parameters:
Adapter type : JMS
Transport Protocol : WebSphere MQ (non-jms)
Message Protocol : JMS1.x
Adapter Engine : Integration Server
Queue Connection Factory java class :Com.ibm.mq.jms.MQQueueConnectionFactory
Queue java class : com.ibm.mq.jms.MQQueue
ipadd : localhost
port : 1414
Queue Manager name : TEST.QMGR
Channel Name : CH1
JMS Queue : LQ
CCSID : 437
Protocol : TCP/IP
JMS-compliant : WebSphere MQ(non-jms)
JMS Queue user : MUSR_MQADMIN
Mapping of message : Entire Message = JMS Payload
But the status is red with an error message Sender Details : NULL
Could you please tell me what went wrong?
Regards
Sathya

Hi,
Make sure that Websphere MQ server is running.
If u r comfortable with java, you can even write a Java code to acces the server and check if the JMS server is working fine. Some times there will be sample applications provided by Websphere MQ itself.
Once the java program works then it will be easy to debug the error over here.
Regards,
P.Venkat

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

Local and central intergration Engine?

Similar Messages

Maybe you are looking for