Nevine El-Saeed

I created a new WebApp and want to deploy it on WebSphere_Portal(intending to run the model standalone on the Websphere Portal Server).

I deployed the ear file via the Websphere admin console (http://<machinename>:9090/admin/), using Applications..Install New Application.., choosing in Step 3 to map the module to the Websphere_Portal server. I completed the deployment, it said it was successful, I saved the changes to Master Configuration in the admin console.

But I try to start the Enterprise App that I just deployed, and there's an "unavailable" icon next to it, even though the EAR is showing up in the installed applications directory. The message in the Messages(s) window says "The application can not be started on server WebSphere_Portal. Make sure the server is started." (And it is)
Later on,I found out that I must run that application from the portal server admin console not the WAS admin console.
When I tried accessing the portal admin console however I couldn't. I added the property:
WpsAdminConsolePort=9091
in wpconfig.properties but I still get HTTP 404 Not Found on:
http://localhost:9091/admin

I really need to deploy an EAR file on the WebSphere_Portal. Can anyone help me?
How can I enable the portal admin console? How do I get to it to run my application?

Thanks in advance.

Hello all

In my application, I am using EJBs. I have 2 EJBs that have a 0ne-to-many relationship (customer-customerNumbers). I have enabled the cascade delete.
When I was using DB2 legacy CLI based type 2 JDBC driver, when I tried to delete the customer, it would delete the customer and all of its numbers without any problems.
When I enabled caching (Life time in cache) and changed to DB2 universal JDBC driver, when I try to do the same, I get the following error:

javax.transaction.TransactionRolledbackException: CORBA TRANSACTION_ROLLEDBACK 0x0 No; nested exception is:
org.omg.CORBA.TRANSACTION_ROLLEDBACK:

Trace from server: 306148906 at host a25ciwps001.toronto.ca.ibm.com >>
org.omg.CORBA.TRANSACTION_ROLLEDBACK: javax.transaction.TransactionRolledbackException: ; nested exception is:
javax.ejb.TransactionRolledbackLocalException: ; nested exception is: com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -532, SQLSTATE: 23504, SQLERRMC: CCSP.CUSTOMER_NUMBER.CUSTOMERN_FK vmcid: 0x0 minor code: 0 completed: No
at com.ibm.ejs.csi.OrbUtilsImpl.mapException(OrbUtilsImpl.java:76)
at com.ibm.ejs.container.RemoteExceptionMappingStrategy.mapEJBException(RemoteExceptionMappingStrategy.java:391)
at com.ibm.ejs.container.RemoteExceptionMappingStrategy.mapException(RemoteExceptionMappingStrategy.java:112)
at com.ibm.ejs.container.RemoteExceptionMappingStrategy.setUncheckedException(RemoteExceptionMappingStrategy.java:202)
at com.ibm.ejs.container.EJSDeployedSupport.setUncheckedException(EJSDeployedSupport.java(Compiled Code))


For some reason, activating the cache and changing the driver caused this error to happen. I don't know whether this is a WAS bug or not. Can anyone help me out?
Thanks alot

Hello all

In my application, I am using EJBs. I have 2 EJBs that have a 0ne-to-many relationship (customer-customerNumbers). I have enabled the cascade delete.
When I was using DB2 legacy CLI based type 2 JDBC driver, when I tried to delete the customer, it would delete the customer and all of its numbers without any problems.
When I enabled caching (Life time in cache) and changed to DB2 universal JDBC driver, when I try to do the same, I get the following error:

javax.transaction.TransactionRolledbackException: CORBA TRANSACTION_ROLLEDBACK 0x0 No; nested exception is:
org.omg.CORBA.TRANSACTION_ROLLEDBACK:

Trace from server: 306148906 at host a25ciwps001.toronto.ca.ibm.com >>
org.omg.CORBA.TRANSACTION_ROLLEDBACK: javax.transaction.TransactionRolledbackException: ; nested exception is:
javax.ejb.TransactionRolledbackLocalException: ; nested exception is: com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -532, SQLSTATE: 23504, SQLERRMC: CCSP.CUSTOMER_NUMBER.CUSTOMERN_FK vmcid: 0x0 minor code: 0 completed: No
at com.ibm.ejs.csi.OrbUtilsImpl.mapException(OrbUtilsImpl.java:76)
at com.ibm.ejs.container.RemoteExceptionMappingStrategy.mapEJBException(RemoteExceptionMappingStrategy.java:391)
at com.ibm.ejs.container.RemoteExceptionMappingStrategy.mapException(RemoteExceptionMappingStrategy.java:112)
at com.ibm.ejs.container.RemoteExceptionMappingStrategy.setUncheckedException(RemoteExceptionMappingStrategy.java:202)
at com.ibm.ejs.container.EJSDeployedSupport.setUncheckedException(EJSDeployedSupport.java(Compiled Code))


For some reason, activating the cache and changing the driver caused this error to happen. I don't know whether this is a WAS bug or not. Can anyone help me out?
Thanks alot

Sorry, the paste didn't come out
what I did was:
in Bean cache area of the deployment descriptor:

I set
ACTIVATE AT: ONCE
LOAD AT: ACTIVATION
PINNED FOR: ACTIVATION_PERIOD

and in the data cache:
Life time in cache usage: OFF


what am I doing wrong?

Working with Websphere is my second experience with application servers after JBoss. Back when I was using JBoss, I was able to work fine with commit option A which caused a remarkable performance boost. When I tried using that option we Websphere 5.1 however, I got a difference of only 2 secs!!!
I am wondering if I am doing something wrong..
The only change I did to the deployment descriptor to allow the commit option A is:
<ejbExtensions xmi:type="ejbext:ContainerManagedEntityExtension" xmi:id="ContainerManagedEntityExtension_1125988416573">
<enterpriseBean xmi:type="ejb:ContainerManagedEntity" href="META-INF/ejb-jar.xml#Customer"/>
<beanCache xmi:id="BeanCache_1125988416573" activateAt="ONCE" loadAt="ACTIVATION" pinnedFor="ACTIVATION_PERIOD"/>
<dataCache xmi:id="DataCache_1125989799043" lifetimeInCache="0" lifetimeInCacheUsage="OFF"/>
</ejbExtensions>
I am a bit confused by what pinnedFor means and how is data caching different from bean caching? I thought that caching beans means caching the results of specfic finder methods and so whenever a second call is made to that method, it retrieved cached beans (data) rather than go to the database.
Please help me out. Websphere turned out to be much more complicated than I though and to be honest, JBoss was working great for me until I moved to work for IBM )
Thanks in advance