Z-Archive » IBM Porting » OnlineApps - RIB/RSS

-grant "load" privilege to user RIB.
-increase tablespace page size (table IB_SERVICE_INFO too large, need to increase page size)
-create new buffer space with larger page size
-create new tablespace with the new buffer space, having larger page size.

RIB table schema import completed, data of IB_SERVICE_INFO not imported yet, need to import manually or use the tool (have to drop the rib schema and re-import everything again.)

successfully ported the data and schema of RIB from oracle to the db2.

ported the schema and data into the DB2.
deployed RSS, RIB and Upass server(webservice) into the WAS7.
Upass web service is working through JNDI datasource.
RSS is working properly.

Now working on RIB, try to register a new user using "first time login" with the mockup mode. Faced some problems with the way upass getting the sequence. "SELECT seq_user_id.NEXTVAL FROM dual". Need some time to work on it, may have to rewrite all of the code related to database sequence.

Discovered another issue caused by the usage of "Insert All" which used to insert multiple rows in one SQL call.

DB2 uses different syntax for this.

Ref:
http://en.wikipedia.org/wiki/Insert_(SQL)#Multirow_inserts

update the upass core query to insert one by one instead of using the oracle syntax "insert all".

created new rib user successfully using the "first time login" with mock up.

tried to deploy the jms stuff.
created connection factory and queues.

deployed message driven bean. seems to be working.

tried to deploy web service ejb for request queue and response queue , error. Probably because it is compiled using weblogic ant script and written on weblogic syntax.

Need to decide whether to proceed with making them to work on WAS, or go for clustering, or end the engagement.

JMS is not part of our deployment. As long as our MSS and RIB is up and running. Thanks for the update.

WAS Clustering (Pre-configuration)

Server: T2 & T3

Prerequisite:
1)Date & Time should 5 minutes different for both servers
2)edit the /etc/hosts files for hostname

On T2:
1)Create Deployment Manager profile - create cell
2)Add Node 1 to cell

On T3:
1)Install WAS
2)Create Node 2 profile
3)Add Node 2 to cell
4)Install IBM HTTP Server
5)Configure IHS plugin - mapping the application to IHS

Verify all the application are work when accessing from IHS.
After this proceed with WAS Clustering.

WAS Clustering setup successfully.

Now issue on RIB & RSS, after success to login, cannot do anything as the browser session expired after clicked any links. Will proceed on Wednesday

RSS browser error message:

You have left the browser idle for more than 30 minutes. Please login again.

RIB browser error message:

You have left the browser idle for more than 5 minutes. Please login again.

RIB log
-------

2011/04/25 17:32:43:556 ERROR ib.common.utils.SetSessionTimeout: java.lang.NullPointerException
Exception class : org.apache.struts.action.RequestProcessor, class method : processException, line number : 545org.apache.struts.action.RequestProcessor.processException(RequestProcessor.java:545)
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:486)
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
com.ib.common.utils.IBActionServlet.doGet(IBActionServlet.java:64)
javax.servlet.http.HttpServlet.service(HttpServlet.java:718)
javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1657)
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1597)
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:131)
com.ib.common.utils.SetSessionTimeout.doFilter(SetSessionTimeout.java:94)
com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)
com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908)
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:934)
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)
com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:179)
com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:91)
com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:864)
com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583)
com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:445)
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:504)
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:301)
com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83)
com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)

im guessing.. - could be the sticky session.
continue on Wednesday.

session fail-over not working as some of the objects we stored in the session is not serialized. Turn off the session replicating and the applications work well in the clustering environment. It works like normal load balancing without the session fail-over. User would need to login again to server B if the server A died.

Mahem suggests that we do not need to use the clustering version of WAS if we do not utilize the session replicating feature.

A formal engagement from IBM international team would be needed for the banking framework certification. We would have to setup our applications again and demo it to them. Then the logs would be sent to them and they will ask question if there are any bad practice or error.