Win a copy of Zero to AI - A non-technical, hype-free guide to prospering in the AI era this week in the Artificial Intelligence and Machine Learning forum!

Tony Per

Greenhorn
+ Follow
since Nov 11, 2003
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Tony Per

1. Ripple goes through the process of taking any configuration settings in the server group (cluster) and distributing them amongs your declared clones. this proecess also performs the a sequential stop and restart of the cloned app server in order for the configurations setting to take place through out your cluster without causing any down time.
2. it is my understanding that the only time you need to regen the plugin confing is when either the console in the admin console states that "the action preformed ... invalidates the server pluggin, you will need to regen the plugin" or when there is a change within your EAR (adding a new servlet, adding another clone, changind the transport setting).
3. if you are in a cloned environment and you regen the plugin, you will have to manually copy it out to another server only if the http server is located on a remote machine from where your nodes are setup. easier ways might include writting a script to do this or getting technologies such as AFS working within your cluster.
hope some of this helps,
--Tony
16 years ago
Well I have set up the persistent session DB using Oracle Using the DB2 specifications in the IBM white paper entitled "http session best practices". in the DB specs for DB2 there is a data type for column named "MEDIUM" that is declared as a LONG in DB2. I have been told by our DBA staff that LONG is no longer supported in Oracle and that now it has been replaced by the BLOB. so in any case I am still looking for someone who has succesfuly implemented the persisten session DB using WAS 4.05 and Oracle 8.17 if anyone has any leads it is strongly appreciated.

thanks,
--Tony
16 years ago
I have found numerous documents on setting up a persistent session database using DB2. I had our DB group create a sessions table that follows the same spect that DB2 but using Oracle. on the admin console we keep on getting errors that are in the nature of errors trying to insert a long into a non long column. I know, the solution would be making the column a LONG in Oracle, but it is my understanding that LONG was depracated in Oracle and now they use a BLOB instead
Has anyone encountered this and found a different solution? it specially happens on the MEDIUM colum.

Thank you,
--Tony
16 years ago