SDM Deployment issue

Hi Guys,
I am trying to deploy the .jar file for an EJB as a part of adapter module ejb deployment and i am getting the following error
have an ejb file in .jar and when i try to deploy it using sdm i am getting the following error. any body has the idea
) Error loading archive
C:\Documents and Settings\x10adm\Desktop\EJBXiPayAuthReq.jar
(server side name is: D:/usr/sap/X10/DVEBMGS01/SDM/program/temp/EJBXiPayAuthReq.jar)
com.sap.sdm.util.sduread.IllFormattedSduFileException: There is no deployment descriptor found in the SDA manifest
any help would be really appreciated
Thanks,
Srini

Hello Srini,
According to J2EE Specifications jar files cannot be deployed to a J2EE Engine.
I suggest you use the NWDS instead of plain Eclipse.
In NWDS you have a J2EE perspective, which sould be used for Development for J2EE Componnets like EJBs.
You need to create EJB Module Project and an Enterprise Application Project.
The final build product of a Enterprise Application Project will be an .ear file, which will contain the jar file. The ear file will also have the required Deployment Descriptors which can be deployed using SDM or NWDS itself.
Please refer to this document for Module Development and Deployment. Technically a adapter module is also a EJB.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3bdc14e1-0901-0010-b5a9-a01e29d75a6a
Please award points if you find this post useful.
Best Regards,
Kanwal

Similar Messages

  • SDM Deployment issues....

    Hi Experts,
       We are using ISA b2b 4.0 application over Enterprise portal.  Generally we used to deploy   EAR file by SDM tool..  Usuallaly it takes 6-7 mins take to finish deploymentation successfully...
        But today, In production,  it takes less than 2 min and log says the "deployment suffcessfull".   But the chagnges are not getting affected.
    What may the reason for this ubnormal time taken..?  Could anyone help me ?
    Thanks in Advance.
    Regards,
    Murugan Arumugam.

    Few possibilities:
    The EAR file has an issue - Check locally if this works correct
    The date of the EAR file is older than the deplyed files - You can override this by chosing - Update deployed _SDAs/SCAs that have any version. (You have to expand the section "Deployment Configuration"  available at the bottom of the screen just above the buttons.
    What does the "Log Viewer" say?
    Undeploy and redeploy
    Easwar Ram
    http://www.parxlns.com

  • J2ee Admin User locked on SDM Deployment - BI 7.0 and EP 7.0

    Hi,
    We had a recent issue on BI iview publishing from the BEX WAD 7.0 in our Production Portal server.
    The BEX WAD had the error " Java communication error"
    " An Error occured during communication with the BI Components of the J2ee engine"
    We traced down to identify that the current stack NW 7.0 SP14 BI Components had issues and had to patch to the next level
    However, during deployment of the patch using SDM, the components (all) failed posting the following error. The SDM deployment got struck and the J2ee Engine user j2ee_admin was locked.
    Only a restart of the j2ee engine is allowing us to get the Visual Admin connected. But the SDM deployment again is failing and admin user gets locked. Is there any tested solution to solve this.
    Kindly help asap.
    Trace:
    SDM:
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [xxxx] with user name: [j2ee_admin]check your login information.
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]          
    J2ee Engine:
    Error while connecting
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: This call must be performed from a system thread.
         at com.sap.engine.services.security.login.SecuritySession.setExpirationPeriod(SecuritySession.java:479)
         at com.sap.engine.services.security.login.TicketGenerator.getSecuritySession(TicketGenerator.java:180)
         at com.sap.engine.services.security.login.SecurityContext.load(SecurityContext.java:313)
         at com.sap.engine.services.rmi_p4.Message.loadContextObject(Message.java:345)
         at com.sap.engine.services.rmi_p4.Message.parseMessage(Message.java:239)
         at com.sap.engine.services.rmi_p4.Message.getByteArrayInputStream(Message.java:314)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:212)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

    Hi Anup,
    The restart unlocks the j2ee engine admin user and i am able to login to Visual admin and SDM and not otherwise (SDM is hanged and doesnot allow another session and hence only restart helps me to get into SDM again)
    Admin Pwds reset etc from config tool secure store and all possible solutions have been tried before restart.
    However, after restart, when we try to deploy again, the deploy fails saying the same msg
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [xxx] with user name: [j2ee_admin]check your login information.
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
    Any clues ?
    Regards
    Venkat.

  • SDM deployment error during XI 3.0 installation

    (nobody in the PI forum replied, so I'm reposting here)
    I need to install a sandbox using this old version. Installation base is 6.40 WebAS plus Java addon SR1. System installs fine, however during final SDM deployment I get a problem during the J2EE engine restart:
    errors:
    service sld ================= ERROR =================
    Cannot start service com.sap.aii.af.cpa.svc; it has hard reference to service sld which is not started.
    and around 20 more services which have a dependency on sld
    sld does not start because:
    /Applications/SLD#sap.com/com.sap.lcr#com.sap.lcr.sagent.BuilderDirector#J2EE_
    GUEST#328####e4cd3451819411dec19c001d72bd0666#SAPEngine_Application_Threadimpl:3_0##0#0#Error#1#com.sap.lcr.sagent.BuilderDirector#Plain###Can't access http store#
    OR:
    SAPEngine_System_Threadimpl:5_32##0#0#Error#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service sld error. Nested exception is: com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='sld_3012', A
    rguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key sld_3012
    at com.sap.sldserv.SldServerFrame.start(SldServerFrame.java:109)
    at com.sap.sldserv.SldServerFrame.start(SldServerFrame.java:78) ...........
    further suspicious warnings:
    Aug 5, 2009 12:51:17 AM Info: No action: Selected development component 'com.sap.aii.af.ms.svc'/'sap.com'/'SAP AG'/'3.0.0920041027171222.0000' will not be deployed because containing software component 'SAP-XIAFC'/'sap.com'/'SAP AG'/'1000.3.0.9.1.20041028052722' will not be deployed.
    and this for around 20 more components from comp.sap.aii*
    What went wrong, and, what can I do to fix this? Redeploy sld ? I could not find how.
    Java version is latest 1.4.2 x86_64 from IBM (1.4.2_13) for my architecture (x86_64 Linux RHEL5), DB is maxdb 7.6
    Any help is appreciated, Thanks.
    Sanjay

    Can you please check thet if you have given a central SLD then that SLD is up and running as you are getting the message.
    Cannot start service com.sap.aii.af.cpa.svc; it has hard reference to service sld which is not started.
    Please check this note it will solve your issue.
    Note 994433 - XI AF on J2EE Engine terminates with OutOfMemoryError
    you can manually start th services.
    Thanks Rishi Abrol

  • Outbound BPEL Process deployment Issue in SOA (binding.jca-12600)

    Hi,
    I have Designed an Outbound BPEL Process for Siebel CRM Service Integration using Jdeveloper (11.1.1.3.0). After that I am facing the deployment issue of this application in SOA suite (11.1.1.6.0). Following is the deployment.log status in jdeveloper:-
    [10:57:54 AM] ---- Deployment started. ----
    [10:57:54 AM] Target platform is (Weblogic 10.3).
    [10:57:54 AM] Running dependency analysis...
    [10:57:54 AM] Building...
    [10:57:58 AM] Deploying profile...
    [10:57:58 AM] Wrote Archive Module to C:\JDeveloper\mywork\Siebel_Outbound_BPEL\QueryWithView_Invoke\deploy\sca_QueryWithView_Invoke_rev1.0.jar
    [10:57:58 AM] Deploying sca_QueryWithView_Invoke_rev1.0.jar to partition "default" on server AdminServer [10.10.22.81:7001]
    [10:57:58 AM] Processing sar=/C:/JDeveloper/mywork/Siebel_Outbound_BPEL/QueryWithView_Invoke/deploy/sca_QueryWithView_Invoke_rev1.0.jar
    [10:57:58 AM] Adding sar file - C:\JDeveloper\mywork\Siebel_Outbound_BPEL\QueryWithView_Invoke\deploy\sca_QueryWithView_Invoke_rev1.0.jar
    [10:57:58 AM] Preparing to send HTTP request for deployment
    [10:57:59 AM] Creating HTTP connection to host:10.10.22.81, port:7001
    [10:57:59 AM] Sending internal deployment descriptor
    [10:57:59 AM] Sending archive - sca_QueryWithView_Invoke_rev1.0.jar
    [10:58:00 AM] Received HTTP response from the server, response code=500
    [10:58:00 AM] Error deploying archive sca_QueryWithView_Invoke_rev1.0.jar to partition "default" on server AdminServer [10.10.22.81:7001]
    [10:58:00 AM] HTTP error code returned [500]
    [10:58:00 AM] Error message from server:
    #;There was an error deploying the composite on AdminServer: Deployment Failed: [JCABinding] [QueryWithView_Invoke.QueryWithView/1.0]Unable to complete load due to: Generic error.
    #;Generic error.
    #;Cause: Unable to find suitable outbound binding.
    #;Please create a Service Request with Oracle Support.
    #;: Generic error.
    #;Generic error.
    #;Cause: Unable to find suitable outbound binding.
    #;Please create a Service Request with Oracle Support.
    [10:58:00 AM] Check server log for more details.
    [10:58:00 AM] Error deploying archive sca_QueryWithView_Invoke_rev1.0.jar to partition "default" on server AdminServer [10.10.22.81:7001]
    [10:58:00 AM] #### Deployment incomplete. ####
    [10:58:00 AM] Error deploying archive file:/C:/JDeveloper/mywork/Siebel_Outbound_BPEL/QueryWithView_Invoke/deploy/sca_QueryWithView_Invoke_rev1.0.jar
    (oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
    And the following is the SOA Server Side log file status:-
    ####<Jun 3, 2013 10:36:05 AM AST> <Info> <Health> <HOSADDAT02> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <4be72ac3bdb5ebae:-a61256d:13f08d94c98:-8000-00000000000000f4> <1370244965280> <BEA-310002> <36% of the total memory in the server is free>
    ####<Jun 3, 2013 10:36:12 AM AST> <Error> <ServletContext-/soa-infra> <HOSADDAT02> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <4be72ac3bdb5ebae:-a61256d:13f08d94c98:-8000-000000000000182b> <1370244972343> <BEA-000000> <Error during deployment
    oracle.fabric.common.FabricException: Deployment Failed: [JCABinding] [QueryWithView_Invoke.QueryWithView/1.0]Unable to complete load due to: Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
    : Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
         at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:64)
         at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
         at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:99)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
         at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:219)
         at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:130)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused By: oracle.fabric.common.FabricDeploymentException: [JCABinding] [QueryWithView_Invoke.QueryWithView/1.0]Unable to complete load due to: Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
    : Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
    {rootCauses=[]}
         at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:458)
         at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:82)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployReferences(CompositeDeploymentConnection.java:201)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deploy(CompositeDeploymentConnection.java:93)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.initDeployment(CompositeDeploymentManagerImpl.java:150)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.load(CompositeDeploymentManagerImpl.java:63)
         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 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
         at oracle.integration.platform.blocks.deploy.DeploymentEventPublisher.invoke(DeploymentEventPublisher.java:77)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
         at $Proxy314.load(Unknown Source)
         at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:59)
         at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
         at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:99)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
         at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:219)
         at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:130)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused By: BINDING.JCA-12600
    Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterBindingConfig.addAdapterReference(AdapterBindingConfig.java:206)
         at oracle.integration.platform.blocks.adapter.AdapterReference.setupAdapterReference(AdapterReference.java:506)
         at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:425)
         at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:82)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployReferences(CompositeDeploymentConnection.java:201)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deploy(CompositeDeploymentConnection.java:93)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.initDeployment(CompositeDeploymentManagerImpl.java:150)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.load(CompositeDeploymentManagerImpl.java:63)
         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 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
         at oracle.integration.platform.blocks.deploy.DeploymentEventPublisher.invoke(DeploymentEventPublisher.java:77)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
         at $Proxy314.load(Unknown Source)
         at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:59)
         at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
         at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:99)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
         at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:219)
         at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:130)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Kindly help me in this regard

    Solution:
    Workaround the issue immediately by removing the "ns1:" qualification on the operation for the binding.jca entry in the composite.xml and redeploying.
    For example:
    From:
    <binding.jca config="BAPI_COMPANYCODE_GETDETAIL_invoke_3P.jca"
    operation="ns1:BAPI_COMPANYCODE_GETDETAIL"/>
    To:
    <binding.jca config="BAPI_COMPANYCODE_GETDETAIL_invoke_3P.jca"
    operation="BAPI_COMPANYCODE_GETDETAIL"/>
    Regards,
    Shaheer Badar

  • Adobe Acrobat 9 Pro deployment issue

    Hello. I am having a deployment issue with Adobe Acrobat 9 using Altiris. I create the rip which is bassically an image of the install. My facility has pruchased 50 seats for this software so I know we are covered for the users that we have to use this software. The issue that I am having after I make the rip, and deploy it to a machine it asks for the CD key again in order to use. Am I having an issue with my installation or is Adobe put some kind of security into their software so that when you try to make a rip of the installation is asks for teh CD Key again after the install? Is this an issue that can be resolved?

    SOLUTION:
    The issue was somehow related to DPI (START > Settings > Control Pannel > Display > Settings Tab > Advanced button). Eventhough the DPI was set to normal, I switched it to LARGE, restarted the machine, logged in after the reboot, changed it back to normal size, restarted again, logged in once more, checked the Printer Preferences and PRESTO --- a properly displayed window.

  • Deploy issue from JDeveloper 10.1.3.5 to OAS 10.1.2

    I have written an application using ADF on JDeveloper 10.1.3.5 and need to deploy it to our OAS 10.1.2. I have run the adfinstaller on the linux server to upgrade the ADF libraries to the correct versions, updated the web.xml files to have the correct versions, changed to J2SE 1.4.2_19 for the application and have still got deployment issues.
    Error
    An error occurred while redeploying application "FormsSiebelIntegration". See base exception for details.
    Resolution:
    See base exception for details.
    Base Exception:
    java.lang.UnsupportedClassVersionError
    com/sun/faces/application/ApplicationAssociate (Unsupported major.minor version 49.0). com/sun/faces/application/ApplicationAssociate (Unsupported major.minor version 49.0)
    Removing the jsf-impl.jar file allows the application to deploy, but when running on the app server I get the following errors:
    OracleJSP: oracle.jsp.parse.JspParseException:
    /codename.jspx: Line # 6, <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.0" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:af="http://xmlns.oracle.com/adf/faces" xmlns:afh="http://xmlns.oracle.com/adf/faces/html">
    Help! I'm starting to have total mind block as to what to do next.
    Error: Unable to load taghandler class: http://java.sun.com/jsf/html

    I had already applied all of this before trying to deploy.
    The error seems to be a versioning error in the jsf-impl.jar file as the ApplicationAssociate class is found there. I have changed the JDK and J2EE to 1.4.2 and 1.3 respectively, rebuilt everything, updated all the settings to the right versions for 10.1.2 but it still keeps failing on the deploy.

  • SDM Deployment fails - Dependency caf/core/ear missing

    crosspost from: SDM Deployment fails - Dependency caf/core/ear missing
    deploying a DC from NWDS into SDM the following Exception is thrown:
    07.01.2008 16:20:38 /userOut/daView_category (eclipse.UserOutLocation) [ThreadDeploy Thread,5,main] INFO:
    002Additional log information about the deployment
    <!LOGHEADERSTART/>
    <!HELPManual modification of the header may cause parsing problem!/>
    <!LOGGINGVERSIONhttp://1.5.3.7185 - 630/>
    <!NAME[/usr/sap/IT1/DVEBMGS00/SDM/program/log/sdmcl20080107151422.log]/>
    <!PATTERNhttp://sdmcl20080107151422.log/>
    <!FORMATTERcom.sap.tc.logging.TraceFormatter(%24d %s: %m)/>
    <!ENCODINGUTF8/>
    <!LOGHEADEREND/>
    Jan 7, 2008 4:14:22 PM Info:
    Starting deployment
    Jan 7, 2008 4:14:22 PM Info: Error handling strategy: OnErrorStop
    Jan 7, 2008 4:14:22 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
    Jan 7, 2008 4:14:22 PM Info: Update strategy: UpdateAllVersions
    Jan 7, 2008 4:14:22 PM Info: Starting deployment prerequisites:
    Jan 7, 2008 4:14:23 PM Info: Loading selected archives...
    Jan 7, 2008 4:14:23 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23425innobis.dewkbtmetadata.ear'
    Jan 7, 2008 4:14:24 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23426innobis.dewkbtear.ear'
    Jan 7, 2008 4:14:24 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23427innobis.dewkbtdictionary.sda'
    Jan 7, 2008 4:14:25 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23428innobis.dewkbtpermissions.ear'
    Jan 7, 2008 4:14:26 PM Info: Selected archives successfully loaded.
    Jan 7, 2008 4:14:26 PM Error: Unresolved dependencies found for the following SDAs:
    1.: development component 'wkbt/ear'/'innobis.de'/'NetWeaver Developer Studio'/'20080107144202'/'0'
    dependency:
    name: 'caf/core/ear'
    vendor: 'sap.com'
    There is no component either in SDM repository or in Deployment batch that resolves the dependency.
    Deployment will be aborted.
    Jan 7, 2008 4:14:26 PM Error: Prerequisites were aborted.
    Jan 7, 2008 4:14:27 PM Error: Error while creating deployment actions.
    system:
    sap.com/SAP-JEECOR 7.00 SP10 (1000.7.00.10.0.20061026144500)
    sap.com/SAP-JEE 7.00 SP10 (1000.7.00.10.0.20061026144500)
    I checked http://<srv>/sap/monitoring/ComponentInfo
    the missing 'caf/core/ear' is not listed, however several other CAFs are:
    sap.com caf/core null (964250) SAP AG MAIN_APL70VAL_C 20061212133926 sap.com/CAF
    sap.com caf/core/dict null (964586) SAP AG MAIN_APL70VAL_C 20061212131613 sap.com/CAF
    sap.com caf/core/gp/facade/backgroundco/ear null (964227) SAP AG MAIN_APL70VAL_C 20061212134201 sap.com/CAF
    sap.com caf/core/metadata null (963689) SAP AG MAIN_APL70VAL_C 20061212133653 sap.com/CAF
    etc....
    Is it possible to deploy this missing caf-ear component supplementary?
    I have the strange feelings caf/core/ear is something 7.1 CE only related....
    thanks for any hint!
    kai

    Kai, I didn't mean to offend you. But good forum practice is to avoid duplicate posts.
    Regards,
    \-- Vladimir

  • A very urgent deployment issue about DBAdapter

    Hello All,
    I have a very urgent deployment issue about DBAdapter.
    That DBAdapter is connect to DB2 AS400 Database. I have a developing database (jdbc:as400://server01/TEST) and a production database (jdbc:as400://server01/PROD).
    During developing, I used DBAdapter wizard to create it, and import some tables, and set the Adapter to use jabc/DB2DS as connection information for easily deployment later.
    Then I deploy to Production. I configured Data-source.xml and oc4j-ra.xml rightly; I set DB connection point to production database. But the DBAdapter still write into developing Database.
    I checked the DBAdapter, the imported tables are something like this, TEST.table1, TEST.table2. And there are a lot "TEST" located in DB2Writer_toplink_mapping.xml, DB2Writer.xml, TEST.schema, DB2Writer.table1.ClassDescriptor.xml.
    This TEST is refrer to the TEST in connect String jdbc:as400://server01/TEST.
    I think this might be the reason cause the problem. As to production database, "TEST" should replaced by "PROD". If I changed it manually, I have to change every time when switch between TEST and PROD. And I also don't know if it is safe to do it? (I tried, and bring some toplink mapping problem)
    By the way, for Oracle Database, because we use 2 instances for testing and production with same schema name, and do not have this issue.
    Anyone could help and many thanks.
    Kerr
    Message was edited by:
    Kerr

    Hi Kerr,
    The idea is to set up all connections in the BPEL or ESB services with logical names, e.g. typically of the form eis/DB/MyFinancialSystem or eis/DB/MyLogisticsSystem. This way, you do not have to modify code when deploying it onto different environments that serve different purposes.
    When moving your services through their lifecyle, on every environment you deploy these to you will have the same logical connections configured on each instance, e.g. for DEV, QA, SIT, UAT and PROD. Only, in case of QA the actual physical connection is configured to point to the QA instance of the systems that your services interact with whereas in case of UAT it points to the UAT instance of the same system.
    Maybe your problem is caused by connecting as user "SomeUser" when running the DB Adapter wizard during development and actually selecting objects from a different schema than you used to connect with, e.g. "Test" in your case.
    Hth,
    Sjoerd

  • Error in SDM-deploy Step

    <h5>Good Morning Gentleman,</h5>
    <h5>"When i'm trying to import a transport order to our productive system the import fails in step SDM-deploy with the following error:</h5>
    <h5>20120228122646 Info   :Starting Step SDM-deploy at 2012-02-28 12:26:46.0143 +0:00
    20120228122646 Info   :start deployment of archives:http://sapsps.sonaesierra.com:50004
    20120228122646 Fatal  :caused by Exception:com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'j2ee_admin' could not be connected to the specified host 'sapsps.sonaesierra.com'and port '50004'.:The user 'j2ee_admin' could not be connected to the specified host 'sapsps.sonaesierra.com'and port '50004'.
    com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'j2ee_admin' could not be connected to the specified host 'sapsps.sonaesierra.com'and port '50004'.
         at com.sap.cms.tcs.beans.deployer.DeployConnector.openConnection(DeployConnector.java:160)
         at com.sap.cms.tcs.beans.TCSDeployBean.performDirectDeployment(TCSDeployBean.java:194)
         at com.sap.cms.tcs.beans.TCSDeployObjectImpl0_0.performDirectDeployment(TCSDeployObjectImpl0_0.java:1342)
         at com.sap.cms.tcs.beans.TCSDeploy_Stub.performDirectDeployment(TCSDeploy_Stub.java:1296)
         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:331)
         at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
         at $Proxy225.performDirectDeployment(Unknown Source)
         at com.sap.cms.tcs.core.SDMDeployTask.processImport(SDMDeployTask.java:302)
         at com.sap.cms.tcs.core.SDMDeployTask.process(SDMDeployTask.java:366)
         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:447)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:176)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:113)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:648)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:620)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImport(LocalCmsTransportProxyLocalObjectImpl0_0.java:1640)
         at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1637)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2817)
         at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:1042)
         at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2866)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    20120228122646 Info   :Step SDM-deploy ended with result 'fatal error' ,stopping execution at 2012-02-28 12:26:46.0306 +0:00"</h5>
    <h5>I'm new to NWDI and related subjects. I've already checked:</h5>
    <h5>1. Port 50004 is available in the productive system</h5>
    <h5>2. J2EE Visual Administrator in productive is accessible by j2ee_admin</h5>
    <h5>3. j2ee_admin isn't locked in productive system</h5>
    <h5>What more should i check? What could be the reason behind this error?</h5>
    <h5>Thank you.</h5>
    <h5>Best Regards,</h5>
    <h5>Pedro Gaspar</h5>

    Good Morning Kumar,
    If i tell you what happened you're going to laugh... But i'll tell you anyway.
    After watching your post i went to the CMS Landscape Configurator in order to look into the configuration. I noticed that the Selected Tool for deployment in the Productive Runtime system was configured as Deploy Controller (this is a NW 7.01 and as far as i've read before... in this version it's advisable to configure it as you told me in your post - SDM Deploy, thanks for that).
    So i tried to change it, but nothing happened, i've tried a second time, but the changes wouldn't take effect and no message was generated. I've spent a few hours trying to understand what was happening... So i told to myself, let me try it with another browser (was using Firefox 3.6.27, changed to IE 9.0.8112) and when trying to change the runtime system configuration a message outputs... "... More than one name server configured in SLD"
    Immediately searched and got SAP note 1118009 - SLD name-server configuration error in CMS. After executing note steps i was able to change the runtime system tool for deployment, and i could finish the transport.
    The difference a message and the browser version can do in your life
    Thanks for your reply, which helped me solve the problem.
    Best Regards,
    Pedro Gaspar

  • SAP SDM Deployment failed

    Hello everybody i have a problem with my SAP ERP Installation the Error is :
    An error occurred while processing service SAP ERP 6.0 Support Release 3 > SAP Systems > Oracle > Central System > Central System( Last error reported by the step :uncaught exception: nw.sdm.deploymentErrorWithLog: SDM deployment failed for at least one of the components to be deployed. SOLUTION: Check C:\Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/callSdmViaSapinst.log for more information. (in script unknown, line 0:
    And here are my logfile , i hope you can help me for a solution. I have restart the SAP System and start it again and click retry but nothing happen, the same error comes again.
    Jan 19, 2010 7:34:14 AM  Info: Initial deployment: Selected development component 'tc/kmc/bc.uwl.ui/wd_pp'/'sap.com'/'SAP AG'/'7.0010.20061109164817.0000'/'1' will be deployed.
    Jan 19, 2010 7:34:14 AM  Info: No action: Selected development component 'com.sap.portal.nav.ws.NavigationWSEar'/'sap.com'/'SAP AG'/'7.0014.20071210113331.0000'/'2' will not be deployed because containing software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210193159''/'2' will not be deployed.
    Jan 19, 2010 7:34:14 AM  Info: No action: Selected development component 'caf/eu/gp/ui/gpconf'/'sap.com'/'MAIN_APL70VAL_C'/'1534144'/'3' will not update currently deployed development component 'caf/eu/gp/ui/gpconf'/'sap.com'/'MAIN_APL70VAL_C'/'1534144'/'2'.
    Jan 19, 2010 7:34:14 AM  Info: No action: Selected development component 'caf/eu/gp/croom/content'/'sap.com'/'MAIN_APL70VAL_C'/'1498043'/'3' will not update currently deployed development component 'caf/eu/gp/croom/content'/'sap.com'/'MAIN_APL70VAL_C'/'1498043'/'1'.
    Jan 19, 2010 7:34:14 AM  Info: No action: Selected development component 'com.sap.prt.ws.container'/'sap.com'/'SAP AG'/'7.0010.20061109164817.0000'/'2' will not be deployed because containing software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210152356''/'2' will not be deployed.
    Jan 19, 2010 7:34:14 AM  Info: Ending deployment prerequisites. All items are correct.
    Jan 19, 2010 7:35:49 AM  Info: Saved current Engine state.
    Jan 19, 2010 7:35:49 AM  Info: Starting: Initial deployment: Selected development component 'caf/eu/gp/ws/msosrv'/'sap.com'/'MAIN_APL70VAL_C'/'963790'/'3' will be deployed.
    Jan 19, 2010 7:35:49 AM  Info: SDA to be deployed: C:\usr\sap\DRC\DVEBMGS00\SDM\root\origin\sap.com\caf\eu\gp\ws\msosrv\MAIN_APL70VAL_C\3\963790\sap.com_cafeugpwsmsosrv.sda
    Jan 19, 2010 7:35:49 AM  Info: Software type of SDA: J2EE
    Jan 19, 2010 7:35:49 AM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Jan 19, 2010 7:35:56 AM  Info: Begin of log messages of the target system:
    10/01/19 07:35:50 -  ***********************************************************
    10/01/19 07:35:51 -  Start updating EAR file...
    10/01/19 07:35:51 -  start-up mode is lazy
    10/01/19 07:35:51 -  EAR file updated successfully for 47ms.
    10/01/19 07:35:51 -  Start deploying ...
    10/01/19 07:35:51 -  EAR file uploaded to server for 32ms.
    10/01/19 07:35:56 -  ERROR: NOT deployed. The Deploy Service returned the following error:
                         For detailed information see the log file of the Deploy Service.
                         Exception is:
                         com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
                              at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:700)
                              at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:688)
                              at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:180)
                              at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:427)
                              at java.lang.Thread.run(Thread.java:534)
    10/01/19 07:35:56 -  ***********************************************************
    Jan 19, 2010 7:35:56 AM  Info: End of log messages of the target system.
    Jan 19, 2010 7:35:56 AM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Jan 19, 2010 7:35:56 AM  Error: Aborted: development component 'caf/eu/gp/ws/msosrv'/'sap.com'/'MAIN_APL70VAL_C'/'963790'/'3', grouped by software component 'SAP-EU'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071210153525''/'3':
    Caught exception during application deployment from SAP J2EE Engine's deploy API:
    com.sap.engine.deploy.manager.DeployManagerException: ERROR: NOT deployed. The Deploy Service returned the following error: com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
    Exception is:
    com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
         at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:700)
         at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:688)
         at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:180)
         at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:427)
         at java.lang.Thread.run(Thread.java:534)
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)
    Jan 19, 2010 7:35:56 AM  Info: Starting to save the repository
    Jan 19, 2010 7:35:57 AM  Info: Finished saving the repository

    Hi,
    Check below thread:
    /message/441671#441671 [original link is broken]
    Thanks
    Sunny

  • SDM Deploy Tool

    Hi,
    I need to know what are the requirements that the war file and ear file
    shoud be complience with the SDM deployment tool beacuse we can not do the deploy and we think that our war and ear are not complience with SDM.
    Regards,
    Sérgio Salomã

    Hi,
    Yes, it should be in format that SDM can support.
    Thanks
    Sunny

  • Re: Deployment Issues

    Hi Dale;
    We have the similar situation. We wrote an application to be able to send
    alert message before we shut down the Forte application. When we upgrade our
    applications, we will send alert message to all users before we shut down the
    Forte application through ECONSOLE which forces all users to log out, and then
    overwrite the files.
    Our client files are sitting at one of our network servers instead of
    individual user's PC, so the user accesses the files through network. So we
    are facing the same issue that we have to shut all users down before we
    upgrade our applications. If you install those files on your individual user's
    PC, you may try to use "compatible level" to update your application.
    Hope this helps.
    Lu Wang
    Eli Lilly and Company
    [email protected]

    My problem lies more in the way that we update the Forte software. We are
    controlled enough with a new distribution from the application side that
    there are not problems there.
    My question is: how is everyone updating their client PC's from say Forte
    R2 to R3. This was not a problem before because we didn't have very many
    clients. Now we have quite a few and we can't just copy the proper files
    because of the registry updates that are required.
    Does anyone have any suggestions? Can I run the Forte client software off
    the Novell server?
    Thanks,
    Tony
    -----Original Message-----
    From: Lu Wang X1 <[email protected]>
    To: Dale V. Georg <[email protected]>
    Cc: Forte Users <[email protected]>; Gardner, Steve
    <[email protected]>
    Date: Wednesday, November 19, 1997 11:17 AM
    Subject: Re: Deployment Issues
    You are right. Through econsole, we can only shut down the serverpartitions,
    even though we can uninstall the application, as long as the clientpartition
    is running, we can't overwrite the files. We were probably lucky that nouser
    was running the application when we upgraded it.
    Since our applications can capture the system alert message, probably wecan
    make changes to our application to be able to shut itself down when it
    receives certain type of alert message. Just a thought. Don't know ifthere
    is any better way to handle it.
    Lu
    "Dale V. Georg" <[email protected]> on 11/19/97 03:02:27 AM
    Please respond to "Dale V. Georg" <[email protected]>
    To: Lu Wang X1/AM/LLY
    cc: Forte Users <[email protected]>, "Gardner, Steve"
    <[email protected]>
    Subject: Re: Deployment Issues
    On Tue, 18 Nov 1997 11:04:53 -0500, Lu Wang X1 wrote:
    Hi Dale;
    We have the similar situation. We wrote an application to be able to send
    alert message before we shut down the Forte application. When we upgradeour
    applications, we will send alert message to all users before we shut down
    the
    Forte application through ECONSOLE which forces all users to log out, andthen
    overwrite the files.If I remember correctly, econsole will only forcibly close down the
    server partitions, not the client partitions.
    Our client files are sitting at one of our network servers instead of
    individual user's PC, so the user accesses the files through network. So
    we
    are facing the same issue that we have to shut all users down before we
    upgrade our applications. If you install those files on your individualuser's
    PC, you may try to use "compatible level" to update your application.We did think about using the compatibility level at one point, but that
    introduces extra maintenence whenever a new version of the application
    is rolled out. On the other hand, if that's the cost of a smooth and
    reliable upgrade, then it may be worth paying.
    Dale
    ================================================
    Dale V. Georg
    Systems Analyst
    Indus Consultancy Services
    [email protected]
    ================================================

  • Ear deployment issue.

    Hi,
    i am using jdev Studio Edition Version 11.1.1.4.0
    I have created EAR of my application and trying to depoly it on Weblogic server.
    I have following entry in weblogic-application.xml
    <library-ref>
    <library-name>adf.oracle.domain</library-name>
    </library-ref>
    [03:12:39 PM] ---- Deployment started. ----
    [03:12:39 PM] Target platform is (Weblogic 10.3).
    [03:13:07 PM] Retrieving existing application information
    [03:13:07 PM] Running dependency analysis...
    [03:13:07 PM] Building...
    [03:13:28 PM] Deploying 3 profiles...
    [03:13:29 PM] Moving WEB-INF/adfc-config.xml to META-INF/adfc-config.xml
    [03:13:30 PM] Wrote Archive Module to /home/kpophale/CDMR/13June/frontend/ConsoleApps/AppsInventoryManagerUi/deploy/AppsInventoryManagerUi.jar
    [03:13:38 PM] Wrote Web Application Module to /home/kpophale/CDMR/13June/frontend/ConsoleApps/AppsInventoryManagerUi/deploy/AppsInventory.war
    *[03:13:38 PM] Removing the following prohibited entry from the EAR: lib/trinidad-api.jar*
    *[03:13:38 PM] Removing the following prohibited entry from the EAR: lib/trinidad-impl.jar*
    [03:13:38 PM] removed bundleresolver.jar from lib because it cannot be part of an EJB deployment
    [03:13:54 PM] Wrote Enterprise Application Module to /home/kpophale/CDMR/13June/frontend/deploy/AppsInventoryManager.ear
    [03:13:55 PM] Entering Oracle Deployment Plan Editor
    [03:15:53 PM] Deploying Application...
    [03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'bam_server1'. Deployment is deferred until 'bam_server1' becomes available.; nested exception is:
         java.rmi.UnknownHostException: Could not discover administration URL for server 'bam_server1'.
    [03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'osb_server1'. Deployment is deferred until 'osb_server1' becomes available.; nested exception is:
         java.rmi.UnknownHostException: Could not discover administration URL for server 'osb_server1'.
    [03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'soa_server1'. Deployment is deferred until 'soa_server1' becomes available.; nested exception is:
         java.rmi.UnknownHostException: Could not discover administration URL for server 'soa_server1'.
    [03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'adf_server1'. Deployment is deferred until 'adf_server1' becomes available.; nested exception is:
         java.rmi.UnknownHostException: Could not discover administration URL for server 'adf_server1'.
    [03:16:41 PM] [Deployer:149193]Operation 'deploy' on application 'AppsInventoryManager' has failed on 'AdminServer'
    [03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: Failed to load webapp: 'trellis-AppsInventoryManagerUi-context-root'.
    [03:16:41 PM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: 'trellis-AppsInventoryManagerUi-context-root'
    *[03:16:41 PM] Caused by: java.lang.NoClassDefFoundError: org/apache/myfaces/trinidad/webapp/UIXComponentELTag*
    [03:16:41 PM] See server logs or server console for more details.
    [03:16:41 PM] weblogic.application.ModuleException: Failed to load webapp: 'trellis-AppsInventoryManagerUi-context-root'
    [03:16:41 PM] #### Deployment incomplete. ####
    [03:16:41 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
    I am getting above exception while i am trying to depoly the my ear. please see bold lines.
    Please give me some guide line .
    Regards,
    Kiran.

    Hi John,
    Yes I have. I even tried on two seperate WebLogic installations. I noticed, even when I create just an ear file (not deploy to server), it gives me the same warnings about removing trinidad. Is there something i'm missing in JDeveloper?
    For my installations:
    On one Middleware home: I installed: WLS 10.3.5, ADF 11.1.1.5, then ADF 11.1.2 Patch 12611176. configured domain with all ADF/JRF libraries, followed by upgradeADF WLST command. I got same deployment issue.
    On another middleware home: I even just installed JDeveloper 11.1.2, configured a new domain with all librearies. I got same deployment issue.
    FYI: I also added the two Trinidad JSP Tag Libraries to my View Controller Project. I got same error.
    Thank you,
    Gavin
    Edited by: GavinWoods on Feb 14, 2012 6:25 AM

  • EPMA Deployment Issues (Rollback Database)

    I have seen some posts where users were able to rollback their EPMA databases. This could be helpful when running into deployment issues. Can anyone outline the steps that are needed to rollback an EPMA database?
    Thank you

    spring_patel wrote:
    i really appreciate you trying to solve my problem..
    but i think...my estion is fairly simple and straight forward...and i've provided every detail of my problem(if uv'e read my opening post of this thread)....
    and as far as that link goes...i've already checked it b4 u guys mentioned it... as it is provided right there in the tutorial i've provided link of...
    and i've tried my options b4 making use of this forum...and i didnt find a solution that's why i'm taking ur help..
    nevertheless...i repeat my question...
    there's a tutorial at this link...[http://www.netbeans.org/kb/docs/java/gui-db.html]...in it is described how to create a java desktop database applicaiton...
    at the end of the tuorial there is a section called: "Building and Deploying the Application"
    in that section they have instructed to exit netbeans IDE and try and run the application outside it...which is not happening
    the reason they say is that i've to start Java DB from outside of the IDE...that is wat my problem is ..
    i dont know how to start Java DB from outside the Netbeans ide...You are not telling us anything.
    If I tell you "my automobile doesn't work" how do you know what is wrong. Instead I need to tell you one of the following.
    1. The engine didn't start.
    2. The wheel fell off.
    3. The engine caught fire.
    4. When I went to the driveway the car wasn't even there.
    When you "run" something then something happens. When I run notepad from a console window if notepad is not in the path then I will get an error about command not found. if it is in the path then the command executes and notepad pops up. Even if I don't see notepad pop up I know that the command seemed to execute from the command window.
    The above are examples of describing what you did and what did happen. In detail.
    "It doesn't work" provides neither detail about how you ran it nor what did happen when you did attempt to run it.

Maybe you are looking for

  • Custom Calculation Script Pop-up Window If Statement

    I have a field that will be marked with a 1 or a 0 like below: if(Field1 == true) { event.value = "1"; } else { event.value = "0"; If the field I equals "1" then how do I put it in other fields: var RM = this.getField("TRA").value; if(RM >= 4.51 && U

  • Traffic shaping G723 traffic between 2 companies

    Hi, Can someone put me on the right way to implement traffic shaping (QoS) for G723 traffic. Situation: Two companies connected to each other with a vpn tunnel. The hardware is Cisco 2621xm at the sublocation and on the hq location is an 2651XM. Ther

  • How can I measure the time difference between spikes (interspik​e intervals)

    I have used NI USB-6008 (DAQ) to sample a continous signal, after sampling I compared the amplitude of the resulted signal with a value. If the amplitude is greater than a specific value (threshold) then it can pass. Now I want to measure the time di

  • Firefox using too much memory after an update

    Since I updated to firefox 14, it started using WAY too much memory, which is 2GB+. This has never happened to me, and none of the solutions on the website have helped me. It starts off normally at about 80 MBs and then starts growing and growing. I

  • Front Operation Buttons not functioning - Portege M500

    Hi everyone, I would like to ask something regarding the Front Operation Buttons on my Protege M500 laptop. They are the 6 buttons above the keyboard which can lead me to the Internet Explorer, CD/DVD, Windows Media Player Play/Stop/Previous/Next. Th