Websphere and Two Enterprise Servers

[Sanjeev_Harrish]

Hi,

I've got an issue at a client's site with Websphere/JAS setup. Briefly, client has 2 Enterprise Servers (DEV running DV/PY and PROD running PD). Originally DEV was setup. The environment configured for HTML was PY7333. The PROD server was added recently and configured for PD7333 environment. A couple of days ago, SYS7333, DD7333 and OL7333 was moved from DEV server to PROD server. All the necessary CNC config was carried out (datasources/ODBC etc.). Fat clients are all fine with this change. However, cannot logon to JPY7333 via browser. Generator PC will also no longer connect to the Webserver.

The jas logs indicate that the system cannot find any of the security files. I've proved this by putting the system back on DEV server - both HTML and generator PC were fine again. I can see that Web server still looks at the DEV box for SYS7333 from the logs.

Does anyone know where I can change this? All the entries in the JAS.ini point to the PROD box. Any input would be appreciated.

Rgds.,

Sanjeev
(CNC Consultant)

AS/400 v5r1, SP18.1, Update 5, Coexistent, Websphere 3.5 fix pack 5 running on AS/400.

 

[andymcclure]

Sanjeev,

The boot-strap settings that tell the JAS server where to find the system
tables is in the JAS.INI Search and replace the old system name with the
new prod system.


Hope this helps,

Andy



I've got an issue at a client's site with Websphere/JAS setup. Briefly,
client has 2 Enterprise Servers (DEV running DV/PY and PROD running PD).
Originally DEV was setup. The environment configured for HTML was PY7333.
The PROD server was added recently and configured for PD7333 environment. A
couple of days ago, SYS7333, DD7333 and OL7333 was moved from DEV server to
PROD server. All the necessary CNC config was carried out (datasources/ODBC
etc.). Fat clients are all fine with this change. However, cannot logon to
JPY7333 via browser. Generator PC will also no longer connect to the
Webserver.

The jas logs indicate that the system cannot find any of the security files.
I've proved this by putting the system back on DEV server - both HTML and
generator PC were fine again. I can see that Web server still looks at the
DEV box for SYS7333 from the logs.

Does anyone know where I can change this? All the entries in the JAS.ini
point to the PROD box. Any input would be appr!

Rgds.,

Sanjeev
(CNC Consultant)

AS/400 v5r1, SP18.1, Update 5, Coexistent, Websphere 3.5 fix pack 5 running
on AS/400.






Consultant with clients
at B7331 - Xe
Various Deployment Servers, Citrix and JAS

 

[kuji86]

Sanjeev,

There is a document on the knowledge garden that shows you how to change the
ini file to point to the new server. Your Generator machine may not have the
new package loaded onto it as well. Find this document and your problems
will be over!



I've got an issue at a client's site with Websphere/JAS setup. Briefly,
client has 2 Enterprise Servers (DEV running DV/PY and PROD running PD).
Originally DEV was setup. The environment configured for HTML was PY7333.
The PROD server was added recently and configured for PD7333 environment. A
couple of days ago, SYS7333, DD7333 and OL7333 was moved from DEV server to
PROD server. All the necessary CNC config was carried out (datasources/ODBC
etc.). Fat clients are all fine with this change. However, cannot logon to
JPY7333 via browser. Generator PC will also no longer connect to the
Webserver.

The jas logs indicate that the system cannot find any of the security files.
I've proved this by putting the system back on DEV server - both HTML and
generator PC were fine again. I can see that Web server still looks at the
DEV box for SYS7333 from the logs.

Does anyone know where I can change this? All the entries in the JAS.ini
point to the PROD box. Any input would be appr!

Rgds.,

Sanjeev
(CNC Consultant)

AS/400 v5r1, SP18.1, Update 5, Coexistent, Websphere 3.5 fix pack 5 running
on AS/400.




Brian Turner
CNC Consultant

 

[Sanjeev_Harrish]

Re: Websphere and Two Enterprise Servers - RESOLVED

Thanks for your replies. This has been resolved.

I deleted the SYSTEM - B7333 datasources and re-created them. Originally, when the SYSTEM was moved from one Enterprise Server to the other, the data sources were 'changed'.

This seems to have resolved the issue. It's quite odd but I have seen this at one other site as well.