Multiple enterprise applications

We are in the process of designing multiple enterprise applications. We want to utilize some of the basic core Java EE patterns i a Websphere environment. My question centers around the architecture of the applications/components and the deployment.
For example, since I have multiple apps, can I deploy multiple web apps (war files) while utilizing an enterprise suite of EJBs to service requests from any/all applications? Let's assume that the web apps are all deployed in the same box (jvm) for now but it may be necessary to deploy them in their own web container (physical server) in the future.
Is this possible and has anyone done this? How should we develop and deploy the war/jar/ear files?
I have done this in the past but with home grown middleware. Thanks.

For example, since I have multiple apps, can I deploy multiple web apps (war files) while utilizing an enterprise suite of EJBs to service requests from any/all applications? Yes. The deployment strategy you're outlining is a good fit for the Remote EJB view. The Remote EJB clients(your web apps) can be packaged within the same .ear as the EJBs themselves, or in separate applications(.wars or .ears) Those separate applications can either be deployed to the same server that hosts the EJBs or to a different tier altogether. Because the Remote EJB view is location transparent, the application behavior will be the same. Of course, performance will differ.

Similar Messages

Problem in synching multiple web applications

I have a domain called myDomain. In this domain I have 2 enterprise applications
say
ent1App with ent1App-project and ent2App with its ent2App-project. Each enterpsrise
application has one web application
(webApp1 and webApp2 respectively). I have the same set of webflow files (.wf
files) in both
ent1App-project/application-sync/web-apps/webApp1 and ent2App-project/application-sync/web-apps/webApp2
directories.
Now suppose I synchronize my webflows (using EBCC) for say ent1App. The synchronization
is accomplished without any problems
and this is confirmed when the entries get updated in the Master Data Repository
where all the webflows for ent1App get
stored. This is as viewd using the datasyncservlet.
If I now do a synchronization on the other enterprise application called ent2App,
the synchronization takes place
successfully but when viewed in the datasyncservlet, it shows up the entries for
the webflows of ent2App. i.e. the entries
for all the weblows of ent1App which were shown in the Master Data repository
are not shown.
We looked up the Cloudscape database to ensure that the entries for both the enterprise
applications are present and it does
contain the records for both the applications. This however does not show up in
the datasync servlet. Due to this we get a
namespace not found error whenever we try to access the application whose entries
are missing in the master data repository.
I have separate names for my datasync folder for each of the applications in my
config.xml as shown below
ent1App
<Application Deployed="true" Name="ent1App"
Path=".\config\myDomain\applications\ent1App" StagedTargets="iden_staging">
<WebAppComponent DeploymentOrder="1002" Name="datasync" Targets="iden_staging"
URI="datasync"/>
ent2App
<Application Deployed="true" Name="ent2App"
Path=".\config\myDomain\applications\ent2App" StagedTargets="iden_staging">
<WebAppComponent DeploymentOrder="1002" Name="datasyncDev"
Targets="iden_staging" URI="datasyncDev"/>
I am using WLS6.1 SP4 and WLP 4.0 SP3
Can someone please tell me what could be the problem?
Thanks
Shah Jimmy

When you peform a data sync you are updating the data_sync_item table
with the EBCC xml files. For those files that are not present in the
EBCC project they will be deleted from the table.
You can not use multiple enterprise applications that contain Portals.
Try using using multiple domains that contain separate databases for
datasyncs.
Here is a snippet I recently sent out in a support case:
Unfortunately there is not a documented best practice for maintaining
multiple projects and enterprise applications. In my opinion if you
plan to create multiple enterprise applications they will need to
maintain separate application components and web applications. The
enterprise applications will need to use the same portal resources
(pools) and therefore same tables. The synchronization modes documented
at http://e-docs.bea.com/wlp/docs40/deploygd/appdata.htm explain the
limitations in data sync -- either all files are deleted and updated or
only modified files are updated. Either mode will delete files from the
data_sync_item table that do not exist in the current project.
Therefore one project will need to be used per domain.
-- Jim
Jimmy Shah wrote:
I have a domain called myDomain. In this domain I have 2 enterprise applications
say
ent1App with ent1App-project and ent2App with its ent2App-project. Each enterpsrise
application has one web application
(webApp1 and webApp2 respectively). I have the same set of webflow files (.wf
files) in both
ent1App-project/application-sync/web-apps/webApp1 and ent2App-project/application-sync/web-apps/webApp2
directories.
Now suppose I synchronize my webflows (using EBCC) for say ent1App. The synchronization
is accomplished without any problems
and this is confirmed when the entries get updated in the Master Data Repository
where all the webflows for ent1App get
stored. This is as viewd using the datasyncservlet.
If I now do a synchronization on the other enterprise application called ent2App,
the synchronization takes place
successfully but when viewed in the datasyncservlet, it shows up the entries for
the webflows of ent2App. i.e. the entries
for all the weblows of ent1App which were shown in the Master Data repository
are not shown.
We looked up the Cloudscape database to ensure that the entries for both the enterprise
applications are present and it does
contain the records for both the applications. This however does not show up in
the datasync servlet. Due to this we get a
namespace not found error whenever we try to access the application whose entries
are missing in the master data repository.
I have separate names for my datasync folder for each of the applications in my
config.xml as shown below
ent1App
<Application Deployed="true" Name="ent1App"
Path=".\config\myDomain\applications\ent1App" StagedTargets="iden_staging">
<WebAppComponent DeploymentOrder="1002" Name="datasync" Targets="iden_staging"
URI="datasync"/>
ent2App
<Application Deployed="true" Name="ent2App"
Path=".\config\myDomain\applications\ent2App" StagedTargets="iden_staging">
<WebAppComponent DeploymentOrder="1002" Name="datasyncDev"
Targets="iden_staging" URI="datasyncDev"/>
I am using WLS6.1 SP4 and WLP 4.0 SP3
Can someone please tell me what could be the problem?
Thanks
Shah Jimmy

Deploying multiple versions of an enterprise application

hi,
trying to find a solution to deploy several versions of an enterprise
application i came up with the following considerations. i would highly
appreciate feedback on which method would be feasable and the issues
involved.
o version specific jndi names
creating a separate deployment descriptor for each version of the
enterprise application and binding each ejb to a different jndi name.
utilize jndi enc mappings to keep the application code unaffected.
the following deployment descriptor excerpt shows the relevant parts of
the weblogic-ejb-jar.xml for "versions01". each further version would
have different jndi names and jndi enc mappings.
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>SomeEJB</ejb-name>
<local-jndi-name>version01/SomeHomeLocal</local-jndi-name> 
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>AnotherEJB<ejb-name>
<reference-descriptor>
<ejb-ref-name>ejb/SomeHomeLocal</ejb-ref-name>
<jndi-name>version01/SomeHomeLocal</jndi-name> 
</reference-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
is it possible to deploy the same classes with different jndi names? are
there any issues concerning the internal handling of weblogic
(classloading, classpath, ...)? can multiple versions be deployed from
the same source directory structure (hence is weblogic creating it's own
copy of class files during deployment by copying them into the domain
configuration directory)?
o multiple managed servers
configuring multiple managed servers and deploying each version of the
enterprise application to it's own server instance.
o built in support
does bea weblogic server provide some built in version support that
allows the deployment of multiple versions of the same enterprise
application within a single server instance? are there any deployment
tools that help to generate version specific deployment descriptors?
thanks in advance
best regards
erich liebmann

hi,
trying to find a solution to deploy several versions of an enterprise
application i came up with the following considerations. i would highly
appreciate feedback on which method would be feasable and the issues
involved.
o version specific jndi names
creating a separate deployment descriptor for each version of the
enterprise application and binding each ejb to a different jndi name.
utilize jndi enc mappings to keep the application code unaffected.
the following deployment descriptor excerpt shows the relevant parts of
the weblogic-ejb-jar.xml for "versions01". each further version would
have different jndi names and jndi enc mappings.
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>SomeEJB</ejb-name>
<local-jndi-name>version01/SomeHomeLocal</local-jndi-name> 
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>AnotherEJB<ejb-name>
<reference-descriptor>
<ejb-ref-name>ejb/SomeHomeLocal</ejb-ref-name>
<jndi-name>version01/SomeHomeLocal</jndi-name> 
</reference-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
is it possible to deploy the same classes with different jndi names? are
there any issues concerning the internal handling of weblogic
(classloading, classpath, ...)? can multiple versions be deployed from
the same source directory structure (hence is weblogic creating it's own
copy of class files during deployment by copying them into the domain
configuration directory)?
o multiple managed servers
configuring multiple managed servers and deploying each version of the
enterprise application to it's own server instance.
o built in support
does bea weblogic server provide some built in version support that
allows the deployment of multiple versions of the same enterprise
application within a single server instance? are there any deployment
tools that help to generate version specific deployment descriptors?
thanks in advance
best regards
erich liebmann

Storing SessionManager or Server for multiple web applications

We currently have one enterprise application with 2 web applications installed. These 2 web applications must share the same session cache.
Toplink is installed as a shared library for both of these web applications.
What I am wondering is how Server and SessionManager should be utilized.
In our servlet initialization of web application one we get an instance of the SessionManager and assign the SessionManager to a static instance variable.
static SessionManager sessionManager;
sessionManager = SessionManager.getManager();
Now whenever we want to get a client session from either web application we make the call
Server serverSession = (Server) sessionManager.getSession("XXX");
From looking at the code for the sessionManager.getSession("XXX") I see that this
results in a synchronized method invocation which is in turn bottlenecking our database access code.
My question is should we not just be storing the Server in a static instance variable to distribute client sessions to both web applications and not the SessionManager.

Hi,
One SSA is ok, but you should think about access rights. If the access is clear cut between all the web apps you should be ok with one SSA. Multiple result sources limiting on content source also works, but could easily be bypassed.
Multiple SSA's will eat up RAM/CPU like a mother :)
As for popular etc.. it could be due to how those sources are set up, but haven't investigated or tested this much.
Thanks,
Mikael
Search Enthusiast - SharePoint MVP/MCT/MCPD - If you find an answer useful, please up-vote it.
http://techmikael.blogspot.com/
Author of Working with FAST Search Server 2010 for SharePoint

Sharing portlets across multiple portal applications

Hello all,
I have a single enterprise application that consists of several portal web applications. Most of these portal web applications have common portlets within their codebase. Is it possible to share portlet code across multiple web applications?
Thanks

No, not possible, in the same way that sharing JSPs and Pageflows wouldn't be possible across multiple webapps. You can, however, have multiple portals within one Portal webapp, and then you could share portlets and portlet resources amongst those portals.
George

Development of enterprise applications

Hello
What are your advises on using model driven development in developing enterprise applications. LiveCycle Data Services looks very promising, I have found numerous tutorials/videos that shows how fast an application can be build by having methods/functions auto-generated.
What are the best-practices, is it good/bad to use those auto-generated methods, they can really save a lot of time.
All suggestions are welcome, also if you know some existing blog/discussion please let me know.
Thanx

Any generated code is going to follow a specific pattern, and is not a one size fits all solution. Depending on the application, it is important that developers have the ability to customize the generated code to suit their needs. With Data Services, not only can you generate code, you can customize the generated code.
There are a couple of options to customize code:
1. Modify the template: All generated code is backed by a template (we use Freemarker). You can modify the template to fit your application design pattern. The limitation with this approach is that you cannot add/remove templates.
2. Plugin to Modeling plugin: Developers can extend the modeling plugin, and hence the code generation capability. With this approach, developers have full control on what gets generated.
Note: You need to have a good understanding of Fiber core and it's APIs to successful control code generation. These API are in Java and provides you a run-time representation of the data model.
Model driven form follows the same pattern. It is unlikely that you like the generated code as is - I would recommending modifying the template (especially the look and feel) to suit your application design.
However with some application all forms may not have the same consistent look and feel. In such cases, the generated code may be a good starting point, but may require context specific customization.
One of the limitations with LCDS code generation today is that we don't support multiple templates in an application. Developers cannot choose a different template for each entity. We may add this capability in the future. However, if this is really important, you can always extend the plugin to offer this functionality.
Hopefully this provides the information you were looking for.
Thanks,
-Anil

Enterprise Application and Web Portal Projects

I know its possible to have one enterprise application that contains 2 web portal projects. The part Im unsure about is if it is possible to update one web project without having to bring down the other project. Supposedly through console you can do this however I have been unable to get this to successfully work. Is this a known error?

Hi Anikumar!
Yes it is true! The webDynpro make it automaticaly.
I'm not clear with J2EE web application. I don't know how i should get the login parameter for my RFC calls.
I have try:
DestinationService dstserv =(DestinationService) ctx.lookup(DestinationService.JNDI_KEY);
RFCDestination dest =(RFCDestination) dstserv.getDestination("RFC", "test");
Properties destprop = dest.getDestinationProperties();
String user1="MYSAPSSO2";
String passwd1=pass;// pass is encrypted ticket;
destprop.setProperty("jco.client.user",user1);
destprop.setProperty("jco.client.passwd",passwd1);
JCO.Client cl = JCO.createClient(destprop);
cl.connect();
cl.ping();
cl.disconnect();
I also try
IWDJCOClientConnection ca = WDSystemLandscape.getJCOClientConnection("ModelData");
In the contentadministrator Modeldata Destination set to Ticket authentification and it works fine when i test it in webdynpro contentadministrator, but when i try to get the JCOConnection i get a SystemLandscapeException:Error while obtaining JCO connection.
I debugged it and i get a WDRuntimeException--->Nullpointerexception. It seems that the jco destination is not initialized at this time.
Maybe i understand something wrong.
Regards!

Which services should be moved to a new SharePoint Enterprise Application server?

Our farm is currently a WFE and a SQL server. I've been tasked with creating a new SP Enterprise Application/Search server.
Which services should be moved? This is what's currently listed in Services on Server:
Access Database Service Started Stop
Application Registry Service Started Stop
Business Data Connectivity Service Started Stop
Central Administration Started Stop
Claims to Windows Token Service Started Stop
Document Conversions Launcher Service Stopped Start
Document Conversions Load Balancer Service Stopped Start
Excel Calculation Services Started Stop
Lotus Notes Connector Stopped Start
Managed Metadata Web Service Started Stop
Microsoft SharePoint Foundation Incoming E-Mail Started Stop
Microsoft SharePoint Foundation Sandboxed Code Service Stopped Start
Microsoft SharePoint Foundation Subscription Settings Service Stopped Start
Microsoft SharePoint Foundation Web Application Started Stop
Microsoft SharePoint Foundation Workflow Timer Service Started Stop
PerformancePoint Service Started Stop
Search Query and Site Settings Service Started Stop
Secure Store Service Started Stop
SharePoint Foundation Search Stopped Start
SharePoint Server Search Started Stop
User Profile Service Started Stop
User Profile Synchronization Service Started Stop
Visio Graphics Service Started Stop
Web Analytics Data Processing Service Started Stop
Web Analytics Web Service Started Stop
Word Automation Services Started Stop

Take a look at http://www.microsoft.com/en-us/download/details.aspx?id=37000. It should help you decide where it is most appropriate to locate services.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Getting error while deploying the Enterprise application

iam getting the Error while i deploying enterprise application which contain the EJB methods.
that Error iam getting like follow.
java.rmi.RemoteException: Cannot deploy application sap.com/Energy_eap.. Reason: Incorrect application sap.com/Energy_eap:Error in the remote interface com.bean.Stateless_bean of bean Stateless_beanBean: No corresponding business method in the bean class com.bean.Stateless_beanBean was found for method Insert.nested exception is: com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Incorrect application sap.com/Energy_eap:Error in the remote interface com.bean.Stateless_bean of bean Stateless_beanBean: No corresponding business method in the bean class com.bean.Stateless_beanBean was found for method Insert.Error in the remote interface com.bean.Stateless_bean of bean Stateless_beanBean: No corresponding business method in the bean class com.bean.Stateless_beanBean was found for method view.
at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:66)

Hello,
based on the exception message there is a missing method in your ejb (insert)
take a look at the signature of the method and the visibilty (public) - and look for typos
regards franz
...close thread if question is answered

Deployment Problems of Enterprise Application in NWDS 7.1

Hello Everyone, 
 
I am having a problem when trying to deploy an application I made to the server. The project consists of two DCs, one which is an Enterprise Application and the other is a Web Module. I have configured the web module to be a dependency of the Enterprise application, so that the .war file generated from the Web Module DC is contained within the .ear file created when the Enterprise Application DC is built. The only dependency that the Web Module DC has is "engine.jee5.facade," which is there by default when it is created. I have not added any code to either DC, because I was just trying to test if I could deploy something to the server before I got into that. When I build the Enterprise Application DC, both DCs build successfully (because of the dependency). When I deploy the Enterprise Application DC, I get an "[ERROR CODE DPL.DC.5089]" error message. When I checked the SDN for what that error code means, I get sent to <a href="http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P58">http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P58</a>, which is pretty vague.
I did try to see if I could deploy the .ear by itself, without the war file within it (by removing the dependency on the Enterprise Application DC) and that seemed to work ok. Its just seems to be when the Web Module is a dependency of the Enterprise Application is when it fails. I have included the error message I get from NWDS below. Thanks in advance for any help you can offer. SUMMARY 
~~~~~~~~~~~~~~~~~~~ 
Successfully deployed: 0 
Deployed with warnings: 0 
Failed deployments: 1 
~~~~~~~~~~~~~~~~~~~ 
ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
; nested exception is:
 com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it. 
 
1. File:C:\Develop\workspace.jdi\2\DCs\sap.com\test\sgj_ent_app_test_three\_comp\gen\default\deploy\sap.comtestsgj_ent_app_test_three.ear 
 Name:test~sgj_ent_app_test_three 
 Vendor:sap.com 
 Location:PDI_J2EETST1_D 
 Version:20100716152020 
 Deploy status:Aborted 
 Version:HIGHER 
 
 Description: 
 1. [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container. 
 
Exception: 
com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
Reason: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
; nested exception is:
 com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it.
 at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:715)
 at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:226)
 at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:112)
 at com.sap.ide.eclipse.j2ee.engine.deploy.view.deploy.action.DeployAction$DeployActionJob.run(DeployAction.java:222)
 at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
; nested exception is:
 com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it.
 at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:188)
 at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it.
 at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:81)
 at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:110)
 at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
 at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
 ... 8 more
Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
 com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.
 at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:4712)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:426)
 at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:67)
 ... 11 more
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:496)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:197)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2534)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:525)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:424)
 ... 12 more
Caused by: java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException:
 at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:73)
 at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:54)
 at com.sap.engine.services.security.server.AuthenticationContextImpl.setProperty(AuthenticationContextImpl.java:533)
 at com.sap.engine.services.servlets_jsp.server.deploy.util.SecurityUtils.initSecurityConfiguration(SecurityUtils.java:722)
 at com.sap.engine.services.servlets_jsp.server.deploy.util.SecurityUtils.createSecurityResources(SecurityUtils.java:143)
 at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.initXmls(DeployAction.java:778)
 at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.deploy(DeployAction.java:301)
 at com.sap.engine.services.servlets_jsp.server.deploy.UpdateAction.makeUpdate(UpdateAction.java:340)
 at com.sap.engine.services.servlets_jsp.server.deploy.WebContainer.makeUpdate(WebContainer.java:341)
 at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.makeUpdate(ContainerWrapper.java:279)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:490)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:197)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2534)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:525)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:424)
 at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:67)
 at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:110)
 at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
 at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
 at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Edited by: Savin on Aug 5, 2010 10:25 PM
Edited by: Savin on Aug 5, 2010 10:26 PM
Edited by: Savin on Aug 5, 2010 10:31 PM
Edited by: Savin on Aug 5, 2010 5:27 PM
Edited by: Savin on Aug 5, 2010 5:38 PM
Edited by: Savin on Aug 5, 2010 5:44 PM

Hi Veera/Abhi
I have installed MinDB and all the required files on the PDA. It is synchronizing with the middleware.
On my NWDS PDA Simulator , the application is appearing but when i click on the application there is no data and it is giving exception
2009-02-11 13:02:40 ... (com.sap.tc.mobile.cfs.pers.PersistenceManager:release resultset) Thread: Finalizer Error: java.sql.SQLException: Result set is closed
Madhu--
Please find my ans to the following points mentioned by you
1) BASIS SWCV must be assigned in the Distribution Model Software Component Version tab of the device.
It is assigned
2) Activate the "DISTRIBUTE_USER_DETAILS" Rule in the admin.
Rule is activated
3) Activate the "DISTRIBUTE_USER_AUTHORIZATIONS" Rule in the admin.
Rule is activated
4) Make sure that you have installed the following components in the following sequence in the PDA
- Creme
- MinDB/DB2e
- PDA_eswt_container
- PDA Runtime.
Client is installed in this sequence only. I referrred to help.sap.com while installing
the application should atleast work in the NWDS PDA simulator. My basic problem is it is not picking up the data. giving the above mentioned error.
Regards
Priya

OIM (11.1.2.0.0) Enterprise Application is in 'failed' state

Problem Summary
OIM (11.1.2.0.0) Enterprise Application is in 'failed' state after the installation and configuratio
Problem Description
We have installed IDM suite relese2, as part of this Oracle SOA, OIM is installed and configigured; All the manage server and Admin server are up and running. When i look into OIM manage server -> deployments one of the application 'OIM (11.1.2.0.0) ' is in failed state.
Below are the errors it thrown
<BEA-149205> <Failed to initialize the application 'oim [Version=11.1.2.0.0]' due to error java.security.AccessControlException: access denied ("oracle.security.jps.service.credstore.CredentialAccessPermission" "context=SYSTEM,mapName=oim,keyName=OIMSchemaPassword" "read").
java.security.AccessControlException: access denied ("oracle.security.jps.service.credstore.CredentialAccessPermission" "context=SYSTEM,mapName=oim,keyName=OIMSchemaPassword" "read")
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:366)
at java.security.AccessController.checkPermission(AccessController.java:560)
at oracle.security.jps.util.JpsAuth$AuthorizationMechanism$3.checkPermission(JpsAuth.java:458)
at oracle.security.jps.util.JpsAuth.checkPermission(JpsAuth.java:518)
at oracle.security.jps.util.JpsAuth.checkPermission(JpsAuth.java:544)
Truncated. see log file for complete stacktrace
Caused By: java.security.AccessControlException: access denied ("oracle.security.jps.service.credstore.CredentialAccessPermission" "context=SYSTEM,mapName=oim,keyName=OIMSchemaPassword" "read")
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:366)
at java.security.AccessController.checkPermission(AccessController.java:560)
at oracle.security.jps.util.JpsAuth$AuthorizationMechanism$3.checkPermission(JpsAuth.java:458)
at oracle.security.jps.util.JpsAuth.checkPermission(JpsAuth.java:518)
at oracle.security.jps.util.JpsAuth.checkPermission(JpsAuth.java:544)
Truncated. see log file for complete stacktrace
Edited by: 1000558 on Apr 17, 2013 1:25 AM

No,
The OIM 11.1.2.1 is PS1.
You can apply BP of PS1 on OIM 11.1.2.1 only.
You can not apply BP of PS1 to 11.1.2.0.10. Oracle some times provide PSA(Patch set assitance) to upgrade to PS1. You can better check with Oracle about uses on this.
~J

How to manage large database records in enterprise application

Hi All,
I am working on a large enterprise application relating to Capital Market. I am working in Java and with its extended technology. I am facing one critical problem which needs solution from your side. I have a database table which contains approximately more than 5 millions of records, I want to display the records with proper pagination. Here I am using Hibernate for database related stuffs. I am using a query which contains a join query to load the records. After the query the filtered records come to approcimately 80,000. I am unable to make proper pagination, everytime for next or previous set of 10 records I hit the database which is a time consuming affair. I do not know what I will do , should I cache the data for pagination. Everytime I load more than 80,000 records, think that in an web based application, the no of users are 5000, then how to manage. I need core java level solution not in the JSP level. Please help me in this regard.

After the query the filtered records come to approcimately 80,000. I am unable to
make proper pagination,Just a thought. If you display 50 per page, that's 1600 pages. Say it takes the user
15 seconds to read the page: total 400min=6 2/3 hours and probably a bad case of RSI.
The proper pagination would possibly be no pagination.

How do I configure an enterprise application using Weblogic 10 wlconfig

Hi All,
I am converting an installer from WL8 to WL10. We use wlconfig to configure our EAR in wl8 with several wlconfig commands. These don't seem to work though when attempting to use wl10. The following error comes up more often than not and does not seem to be appropriate to what is actually happening.
Unable to create new bean of type WebAppComponent for pcidomain_new:Name=GenPortal,Type=Application:missing create method
I have searched the Weblogic Documentation and have found only general information on how to use wlconfig with a simple example that does not touch on application deployment. I have also found an MBean Reference but am unclear as to how to marry the two.
It would be really great if someone knew where I might find a concrete example of creating an Enterprise application using WL10.
Here is the current wlconfig task that we use successfully in weblogic 8.
${server-mbean} is read in earlier with a wlconfig query command.
 <wlconfig url="t3://${env.COMPUTERNAME}:${weblogic_port}" username="${weblogic_username}" password="${weblogic_password}">
 <create type="Application" name="GenPortal" property="GenPortalApp">
 <set attribute="Path" value="${domain_home}/${domain_name}/applications/GenPortal.ear" />
 <set attribute="StagingMode" value="nostage" />
 <set attribute="TwoPhase" value="true" />
 <create type="WebAppComponent" name="GenPortal">
 <set attribute="Targets" value="${server-mbean}" />
 <set attribute="URI" value="GenPortalWebApp.war" />
 </create>
 <create type="EJBComponent" name="GenPortalEJB">
 <set attribute="Targets" value="${server-mbean}" />
 <set attribute="URI" value="GenPortalEJB.jar" />
 </create>
 <create type="EJBComponent" name="BidEvaluatorEJB">
 <set attribute="Targets" value="${server-mbean}" />
 <set attribute="URI" value="BidEvaluatorEJB.jar" />
 </create>
 <create type="EJBComponent" name="BidFormulatorEJB">
 <set attribute="Targets" value="${server-mbean}" />
 <set attribute="URI" value="BidFormulatorEJB.jar" />
 </create>
 <create type="EJBComponent" name="ConfiguratorEJB">
 <set attribute="Targets" value="${server-mbean}" />
 <set attribute="URI" value="ConfiguratorEJB.jar" />
 </create>
 <create type="EJBComponent" name="ISOCommunicationEJB">
 <set attribute="Targets" value="${server-mbean}" />
 <set attribute="URI" value="ISOCommunicationEJB.jar" />
 </create>
 <create type="EJBComponent" name="LMPManagerEJB">
 <set attribute="Targets" value="${server-mbean}" />
 <set attribute="URI" value="LMPManagerEJB.jar" />
 </create>
 <create type="EJBComponent" name="ScriptCalcEJB">
 <set attribute="Targets" value="${server-mbean}" />
 <set attribute="URI" value="ScriptCalcEJB.jar" />
 </create>
 <create type="EJBComponent" name="SettlementEJB">
 <set attribute="Targets" value="${server-mbean}" />
 <set attribute="URI" value="SettlementEJB.jar" />
 </create>
 </create>
 <create type="StartupClass" name="PCI_Initializer">
 <set attribute="Targets" value="${server-mbean}" />
 <set attribute="ClassName" value="com.pci.gtdw.bean.Initialize" />
 <set attribute="Arguments" value="port=${weblogic_port},user=background,password=${background_user_password},debug=false,loggerLevel=debug" />
 </create>
 <set mbean="${domain_name}:Name=${domain_name},Type=JTA" attribute="TimeoutSeconds" value="1200" />
 </wlconfig>
As I mentioned earlier right now this fails with when trying to create the WebAppComponent as seen in the error message above.
Thanks for any help you can provide.

Here's a couple ideas:
1. Easier, but with non-deterministic response time: Wire the button up to one of your I/O pins and poll it. When you detect the button, issue a software call to stop the pulse train. If the duration of the button press may be short compared to your polling rate, then wire it to a counter source pin and perform edge counting. When you poll any value > 0, the press has happened. (Sometimes the value may be >1 if the switch has "bounce").
2. Trickier, but with deterministic hardware timing: Configure another counter, call it counter B, for triggered pulse generation. Wire/configure the button as the trigger. Make sure that the "high time" of the pulse is long enough to let your software respond, if needed. Also configure your original continuous pulse train counter to use Ctr B's output as a "pause trigger", specifying to pause when high. When the button is pressed, counter B will fire a pulse and that pulse will inhibit your original counter's pulse generation. In short, the pulses will stop until counter B's pulse has completed its full duration. Your software can monitor for this series of events and stop the original counter task if needed.
-Kevin P.

Enterprise application conversion problem from WLS 10.3.0 to WLS 10.3.2

Hi all,
I'm posting this just to document a problem I had when converting an Enterprise Application from WLS 10.3.0 across to WLS 10.3.2 environment.
Upon deployment of the application I was getting this error:
Caused By: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j2ee.descriptor.wl.ApplicationParamBeanImpl@b720894d(/ApplicationParams[webapp.encoding.default])"
 at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:227)
 at weblogic.j2ee.descriptor.wl.WeblogicApplicationBeanImpl.setApplicationParams(WeblogicApplicationBeanImpl.java:560)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:48)
 at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindingType.java:536)
 at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType$QNameRuntimeProperty.fillCollection(AttributeRuntimeBindingType.java:381)
 at com.bea.staxb.runtime.internal.MultiIntermediary.getFinalValue(MultiIntermediary.java:52)
 at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType.getFinalObjectFromIntermediary(AttributeRuntimeBindingType.java:140)
 at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:200)
 at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)
 at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
 at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)
 at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
 at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
 at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
 at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
 at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
 at weblogic.application.ApplicationDescriptor.getWeblogicApplicationDescriptor(ApplicationDescriptor.java:329)
 at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:181)
 at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
 at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
 at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
 at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
 at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
 at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:81)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:97)
 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)
It turns out this was an issue with the META-INF/weblogic-application.xml having duplicate entries for the "webapp.encoding.default" parameter.
This obviously got duplicated when my app was re-imported into the Eclipse OPEP environment for WLS 10.3.2
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-application xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-application" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/javaee_5.xsd http://xmlns.oracle.com/weblogic/weblogic-application http://xmlns.oracle.com/weblogic/weblogic-application/1.0/weblogic-application.xsd">


<wls:application-param>
<wls:param-name>webapp.encoding.default</wls:param-name>
<wls:param-value>UTF-8</wls:param-value>
</wls:application-param>
<wls:application-param>
<wls:param-name>webapp.encoding.default</wls:param-name>
<wls:param-value>UTF-8</wls:param-value>
</wls:application-param>
</wls:weblogic-application>
Removing the duplicate entry resolved this problem.
I hope this helps anyone else that experiences this issue.
Regards,
Paul

Below link might be helpful.
http://kr.forums.oracle.com/forums/thread.jspa?threadID=1049509&tstart=0
Regards,
Anandraj
http://weblogic-wonders.com/

@Startup doesn't work in Enterprise application

Hi,
I've done a simple web application. Here when use the @Startup annotation the method @PostConstruct is called every time i start my application.
When I do the same with an Enterprise application the @PostConstruct method of my ejb is never called.
I'm using Glasfish 4 and Java 7
Thank you!
Fabio

Nobody knows or has an idea about this strange issue?

Multiple enterprise applications

Similar Messages

Maybe you are looking for