Uniflow deployment returns 0x800704ec

We're trying to deploy a uniflow printqueue (It's configured with a NUL; port), but doing so with a GPO (shared printer) returns: Group Policy object did not apply because it failed with error code 0x800704ec.
This program is blocked by group policy.
So far we've tested the following:
Deploying the driver with dummy printer - Success
Deploying a NUL; port on a dummy printer - Success
Deploying any other printer on the print server - Success
We've checked any GPO that might restrct access, but we're not able to find anything that deny this printer from being deployed.
Any help is appreciated.

Below thread might be helpful,
http://social.technet.microsoft.com/Forums/en-US/d451a1df-2283-4095-8408-e6b3598f9700/group-policy-object-did-not-apply-because-it-failed-with-error-code-0x800704ec?forum=winserverGP
Regards,
Gopi
JiJi
Technologies

Similar Messages

  • SSAS Deploy returns error on existing database instead of overwriting

    I am aware that this issue has been discussed before. However I have not found a satisfactory answer. I occasionally run into this issue: I have a deployed SSAS database on the server from a project in SSDT. I open the project again at a later
    time in SSDT, make some changes such as adding a new attribute to a dimension and deploy with the same name. I get a metadata engine error "Errors in the metadata manager. The database with the name of 'XYZ' already exists in the 'SERVER' server.".
     Please note that unlike commonly discussed scenarios, I have not renamed anything. The Database Name property in SSDT matches exactly both the Name and ID properties on the server, and the Deploy Changes Only property is set in SSDT. Why doesn't it
    see that I want to overwrite, or at least ask me whether I want to overwrite? Since the ID and Name properties on the server are derived from the Database Name property in SSDT, it is clear I want to overwrite?
    I know I can delete the database on the server and deploy successfully, but I don't want to do this. The only way I found of deploying successfully without deleting the database on the server is to change the Database Name property in SSDT (e.g.
    by adding a 2 to the original name) then deploy, rename back to the original name then deploy with overwriting, then delete the renamed one from the server.
    The fact that I can circumvent the error in this way surely proves the current functionality is a bug?
    Charles
    Charles Kangai, MCT

    Hi Charles,
    For the error message "Errors in the metadata manager. The database with the name of '' already exists in the '' server",
    generally there are two reason that can cause this issue.
    Deploy this solution to a different name than your existing database.
    Rename the previous database before deploying the new version with the new cube
    Please refer to the link below to see the detail information.
    http://geekswithblogs.net/darrengosbell/archive/2008/09/28/ssas-deploying-to-renamed-databases.aspx 
    Hope this helps.
    Regards,
    Charlie Liao
    If you have any feedback on our support, please click
    here.
    Charlie Liao
    TechNet Community Support

  • Planning Application 11.1.2 Cannot Deploy Application from Workspace

    Hi All,
              Everytime I try to deploy a Planning EPMA app, I've got the following error :
    Error Reported:
    HTTP/1.1 500 Internal Server Error
    Action aborted.
    Log file Says nothing but:
    HTTP/1.1 500 Internal Server Error
           The valdation run as well without any issue, but the deployment returns this error.
           Does anyone could help me on that ?
    My Environment:
    Hyperion: 11.1.2
    OS: Linux Red Hat 5 64bits
    DB : Oracle
    IIS6
    Thanks

    Hi Celvin
    I see this article on KB after reading DattaRay's commend. It suggests that Essbase Studio should be installed for Essbase applications to be deployed.
    Validation of Essbase EPMA Application Results in Error "Status: 500 - Internal Server Error" (Doc ID 1350014.1)

  • Error in deploying a web service from jdeveloper 10 to weblogic 10

    hi , I succeed to create connexiion to weblogic 10 from jdeveloper 10 but in deploying my service i have this Exception:
    ---- Deployment started. ---- 1 mai 2009 09:21:45
    Target platform is WebLogic Server 9.x (webAppli).
    Checking weblogic.xml for completeness...
    Wrote WAR file to D:\jdevstudio10134\jdev\mywork\Soustraction\SoustarctionWS\deploy\WebServices.war
    Wrote EAR file to D:\jdevstudio10134\jdev\mywork\Soustraction\SoustarctionWS\deploy\Soustraction-SoustarctionWS-WS.ear
    D:\jdevstudio10134\jdk\jre\bin\javaw.exe -classpath C:\bea\wlserver_10.3\server\lib\wlclient.jar weblogic.Deployer -adminurl http://aymen:7001 -user weblogic -password **** -debug -verbose -deploy -upload -source D:\jdevstudio10134\jdev\mywork\Soustraction\SoustarctionWS\deploy\Soustraction-SoustarctionWS-WS.ear -name Soustraction-SoustarctionWS-WS
    weblogic.Deployer invoked with options: -adminurl http://aymen:7001 -user weblogic -debug -verbose -deploy -upload -source D:\jdevstudio10134\jdev\mywork\Soustraction\SoustarctionWS\deploy\Soustraction-SoustarctionWS-WS.ear -name Soustraction-SoustarctionWS-WS
    WebLogicDeploymentManagerImpl.<init>():103 : Constructing DeploymentManager for J2EE version V1_4 deployments
    WebLogicDeploymentManagerImpl.getNewConnection():146 : Connecting to admin server at aymen:7001, as user weblogic
    ServerConnectionImpl.getEnvironment():282 : setting environment
    ServerConnectionImpl.getEnvironment():285 : getting context using http://aymen:7001
    ServerConnectionImpl.close():328 : Closing DM connection
    ServerConnectionImpl.close():348 : Unregistered all listeners
    weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 'http://aymen:7001': Destination unreachable; nested exception is:
    java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'aymen' and port: '7001' a WebLogic Server?; No available router to destination. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.
    at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:306)
    at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:143)
    at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:93)
    at weblogic.utils.compiler.Tool.run(Tool.java:158)
    at weblogic.utils.compiler.Tool.run(Tool.java:115)
    at weblogic.Deployer.run(Deployer.java:70)
    at weblogic.Deployer.main(Deployer.java:54)
    Caused by: javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException
    at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:121)
    at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:84)
    at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:425)
    at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:287)
    ... 6 more
    Caused by: weblogic.deploy.api.spi.exceptions.ServerConnectionException
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:142)
    at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:148)
    at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:118)
    ... 9 more
    Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: http://aymen:7001: Destination unreachable; nested exception is:
    java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'aymen' and port: '7001' a WebLogic Server?; No available router to destination]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:48)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:739)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:343)
    at weblogic.jndi.Environment.getContext(Environment.java:263)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:167)
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getContext(ServerConnectionImpl.java:324)
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getEnvironment(ServerConnectionImpl.java:296)
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:140)
    ... 11 more
    Caused by: java.net.ConnectException: http://aymen:7001: Destination unreachable; nested exception is:
    java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'aymen' and port: '7001' a WebLogic Server?; No available router to destination
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:137)
    at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:324)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:319)
    ... 16 more
    Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'aymen' and port: '7001' a WebLogic Server?; No available router to destination
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:465)
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:316)
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:255)
    at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:199)
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:220)
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:187)
    ... 21 more
    **** weblogic.deploy returned with non-zero exit status: 1
    **** weblogic.deploy returned with non-zero exit status: 1
    Elapsed time for deployment: 2 seconds
    #### Deployment incomplete. #### 1 mai 2009 09:21:47
    please someone help me.
    thank you
    aymen

    Hi Wenhao,
    I did face something similar ....but when i tried it again...it worked..
    In case it does not then before u try to start the procedure to dwnld the Enterprise service wsdl....
    uncheck the wsdl validator check box in NWDS...
    I suggest u first try to consume the wsdl by importing it locally...
    just follow this blog by Boris step by step..
    /people/boris.mohr/blog/2007/01/23/how-to-guide-for-consuming-a-web-service-with-a-standalone-client-using-sap-netweaver-application-server-javatm-ee-5-edition
    Once u r able to do this..then u can try to consume it from service registry
    Edited by: Mohd Tauseef Ibrahim on Jun 26, 2008 2:28 PM
    Edited by: Mohd Tauseef Ibrahim on Jun 26, 2008 2:30 PM

  • Error while deploying to a new connection

    java.lang.NoClassDefFoundError: weblogic/Deployer
    Exception in thread "main" **** weblogic.deploy returned with non-zero exit status: 1
    ruchi

    We need more details on what you are trying to deploy to which platform and the full error stack.

  • Deploying a web service to WebLogic 7 - error with RemoteDispatcherBean

    Hi there,
    I have just created a web service through WebLogic Workshop. The web service can be tested through the workshop and it works fine
    I am trying now to deploy it to a development server, and I am having the following error:
    preparing application <appName> on mope
    Exception caught for task Activate application <appName> on mope: Prepare failed. Task Id = 1
    Module, AP_NotificationEJB.jar, reported error: Exception preparing module: EJBModule(AP_NotificationEJB.jar,status=NEW)
    Unable to deploy EJB: C:\bea\<deploymentPath>\.wlnotdelete\<appName>\AP_NotificationEJB.jar from AP_NotificationEJB.jar:
    weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: weblogic.knex.bean.RemoteDispatcherBean
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:440)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:165)
         at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfo(EJBDeployer.java:965)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1276)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:235)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1742)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:745)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:559)
         at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1116)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:784)
         at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:251)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:219)
    Looking inside the EAR I generated (using jwsCompile), I can find several classes RemoteDispatchBean_bu6zup_....class but no RemoteDispatchBean.class file anywhere
    Am I doing anything wrong to generate the EAR file? Anything fancy I need to include to my jws file or any descriptor?
    Any idea or suggestion would be much appreciated
    Thank you,
    Miguel

    We have found a work around for that specific problem.
    We have included the whole knex library within our libs folder. Now we can deploy the Web services as a web application to the webLogic, The deployment returns successful, but any time we initiate the server, there is another ClassNotFoundException. This time the missing class is weblogic.knex.bean.DeploymentListener.
    The strange thing is that that specific class is part of the knex.jar library we have included within our libs folder ...
    It seems that the folder is not read from the server when starting, but it is read when executing the application.
    Any suggestion to this nonsense?
    Thanks,
    Miguel

  • Deploying jdev appln to weblogic-Errors !Help Resolve

    while creating a new connection and deploying to it am gettin th following error
    Java Virtual Machine Launcher :Could not find the main class
    java.lang.NoClassDefFoundError: weblogic/Deployer
    Exception in thread "main" **** weblogic.deploy returned with non-zero exit status: 1
    **** weblogic.deploy returned with non-zero exit status: 1

    The weblogic.Deployer class is in the weblogic.jar file.
    Is the weblogic.jar in the Classpath. Also, add <J2SDK>/lib/tools.jar to the classpath which has the main class.
    thanks,
    Deepak

  • Weblogic deployment errors

    When I try to deploy to a (successfully) tested weblogic connection I get the following:
    Sending EAR file to remote WebLogic server...
    C:\jdeveloper\jdk\jre\bin\javaw.exe -Ddeploy.debug=true -classpath C:\bea\weblogic700\server\lib\weblogic.jar weblogic.deploy -host apo -port 7001 -debug deploy iais file:/C:/jdeveloper/jdev/mywork/Workspace1/IAIS/iais.ear
    You must specify at least a name and a source when deploying
    Usage: java weblogic.deploy [options] list password {name} {source}
    Note: when using 'deploy', if the source is specified, the server assumes a new deployment. For updates, use 'update'. If -url is specified, then -host and -port are ignored.
    where options include:
    -help Print this help message.
    -version Print version information.
    -port <port> The port to connect on, default is 7001.
    -host <host> The host to connect to, default is localhost.
    -url <url> The admin server to connect to, default is
    t3://localhost:7001
    -username <username> The username to connect with.
    -component Component to be deployed on various targets,
    must be specified as [<component
    name>:Target1,Target2]...component
    corresponds to the Name attribute for the
    component MBean. If you are deploying a new
    application or standalone component,
    component is the name of the .jar/.war/etc.
    minus the .jar/.war suffix.
    -jspRefreshFiles <file1.jsp,file2.html,file3.gif,...> This option is only used with the refresh
    flag. This is the list of files that are to
    be refreshed. Any static file type may be
    refreshed. (jsp, gif, jpeg, html, etc).
    .class files may not be refreshed. To update
    class files, please use the update flag to
    redeploy your application. This must be
    specified as a comma separated list.
    -jspRefreshComponentName <jspRefreshComponentName> This option is only used with the refresh
    flag. The name of the component that contains
    the files being refreshed.
    -debug If set, detailed debug information is
    printed.
    **** weblogic.deploy returned with non-zero exit status: 1
    #### Deployment incomplete. #### Jun 11, 2002 9:36:11 AM
    From what I see, it has both a name and a source. The help indicates that the username/password is not required, and so I omitted it. I really need to get this working without a username/password, as my systems folks don't want the developers to have the console password for the weblogic server.

    When I try to deploy to a (successfully) tested weblogic connection I get the following:
    Sending EAR file to remote WebLogic server...
    C:\jdeveloper\jdk\jre\bin\javaw.exe -Ddeploy.debug=true -classpath C:\bea\weblogic700\server\lib\weblogic.jar weblogic.deploy -host apo -port 7001 -debug deploy iais file:/C:/jdeveloper/jdev/mywork/Workspace1/IAIS/iais.ear
    You must specify at least a name and a source when deploying
    Usage: java weblogic.deploy [options] list password {name} {source}
    Note: when using 'deploy', if the source is specified, the server assumes a new deployment. For updates, use 'update'. If -url is specified, then -host and -port are ignored.
    where options include:
    -help Print this help message.
    -version Print version information.
    -port <port> The port to connect on, default is 7001.
    -host <host> The host to connect to, default is localhost.
    -url <url> The admin server to connect to, default is
    t3://localhost:7001
    -username <username> The username to connect with.
    -component Component to be deployed on various targets,
    must be specified as [<component
    name>:Target1,Target2]...component
    corresponds to the Name attribute for the
    component MBean. If you are deploying a new
    application or standalone component,
    component is the name of the .jar/.war/etc.
    minus the .jar/.war suffix.
    -jspRefreshFiles <file1.jsp,file2.html,file3.gif,...> This option is only used with the refresh
    flag. This is the list of files that are to
    be refreshed. Any static file type may be
    refreshed. (jsp, gif, jpeg, html, etc).
    .class files may not be refreshed. To update
    class files, please use the update flag to
    redeploy your application. This must be
    specified as a comma separated list.
    -jspRefreshComponentName <jspRefreshComponentName> This option is only used with the refresh
    flag. The name of the component that contains
    the files being refreshed.
    -debug If set, detailed debug information is
    printed.
    **** weblogic.deploy returned with non-zero exit status: 1
    #### Deployment incomplete. #### Jun 11, 2002 9:36:11 AM
    From what I see, it has both a name and a source. The help indicates that the username/password is not required, and so I omitted it. I really need to get this working without a username/password, as my systems folks don't want the developers to have the console password for the weblogic server.

  • Deploying to weblogic 6.1

    Hi
    I am trying to deploy web application created in jdeveloper to weblogic 6.1,
    successfully able to connect to weblogic but when i try to deploy the application to the the weblogic connection i get the following error
    ---- Deployment started. ---- May 4, 2004 2:50:29 PM
    Checking weblogic.xml for completeness...
    Wrote WAR file to C:\oracle\ora92\jdev\mywork\Workspace16\Project1\deploy\webapp5.war
    Wrote EAR file to C:\oracle\ora92\jdev\mywork\Workspace16\Project1\deploy\webapp5.ear
    java.lang.NullPointerException
         void java.io.File.<init>(java.lang.String)
              File.java:180
         void oracle.jdevimpl.deploy.Wl6CommandLine.deployEar(java.net.URL, java.lang.String, java.lang.String)
              Wl6CommandLine.java:73
         void oracle.jdevimpl.deploy.WlRemoteDeployer.deploy(oracle.jdevimpl.deploy.DeployShell)
              WlRemoteDeployer.java:67
         void oracle.jdevimpl.deploy.DynamicDeployer.deploy(oracle.jdevimpl.deploy.DeployShell)
              DynamicDeployer.java:53
         void oracle.jdevimpl.deploy.BatchDeployer.deploy(oracle.jdevimpl.deploy.DeployShell)
              BatchDeployer.java:46
         void oracle.jdevimpl.deploy.DynamicDeployer.deploy(oracle.jdevimpl.deploy.DeployShell)
              DynamicDeployer.java:53
         void oracle.jdevimpl.deploy.J2eeProfileDt$CleanupTransientProfilesDeployer.deploy(oracle.jdevimpl.deploy.DeployShell)
              J2eeProfileDt.java:122
         void oracle.jdevimpl.deploy.FinalDeployer.deploy(oracle.jdevimpl.deploy.DeployShell)
              FinalDeployer.java:44
         void oracle.jdevimpl.deploy.AsyncDeployer$1.runImpl()
              AsyncDeployer.java:63
         void oracle.jdevimpl.deploy.AsyncDeployer$1.run()
              AsyncDeployer.java:49
    Elapsed time for deployment: 8 seconds
    #### Deployment incomplete. #### May 4, 2004 2:50:37 PM
    Any Idea ?
    Thanks
    Dolphy

    now i am getting the following error for deploy
    ---- Deployment started. ---- May 4, 2004 3:34:44 PM
    Checking weblogic.xml for completeness...
    Wrote WAR file to C:\oracle\ora92\jdev\mywork\Workspace17\Project1\deploy\webapp6.war
    Wrote EAR file to C:\oracle\ora92\jdev\mywork\Workspace17\Project1\deploy\webapp6.ear
    Making sure that the 'webapp6' application doesn't exist on the server...
    C:\oracle\ora92\jdk\jre\bin\javaw.exe -classpath C:\BEA\wlserver6.1\lib\weblogic.jar weblogic.deploy -username system -host 149.21.33.90 -port 7001 delete **** webapp6
    java.lang.NoClassDefFoundError: weblogic/deploy
    Exception in thread main
    Sending EAR file to remote WebLogic server...
    C:\oracle\ora92\jdk\jre\bin\javaw.exe -Ddeploy.debug=true -classpath C:\BEA\wlserver6.1\lib\weblogic.jar weblogic.deploy -username system -host 149.21.33.90 -port 7001 -debug -component webapp6:myserver deploy **** webapp6 file:/C:/oracle/ora92/jdev/mywork/Workspace17/Project1/deploy/webapp6.ear
    java.lang.NoClassDefFoundError: weblogic/deploy
    Exception in thread main
    **** weblogic.deploy returned with non-zero exit status: 1
    **** weblogic.deploy returned with non-zero exit status: 1
    Elapsed time for deployment: 16 seconds
    #### Deployment incomplete. #### May 4, 2004 3:35:01 PM

  • Trouble deploying application in Tomcat!

    When I try to open the deployed application in the TomCat webserver, it throws a HTTP 404 error!
    However, the same application is working fine in NetBeans, which has a bundled TomCat server!
    Where am I going wrong? The applications that come with Tomcat are working fine, but no matter whatever appl I deploy, it isnt working!

    First, thanks for the suggestions Nick! And I have tried each of these steps you mentioned!
    1) Check your app is deployed and running in Tomcat Web Application Manager. -- YES, IT IS! I CAN SEE THE APPLICATION, RELOAD IT, STOP IT, ETC!
    2) If not deployed, check log file in logs\stdout.log to find out why it didn't deploy. (How are you deploying? Copying the war file across to \webapps?) - I TRIED DEPLOYING THE WAR FILE, THEN I DEPLOYED AN APPL CREATING THE DIRECTORY STRUCTURE, ETC! STILL NO LUCK!
    3) Make sure you're definitely hitting the correct URL (including the context path, which should also be shown in Web Application Manager) - OF COURSE I AM; EVERY APPL I DEPLOY RETURNS 404! THE NATIVE APPLICATIONS HOWEVER WORK FINE
    4) Can you deploy and run any apps in your standalone Tomcat instance? - I DIDNT GET THIS BUT AN APPL WHICH WORKS PERFECTLY FINE IN NETBEANS, ISNT WORKING IN THE STANDALONE TOMCAT!
    5) Try deploying a really simple app to see if that works. - DID & FAILED!

  • Javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException

    Hi,
    i'm trying to deploy an J2ee application with adf libraries in a Weblogic Server 9.2 with SOA Suite. My application was developed in JDeveloper 10.1.3.3. in Windows XP. My application server is in Linux RedHat 5 Enterprise. In Jdeveloper, when i tried to deploy my application I got the next log:
    ---- Deployment started. ---- Aug 17, 2009 3:39:17 PM
    Target platform is WebLogic Server 9.x (weblogic).
    Checking weblogic.xml for completeness...
    Wrote WAR file to C:\jd\jdev\mywork\ECSBPM\ViewController\deploy\ECSBPM.war
    Wrote EAR file to C:\jd\jdev\mywork\ECSBPM\ViewController\deploy\ECSBPM.ear
    java -classpath C:\jd\jdev\mywork\weblogic.jar weblogic.Deployer -adminurl http://10.10.1.190:8001 -user weblogic -password **** -debug -verbose -deploy -upload -source C:\jd\jdev\mywork\ECSBPM\ViewController\deploy\ECSBPM.ear -name ECSBPM
    weblogic.Deployer invoked with options: -adminurl http://10.10.1.190:8001 -user weblogic -debug -verbose -deploy -upload -source C:\jd\jdev\mywork\ECSBPM\ViewController\deploy\ECSBPM.ear -name ECSBPM
    [WebLogicDeploymentManagerImpl.<init>():103] : Constructing DeploymentManager for J2EE version V1_4 deployments
    [WebLogicDeploymentManagerImpl.getNewConnection():146] : Connecting to admin server at 10.10.1.190:8001, as user weblogic
    [ServerConnectionImpl.getEnvironment():288] : setting environment
    [ServerConnectionImpl.getEnvironment():291] : getting context using http://10.10.1.190:8001
    [ServerConnectionImpl.close():334] : Closing DM connection
    [ServerConnectionImpl.close():354] : Unregistered all listeners
    weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 'http://10.10.1.190:8001': invalid type code: 31. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.
         at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:314)
         at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:137)
         at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
         at weblogic.utils.compiler.Tool.run(Tool.java:158)
         at weblogic.utils.compiler.Tool.run(Tool.java:115)
         at weblogic.Deployer.run(Deployer.java:70)
         at weblogic.Deployer.main(Deployer.java:54)
    Caused by: javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException
         at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:121)
         at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:84)
         at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:482)
         at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:295)
         ... 6 more
    Caused by: weblogic.deploy.api.spi.exceptions.ServerConnectionException
         at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:143)
         at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:148)
         at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:118)
         ... 9 more
    Caused by: javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: failed to unmarshal class weblogic.security.acl.internal.AuthenticatedUser; nested exception is:
         java.io.StreamCorruptedException: invalid type code: 31]
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:85)
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:41)
         at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:773)
         at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:673)
         at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:466)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:373)
         at weblogic.jndi.Environment.getContext(Environment.java:307)
         at weblogic.jndi.Environment.getContext(Environment.java:277)
         at weblogic.jndi.Environment.createInitialContext(Environment.java:200)
         at weblogic.jndi.Environment.getInitialContext(Environment.java:184)
         at weblogic.jndi.Environment.getInitialContext(Environment.java:162)
         at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getContext(ServerConnectionImpl.java:330)
         at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getEnvironment(ServerConnectionImpl.java:302)
         at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:141)
         ... 11 more
    Caused by: java.rmi.UnmarshalException: failed to unmarshal class weblogic.security.acl.internal.AuthenticatedUser; nested exception is:
         java.io.StreamCorruptedException: invalid type code: 31
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:223)
         at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:224)
         at weblogic.common.internal.RMIBootServiceImpl_923_WLStub.authenticate(Unknown Source)
         at weblogic.security.acl.internal.Security$1.run(Security.java:185)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.security.acl.internal.Security.authenticate(Security.java:181)
         at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRemotely(WLInitialContextFactoryDelegate.java:734)
         at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:667)
         ... 21 more
    Caused by: java.io.StreamCorruptedException: invalid type code: 31
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.readObject(Unknown Source)
         at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
         at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
         at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:191)
         at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:221)
         ... 29 more
    **** weblogic.deploy returned with non-zero exit status: 1
    **** weblogic.deploy returned with non-zero exit status: 1
    Elapsed time for deployment: 17 seconds
    #### Deployment incomplete. #### Aug 17, 2009 3:39:34 PM
    ---- Deployment started. ---- Aug 17, 2009 3:39:17 PM
    Target platform is WebLogic Server 9.x (weblogic).
    Checking weblogic.xml for completeness...
    Wrote WAR file to C:\jd\jdev\mywork\ECSBPM\ViewController\deploy\ECSBPM.war
    Wrote EAR file to C:\jd\jdev\mywork\ECSBPM\ViewController\deploy\ECSBPM.ear
    java -classpath C:\jd\jdev\mywork\weblogic.jar weblogic.Deployer -adminurl http://10.10.1.190:8001 -user weblogic -password **** -debug -verbose -deploy -upload -source C:\jd\jdev\mywork\ECSBPM\ViewController\deploy\ECSBPM.ear -name ECSBPM
    weblogic.Deployer invoked with options: -adminurl http://10.10.1.190:8001 -user weblogic -debug -verbose -deploy -upload -source C:\jd\jdev\mywork\ECSBPM\ViewController\deploy\ECSBPM.ear -name ECSBPM
    [WebLogicDeploymentManagerImpl.<init>():103] : Constructing DeploymentManager for J2EE version V1_4 deployments
    [WebLogicDeploymentManagerImpl.getNewConnection():146] : Connecting to admin server at 10.10.1.190:8001, as user weblogic
    [ServerConnectionImpl.getEnvironment():288] : setting environment
    [ServerConnectionImpl.getEnvironment():291] : getting context using http://10.10.1.190:8001
    [ServerConnectionImpl.close():334] : Closing DM connection
    [ServerConnectionImpl.close():354] : Unregistered all listeners
    weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 'http://10.10.1.190:8001': invalid type code: 31. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.
         at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:314)
         at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:137)
         at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
         at weblogic.utils.compiler.Tool.run(Tool.java:158)
         at weblogic.utils.compiler.Tool.run(Tool.java:115)
         at weblogic.Deployer.run(Deployer.java:70)
         at weblogic.Deployer.main(Deployer.java:54)
    Caused by: javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException
         at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:121)
         at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:84)
         at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:482)
         at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:295)
         ... 6 more
    Caused by: weblogic.deploy.api.spi.exceptions.ServerConnectionException
         at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:143)
         at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:148)
         at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:118)
         ... 9 more
    Caused by: javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: failed to unmarshal class weblogic.security.acl.internal.AuthenticatedUser; nested exception is:
         java.io.StreamCorruptedException: invalid type code: 31]
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:85)
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:41)
         at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:773)
         at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:673)
         at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:466)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:373)
         at weblogic.jndi.Environment.getContext(Environment.java:307)
         at weblogic.jndi.Environment.getContext(Environment.java:277)
         at weblogic.jndi.Environment.createInitialContext(Environment.java:200)
         at weblogic.jndi.Environment.getInitialContext(Environment.java:184)
         at weblogic.jndi.Environment.getInitialContext(Environment.java:162)
         at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getContext(ServerConnectionImpl.java:330)
         at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getEnvironment(ServerConnectionImpl.java:302)
         at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:141)
         ... 11 more
    Caused by: java.rmi.UnmarshalException: failed to unmarshal class weblogic.security.acl.internal.AuthenticatedUser; nested exception is:
         java.io.StreamCorruptedException: invalid type code: 31
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:223)
         at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:224)
         at weblogic.common.internal.RMIBootServiceImpl_923_WLStub.authenticate(Unknown Source)
         at weblogic.security.acl.internal.Security$1.run(Security.java:185)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.security.acl.internal.Security.authenticate(Security.java:181)
         at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRemotely(WLInitialContextFactoryDelegate.java:734)
         at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:667)
         ... 21 more
    Caused by: java.io.StreamCorruptedException: invalid type code: 31
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.readObject(Unknown Source)
         at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
         at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
         at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:191)
         at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:221)
         ... 29 more
    **** weblogic.deploy returned with non-zero exit status: 1
    **** weblogic.deploy returned with non-zero exit status: 1
    Elapsed time for deployment: 17 seconds
    #### Deployment incomplete. #### Aug 17, 2009 3:39:34 PM
    I verified and my credentials are correct. Please your help.
    Thanks
    Eve

    Hi,
    I hope you are deploying application through build file.
    Can you check build.xml file whether you had given correct Admin url and port number.
    Regards,
    Kal
    Edited by: kalyan Pasupuleti on Sep 12, 2012 1:39 AM

  • Trouble deploying hotbids in bc4jauctions

    I am following the tutorial (bc4jauctions.html) with the intent of testing out the bc4j auctions example. I have populated the auctions tables, and have compiled the respective projects. I am now trying to deploy the hotbids.jpr project, but
    Has anyone succesfully deployed this on NT? Please let me know what I am doing wrong.
    The error I get at deployment time is:
    Exhausted Resultset
    and the deployment log shows the following:
    java.sql.SQLException: Exhausted Resultset
    void oracle.jdbc.dbaccess.DBError.throwSqlException(java.lang.String, java.lang.String, int)
    void oracle.jdbc.dbaccess.DBError.throwSqlException(int, java.lang.Object)
    void oracle.jdbc.dbaccess.DBError.throwSqlException(int)
    void oracle.jdbc.driver.OracleStatement.prepare_for_new_get(boolean, int)
    java.lang.String oracle.jdbc.driver.OracleStatement.getStringValue(boolean, int)
    java.lang.String oracle.jdbc.driver.OracleResultSetImpl.getString(int)
    void oracle.jdeveloper.deployment.model.JServerDepModel.deploy()
    void oracle.jdeveloper.deployment.model.SPDepModel.deploy()
    void oracle.jdeveloper.deployment.ui.DeploymentMonitor.run()
    void oracle.jdeveloper.wizard.common.ProgressDialog.run()
    void java.lang.Thread.run()
    null

    First, thanks for the suggestions Nick! And I have tried each of these steps you mentioned!
    1) Check your app is deployed and running in Tomcat Web Application Manager. -- YES, IT IS! I CAN SEE THE APPLICATION, RELOAD IT, STOP IT, ETC!
    2) If not deployed, check log file in logs\stdout.log to find out why it didn't deploy. (How are you deploying? Copying the war file across to \webapps?) - I TRIED DEPLOYING THE WAR FILE, THEN I DEPLOYED AN APPL CREATING THE DIRECTORY STRUCTURE, ETC! STILL NO LUCK!
    3) Make sure you're definitely hitting the correct URL (including the context path, which should also be shown in Web Application Manager) - OF COURSE I AM; EVERY APPL I DEPLOY RETURNS 404! THE NATIVE APPLICATIONS HOWEVER WORK FINE
    4) Can you deploy and run any apps in your standalone Tomcat instance? - I DIDNT GET THIS BUT AN APPL WHICH WORKS PERFECTLY FINE IN NETBEANS, ISNT WORKING IN THE STANDALONE TOMCAT!
    5) Try deploying a really simple app to see if that works. - DID & FAILED!

  • SU DeploymentException - when to throw and when to return a failed status

    When a SUManager's deploy method is invoked and the operation fails is it a matter of preference to throw a DeploymentException with a XML message containing the component-task-result like the ri-component examples do or to simply return a XML message containing the component-task-result with a status of failure for the operation?

    The general rule is to have the SUM.deploy() method return an XML result/status string (as defined in section 6.9). This produces a structured result that is returned to the admin tool, allowing it to produce a detailed, human-friendly error message.
    Alternatively a DeploymentException can be thrown. I am not aware of any circumstances where this must be used instead of the return value to indicate a deploy() failure, but if memory serves the RI team had identified some corner case where such an exception was considered necessary. If you wish, I can follow up with them to get some details.
    Regardless of whether the SUM.deploy() returns a result/status with an ERROR result or if it throws an exception, the DeploymentServiceMBean supplied by the JBI implementation must return a result/status string for the service assembly deployment, throwing an exception only if the entire SA fails to deploy. A result/status string produced from a SUM.deploy DeploymentException won't contain as much information as a result/status string.

  • How can I use mySQL with OC4J

    Hello,
    I have standalone OC4J and I want to use mySQL database (Oracle is no problem). My data-sources.xml for application (not global data-sources) is:
    <data-sources>
    <data-source class="com.evermind.sql.DriverManagerDataSource"
         connection-driver="org.gjt.mm.mysql.Driver"
         ejb-location="jdbc/MG_DBDS"
         inactivity-timeout="30"
         location="jdbc/MG_DBCoreDS"
         name="MG_DBDS"
         password=""
         pooled-location="jdbc/MG_DBPooledDS"
         url="jdbc:mysql://127.0.0.1:3306/test"
         username="root"
         xa-location="jdbc/xa/MG_DBXADS"/>
    </data-sources>
    Deploy return me:
    Error initializing data-source 'jdbc/MG_DBCoreDS': DriverManagerDataSource driver 'org.gjt.mm.mysql.Driver' not found
    Then I run this command:
    java -jar %OC4J_HOME%\admin.jar ormi://192.168.1.14:23791/ admin heslo -application Register -updateDataSource -oldLocation jdbc/MG_DBCoreDS -jar mysql-2.0.11-bin.jar
    this action is success and create in OC4J folder lib with jar file mysql-2.0.11-bin.
    When I use this configuration in application, I get connection but creating Statement cause SQL Exception - No suitable driver.
    When I try to restart OC4J, I get the same message as throught deploy - Error initializing data-source ...
    What is go wrong???? Could me help anyone?
    Thanks
    Libor

    pooling solution:
    1) put driver mysql.jar into any directory wich described in OC4J application.xml file like
    " <library path="D:\j2ee\home\lib">jdev-generated</library>"
    2) put a new datasource in data-sources.xml:
    <data-sources>
    <data-source name="MySqlDS"
    location="jdbc/MySqlDS"
    class="com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource"
    max-connections="100"
    min-connections="5"
    inactivity-timeout="200"
    wait-timeout="10"
    username="scott"
    password="tiger"
    url="jdbc:mysql://localhost:3306/oln?useUnicode=true"/>
    </data-sources>
    OC4J needs a special pooling class in comparision with other containers. For example, JBoss has own implementation of pooling broker, so pooling is enabled by default.

  • I need Fusion help creating a demo of BRM JCA Resource Adapter

    I need Fusion help creating a demo of BRM JCA Resource Adapter.
    I know BRM well but am clueless with Fusion.
    I am trying to figure out what Fusion products to download and install and how I manipulate the Fusion side to manipulate BRM.
    My BRM docs say:
    Installing the BRM JCA Resource Adapter ->
    Software requirements
    (yada yada install a bunch of BRM stuff I know how to do)
    The adapter must be deployed on a J2EE 1.4-compliant application server that has implemented the JCA 1.5 specification. The adapter runs only in a managed environment. (Does this imply some particular Fusion package?)
    (more yada yada about installing more BRM packages I know how to do)
    Deploying and configuring the BRM JCA Resource Adapter ->
    Overview of the BRM JCA Resource Adapter configuration procedure
    The procedure for setting up the BRM JCA Resource Adapter includes the following tasks:
    Installing the adapter on your BRM system, if you have not already done so. See Installing the BRM JCA Resource Adapter.
    Generating the schema files for the adapter. See Generating the schema files for your system. (links to some BRM commands np)
    Specifying how to construct XML tags. See Specifying the XML tags for extended fields. (links to an oob file included with directions on how to address BRM customizations np)
    Generating the WSDL files for the adapter. See Generating the WSDL files for your system. (links to an oob file with directions to configure. I could use some help if/when I get this far)
    The last two look pretty important but I haven't a clue. I pasted the text from the docs below.
    Deploying the adapter on your application server. See Deploying the BRM JCA Resource Adapter on an Oracle application server.
    Connecting the adapter to the BRM software. See Connecting the adapter to BRM in Oracle AS.
    Deploying the BRM JCA Resource Adapter on an Oracle application server
    The adapter is dependent on Java Archive (JAR) files to deploy properly. The following table lists the JAR files that the adapter requires from each application in your system.
    Application
    JAR files
    J2EE application server
    classes12.jar, connector15.jar, and jta.jar
    Oracle BPEL process
    bpm-infra.jar, orabpel-thirdparty.jar, orabpel.jar, and xmlparserv2.jar
    BRM J2EE Resource Adapter
    pcm.jar and pcmext.jar
    Apache
    xercesImpl.jar
    If you are deploying the adapter in a standalone Oracle Containers for Java EE (OC4J) instance, make sure these JAR files are available to the class loader that is loading the adapter.
    If you are deploying the adapter by using Oracle SOA Suite, these JAR files are available as part of the oracle.bpel.common code source. You import these libraries as follows:
    Open the Oracle_home/j2ee/Instance/config/applications.xml configuration file for the J2EE instance.
    Add the oracle.bpel.common entry (shown in bold below) to the imported-shared-libraries section of the file:
    <imported-shared-libraries>
    <import-shared-library name="adf.oracle.domain"/>
    <import-shared-library name="oracle.bpel.common"/>
    </imported-shared-libraries>
    Save and close the file.
    Restart the application server or the J2EE instance.
    After you make the JAR files available, deploy the adapter on the Oracle application server by using either the Oracle Application Server (Oracle AS) Application Server Control (ASC) or the Oracle admintool.jar file. Copy the adapter archive file (BRM_home/apps/brm_integrations/jca_adapter/OracleBRMJCA15Adapter.rar) from the installation directory to a location that is accessible to the adapter deployment tool. You can then open and deploy the archive file on your application server.
    After successful deployment, return the applications.xml file to its original settings and add the oracle.bpel.common codesource to the BRM Adapter oc4j-ra.xml file:
    Open the Oracle_home/j2ee/Instance/config/applications.xml configuration file for the J2EE instance.
    Remove the following oracle.bpel.common entry (shown in bold below):
    <imported-shared-libraries>
    <import-shared-library name="adf.oracle.domain"/>
    <import-shared-library name="oracle.bpel.common"/>
    </imported-shared-libraries>
    Save and close the file.
    Open the JCA Resource Adapter oc4j-ra.xml file from the Oracle_home/j2ee/Instance/application-deployments/default/BRMAdapterDeploymentName directory.
    Add the oracle.bpel.common entry (shown in bold below) to the oc4j-connector-factories section of the file:
    <oc4j-connector-factories...>
    <imported-shared-libraries>
    <import-shared-library name="oracle.bpel.common"/>
    </imported-shared-libraries>
    <oc4j-connector-factories>
    Save and close the file.
    Restart the application server or the J2EE instance.
    For more information about deploying the adapter, see your application server’s documentation.
    Connecting the adapter to BRM in Oracle AS
    You connect the adapter to the BRM software by creating connection pools and connection factories. As part of the adapter deployment, the application server creates oc4j-ra.xml from the packaged ra.xml. The ra.xml file is located in the Oracle_home/j2ee/Instance/connectors/AdapterDeploymentName/AdapterDeploymentName/META-INF directory. For example, Oracle_home/j2ee/home/connectors/BRMAdapter/BRMAdapter/META-INF/ra.xml.
    Use the resource adapter home page from the Oracle AS ASC page to create connection pools and connection factories.
    Create your connection pool by following the performance and tuning guidelines in Configuring Connection Pooling in OC4J in Oracle Containers for J2EE Resource Adapter Administrator's Guide. See download.oracle.com/docs/cd/B31017_01/web.1013/b28956/conncont.htm.
    Make sure you set the pool’s Maximum Connections parameter (maxConnections XML entity) equal to or greater than the Oracle BPEL process manager’s dspMaxThreads parameter. For more information, see Oracle BPEL Process Manager Performance Tuning in Oracle Application Server Performance Guide for 10g Release 3 (10.1.3.1.0) at download.oracle.com/docs/cd/B31017_01/core.1013/b28942/tuning_bpel.htm.
    Note To set up JCA Resource Adapter transaction management in BPEL, you must create a private connection pool and set its Inactive Connection Timeout property (inactivity-timeout XML entity) to 0. See About JCA Resource Adapter transaction management in BPEL for more information.
    Create as many connection factories as your system needs. For each connection factory, specify the following:
    The JNDI location for the connection factory.
    The connection pool to use.
    How to connect to BRM by using these entries:
    Entry
    Description
    ConnectionString
    Specify the protocol, host name, and port number for connecting to the BRM software. For example: ip Server1 12006.
    DBNumber
    Specify the database number for the BRM database. For example, enter 1 or 0.0.0.1 for database 0.0.0.1.
    InputValidation
    Specifies whether to validate the input XMLRecord:
    True — The adapter validates the input XMLRecord against the opcode schema.
    False — The adapter does not validate the input XMLRecord.
    The default is False.
    This overrides any other validation parameter specified in the WSDL file.
    OutputValidation
    Specifies whether to validate the output XMLRecord:
    True — The adapter validates the output XMLRecord against the opcode schema.
    False — The adapter does not validate the output XMLRecord.
    The default is False.
    This overrides any other validation parameter specified in the WSDL file.
    LoginType
    Specifies the authentication method:
    1 — The adapter logs in to BRM by using the specified login name and password.
    0 — The adapter logs in to BRM by using the specified service type and POID ID.
    The default is 1.
    UserName
    Specifies the login name the adapter uses for logging in to the BRM software.
    Note This entry is required only if LoginType is set to 1.
    Password
    Specify the password the adapter uses for logging in to the BRM software.
    Note This entry is required only if LoginType is set to 1.
    PoidID
    Specifies the POID ID. This entry should be set to 1.
    ServiceType
    Specifies the service the adapter uses to log in to the BRM software.
    The default is /service/pcm_client.
    You have successfully configured the adapter to connect to BRM.

    I need Fusion help creating a demo of BRM JCA Resource Adapter.
    I know BRM well but am clueless with Fusion.
    I am trying to figure out what Fusion products to download and install and how I manipulate the Fusion side to manipulate BRM.
    My BRM docs say:
    Installing the BRM JCA Resource Adapter ->
    Software requirements
    (yada yada install a bunch of BRM stuff I know how to do)
    The adapter must be deployed on a J2EE 1.4-compliant application server that has implemented the JCA 1.5 specification. The adapter runs only in a managed environment. (Does this imply some particular Fusion package?)
    (more yada yada about installing more BRM packages I know how to do)
    Deploying and configuring the BRM JCA Resource Adapter ->
    Overview of the BRM JCA Resource Adapter configuration procedure
    The procedure for setting up the BRM JCA Resource Adapter includes the following tasks:
    Installing the adapter on your BRM system, if you have not already done so. See Installing the BRM JCA Resource Adapter.
    Generating the schema files for the adapter. See Generating the schema files for your system. (links to some BRM commands np)
    Specifying how to construct XML tags. See Specifying the XML tags for extended fields. (links to an oob file included with directions on how to address BRM customizations np)
    Generating the WSDL files for the adapter. See Generating the WSDL files for your system. (links to an oob file with directions to configure. I could use some help if/when I get this far)
    The last two look pretty important but I haven't a clue. I pasted the text from the docs below.
    Deploying the adapter on your application server. See Deploying the BRM JCA Resource Adapter on an Oracle application server.
    Connecting the adapter to the BRM software. See Connecting the adapter to BRM in Oracle AS.
    Deploying the BRM JCA Resource Adapter on an Oracle application server
    The adapter is dependent on Java Archive (JAR) files to deploy properly. The following table lists the JAR files that the adapter requires from each application in your system.
    Application
    JAR files
    J2EE application server
    classes12.jar, connector15.jar, and jta.jar
    Oracle BPEL process
    bpm-infra.jar, orabpel-thirdparty.jar, orabpel.jar, and xmlparserv2.jar
    BRM J2EE Resource Adapter
    pcm.jar and pcmext.jar
    Apache
    xercesImpl.jar
    If you are deploying the adapter in a standalone Oracle Containers for Java EE (OC4J) instance, make sure these JAR files are available to the class loader that is loading the adapter.
    If you are deploying the adapter by using Oracle SOA Suite, these JAR files are available as part of the oracle.bpel.common code source. You import these libraries as follows:
    Open the Oracle_home/j2ee/Instance/config/applications.xml configuration file for the J2EE instance.
    Add the oracle.bpel.common entry (shown in bold below) to the imported-shared-libraries section of the file:
    <imported-shared-libraries>
    <import-shared-library name="adf.oracle.domain"/>
    <import-shared-library name="oracle.bpel.common"/>
    </imported-shared-libraries>
    Save and close the file.
    Restart the application server or the J2EE instance.
    After you make the JAR files available, deploy the adapter on the Oracle application server by using either the Oracle Application Server (Oracle AS) Application Server Control (ASC) or the Oracle admintool.jar file. Copy the adapter archive file (BRM_home/apps/brm_integrations/jca_adapter/OracleBRMJCA15Adapter.rar) from the installation directory to a location that is accessible to the adapter deployment tool. You can then open and deploy the archive file on your application server.
    After successful deployment, return the applications.xml file to its original settings and add the oracle.bpel.common codesource to the BRM Adapter oc4j-ra.xml file:
    Open the Oracle_home/j2ee/Instance/config/applications.xml configuration file for the J2EE instance.
    Remove the following oracle.bpel.common entry (shown in bold below):
    <imported-shared-libraries>
    <import-shared-library name="adf.oracle.domain"/>
    <import-shared-library name="oracle.bpel.common"/>
    </imported-shared-libraries>
    Save and close the file.
    Open the JCA Resource Adapter oc4j-ra.xml file from the Oracle_home/j2ee/Instance/application-deployments/default/BRMAdapterDeploymentName directory.
    Add the oracle.bpel.common entry (shown in bold below) to the oc4j-connector-factories section of the file:
    <oc4j-connector-factories...>
    <imported-shared-libraries>
    <import-shared-library name="oracle.bpel.common"/>
    </imported-shared-libraries>
    <oc4j-connector-factories>
    Save and close the file.
    Restart the application server or the J2EE instance.
    For more information about deploying the adapter, see your application server’s documentation.
    Connecting the adapter to BRM in Oracle AS
    You connect the adapter to the BRM software by creating connection pools and connection factories. As part of the adapter deployment, the application server creates oc4j-ra.xml from the packaged ra.xml. The ra.xml file is located in the Oracle_home/j2ee/Instance/connectors/AdapterDeploymentName/AdapterDeploymentName/META-INF directory. For example, Oracle_home/j2ee/home/connectors/BRMAdapter/BRMAdapter/META-INF/ra.xml.
    Use the resource adapter home page from the Oracle AS ASC page to create connection pools and connection factories.
    Create your connection pool by following the performance and tuning guidelines in Configuring Connection Pooling in OC4J in Oracle Containers for J2EE Resource Adapter Administrator's Guide. See download.oracle.com/docs/cd/B31017_01/web.1013/b28956/conncont.htm.
    Make sure you set the pool’s Maximum Connections parameter (maxConnections XML entity) equal to or greater than the Oracle BPEL process manager’s dspMaxThreads parameter. For more information, see Oracle BPEL Process Manager Performance Tuning in Oracle Application Server Performance Guide for 10g Release 3 (10.1.3.1.0) at download.oracle.com/docs/cd/B31017_01/core.1013/b28942/tuning_bpel.htm.
    Note To set up JCA Resource Adapter transaction management in BPEL, you must create a private connection pool and set its Inactive Connection Timeout property (inactivity-timeout XML entity) to 0. See About JCA Resource Adapter transaction management in BPEL for more information.
    Create as many connection factories as your system needs. For each connection factory, specify the following:
    The JNDI location for the connection factory.
    The connection pool to use.
    How to connect to BRM by using these entries:
    Entry
    Description
    ConnectionString
    Specify the protocol, host name, and port number for connecting to the BRM software. For example: ip Server1 12006.
    DBNumber
    Specify the database number for the BRM database. For example, enter 1 or 0.0.0.1 for database 0.0.0.1.
    InputValidation
    Specifies whether to validate the input XMLRecord:
    True — The adapter validates the input XMLRecord against the opcode schema.
    False — The adapter does not validate the input XMLRecord.
    The default is False.
    This overrides any other validation parameter specified in the WSDL file.
    OutputValidation
    Specifies whether to validate the output XMLRecord:
    True — The adapter validates the output XMLRecord against the opcode schema.
    False — The adapter does not validate the output XMLRecord.
    The default is False.
    This overrides any other validation parameter specified in the WSDL file.
    LoginType
    Specifies the authentication method:
    1 — The adapter logs in to BRM by using the specified login name and password.
    0 — The adapter logs in to BRM by using the specified service type and POID ID.
    The default is 1.
    UserName
    Specifies the login name the adapter uses for logging in to the BRM software.
    Note This entry is required only if LoginType is set to 1.
    Password
    Specify the password the adapter uses for logging in to the BRM software.
    Note This entry is required only if LoginType is set to 1.
    PoidID
    Specifies the POID ID. This entry should be set to 1.
    ServiceType
    Specifies the service the adapter uses to log in to the BRM software.
    The default is /service/pcm_client.
    You have successfully configured the adapter to connect to BRM.

Maybe you are looking for

  • Getting Audio/MIDI to recognize my Digidesign 002 rack

    I just upgraded from a G4 with Tiger to an iMac with Leopard. As I wait for Pro Tools LE to upgrade for Leopard compatibility, I thought I'd try to learn Garageband. Although I copied my old hard drive over to my new one and attached my Digi 002 rack

  • Frozen Form in B1 2007

    Hi guys, I have a tricky problem here. I just started to develop on SDK 2007. And now I'm stuck in my first problem. I made a Form in ScreenPainter. It contains a Grid Item.  Then I load the Form, like i did 2005. At first glance everthing looks fine

  • Connect one Business system with two Integration Server

    Hello, Can we able to connect one Business System with two Integration Server? I have one Business system (ECC 6.0 with the client 900) and it is already connected with PI 7.0 system.Can I able to connect the same sytem (with same client) with PI7.1?

  • Print to Video Start Stop recording

    Hello Ok is their any way to have FCP mark a Start Stop after each clip when recording a timeline with many clips. So that when recaptured it imports each clip in the Timeline as an individual clip. Perhaps their is another software for this. I have

  • A foreign object is stuck in my drive slot

    I was blowing dust from my slot-loading drive using compressed air - you know, a small metal canister attached to a red plastic nib. Well, the nib blew into the drive opening. Now, obviously, the drive won't work, and I don't exactly know that to do.