Integration Directory changes not reaching Runtime

Dear all,
    I changed a few values on one of the communication channels but is not getting reflected on the runtime. Looks like a cache refresh issue, so I did a 'cache connectivity test' in RWB.
‘Integration server – JAVA’ and ‘Integration Server – ABAP’ and ‘Central adapter engine’ are the three entries present under integration directory.
The first two are fine and are in green but the third one(Central adapter engine) is in yellow. The details show
--Cache notification from Integration Directory received successfully (in green)
--Attempt to fetch cache data from Integration Directory not yet started or still in process(yellow)
Tried to refresh the result but it is still in yellow.
So as per the 'how to handle cache' guide, I checked the RFC destination INTEGRATION_DIRECTORY_HMI and it seems to be fine. Also I have checked http://<host name>:<port>/dir/hmidiag/ext?method=info and that seems to be working fine as well…
Please can you suggest what could be going wrong or what else need to be checked
Cheers
danus

Danus,
Just check this document and follow the steps given:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1a69ea11-0d01-0010-fa80-b47a79301290
Regards,
---Satish

Similar Messages

  • Integration directory is not getting displayed..

    Hi Gurus,
    Our developers are facing an issue here- they are not able to view the Integration Directory (ID) window with their own ID's as well as PISUPER. They are able to view the same instance ID from a different server. But I'm able to view to ID from my machine. When they key in their login credentials in the integration directory, after which a window will be opened and that they cannot see it.The process and the application keeps running in the windows task manager. Is this sort of a display problem or something?
    Any thoughts would be appreciated!
    Regards,
    Sriram

    Hi,
    Also make sure they are have JDK1.5 and not any other version installed. Try to delete your temporary Java files on your PCs and do the re-initialization Raj mentioned, and try again. You can also enable Java console from control panel to see where you're getting stuck.
    Regards,
    Gökhan

  • Create folder in Integration Directory - Can not be uniquely addressed

    Hi experts,
    I have the following issue. When creating a folder in Integration Directory I get a warning info, like the following:
    E.g. folder name should be "test"
    "The folder test could not be uniquely addressed by the path /test/ because two or more folders share the same name"
    I checked the repository for another folder with the same name but without success.
    The point is, that I want to use the API to add objects to the folder. But without a unique address the creation will fail.
    What makes this very strange is, that sometimes it works.
    Is there any place in the repository where folder ids can be checked for uniqueness ?
    Thanks a lot.
    Timo

    Hi Jon
    On the first topic, try this.
    import java.io.File;
    public class MakeDir {
         public static void main(String[] args) {
              if (args.length != 1 || args[0] == null || args[0].trim().length() == 0) {
                   System.out.println("Usage: java MakeDir <folder name>");
                   System.exit(-1);
              File f = new File(System.getProperty("user.dir") + "\\" + args[0]);
              f.mkdir();
    }/John

  • NWDI does not reach runtime systems ... sometimes

    Hi all,
    we have a strange problem with our new NWDI (7.40 SP5). Globally the NWDI works fine. Until now we have migrated 60 of our 180 tracks to the new environment and beside some smaller errors everything works fine.
    Now the first track users try to deploy their developments to the runtime systems. Until now there are about 30 runtime systems connected, from 7.00 up to 7.40 systems. 7.00 systems work fine, all above it is a question of luck whether a deployment/import works or not.
    The error message (severity = fatal) is always the same:
    Exc=com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'DeployerNWDI' could not be connected to the specified host 'xxx' and port '5xxx4'
    At the same time there are these four error messages at the logfiles:
    1. Import failed
    2. User cannot connect (the one above)
    3. User cannot connect with stacktrace
    4. Connection lost (the one below)
    I have written a small WebDynpro-application at the NWDI-server which tries to open a connection to the runtime systems at a specific port and it is always OK (no firewall problem). I have tried to connect to the runtime systems with the connection user and it is OK too.
    What we have figured out so far is that the application server has a problem in its default configuration when the OS has several network adapters and thus several IP addresses. This problem is solved already (there is a SAP note for that). Also we have increased the maximum number of connection the server is able to keep open at the same time.
    The strangest part is that it works sometimes if you hit import just a second time after a failed import ...
    Does anyone knows the problem or even better a solution? Thanks in advance!
    Here is the full stacktrace:
    Could not establish connection to AS Java on [P4://xxx:5xxx4]. Connection lost. Check if the host and port specified are correct and AS Java is up and running.
    [EXCEPTION]
    javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
    at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
    at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
    at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:64)
    at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:45)
    at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
    at javax.naming.InitialContext.init(InitialContext.java:223)
    at javax.naming.InitialContext.<init>(InitialContext.java:197)
    at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
    at com.sap.engine.services.dc.api.session.impl.SessionImpl.<init>(SessionImpl.java:150)
    at com.sap.engine.services.dc.api.session.impl.SessionFactoryImpl.newSession(SessionFactoryImpl.java:36)
    at com.sap.engine.services.dc.api.impl.ClientFactoryImpl.createClient(ClientFactoryImpl.java:127)
    at com.sap.sdm.apiimpl.remote.client.P4APIClientSessionImpl.getDeployControllerClient(P4APIClientSessionImpl.java:166)
    at com.sap.sdm.apiimpl.remote.client.P4APIClientSessionImpl.initClient(P4APIClientSessionImpl.java:137)
    at com.sap.sdm.apiimpl.remote.client.P4APIClientSessionImpl.<init>(P4APIClientSessionImpl.java:60)
    at com.sap.sdm.apiimpl.remote.client.P4APIClientSessionImpl.newInstance(P4APIClientSessionImpl.java:47)
    at com.sap.sdm.apiimpl.remote.client.APIClientSessionFactoryImpl.createAPIClientSession(APIClientSessionFactoryImpl.java:53)
    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:597)
    at com.sap.sdm.api.remote.ClientSessionFactory.createRemoteClientSession(ClientSessionFactory.java:299)
    at com.sap.sdm.api.remote.ClientSessionFactory.createRemoteClientSession(ClientSessionFactory.java:249)
    at com.sap.cms.tcs.beans.deployer.DeployConnector.openConnection(DeployConnector.java:148)
    at com.sap.cms.tcs.beans.TCSDeployBean.performDirectDeployment(TCSDeployBean.java:188)
    at sun.reflect.GeneratedMethodAccessor1040.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
    at com.sun.proxy.$Proxy407.performDirectDeployment(Unknown Source)
    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:597)
    at com.sap.engine.services.rmi_p4.reflect.LocalInvocationHandler.invokeInternal(LocalInvocationHandler.java:101)
    at com.sap.engine.services.rmi_p4.reflect.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:52)
    at com.sun.proxy.$Proxy412.performDirectDeployment(Unknown Source)
    at sun.reflect.GeneratedMethodAccessor1039.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sap.engine.services.ejb3.runtime.impl.StatelessRemoteStubInvocationHandler.invoke(StatelessRemoteStubInvocationHandler.java:89)
    at com.sun.proxy.$Proxy413.performDirectDeployment(Unknown Source)
    at com.sap.cms.tcs.core.SDMDeployTask.processImport(SDMDeployTask.java:292)
    at com.sap.cms.tcs.core.SDMDeployTask.process(SDMDeployTask.java:356)
    at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
    at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
    at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:448)
    at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:175)
    at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:499)
    at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:112)
    at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:638)
    at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:610)
    at sun.reflect.GeneratedMethodAccessor690.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
    at com.sun.proxy.$Proxy514.startImport(Unknown Source)
    at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1760)
    at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2809)
    at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:1158)
    at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2856)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
    at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)
    at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)
    at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:326)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
    at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
    at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:367)
    at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:490)
    at com.sap.tc.webdynpro.serverimpl.wdc.ForwardServlet.doPost(ForwardServlet.java:73)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
    at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
    at com.sap.engine.services.security.login.RemoteLoginContextFactoryImpl.getRemoteLoginContext(RemoteLoginContextFactoryImpl.java:95)
    at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:114)
    at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:312)
    ... 163 more
    Caused by: java.io.IOException: Reading reply for initial call failed. Check remote side state
    at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.resolveInitialReference(P4ObjectBrokerServerImpl.java:1486)
    at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
    at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
    ... 166 more
    Caused by: com.sap.engine.services.rmi_p4.exception.P4BaseConnectionException: Connection lost
    at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.getException(P4ObjectBrokerServerImpl.java:1320)
    at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.getException(P4ObjectBrokerServerImpl.java:1309)
    at com.sap.engine.services.rmi_p4.P4Call.fail(P4Call.java:143)
    at com.sap.engine.services.cross.fca.ConnectionImpl.notifyCalls(ConnectionImpl.java:150)
    at com.sap.engine.services.cross.fca.FCAConnectorImpl.notifyConnectionClosed(FCAConnectorImpl.java:253)
    at com.sap.engine.services.cross.fca.FCAConnectorImpl.clientConnectionClosed(FCAConnectorImpl.java:238)
    at com.sap.engine.services.cross.fca.SystemMessageProcessor.parseMessage(SystemMessageProcessor.java:94)
    at com.sap.engine.services.cross.fca.SystemMessage.process(SystemMessage.java:22)
    at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
    ... 3 more

    Hi Richard,
    could you please check whether this note helps?
    1492974 - Deployment to a AS Java does not work
    Regards,
    Ervin

  • Erro to aplly note 764176 - Integration Directory not appear

    Hi everyone...
    After applied note 764176 (step 5) my Integration Directory is not appearing in SLD as tecnical system. Does anybody know how to solve this problem ?
    Best Regards
    Wendell

    Hi All,
    I got solved the error before,  but now my Adapter Engine still is not appearing in Integration Directory. Could you help us ?
    Note. I applied full note 764176.
    Best Regards

  • Unable to Load the Integration scenario into the Integration directory

    Hi All,
    I am new to using SAP XI.
    Require your help on the following issue.
    I have built an Integration scenario, added Component  Type: Product Version, inserted actions and connections.
    I did check for any errors. I found no errors.
    When I am trying to load this scenario into the  Integration directory its not showing up the scenario in the popup.
    Navigation:
    Directory > tools> Transfer scenario from repository
    The status of Integration Scenario in the builder shows as
    "Being processed".
    I created the scenario 2 days back.
    Can some one help me in this? 
    Regards,
    Meher

    Hi All,
    Thanks to all who helped me.
    michal,divija : Can you please let me know in details how to activate Business Scenario?
    I did not create any business process.
    Sridhar: I did releases some locks on my process, no luck.
    Can you please explain me in more details?
    Should I have a process build for my Integration scenario to be activated?
    Thanks,
    Meher

  • Problem in starting Integration Directory

    We are installing xi 3.0 and now everything is working  and also integration repository but only integration Directory is not getting started. Others all are working. we have applied sp9.
    Here is the error that we get when we start integration directory:-
    Unsigned application requesting unrestricted access to system Unsigned resource: http://<Integration Builder server name>:<port>/dir/start/lib/aii_ibdir_client.jar
    and in the administration of XI (Java web start- status in start.txt) we r getting following error :-
    Resources could not be signed:
    aii_ibdir_client.jar aii_ib_client.jar aii_ib_core.jar aii_util_icons.jar aii_util_xml.jar aii_util_misc.jar clientaii_ibdir_sbeans.jar frog.jar jta.jar ejb20.jar
    Can any one help us in solving it? I have see OSS but not helpful.
    Thanks in advance

    Hi,
    I'm in exactly the same situation as you were, (hopefully you have solved the problem)how did you solve it ?
    /Roger

  • How to Change SWCV in Integration Directory for adapters

    Because of new SWCV, I have to point all interfaces to new version of SWCV. How can I assign Service Without Party / Business System Service to point to interfaces that require new SWCV?
    I deleted and recreated Sender Agreement, Receiver Agreement, Interface Determination, Receiver Determination for new SWCV in Integration Directory but I could not assign or create Business System to interfaces for new SWCV. It is still pointing to old version of SWCV.
    Can someone give steps on how I can change the SWCV in the Integration Directory?
    Thanks

    hi,
    >>>>How can I assign Service Without Party / Business System Service to point to interfaces that require new SWCV?
    you can only assing once
    later on you just ADD them to the scenarios
    by using <b>Add to scenario</b> function
    Regards,
    michal

  • Not able to import business system in Integration Directory

    Dear all,
    Currently i involved in XI system copy. As per the standard documetn i have finsihed the initial activites like EXPORT and import of abap and java files is succedded.
    Now in the post instalaltion activites.
    I have changed the exchange profile parameter
    SLD connection.
    And other post installation activites succesfully.
    But I am not able to import the business system in Integration director. It throws an error by mentioning.
    *Access to object list of type business system using the internalEOA service business system accessor failed *
    Here we are maintaing a central SLD and hence i created the service users with specific roles.
    SLDcheck is working fine and it dispalying the businees system as well.
    I confirmed that the user and password are same in XI and SLD system,
    But in SLD I am not able to see the domain under web as Exchagne Infrastructure alonng with the componets. I have tried to registerd the same using the note 761476 but in vain. After the changes i restarted the machin and checked the domain status in SLD technical system under exchagne Inffrastructure its not working.
    Is this the problem or am i missing out somewhere?
    FYI: The users are not locked.
    Kindly suggest me and it will be greatful if i get immediate reply.
    Thanks and regards
    Vijay kumar G

    Hi Vijay,
    It looks like the problem is with the SLD.
    Did you delete the SAP ABAP and Java technical system and business systems and recreate them in the central SLD? If this was the case, then you may not be able to import them into your integration directory anymore, as the GUID of the new technical systems and business systems are not the same with the previous one.
    Why not tried to recopy the SLD again, and this time do not change the technical and business systems. If the reregistration of these systems are not avoidable, then you will have to open up the copied IR for configuration.
    Regards,
    Lim...

  • Integration Directory - Transport using CMS does not appear

    Hi guys,
    I'm having problems with one thing I thought it would be trivial.... I'm not able to get the option 'Transport using CMS' in the Integration Directory available.
    I've done the necessary steps on the exchangeProfile in order to transport objects using CMS.
    1. Configuring ExchangeProfile
    IntegrationDirectory
    com.sap.aii.ibdir.core.cms.enableTransportWizard=true
    com.sap.aii.ibdir.core.cms.enableClTransport=true
    IntegrationRepository
    com.sap.aii.ibrep.core.cms.enableClTransport=true
    com.sap.aii.ibrep.core.cms.enableTransportWizard=true
    Added the values to com.sap.aii.ib.client.properties
    u2022 com.sap.aii.ibrep.core.cms., com.sap.aii.ibdir.core.cms.
    2. And after, I've created the tracks needed for IntegrationRepository and IntegrationDirectory.
    For the IntegrationDirectory I've followed SAP's description:
    "You have created an XI track in the Landscape Configurator and entered the addresses of the development, consolidation, and productive directory. There are no software component versions in the Integration Directory. Therefore, for directory transports using the CMS, you specify the software component version SAP-INTDIR 3.0 (EXCHANGE DIRECTORY 3.0). This refers to all configuration objects of the Integration Directory.
    Once you have made this setting, you can create transport lists for the CMS. The status of the change lists no longer changes to Closed immediately after their release, but first changes to Transportable."
    3. I've restarted the J2EE Server.
    When I export the objects from IntegrationRepository everything runs OK, but on the IntegrationDirectory I'm not able to have the option 'Transport Using CMS' available.
    I've read several threads on the SDN but none of them solved the problem...
    Can anyone give me any hint ?

    Hi Sameer,
    No luck.... There's nothing similiar to what I'm describing and the points which are mentioned i've already covered them.
    Thanks for the tip, I was hoping it could give me a push...
    Any ideas...?

  • Integration Process does not appear in ID or Runtime Cache

    I created an Integration process and it has not appeared as an available service in the Integration Directory when createing a receiver determination. It also does not appear in the runtime cache.
    Last week I created a different IP and that exists in both places. Between that time and now we migrated the SLD from one machine to another; I don't know if this will have an affect, but all messages interfaces created today appear in the Integration Directory, so there is a communication path at least.
    Can anybody advise how to proceed?

    Hi
    You should import the IP from IR to ID.
    In ID Goto Objects tab, here expand Service without party, you got the IP, from here you right click mouse>new>give some name and import your created IP in the IR.
    Then you get the IP in the ID.

  • I am not getting Business System into my Integration Directory.

    Hi All!
       This is satish, <b>I created Business system in SLD. How to get them in Integration Directory.</b>Please help me.
    Thanks in advance!

    Hi Satish,
    Go to Service without Party->Right Click->Assign Business System->it will show you list of Business Systems created in SLD -> then go ahead
    Then
    2 options to refresh the cache-
    Integration Directory->Environment->Clear SLD Data Cache
    Another way is -go to SXI_CACHE / Goto - Business System -> delete the content
    Still , if you are not able to see the Business sytem in the Directory, the just go and check in the SLD. If it exists just change and save it.
    Then synchronise the same by SLD cache refresh as mentiond.
    changing BS
    Also refer for more-
    Problem in Assigning the Business System
    Hope this helps,
    Regards,
    Moorthy

  • Change the SLD adress in Integration Directory

    Hello,
    When I launch the SLD from the integration directory page I get an error and the host adress is not right.
    Could you please show me how to change the host adress of the sld.
    In order to access the integration directory page go to:
    http://<host>:<port>/dir
    Thanks

    URL for SLD is maintained in Exchange Profile.
    In exchange profile you will find the URL maintained for SLD in "Connections". You need to change below  parameters:
    com.sap.aii.connect.cr.name
    com.sap.aii.connect.cr.httpport
    com.sap.aii.connect.landscape.name
    com.sap.aii.connect.landscape.httpport
    Thanks,
    Sunil Singh

  • Integration Directory : getting 404 Page not found error while accessing In

    Hello,
    When i am trying to open the Interation Directory, it is showing me 404 Page not found Error.
    Some Description
    - Executing sxmb_ifr,
    - From http://erpsys07:50300/rep/start/index.jsp,i am getting mentioned error when i am trying to access Integration Directory from URL.
    erpsys07 -> Central SLD -> J2ee Port - 50100
    erpsys07 -> PI system -> J2ee Port - 50300
    When i am clicking on integration directory link, it is pointing to Central SLD J2ee Port (50100) instead of 50300, it is pointing to
    http://erpsys07:50100/dir/start/sso/Directory.jsp instead of http://erpsys0750300/dir/start/sso/Directory.jsp.
    Could some help me where to change and what to change?
    Thanks,
    V.SINGH

    Have you checked port in Netweaver Administration?
    See which port is mentioned there. (If you are using PI 7.1)
    Check in SXMB_ADM transaction, and in your RFC Destination, where it is pointing.
    Thanks,
    Hetal
    Edited by: hetal shah on Nov 24, 2009 4:49 PM

  • Disappeared - Integration Directory - Runtime workbench

    Hi,
    Does not appear (Integration Directory - runtime workbench) after installation I can see if this set is PIXI 7.1
    Thank you very much.
    [Imagen|http://s3.subirimagenes.com:81/otros/previo/thump_5655324001.jpg]
    Greetings

    Hi
    After the installation did you run the PI Install templates from the NWA or configured it manually?
       Please check the Exchange Profile and see you have  all the parameters.
    Login to the below url
    http://hostname:port/webdynpro/dispatcher/sap.com/com.sap.xi.adminweb/AdminApp
    Click on Directory-> All properties and check the key and value information.
    if you dont see the valid system and port name. you have to correct it in the Exchange Profile and restart the system.
    Thanks
    Kiran Nekkanti

Maybe you are looking for