It's all about the answers!

Ask a question

Required steps to configure Non LDAP WAS setup with CLM


Joseph Simon Arokiaraj (21414845) | asked Feb 19 '12, 6:57 p.m.
Hi All,

I am planning to do migration from tomcat to WAS in our test environment.

Current setup:

1. CLM 3.0.1/ Tomcat/ AIX / Oracle

Disbaled the default "ADMIN" user while configuring the JTS. For now, we are not going to use LDAP for this test setup. JTS/CCM/QM/RM gets user information from Tomcat.

Could you please update me the procedure to create users in WAS and configure WAS users with the CLM?

Currently JAZZ is running as "root" and WAS process is running as "wasadmin" user.

Waiting for your reply.

Cheers,
Jose

5 answers



permanent link
Andy Howell (1111) | answered Feb 20 '12, 5:43 a.m.
Hi Jose,

Please refer to

Setting up the WebSphere Application Server custom registry. http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/index.jsp?topic=/com.ibm.jazz.install.doc/topics/t_instl_config_was_registry.html

if you are evaluating without connecting to LDAP.

Good luck
Andy Howell

permanent link
Joseph Simon Arokiaraj (21414845) | answered Feb 20 '12, 8:18 a.m.
Hi Andy,

Thanks a lot for your quick reply.

Deployed the apps to WAS, added the JDBC driver path to the classpath ( http://publib.boulder.ibm.com/infocenter/mpadoc/v6r1m0/index.jsp?topic=%2Fcom.ibm.websphere.wemp.doc%2Fconfiguring%2Fconfiguringandusingtheoracle10gjdbcdriver.html) and restarted the server.

Initially it redirects to https://xxxx:9443/jts/auth/authrequired and prompts for UserID and Password. On submitting the login credentails it redirects to https://xxxx:9443/jts/admin and got hanged with the message "Loading".

Have you come across this type of login issue before? Please update your thoughts on this when you find time.

Cheers,
Jose





















Hi Jose,

Please refer to

Setting up the WebSphere Application Server custom registry. http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/index.jsp?topic=/com.ibm.jazz.install.doc/topics/t_instl_config_was_registry.html

if you are evaluating without connecting to LDAP.

Good luck
Andy Howell

permanent link
Anthony Kesterton (7.5k9180136) | answered Feb 20 '12, 10:05 a.m.
JAZZ DEVELOPER
Hi Andy,

Thanks a lot for your quick reply.

Deployed the apps to WAS, added the JDBC driver path to the classpath ( http://publib.boulder.ibm.com/infocenter/mpadoc/v6r1m0/index.jsp?topic=%2Fcom.ibm.websphere.wemp.doc%2Fconfiguring%2Fconfiguringandusingtheoracle10gjdbcdriver.html) and restarted the server.

Initially it redirects to https://xxxx:9443/jts/auth/authrequired and prompts for UserID and Password. On submitting the login credentails it redirects to https://xxxx:9443/jts/admin and got hanged with the message "Loading".

Have you come across this type of login issue before? Please update your thoughts on this when you find time.

Cheers,
Jose





















Hi Jose,

Please refer to

Setting up the WebSphere Application Server custom registry. http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/index.jsp?topic=/com.ibm.jazz.install.doc/topics/t_instl_config_was_registry.html

if you are evaluating without connecting to LDAP.

Good luck
Andy Howell


Hi

Check the logs for JTS, and your WAS logs to see if there are any problems. Also - RTC will take a while to load the first page the very first time it runs (but not that long....)

anthony

permanent link
Joseph Simon Arokiaraj (21414845) | answered Feb 20 '12, 12:12 p.m.
Hi Anthony,

Found this in the SystemOut.log

0000001a webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: -: com.ibm.ws.webcontainer.webapp.WebAppErrorReport
: CRJAZ1173I Service "com.ibm.team.repository.service.discovery.IDiscoveryService" is not available.
at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.sendError(WebAppDispatcherContext.java:637)
at com.ibm.ws.webcontainer.srt.SRTServletResponse.sendError(SRTServletResponse.java:1187)
at com.ibm.team.repository.common.transport.ServerHttpUtil.sendError(ServerHttpUtil.java:1239)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleException(AbstractTeamServerServlet.java:1276)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:1806)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:1723)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1632)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:75)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:76)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1657)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:939)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:179)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3935)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1592)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:452)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:511)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:305)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1784)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)


Have you got any idea on this errror?

Thanks in advance.

Cheers,
jose





Hi Andy,

Thanks a lot for your quick reply.

Deployed the apps to WAS, added the JDBC driver path to the classpath ( http://publib.boulder.ibm.com/infocenter/mpadoc/v6r1m0/index.jsp?topic=%2Fcom.ibm.websphere.wemp.doc%2Fconfiguring%2Fconfiguringandusingtheoracle10gjdbcdriver.html) and restarted the server.

Initially it redirects to https://xxxx:9443/jts/auth/authrequired and prompts for UserID and Password. On submitting the login credentails it redirects to https://xxxx:9443/jts/admin and got hanged with the message "Loading".

Have you come across this type of login issue before? Please update your thoughts on this when you find time.

Cheers,
Jose





















Hi Jose,

Please refer to

Setting up the WebSphere Application Server custom registry. http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/index.jsp?topic=/com.ibm.jazz.install.doc/topics/t_instl_config_was_registry.html

if you are evaluating without connecting to LDAP.

Good luck
Andy Howell


Hi

Check the logs for JTS, and your WAS logs to see if there are any problems. Also - RTC will take a while to load the first page the very first time it runs (but not that long....)

anthony

permanent link
Joseph Simon Arokiaraj (21414845) | answered Feb 21 '12, 5:22 a.m.
Hi All,

I have problem in connecting to the ORACLE JDBC driver.

Error:

Public URI: "https://xxxx:9443/jts"
2012-02-21 10:03:37,132 INFO .repository.service.internal.rdb.ConnectionFactory - CRJAZ1365I The server is attempting to connect to the following database: "thin:jts_owner
/xxxxxxxx@//xxxx:xxxx/ctmpoc"
2012-02-21 10:03:37,133 ERROR .repository.service.db.provider.AbstractDbProvider - CRJAZ1840W The driver "oracle.jdbc.OracleDriver" could not be loaded and registered. Thi
s JDBC driver jar must be provided in a path configured by the server scripts. Please ensure that the driver is in the expected location of "/oracle/product/11.2_client64/ojdbc5.jar" or consult product set
up instructions to change the location.
2012-02-21 10:03:37,151 ERROR t.internal.registry.AbstractActivationManagerOwner - CRJAZ1093I The following service class was not activated: "com.ibm.team.repository.servic
e.internal.schemagen.PersistentMappingService"

I have created a new variable JDBC_ORACLE (value: /oracle/product/11.2_client64/ojdbc5.jar) under custom properties in Process definition and its not working well.

I also tried JDBC_ORACLE=file:///oracle/product/11.2_client64/ojdbc5.jar and it produced a different error.

Error:

Caused by:
java.lang.IllegalStateException: CRJAZ1855E The driver "oracle.jdbc.OracleDriver" could not be loaded and registered. This JDBC driver jar must be provided in a path configured by the server scripts. It a
ppears that the JDBC driver location, "file:///oracle/product/11.2_client64/ojdbc5.jar", was incorrectly specified as a URL. Please ensure that the JDBC driver location is provided as a normal file path, n
ot a URL.

Please update me if you find any clue on this.


Cheers,
Simon







Hi Andy,

Thanks a lot for your quick reply.

Deployed the apps to WAS, added the JDBC driver path to the classpath ( http://publib.boulder.ibm.com/infocenter/mpadoc/v6r1m0/index.jsp?topic=%2Fcom.ibm.websphere.wemp.doc%2Fconfiguring%2Fconfiguringandusingtheoracle10gjdbcdriver.html) and restarted the server.

Initially it redirects to https://xxxx:9443/jts/auth/authrequired and prompts for UserID and Password. On submitting the login credentails it redirects to https://xxxx:9443/jts/admin and got hanged with the message "Loading".

Have you come across this type of login issue before? Please update your thoughts on this when you find time.

Cheers,
Jose





















Hi Jose,

Please refer to

Setting up the WebSphere Application Server custom registry. http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/index.jsp?topic=/com.ibm.jazz.install.doc/topics/t_instl_config_was_registry.html

if you are evaluating without connecting to LDAP.

Good luck
Andy Howell

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.