Antonio Smoljo

How to deploy EAR into the Websphere Application server cluster and IBM HTTP server by Monitored Directory Deployment functionality?

My goal is to automatically deploy EAR file in WebSphere Application server cluster by Monitored Directory Deployment. So my deployment target is cluster. WAS version is 9.0.0.10. Everything works fine if I drop EAR file in
monitored directory for example '/{monitored_directory_defined_in_WAS}/clusters/my_cluster_name/'. Application is deployed and started. But I also want to deploy that application into the IBM HTTP server(resides in the same WebSphere cell with cluster) in the same automatically process by Monitored Directory Deployment.


I tried to manually predefine deploymentTargets(cluster and ibm http server) in deployment.xml file, put it in the EAR file, and drop EAR in the '/{monitored_directory_defined_in_WAS}/clusters/my_cluster_name/', but WAS deploy EAR only in cluster. As a consequence I must manually via WAS console map all modules from EAR to ibm http server, but I do not want to do it manually.

My second idea/attempt was sto create separate monitored directory for the ibm http server '/{monitored_directory_defined_in_WAS}/servers/my_ibm_http_server_name/'.
First I drop EAR into the '/{monitored_directory_defined_in_WAS}/clusters/my_cluster_name/' and right after that I drop EAR in to the '/{monitored_directory_defined_in_WAS}/servers/my_ibm_http_server_name/'. Result is that the EAR modules are deployed only in to the web server, and that is not my goal.



Is that even possible by WAS Monitored Deployment Directory functionality?
Is it allowed to manually create the deployment.xml file and add it to the EAR file?

I am running a web application on Websphere application server BASE 9.0.0.8
Websphere security is configured with standalone LDAP registry(OpenLdap), which is also registry for application users.

After server is started user log in is normal and takes a few seconds.
After certain time of inactivity application session is timed out and user must log in again, but this time log in takes a few minutes.
I didn't noticed any records in the server logs that would explain such login delay, so I enabled LTPAToken2 tracing with this string '*=info:com.ibm.ws.security.ltpa.LTPAToken2=all'.
After reproducing login delay problem I checked trace log where I found large number of this records:

[9/27/18 14:07:28:532 CEST] 0000009c LTPAToken2    3   Returning existing encrypted bytes from token object.
[9/27/18 14:07:28:532 CEST] 0000009c LTPAToken2    3   Expiration returned from expire field in token: Thu Sep 27 14:35:00 CEST 2018
...
Approximately 1100 of these lines were recorded in trace log during the login delay. Initially almost 200 records in one second, and later less frequently with one record every few seconds.
After about two minutes of delay user is loged into the application with this records in trace log:

[9/27/18 14:09:46:132 CEST] 0000009c LdapRegistryI A   SECJ0419I: The user registry is currently connected to the LDAP server ldap://machineX:389.
[9/27/18 14:09:46:146 CEST] 0000009c LTPAToken2    >  new LTPAToken2 from accessID Entry
[9/27/18 14:09:46:146 CEST] 0000009c LTPAToken2    3   userdata areau:user\:machineX\:389/uid=userX,ou=Users,dc=companyX,dc=xy
[9/27/18 14:09:46:146 CEST] 0000009c LTPAToken2    3   Expiration returned from expire field in token: Thu Sep 27 16:10:00 CEST 2018
[9/27/18 14:09:46:146 CEST] 0000009c LTPAToken2    3   Expiration set to: Thu Sep 27 16:10:00 CEST 2018
[9/27/18 14:09:46:146 CEST] 0000009c LTPAToken2    <  new LTPAToken2 from accessID Exit
[9/27/18 14:09:46:146 CEST] 0000009c LTPAToken2    3   Token was updated thus clearing encrypted bytes to re-encrypt.
[9/27/18 14:09:46:146 CEST] 0000009c LTPAToken2    3   Token was updated thus clearing encrypted bytes to re-encrypt.
[9/27/18 14:09:46:146 CEST] 0000009c LTPAToken2    3   Token was updated thus clearing encrypted bytes to re-encrypt.
[9/27/18 14:09:46:146 CEST] 0000009c LTPAToken2    3   Token was updated thus clearing encrypted bytes to re-encrypt.
[9/27/18 14:09:46:146 CEST] 0000009c LTPAToken2    3   Token was updated thus clearing encrypted bytes to re-encrypt.
[9/27/18 14:09:46:147 CEST] 0000009c LTPAToken2    3   Token was updated thus clearing encrypted bytes to re-encrypt.
[9/27/18 14:09:46:147 CEST] 0000009c LTPAToken2    3   Token was updated thus clearing encrypted bytes to re-encrypt.


I would be very grateful for any help or suggestion

Txh guys,

I solve the problem. I have Windows7 64bit. The only changes I made ​​was 64bit Tomcat switch with 32 bit ,and 64bit java switch for 32 bit .

This is what I'm talking about. A lot of places where you can go wrong, and a huge number of instructions to configure (on the Apache website that is not so clearly). And I accidentally solved the problem. I have not found any information or rules about the 64-bit, 32 bit for Tomcat, Java, OS, DB ...
Unfortunately for this method I've spent so much time.

org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null' - This is very very frustrating

The Internet is full of a variety of instructions for configuring Tomcat database connection. I read a huge number of them. Also all of these instructions is different in some part. Some people solve the problem, but many do not.
Is there somewhere official and accurate step by step, detail by detail instruction (document).... how accurately and precisely configure Tomcat connection to the database ?

Instructions for configuring Tomcat console are terribly bad. Can someone explain simply and efficiently step by step how to enable the administrator console.
I have Tomcat v6.0

Thanks