Deploying application with Customizations

Hi All,
I was working with Customizations and I have a base application on which I added some customizations (seeded only). I created a MAR profile and included that within my EAR. On my integrated weblogic server it works fine.
Now when Im trying to deploy this on a standalone instance of weblogic server, the deployment fails and Im getting this message.
oracle.mds.internal.lcm.exception.ValidationException: MDS-05790: The metadata store definition is either missing or incorrectly specified in the application configuration._ at oracle.mds.internal.lcm.deploy.DeployManager.predeploy(DeployManager.java:353) at oracle.mds.internal.lcm.deploy.DeployManager.startDeployment(DeployManager.java:162) at oracle.mds.internal.lcm.MDSLifecycleListenerImpl.start(MDSLifecycleListenerImpl.java:160) at oracle.mds.lcm.weblogic.WLLifecycleListener.preStart(WLLifecycleListener.java:188) at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199) at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:283) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) Caused By: oracle.mds.config.MDSConfigurationException: MDS-05790: The metadata store definition is either missing or incorrectly specified in the application configuration. at oracle.mds.internal.lcm.MDSLCMManager.getConnectionInfo(MDSLCMManager.java:1953) at oracle.mds.internal.lcm.deploy.DeployManager.predeploy(DeployManager.java:310) at oracle.mds.internal.lcm.deploy.DeployManager.startDeployment(DeployManager.java:162) at oracle.mds.internal.lcm.MDSLifecycleListenerImpl.start(MDSLifecycleListenerImpl.java:160) at oracle.mds.lcm.weblogic.WLLifecycleListener.preStart(WLLifecycleListener.java:188) at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199) at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:283) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Any ideas what might be going wong over here.
Thanks.

Hi,
did you deploy the EAR file to the integrated WLS and this worked? Or did you run the application and have JDeveloper do the deployment ? Is there anything specific to your customization configuration and which version of JDeveloper 11 do you use (see help--> about)
Frank

Similar Messages

Deploying Applications with SCCM 2012 R2 to Server 2008 R2 RDS servers

I'm having some trouble finding some concrete information from Microsoft regarding the deployment of applications to RDS servers using SCCM 2012 R2. There seems to be a lot of conjecture, old information and old wives tales floating around and I was hoping
I could get some information confirmed!
1. MSI installs automatically switch to install mode on RDS servers?
I've seen this mentioned a few times. I've also seen it mentioned that it is only true when running the MSI from the console session manually (i.e clicking the MSI file) not running as SYSTEM as SCCM would usually do. Can someone confirm if they do this
themselves or not?
2. Users still logged in when deploying applications?
Is it possible to deploy an application while users are still logged in? Is this only related to going into 'install' mode and taking the chance that a user will do something that will cause issues? Or is it known to cause issues?
I guess those are the main ones, I'm experienced in SCCM but not with deploying to RDS servers, I cant seem to find any straight answers!
Anyway, thanks in advance!

I've never had large enough RDS environment to use SCCM for app push, but from my experience in managing 2012/R2 RDS and local installs, I never bother with switching to install mode anymore and it works fine. Now if you're skeptical, you can
easily build this into a script that runs as a pre-req to your .MSI as part of the software package in SCCM so it's not a big deal.
As for installing apps while users are logged in, shouldn't be a problem if you're installing a new app., if however you're updating an existing application or uninstalling it, then it may be best to drain that RDS host first of all user sessions then do
the work just to be safe. this also helps avoid reboots.

Error while deploying application with TablePopinToggleCell UI element

Hi
I am using NWDS 7.0 and have developed an application with a Table that uses TablePopinToggleCell. When I deploy this on a server (NW2004s), it gives me the following error:
java.lang.NoClassDefFoundError: com.sap.tc.webdynpro.clientserver.uielib.standard.api.IWDTablePopinToggleCell
I am able to deploy the application without the UI element: TablePopinToggleCell
I understand that the class files are not available in the server. How do I fix this problem?
If I should add the required files in the server, where should I add them?
Thanks
Manoj

Hi Manoj,
I have tried doing something like this.
If you want to try this out running on a NW2004s.You need to first download the entire project from perforce branch (
tc\webdynpro\clientserver)for NWDS 7.0 and then build the project locally in your java perspective.
During the local build of the project.It will also point out the dependent projects required by this project(clientserevr).
Once the project is build.
Create seperate external jars of the clientserver project and its dependent projects and save them locally.
Open your SDM manager,pick up this jar file from there and deploy it.
Once the deployment is over, the server is ready to run the application you created.
But this make your NWDS2004s to behave jus like NWDS7.0 .
Just a small suggestion ,instead of going through this tedious process you can shift to NWDS7.0 itself.
regards
aarthi mathivanan

Error deploying application with security polices: ORA-00904

Hi all,
I am using Jdeveloper 11.1.1.0 and I am trying to deploy an ADF application with secure polices on WebLogic Server 10.3.1
I have deployed the application to an EAR file and I have installed it using the weblogic console, after having defined the JDBC connection.
Have I anything to do for implementing the security polices? Miss anything?
Because when I launch the application from Jdeveloper I have no errors, while when I try to go to the URL where I have deployed the application, after loggin in, I have this error:
Caused by: java.sql.SQLSyntaxErrorException: ORA-00904: "myEntityObject"."myField": invalid identifier
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:91)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1034)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:194)
at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:791)
at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:866)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1187)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3386)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3430)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1491)
at weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:128)
at oracle.jbo.server.ViewObjectImpl.getQueryHitCount(ViewObjectImpl.java:3915)
... 91 more
## Detail 0 ##
java.sql.SQLSyntaxErrorException: ORA-00904: "TICKETEO"."ID_CATEGORIA_APERTURA": identificativo non valido
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:91)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1034)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:194)
at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:791)
at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:866)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1187)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3386)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3430)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1491)
at weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:128)
at oracle.jbo.server.ViewObjectImpl.getQueryHitCount(ViewObjectImpl.java:3915)
at oracle.jbo.server.ViewObjectImpl.getQueryHitCount(ViewObjectImpl.java:3867)
at oracle.jbo.server.QueryCollection.getEstimatedRowCount(QueryCollection.java:3517)
at oracle.jbo.server.ViewRowSetImpl.getEstimatedRowCount(ViewRowSetImpl.java:2318)
at oracle.jbo.server.ViewObjectImpl.getEstimatedRowCount(ViewObjectImpl.java:8782)
at oracle.adf.model.bc4j.DCJboDataControl.estimateRowCount(DCJboDataControl.java:1551)
thanks
Andry
Edited by: user10799119 on 4-set-2009 3.50

Hi,
sincerly now I don't remember what was the problem, but it seems to me the solution was in one of these four settings:
1) check Admin Server when I create the JDBC connection.
2) before deploying the application to an EAR file, you don't forget to uncheck Auto-generate and synchronize weblogic-jdbc.xml Descriptors during deployment in Application properties --> deployment
3) in your application module --> configuration change the connection type from jdbc URL to JDBC DataSource
4) at the end of your URL of the deployed application don't insert the ".jspx" after your page name
Hope this helps
Regards

Not able to deploy application with fast-swap enabled - weblogic 10.3

Hi ,
When i am trying to deploy my exploded directory by adding
<fast-swap>
<enabled>true</enabled>
</fast-swap>
to weblogic.xml , i am getting following error
ClassLoader [com.bea.wls.redef.RedefiningClassLoader] does NOT provide an 'addTransformer(ClassFileTransformer)' method. Specify a custom LoadTimeWeaver or start your Java virtual machine with Spring's agent
if remove fast-swap from my weblogic.xml it deploying successfully.

Full stack trace
<Apr 27, 2013 10:09:52 PM EDT> <Warning> <HTTP> <BEA-101162> <User defined listener org.springframework.web.context.ContextLoaderListener failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.context.weaving.AspectJWeavingEnabler#0': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'loadTimeWeaver': Initialization of bean failed; nested exception is java.lang.IllegalStateException: ClassLoader [com.bea.wls.redef.RedefiningClassLoader] does NOT provide an 'addTransformer(ClassFileTransformer)' method. Specify a custom LoadTimeWeaver or start your Java virtual machine with Spring's agent: -javaagent:spring-agent.jar.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.context.weaving.AspectJWeavingEnabler#0': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'loadTimeWeaver': Initialization of bean failed; nested exception is java.lang.IllegalStateException: ClassLoader [com.bea.wls.redef.RedefiningClassLoader] does NOT provide an 'addTransformer(ClassFileTransformer)' method. Specify a custom LoadTimeWeaver or start your Java virtual machine with Spring's agent: -javaagent:spring-agent.jar
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:480)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
     at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
     Truncated. see log file for complete stacktrace
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'loadTimeWeaver': Initialization of bean failed; nested exception is java.lang.IllegalStateException: ClassLoader [com.bea.wls.redef.RedefiningClassLoader] does NOT provide an 'addTransformer(ClassFileTransformer)' method. Specify a custom LoadTimeWeaver or start your Java virtual machine with Spring's agent: -javaagent:spring-agent.jar
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:480)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
     at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
     Truncated. see log file for complete stacktrace
java.lang.IllegalStateException: ClassLoader [com.bea.wls.redef.RedefiningClassLoader] does NOT provide an 'addTransformer(ClassFileTransformer)' method. Specify a custom LoadTimeWeaver or start your Java virtual machine with Spring's agent: -javaagent:spring-agent.jar
     at org.springframework.context.weaving.DefaultContextLoadTimeWeaver.setBeanClassLoader(DefaultContextLoadTimeWeaver.java:82)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1322)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
     at java.security.AccessController.doPrivileged(Native Method)
     Truncated. see log file for complete stacktrace
>
<Apr 27, 2013 10:09:52 PM EDT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1367114948992' for task '11'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
     Truncated. see log file for complete stacktrace
java.lang.IllegalStateException: ClassLoader [com.bea.wls.redef.RedefiningClassLoader] does NOT provide an 'addTransformer(ClassFileTransformer)' method. Specify a custom LoadTimeWeaver or start your Java virtual machine with Spring's agent: -javaagent:spring-agent.jar
     at org.springframework.context.weaving.DefaultContextLoadTimeWeaver.setBeanClassLoader(DefaultContextLoadTimeWeaver.java:82)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1322)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
     at java.security.AccessController.doPrivileged(Native Method)
     Truncated. see log file for complete stacktrace
>
<Apr 27, 2013 10:09:52 PM EDT> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application 'PDC_1306'.>
<Apr 27, 2013 10:09:52 PM EDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'PDC_1306'.>
<Apr 27, 2013 10:09:52 PM EDT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException:
     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
     Truncated. see log file for complete stacktrace
java.lang.IllegalStateException: ClassLoader [com.bea.wls.redef.RedefiningClassLoader] does NOT provide an 'addTransformer(ClassFileTransformer)' method. Specify a custom LoadTimeWeaver or start your Java virtual machine with Spring's agent: -javaagent:spring-agent.jar
     at org.springframework.context.weaving.DefaultContextLoadTimeWeaver.setBeanClassLoader(DefaultContextLoadTimeWeaver.java:82)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1322)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
     at java.security.AccessController.doPrivileged(Native Method)
     Truncated. see log file for complete stacktrace

Deploying application with several web modules having the same context root

Hi,
I would like to be able to deploy an application in Weblogic 12c having one ejb module and several web modules with the same context root. Even though the web modules have the same context root, each of them is deployed to a different virtual host.
Weblogic allows deploying the modules this way as long as their targets are different (i.e. each having a distinct virtual host). However this works only when I don't select a target for the .ear:
Component Type Current Targets
application.ear Enterprise Application (None specified)
application.jar EJB AdminServer
web1.war WEBAPP virtualHost1
web2.war WEBAPP virtualHost2
However if I select as target for the .ear to be AdminServer, the deployment doesn't work anymore, complaining that the context roots are in conflict.
If I remove web2.war from the .ear and deploy the .ear and .jar to AdminServer and web1.war to virtualHost1, the deployment works but the strange thing is that the web application can be accessed also through the AdminServer's main network channel, even though I would expect that it should be accessible only through virtualHost1 network channel. I believe this is the reason why there are context root conflicts when specifying a target for the .ear, because both wars are made accessible to the main network channel.
The reason why I want to keep the wars inside the same .ear is because I want to make them access the application's local EJBs (since as far as I know it's not possible to access a local EJB outside the application even if they belong to the same VM).
Is there a way to deploy the web modules only to the virtual hosts without being targeted to the main network channel?
Regards,
Alexandru

Murphy's Law: If anything can go wrong it will
A corollary to Murphy's law: When everything fails, read the manual.
Web application funda: Every web application must have its own context root. So, if wkfsocos is one
web application then, wkfsocos1 is another web application -
and hence must have its own context root.
Hello Aman,
If you are in E-Commerce version 4.0, then read this
[ISA_Buildtool document |https://service.sap.com/~sapdownload/011000358700001920472003E/ISA_BuildTool_10.pdf]
to create a copy of the application in its own context root.
From your URL pattern I guess you are in E-Commerce version 4.0.
If you are in E-Commerce 5.0 or above, then the
[Extension Guide |http://service.sap.com/~sapdownload/011000358700006120622006E/]gives steps to create a copy with its own context root for use in modification.
(See the chapter on - Creating a project specific Web Application with own context root )
Both these links require access to SAP Service Marketplace. You can also find the
documents through /instguides shortcut in Service Marketplace.
Easwar Ram
http://www.parxlns.com

Deploying application with EAR file: problems....

Hello!
We been working in a test environment for developing our application. When its done and ready to go in production, we did generate the deployed application archive (EAR) with the console. Then, we used the
java -jar admin.jar -deploy command to deploy in the prod. env.
Meanwhile, we always get this kind of error, as it seems that oc4j is not generating EJB wrapper correctly:
GestionApplicationSBHome_StatelessSessionHomeWrapper120 was not an instance of interface sertir.portail.gap.GestionApplicationSBHome, the interface it implements is sertir.portail.gap.GestionApplicationSBHome
at java.lang.Throwable.fillInStackTrace(Native Method)
AND
java.lang.ClassCastException: ApplicationEBHome_EntityHomeWrapper14 was not an instance of interface sertir.portail.gap.ApplicationEBHome, the interfaces it implements are sertir.portail.gap.ApplicationEBHome, com.evermind[Oracle9iAS (1.0.2.2) Containers for J2EE].util.ExternalComparator, com.evermind[Oracle9iAS (1.0.2.2) Containers for J2EE].server.ejb.EntityContainer
and other errors doing that with almost all EJBs.
My question is, is there a special switch in the deploy command to force the compilation of the EAR file?
Any help would be appreciated...
Thanks!

These are set of jar files that are placed in WEB-INF/lib folder
jsf-api.jar
commons-net-1.4.1.jar
itext-1.4.2.jar
javax.servlet_1.0.0.0_2-5.jar
log4j-1.2.8.jar
lucene-core-2.0.0.jar
ojdbc5.jar
ojdl.jar
ojdl2.jar
orai18n-lcsd.jar
trinidad-api.jar
I think adf-faces-impl.jar is doesn't require for my application because we have migrated our application from ADF Faces to Trinidad.
Thanks
Sukumar

Error while deploying application with WebLogic server

Hi,
I use Jdeveloper 11g and created and ADF application which i want to deploy with WebLogic Server.But i have an error which is :
"There was a failure when processing annotations for application C:\...\xxx.war. Please make sure that the annotations are valid. The error is oracle.adf.library.webapp.ResourceServlet "
Plz help me.
Thx

I am receiving same message for simple servlet. Running JDev11g build 5166 and embedded WLS 10.3. Servlet used to deploy to embedded WLS and ran fine. Recently running newly created servlets produces error message as in this thread.
Investigation turned up the fact that the class file for the servlet was not deployed to the context-root (o.j2ee\drs) on the server. Copying the class file from the mywork project folder to the context-root folder (o.j2ee\drs) permitted the servlet to run.
Don't know if this is the cause of what you are experiencing but it may assist in your investigation! I have not figured out why the class file for servlets does not deploy to server despite the fact that the log file shows war and ear files were deployed. As it turns out, the war file does not have the class file in it so something is wrong before the war file is created.
Cheers!

Errors deploying applications with WLE5.1

Hello, i'm deploying many applications on Wle5.1; i mail two applications which give me problems.
The first application is CodiciSoggetto
i've problem with the boot of the application ( entity bean )because there is a cmp field (id) in the ejb-jar.xml which owns to Primary key class , but not to Bean class. This application works fine in WebLogicServer5.1; have i to change the source code? How can i tell it that this field owns to primary key class? perhaps with the tag >primary-key-field>?
This is the log:
120101.dcsv01!BBL.11193: 10-11-2000: TUXEDO Version 6.5forWLE5.1
120101.dcsv01!BBL.11193: LIBTUX_CAT:262: INFO: Standard main starting
120101.dcsv01!TMSYSEVT.11194: 10-11-2000: TUXEDO Version 6.5forWLE5.1
120101.dcsv01!TMSYSEVT.11194: LIBTUX_CAT:262: INFO: Standard main starting
120102.dcsv01!TMFFNAME.11195: 10-11-2000: TUXEDO Version 6.5forWLE5.1
120102.dcsv01!TMFFNAME.11195: LIBTUX_CAT:262: INFO: Standard main starting
120102.dcsv01!TMFFNAME.11196: 10-11-2000: TUXEDO Version 6.5forWLE5.1
120102.dcsv01!TMFFNAME.11196: LIBTUX_CAT:262: INFO: Standard main starting
120103.dcsv01!TMFFNAME.11197: 10-11-2000: TUXEDO Version 6.5forWLE5.1
120103.dcsv01!TMFFNAME.11197: LIBTUX_CAT:262: INFO: Standard main starting
120103.dcsv01!JavaServer.11198: 10-11-2000: TUXEDO Version 6.5forWLE5.1
120103.dcsv01!JavaServer.11198: LIBTUX_CAT:262: INFO: Standard main starting
120103.dcsv01!JavaServer.11198: IJINFRA_CAT:2: INFO: Starting JVM
120103.dcsv01!JavaServer.11198: IJINFRA_CAT:318: INFO: Static jar management in effect
120105.dcsv01!JavaServer.11198: main: IJENGINE_CAT:11: INFO: Threading level is Single-Threaded (level 0)
120106.dcsv01!JavaServer.11198: main: JTA_CAT:20: INFO: ConnectionPoolDataSource created for JDBC driver: oracle.jdbc.driver.OracleDriver
120106.dcsv01!JavaServer.11198: main: JDBC_CAT:4: INFO: Driver: oracle.jdbc.driver.OracleDriver loaded
120107.dcsv01!JavaServer.11198: main: JDBC_CAT:5: INFO: New JDBC connection created by driver: oracle.jdbc.driver.OracleDriver
120107.dcsv01!JavaServer.11198: main: JTA_CAT:19: INFO: 1 JDBC connection(s) created for JDBC connection pool: clientPool
120108.dcsv01!JavaServer.11198: main: INFO: Considering EJB Cache capacity (MAXEJBCACHE) from TMIB. Ignoring Java property com.beasys.ejb.cache. Capacity=10
120108.dcsv01!JavaServer.11198: main: INFO: Ignoring EJB Cache flush time (EJBCACHE_FLUSH) from TMIB. Ignoring Java property com.beasys.ejb.cache.flushTime. Cach FlushTime=0
120111.dcsv01!JavaServer.11198: main: EJB_CAT:28: ERROR: While deploying bean it.sella.anagrafe.codicisoggetto.CodiciSoggettoEJB :
java.lang.NoSuchFieldException: id
120111.dcsv01!JavaServer.11198: main: EJB_CAT:28: ERROR: While deploying bean it.sella.anagrafe.codicisoggetto.CodiciSoggettoEJB : The EJB Container received weblogic.ejb.common.DeploymentException: EJB_CAT:28: ERROR: While deploying bean it.sella.anagrafe.codicisoggetto.CodiciSoggettoEJB :
java.lang.NoSuchFieldException: id while setting container managed persistence.
120111.dcsv01!JavaServer.11198: main: EJB_CAT:29: ERROR: While deploying jar oggetto/ejb_codicisoggetto.jar : Problem advertising beans to ISM: EJB_CAT:28: ERROR: While deploying bean it.sella.anagrafe.codicisoggetto.CodiciSoggettoEJB : The EJB Container received weblogic.ejb.common.DeploymentException: EJB_CAT:28: ERROR: While deploying bean it.sella.anagrafe.codicisoggetto.CodiciSoggettoEJB :
java.lang.NoSuchFieldException: id while setting container managed persistence.
This is the ejb-jar.xml;
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN' 'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
<ejb-jar>
<enterprise-beans>
<entity>
     <ejb-name>it.sella.anagrafe.codicisoggetto.CodiciSoggettoEJB</ejb-name>
     <home>it.sella.anagrafe.codicisoggetto.CodiciSoggettoHome</home>
     <remote>it.sella.anagrafe.codicisoggetto.CodiciSoggetto</remote>
     <ejb-class>it.sella.anagrafe.codicisoggetto.CodiciSoggettoBean</ejb-class>
     <persistence-type>Container</persistence-type>
     <prim-key-class>it.sella.ejb.DefaultPK</prim-key-class>
     <reentrant>True</reentrant>
<primkey-field>id</primkey-field>
     <cmp-field>
     <field-name>id</field-name>
     </cmp-field>
     <cmp-field>
     <field-name>soggettoId</field-name>
     </cmp-field>
     <cmp-field>
     <field-name>compatibleInstanceId</field-name>
     </cmp-field>
     <cmp-field>
     <field-name>compatibleTypeId</field-name>
     </cmp-field>
     <cmp-field>
     <field-name>value</field-name>
     </cmp-field>
<cmp-field>
<field-name>rightPk</field-name>
</cmp-field>
     <env-entry>
          <env-entry-name>counterHomeName</env-entry-name>
          <env-entry-type>java.lang.String</env-entry-type>
          <env-entry-value>it.sella.counter.CounterHome</env-entry-value>
     </env-entry>
     <resource-ref>
          <res-ref-name>jdbc/clientPool</res-ref-name>
     <res-type>javax.sql.DataSource</res-type>
     <res-auth>Container</res-auth>
     </resource-ref>
</entity>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
     <method>
     <ejb-name>it.sella.anagrafe.codicisoggetto.CodiciSoggettoEJB</ejb-name>
     <method-intf>Remote</method-intf>
     <method-name>*</method-name>
     </method>
     <trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
This is the weblogic-ejb-extensions.xml:
<!DOCTYPE weblogic-ejb-extensions SYSTEM "weblogic-ejb-extensions.dtd" >
<weblogic-ejb-extensions>
<weblogic-enterprise-bean>
<ejb-name>it.sella.anagrafe.codicisoggetto.CodiciSoggettoEJB</ejb-name>
<weblogic-deployment-params>
<max-beans-in-free-pool>20</max-beans-in-free-pool>
<max-beans-in-cache>1000</max-beans-in-cache>


<jndi-name>it.sella.anagrafe.codicisoggetto.CodiciSoggettoHome</jndi-name>

<persistence-store-descriptor>
<is-modified-method-name>isModified</is-modified-method-name>
     

<persistence-store-jdbc>

<pool-name>jdbc/clientPool</pool-name>

<user>ssil</user>

<password>ssil</password>

<driver-url>jdbc:oracle:thin:@171.97.1.5:1521:th2o</driver-url>
<table-name>AN_TR_CODICISOGGETTO</table-name>


<attribute-map>
<attribute-map-entry>
<bean-field-name>id</bean-field-name>
<table-column-name>CS_CODICIFISCALI_ID</table-column-name>
</attribute-map-entry>
<attribute-map-entry>
<bean-field-name>soggettoId</bean-field-name>
<table-column-name>cs_soggetto_id</table-column-name>
</attribute-map-entry>
<attribute-map-entry>
<bean-field-name>compatibleInstanceId</bean-field-name>
<table-column-name>cs_compatible_instance_id</table-column-name>
</attribute-map-entry>
<attribute-map-entry>
<bean-field-name>compatibleTypeId</bean-field-name>
<table-column-name>cs_compatible_type_id</table-column-name>
</attribute-map-entry>
<attribute-map-entry>
<bean-field-name>value</bean-field-name>
<table-column-name>cs_value</table-column-name>
</attribute-map-entry>
<attribute-map-entry>
<bean-field-name>rightPk</bean-field-name>
<table-column-name>CS_RIGHT_PK</table-column-name>
</attribute-map-entry>
</attribute-map>

<finder-descriptor>
<description>
Find method to get accounts with balance over the parameter.
</description>
<method>
<ejb-name>
it.sella.anagrafe.codicisoggetto.CodiciSoggettoEJB
</ejb-name>
<method-name>
findBySoggettoId(Long long1)
</method-name>
</method>
<query-grammar>
(= soggettoId $long1)
</query-grammar>
</finder-descriptor>
</persistence-store-jdbc>
</persistence-store-descriptor>
</weblogic-deployment-params>
</weblogic-enterprise-bean>
</weblogic-ejb-extensions>
This is the bean class:
package it.sella.anagrafe.codicisoggetto;
import it.sella.ejb.EntityBeanAdapter;
import java.util.ResourceBundle;
public class CodiciSoggettoBean extends EntityBeanAdapter
public Long soggettoId;
public Long compatibleInstanceId;
public Long compatibleTypeId;
public Long rightPk;
private Long codiciFisicaliId;
public String value;
private static ResourceBundle res;
private static final String JNDI_FACTORY;
private static final String WL_HOST_URL;
public CodiciSoggettoBean()
protected Long getCounterInitVal()
return new Long(1000L);
public Long getInstanceId()
return compatibleInstanceId;
public Long getRightPk()
return rightPk;
public Long getSoggettoId()
return soggettoId;
public Long getTypeId()
return compatibleTypeId;
public String getValue()
return value;
public void setInstanceId(Long long1)
compatibleInstanceId = long1;
setModified(true);
public void setRightPk(Long long1)
rightPk = long1;
setModified(true);
public void setSoggettoId(Long long1)
soggettoId = long1;
setModified(true);
public void setTypeId(Long long1)
compatibleTypeId = long1;
setModified(true);
public void setValue(String s)
value = s;
setModified(true);
static
res = ResourceBundle.getBundle("EJBFrameWorkLogRes");
JNDI_FACTORY = res.getString("WLInitialContexFactoryNameForJNDI");
WL_HOST_URL = res.getString("WLServerHostURL");
This is the primary key class:
package it.sella.ejb;
// Referenced classes of package it.sella.ejb:
// IPrimaryKey
public class DefaultPK
implements IPrimaryKey
public Long id;
public DefaultPK()
public DefaultPK(Long id)
setId(id);
public Long getId()
return id;
protected void setId(Long id)
this.id = id;
public String toString()
return "Id=" + getId();
public int hashCode()
return getId() == null ? 0 : getId().hashCode();
public boolean equals(Object obj)
if(obj != null && (obj instanceof DefaultPK))
return getId() != null && getId().equals(((DefaultPK)obj).getId());
else
return false;
This is the log to the second application ( not to the boot but with java weblogic.ejbc ... ejb-jar.xml..)
/wle2/wle/components/Dispatcher/it/sella/dispatch/TopicListenerPSJDBC.java:605: Duplicate method declaration:
java.lang.Object findByPrimaryKey(it.sella.dispatch.TopicListenerPK)
public java.lang.Object findByPrimaryKey(it.sella.dispatch.TopicListenerPK topiclistenerpk)
^
1 error
Exec failed .. exiting
This is the ejb-jar.xml:
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN' 'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
<ejb-jar>
<small-icon>it/sella/dispatch/postman-small.gif</small-icon>
<large-icon>it/sella/dispatch/postman.gif</large-icon>
<enterprise-beans>
<session>
     <display-name>Topic Manager Bean</display-name>
     <small-icon></small-icon>
     <large-icon></large-icon>
     <ejb-name>it.sella.dispatch.TopicManager</ejb-name>
     <home>it.sella.dispatch.TopicManagerHome</home>
     <remote>it.sella.dispatch.TopicManager</remote>
     <ejb-class>it.sella.dispatch.TopicManagerBean</ejb-class>
     <session-type>Stateless</session-type>
     <transaction-type>Container</transaction-type>
     <env-entry>
     <description>Select statement for JDBC based topic finder method</description>
     <env-entry-name>SelectStatement</env-entry-name>
     <env-entry-type>java.lang.String</env-entry-type>
     <env-entry-value>select distinct topicname from tbltopics</env-entry-value>
     </env-entry>
     <env-entry>
     <description>The name of the field to select from</description>
     <env-entry-name>TopicFieldName</env-entry-name>
     <env-entry-type>java.lang.String</env-entry-type>
     <env-entry-value>TOPICNAME</env-entry-value>
     </env-entry>
     <env-entry>
     <description>The password for oracle DB Connection</description>
     <env-entry-name>Password</env-entry-name>
     <env-entry-type>java.lang.String</env-entry-type>
     <env-entry-value>ssil</env-entry-value>
     </env-entry>
     <env-entry>
     <description>The Driver class name for the Oracle DB</description>
     <env-entry-name>JDBCDriver</env-entry-name>
     <env-entry-type>java.lang.String</env-entry-type>
     <env-entry-value>oracle.jdbc.driver.OracleDriver</env-entry-value>
     </env-entry>
     <env-entry>
     <description>The driver URL for the database</description>
     <env-entry-name>JDBCURL</env-entry-name>
     <env-entry-type>java.lang.String</env-entry-type>
     <env-entry-value>jdbc:oracle:thin:@171.97.1.5:1521:th2o</env-entry-value>
     </env-entry>
     <env-entry>
     <description>The user name used to connect to the Oracle DB</description>
     <env-entry-name>UserName</env-entry-name>
     <env-entry-type>java.lang.String</env-entry-type>
     <env-entry-value>ssil</env-entry-value>
     </env-entry>
</session>
<session>
     <display-name>Dispatcher Bean</display-name>
     <small-icon></small-icon>
     <large-icon></large-icon>
     <ejb-name>it.sella.dispatch.Dispatcher</ejb-name>
     <home>it.sella.dispatch.DispatcherHome</home>
     <remote>it.sella.dispatch.Dispatcher</remote>
     <ejb-class>it.sella.dispatch.DispatcherBean</ejb-class>
     <session-type>Stateless</session-type>
     <transaction-type>Container</transaction-type>
</session>
<entity>
     <display-name>Topic Listener Bean</display-name>
     <ejb-name>it.sella.dispatch.TopicListener</ejb-name>
     <home>it.sella.dispatch.TopicListenerHome</home>
     <remote>it.sella.dispatch.TopicListener</remote>
     <ejb-class>it.sella.dispatch.TopicListenerBean</ejb-class>
     <persistence-type>Container</persistence-type>
     <prim-key-class>it.sella.dispatch.TopicListenerPK</prim-key-class>
     <reentrant>False</reentrant>
     <cmp-field>
     <field-name>strtopic</field-name>
     </cmp-field>
     <cmp-field>
     <field-name>strjndi</field-name>
     </cmp-field>
</entity>
</enterprise-beans>
<assembly-descriptor>
<security-role>
     <role-name>system</role-name>
</security-role>
<security-role>
     <role-name>guest</role-name>
</security-role>
<method-permission>
     <description></description>
     <role-name>system</role-name>
     <role-name>guest</role-name>
     
</method-permission>
<container-transaction>
     <method>
     <ejb-name>it.sella.dispatch.TopicListener</ejb-name>
     <method-intf>Remote</method-intf>
     <method-name>*</method-name>
     </method>
     <method>
     <ejb-name>it.sella.dispatch.Dispatcher</ejb-name>
     <method-intf>Remote</method-intf>
     <method-name>*</method-name>
     </method>
     <method>
     <ejb-name>it.sella.dispatch.TopicManager</ejb-name>
     <method-intf>Remote</method-intf>
     <method-name>*</method-name>
     </method>
     <trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
This is the weblogic-ejb-extensions.xml:
<!DOCTYPE weblogic-ejb-extensions SYSTEM "weblogic-ejb-extensions.dtd" >
<weblogic-ejb-extensions>
<weblogic-enterprise-bean>
<ejb-name>it.sella.dispatch.TopicManager</ejb-name>
<weblogic-deployment-params>
<jndi-name>it.sella.dispatch.TopicManager</jndi-name>
</weblogic-deployment-params>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>it.sella.dispatch.Dispatcher</ejb-name>
<weblogic-deployment-params>
<jndi-name>it.sella.dispatch.Dispatcher</jndi-name>
</weblogic-deployment-params>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>it.sella.dispatch.TopicListener</ejb-name>
<weblogic-deployment-params>
<jndi-name>it.sella.dispatch.TopicListener</jndi-name>
<persistence-store-descriptor>

<persistence-store-jdbc>
<pool-name>jdbc/oraclePool</pool-name>
<user>ssil</user>
<password>ssil</password>
<driver-url>jdbc:oracle:thin:@171.97.1.5:1521:th2o</driver-url>
<table-name>TBLTOPICS</table-name>
<attribute-map>
<attribute-map-entry>
<bean-field-name>strtopic</bean-field-name>
<table-column-name>topicname</table-column-name>
</attribute-map-entry>
<attribute-map-entry>
<bean-field-name>strjndi</bean-field-name>
<table-column-name>jndiname</table-column-name>
</attribute-map-entry>
</attribute-map>
<finder-descriptor>
<method>
<ejb-name>
it.sella.dispatch.TopicListener
</ejb-name>
<method-name>
findByTopic(String s)
</method-name>
</method>
<query-grammar> (= strtopic $s)</query-grammar>
</finder-descriptor>
<finder-descriptor>
<method>
<ejb-name>
it.sella.dispatch.TopicListener
</ejb-name>
<method-name>findByPrimaryKey(it.sella.dispatch.TopicListenerPK topiclistenerpk)</method-name>
</method>
<query-grammar> (& (= strtopic topiclistenerpk.strtopic) (= strjndi topiclistenerpk.strjndi))</query-grammar>
</persistence-store-jdbc>
</persistence-store-descriptor>
</weblogic-deployment-params>
</weblogic-enterprise-bean>
</weblogic-ejb-extensions>
This is the primary key class:
// FrontEnd Plus for JAD
// DeCompiled : TopicListenerPK.class
package it.sella.dispatch;
import java.io.Serializable;
import java.util.Random;
public class TopicListenerPK
implements Serializable
public String strtopic;
public String strjndi;
public int hashCode()
return strtopic.hashCode() ^ strjndi.hashCode();
public boolean equals(Object obj)
return (obj instanceof TopicListenerPK) && (strtopic == null && ((TopicListenerPK)obj).strtopic == null || strtopic.equals(((TopicListenerPK)obj).strtopic)) && (strjndi == null && ((TopicListenerPK)obj).strjndi == null || strjndi.equals(((TopicListenerPK)obj).strjndi));
public TopicListenerPK()
strtopic = (new Random()).toString();
strjndi = (new Random()).toString();
public TopicListenerPK(String s, String s1)
strtopic = s;
strjndi = s1;
This is the home interface:
package it.sella.dispatch;
import java.rmi.RemoteException;
import java.util.Enumeration;
import javax.ejb.*;
// Referenced classes of package it.sella.dispatch:
// TopicListener, TopicListenerPK
public interface TopicListenerHome
extends EJBHome
public abstract TopicListener create(String s, String s1)
throws RemoteException, CreateException;
public abstract TopicListener findByPrimaryKey(TopicListenerPK topiclistenerpk)
throws RemoteException, FinderException;
public abstract Enumeration findByTopic(String s)
throws RemoteException, FinderException;
I hope somebody could help me.
Thanks

I've never had large enough RDS environment to use SCCM for app push, but from my experience in managing 2012/R2 RDS and local installs, I never bother with switching to install mode anymore and it works fine. Now if you're skeptical, you can
easily build this into a script that runs as a pre-req to your .MSI as part of the software package in SCCM so it's not a big deal.
As for installing apps while users are logged in, shouldn't be a problem if you're installing a new app., if however you're updating an existing application or uninstalling it, then it may be best to drain that RDS host first of all user sessions then do
the work just to be safe. this also helps avoid reboots.

Could not deploy application with Developer Studio 7.0.0

Hi,
I ran into a problem while deploying any of my applications (Web Dynpro, J2EE, Dictionary) to any of my remote servers with NetWeaver Developer Studio version 7.0.0.
<b>Problem:</b>
<i>Deployment exception: Server [Host] did not accept login request as admin on port [Port]. Details: ERROR: Could not establish connection to server [Host] at port [Port]: Connection timed out: connect...</i>
Prior to installing version 7.0.0, I used the version 2.0.9. Everything worked fine then. The Message Server Host and Port on the ver 7.0.0 were configured exactly the same as ver 2.0.9. System settings (Proxy, Firewall) have never been changed.
Anyone has worked on version 7.0.0 and experienced the similar problem?
Thanks.
Teecheu Loh

I think my case is pretty similar to the case in this thread
Problems with connecting NWDS SP15 via VPN
I will open an OSS.

Deploying applications with grid tags

developing with WLS 8.1 on Windows then deploying to WLS 8.3 on Solaris...
Everything deploys fine when migrating my workshop application from development to a test single-domain server. And the DBControls against a MySQL database work fine. However, data returned (relational) to a grid (netui data bindings) object never gets returned or displayed. No idea why. Must be either something in the config.xml that is missing or a bug when deploying from 8.1 to 8.3 on different OSs.
Any clues???
/ Matthew

another thing...
Same problem happens with repeater tags (another netui-databinding). Yet using the select tag (netui) data returned via a pageflow reference from a DBControl:er is returned without problems. Checked the WEB-INF/lib directory to make sure the netui-tar-databinding.jar was present. It is. And the tld package is also there.
Also, took the build Ant xml file used to generate the single-server on Solaris and ran it on my Windows machine. Deployed the application (ear) and data is returned into grid tags. Must be some setup difference or missing jar file.
When generating a single-server I use the setWLSEnv.cmd/sh script to setup environment variables and to run the server the startWeblogic.cmd/sh which are pre-made.
Get one error on the Solaris instance which doesn´t appear when running on Windows. The WLW says there is an unknown database found ("databas name = MySQL, database driver name = MySQL-AB JDBC Driver"). Not sure why this error is logged since the non netui-data tags like select can return data from the underlying MySQL connection.
/ Matthew
Message was edited by young_matthewd at Oct 31, 2004 11:28 AM

Deploying application with specific changes

Hi guys,
I think I might have a weird issue and scratching my head with this one :)
I have an MSI file of a certain application that I packaged with EMCO Packager. When creating a package it I defined a setting that I want to use with this application (which modifies a specific .ini file). When running the MSI locally on a PC everything
works great and the setting is set to how I defined it, but when I deploy the same MSI with SCCM using the same install parameters the setting is changed to default. This issue is also not specific to this one application but other applications as well.
Do you guys have any ideas?
Thanks a lot!
Steve

OK. So you are expecting your (self-created) MSI, run in the System context (which is what ConfigMgr does when running an app as system), to drop the ini into another user's directory?
This is possible, but it requires self-healing which involves some added complexity and a deeper knowledge of Windows Installer.
You can also use Active Setup:
http://blogs.msdn.com/b/aruns_blog/archive/2011/11/02/10176957.aspx
http://blogs.flexerasoftware.com/installtalk/2011/11/using-active-setup-to-repair-user-settings.html
Jason | http://blog.configmgrftw.com

Deploying Applications with BC4J

I am just evaluating BC4J and JDeveloper.
Can Applications / Modules developed with JDeveloper taking full advantage of 'Business Components for Java' and EJB/CORBA be deployed in non Oracle Servers such as WebSphere ? Or does it specifically require Oracle 8i ?
null

In our upcoming 3.2 release, we support deploying Business Components for Java in the following environments:
1. In local mode, to any application server (this is best suited for JSP and Servlet Client UIs).
2. As an EJB to:
- Oracle8i 8.1.7 (session or entity)
- Oracle9i app server
- BEA WebLogic
3. As a CORBA Server Object to:
- Visibroker
- Oracle8i 8.1.7
- Oracle9i App Server
null

Deploying application with security polices on Jdeveloper 11.1.1.0

Hi all,
I am using Jdeveloper 11.1.1.0 and WebLogic Server 10.3.1
I have an application that uses security polices (file jazn-data.xml) and when I launch it from Jdeveloper it works. Now I am trying to deploy it, but I have some problems.
I have try to follow this link:
http://www.oracle.com/technology/products/jdev/tips/muench/credmig111100/index.html
but is not update
I have tried to follow this:
http://download.oracle.com/docs/cd/E12839_01/core.1111/e10043/csfadmin.htm#CACDJHGE
but when I launch this command:
migrateSecurityStore.py -type credStore
-configFile jpsConfigFileLocation
-src srcJpsContext
-dst dstJpsContext
I can't understand where are the file: jpsConfigFileLocation, srcJpsContext, dstJpsContext. In what folder are there?
Are there my links correct? Or are there links or manual simpler to add security to a deploy?
Thanks
Edited by: user10799119 on 4-set-2009 3.52

Hi,
migrateSecurityStore.py -type credStore
-configFile jpsConfigFileLocation
-src srcJpsContext
-dst dstJpsContext
+[-overWrite trueOrFalse]+
+migrateSecurityStore(type="credStore", configFile="jpsConfigFileLocation", src="srcJpsContext", dst="dstJpsContext", [overWrite="trueOrFalse"])+
The meaning of the arguments (all required except overWrite) is as follows:
*+
configFile specifies the location of a configuration file jps-config.xml relative to the directory where the command is run. Typically, this configuration file is created just to be used with the command and serves no other purpose. This files contains two jps-contexts that specify the source and destination stores.
In addition, if the migration involves one or two LDAP-based stores, then this file must contain a bootstrap jps-context that refers to the location of a cwallet.sso file where the credentials to access the LDAP based involved in the migration are kept. See second example below. For complete details, see Section 15.4.7, "Specifying Bootstrap Credentials Manually."
*+
src specifies the name of a jps-context in the configuration file passed to the argument configFile. This context identifies the source credential repository.
*+
dst specifies the name of another jps-context in the configuration file passed to the argument configFile. This context identifies the target credential repository.
*+
overWrite specifies whether a target credential matching a source credential should be overwritten by or merged with the source credential. Set to true to overwrite the target credential; set to false to merge matching credentials. Optional. If not specified, defaults to false. When set to false, if a matching is detected, the source credential is disregarded and a warning is logged.
JPS config is located in <wls install dir>\user_projects\domains\base_domain\config\fmwconfig . The two context references, like srcJpsContext, reference a named area in the jps config file. I agree that the text is a bit hard to parse. So they are no files to search but entries in the file you reference in the "config" parameter
Frank

Problems deploying application with updated method signatures on WLS8.1

Hi,
I have an jar file under applications which I have deployed fine on WLS 8.1 in the past. I changed the method signature on one of the EJB classes in the jar. One of the parameters now takes a different Java class type. I have recompiled everyone and repackaged the jar but when I try to deploy the jar it gives me an error because the the local interface of the EJB does not have the old Java class parameter type.
I have checked the jar, classes in the jar, and the ejb-jar.xml and weblogic-ejb-jar.xml in the jar and it is looks fine. I have cleaned out my server deployment directories and verified the classpath in case the older jar was in there and everything looks OK. It seems for some reason 8.1 is caching the old ejb-jar.xml or somehow is remembering the old method signature and will not process the updated jar. Has anyone seen anything like this?
Thanks for any help or recommendations

Can you show me the error you receive?
Another simple test would be to deploy your application to a new, empty
server.
You can create a new domain as easy as this:
mkdir testDomain;
cd testDomain;
java weblogic.Server
Type in the username/password that you want and answer 'Yes' when it
asks if you want to create a new domain.
Try deploying your jar to this new domain, and let me know if it still
fails.
-- Rob
Jeff Dooley wrote:
Hi,
I have an jar file under applications which I have deployed fine on WLS 8.1 in the past. I changed the method signature on one of the EJB classes in the jar. One of the parameters now takes a different Java class type. I have recompiled everyone and repackaged the jar but when I try to deploy the jar it gives me an error because the the local interface of the EJB does not have the old Java class parameter type.
I have checked the jar, classes in the jar, and the ejb-jar.xml and weblogic-ejb-jar.xml in the jar and it is looks fine. I have cleaned out my server deployment directories and verified the classpath in case the older jar was in there and everything looks OK. It seems for some reason 8.1 is caching the old ejb-jar.xml or somehow is remembering the old method signature and will not process the updated jar. Has anyone seen anything like this?
Thanks for any help or recommendations

Deploying application with Customizations

Similar Messages

Maybe you are looking for