Monthly Archives: November 2008

psSharedLibrary classpath entry missing jar

Problem:

After resolving the port issue (see above), the file E:PSOFTFS900webservPSEMHUB_fsdmologsserver1SystemOut.log shows:

[11/27/08 14:50:03:718 VET] 0000000a ModuleManifes E UTLS0002E: The shared library psSharedLibrary contains a classpath entry which does not resolve to a valid jar file, the library jar file is expected to be found at E:PSOFTFS900webservPSEMHUB_fsdmoinstalledAppsPSEMHUB_fsdmoNodeCellPSEMHUB.earPSIGW.warWEB-INFlibmail.jar.
[11/27/08 14:50:03:843 VET] 0000000a ModuleManifes E UTLS0002E: The shared library psSharedLibrary contains a classpath entry which does not resolve to a valid jar file, the library jar file is expected to be found at E:PSOFTFS900webservPSEMHUB_fsdmoinstalledAppsPSEMHUB_fsdmoNodeCellPSEMHUB.earPSIGW.warWEB-INFlibactivation.jar.

Solution:

Copied:

E:PSOFTFS900webservPIA_fsdmoinstalledAppsPIA_fsdmoNodeCellfsdmo.earPSIGW.war

To:

E:PSOFTFS900webservPSEMHUB_fsdmoinstalledAppsPSEMHUB_fsdmoNodeCellPSEMHUB.ear

After this, the file shows:

************ Start Display Current Environment ************
WebSphere Platform 6.1 [ND 6.1.0.3 cf30646.29] running with process name PSEMHUB_fsdmoNodeCellPSEMHUB_fsdmoNodeserver1 and process id 3576
Host Operating System is Windows Server 2003, version 5.2 build 3790 Service Pack 1
Java version = J2RE 1.5.0 IBM J9 2.3 Windows Server 2003 x86-32 j9vmwi3223-20061001 (JIT enabled)
J9VM – 20060915_08260_lHdSMR
JIT – 20060908_1811_r8
GC – 20060906_AA, Java Compiler = j9jit23, Java VM name = IBM J9 VM
was.install.root = E:IBMWebSphereAppServer
user.install.root = E:PSOFTFS900webservPSEMHUB_fsdmo
Java Home = E:IBMWebSphereAppServerjavajre
ws.ext.dirs = E:IBMWebSphereAppServer/java/lib;E:PSOFTFS900webservPSEMHUB_fsdmo/classes;E:IBMWebSphereAppServer/classes;E:IBMWebSphereAppServer/lib;E:IBMWebSphereAppServer/installedChannels;E:IBMWebSphereAppServer/lib/ext;E:IBMWebSphereAppServer/web/help;E:IBMWebSphereAppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime
Classpath = E:PSOFTFS900webservPSEMHUB_fsdmo/properties;E:IBMWebSphereAppServer/properties;E:IBMWebSphereAppServer/lib/startup.jar;E:IBMWebSphereAppServer/lib/bootstrap.jar;E:IBMWebSphereAppServer/lib/j2ee.jar;E:IBMWebSphereAppServer/lib/lmproxy.jar;E:IBMWebSphereAppServer/lib/urlprotocols.jar;E:IBMWebSphereAppServer/deploytool/itp/batchboot.jar;E:IBMWebSphereAppServer/deploytool/itp/batch2.jar;E:IBMWebSphereAppServer/java/lib/tools.jar
Java Library path = E:IBMWebSphereAppServerjavajrebin;.;E:IBMWebSphereAppServerbin;E:IBMWebSphereAppServerjavabin;E:IBMWebSphereAppServerjavajrebin;E:PSOFTFS900binclientwinx86;C:WINDOWSsystem32;C:WINDOWS;C:WINDOWSSystem32Wbem;E:beaTuxedo9.1bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;C:PS_HOMEbinclientwinx86;C:Program FilesMicrosoft SQL Server80ToolsBinn;C:Program FilesMicrosoft SQL Server90Toolsbinn;C:Program FilesMicrosoft SQL Server90DTSBinn;C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDE;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin
************* End Display Current Environment *************

PSEM Agents Not Starting

Problem:

When the StartAgent.bat command is executed, the following appears:

E:PSOFTFS900PSEMAgent>StartAgent.bat

ERROR main EMF_CATEGORY – Error while connecting to ‘http://glwebapp:8001/PSEMHUB/hub’.
ERROR main EMF_CATEGORY – Error: Internal Exception: – Error registering peer
ERROR main EMF_CATEGORY – Error while connecting to server – retrying attempt 1
ERROR main EMF_CATEGORY – Error while connecting to ‘http://glwebapp:8001/PSEMHUB/hub’.
ERROR main EMF_CATEGORY – Error: Internal Exception: – Error registering peer
ERROR main EMF_CATEGORY – Error while connecting to server – retrying attempt 2

Troubleshooting:

In Command Prompt, stopped the PSEMHUB profile with the following commands:

set PATH=%PATH%;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin

cd /d E:PSOFTFS900webserv

PSEMHUB_fsdmobinstopServer.bat server1 -profileName PSEMHUB_fsdmo

Moved all the files in E:PSOFTFS900webservPSEMHUB_fsdmologsserver1 to backup_20081127a.

Then restarted the PSEMHUB profile:

set PATH=%PATH%;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin

cd /d E:PSOFTFS900webserv

PSEMHUB_fsdmobinstartServer.bat server1 -profileName PSEMHUB_fsdmo

The E:PSOFTFS900webservPSEMHUB_fsdmologsserver1SystemOut.log contains the following error:

************ Start Display Current Environment ************
WebSphere Platform 6.1 [ND 6.1.0.3 cf30646.29] running with process name PSEMHUB_fsdmoNodeCellPSEMHUB_fsdmoNodeserver1 and process id 260
Host Operating System is Windows Server 2003, version 5.2 build 3790 Service Pack 1
Java version = J2RE 1.5.0 IBM J9 2.3 Windows Server 2003 x86-32 j9vmwi3223-20061001 (JIT enabled)
J9VM – 20060915_08260_lHdSMR
JIT – 20060908_1811_r8
GC – 20060906_AA, Java Compiler = j9jit23, Java VM name = IBM J9 VM
was.install.root = E:IBMWebSphereAppServer
user.install.root = E:PSOFTFS900webservPSEMHUB_fsdmo
Java Home = E:IBMWebSphereAppServerjavajre
ws.ext.dirs = E:IBMWebSphereAppServer/java/lib;E:PSOFTFS900webservPSEMHUB_fsdmo/classes;E:IBMWebSphereAppServer/classes;E:IBMWebSphereAppServer/lib;E:IBMWebSphereAppServer/installedChannels;E:IBMWebSphereAppServer/lib/ext;E:IBMWebSphereAppServer/web/help;E:IBMWebSphereAppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime
Classpath = E:PSOFTFS900webservPSEMHUB_fsdmo/properties;E:IBMWebSphereAppServer/properties;E:IBMWebSphereAppServer/lib/startup.jar;E:IBMWebSphereAppServer/lib/bootstrap.jar;E:IBMWebSphereAppServer/lib/j2ee.jar;E:IBMWebSphereAppServer/lib/lmproxy.jar;E:IBMWebSphereAppServer/lib/urlprotocols.jar;E:IBMWebSphereAppServer/deploytool/itp/batchboot.jar;E:IBMWebSphereAppServer/deploytool/itp/batch2.jar;E:IBMWebSphereAppServer/java/lib/tools.jar
Java Library path = E:IBMWebSphereAppServerjavajrebin;.;E:IBMWebSphereAppServerbin;E:IBMWebSphereAppServerjavabin;E:IBMWebSphereAppServerjavajrebin;E:PSOFTFS900binclientwinx86;C:WINDOWSsystem32;C:WINDOWS;C:WINDOWSSystem32Wbem;E:beaTuxedo9.1bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;C:PS_HOMEbinclientwinx86;C:Program FilesMicrosoft SQL Server80ToolsBinn;C:Program FilesMicrosoft SQL Server90Toolsbinn;C:Program FilesMicrosoft SQL Server90DTSBinn;C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDE;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin
************* End Display Current Environment *************
[11/27/08 11:14:53:265 VET] 0000000a ModuleManifes E UTLS0002E: The shared library psSharedLibrary contains a classpath entry which does not resolve to a valid jar file, the library jar file is expected to be found at E:PSOFTFS900webservPSEMHUB_fsdmoinstalledAppsPSEMHUB_fsdmoNodeCellPSEMHUB.earPSIGW.warWEB-INFlibmail.jar.
[11/27/08 11:14:53:390 VET] 0000000a ModuleManifes E UTLS0002E: The shared library psSharedLibrary contains a classpath entry which does not resolve to a valid jar file, the library jar file is expected to be found at E:PSOFTFS900webservPSEMHUB_fsdmoinstalledAppsPSEMHUB_fsdmoNodeCellPSEMHUB.earPSIGW.warWEB-INFlibactivation.jar.
[11/27/08 11:16:00:546 VET] 0000000a TCPPort E TCPC0003E: TCP Channel TCP_4 initialization failed. The socket bind failed for host * and port 8500. The port may already be in use.
[11/27/08 11:16:00:546 VET] 0000000a WSChannelFram E CHFW0034W: The Transport Channel Service detected transport chain WCInboundDefaultSecure failed. The service will retry to start chain WCInboundDefaultSecure every 5000 milliseconds for up to 60 attempts.
[11/27/08 11:16:00:562 VET] 0000000a TCPPort E TCPC0003E: TCP Channel TCP_4 initialization failed. The socket bind failed for host * and port 8500. The port may already be in use.
[11/27/08 11:16:00:562 VET] 0000000a WSChannelFram E CHFW0034W: The Transport Channel Service detected transport chain SOAPAcceptorChain3 failed. The service will retry to start chain SOAPAcceptorChain3 every 5000 milliseconds for up to 60 attempts.

Netstat showed the following output:

E:PSOFTFS900webservPSEMHUB_fsdmo>netstat -na|more

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:86 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2809 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2810 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2811 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8000 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8001 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8002 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8500 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8502 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8880 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8881 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8882 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9043 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9044 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9045 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9060 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9061 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9062 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9100 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9101 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9102 0.0.0.0:0 LISTENING
TCP 10.18.14.30:139 0.0.0.0:0 LISTENING
Note that port 8501 is not used.

Check ports of PIA: pointed web browser to http://glwebapp:9060/ibm/console/. Logged on as admin. On the left pane, navigated to Servers > Application Servers. Click server1, and under Communications, click Ports.

Note that the WC_defaulthost_secure is 8500.

Check ports of PSEM: pointed web browser to http://glwebapp:9061/ibm/console/. Logged on as admin. On the left pane, navigated to Servers > Application Servers. Click server1, and under Communications, click Ports.

Note that the WC_defaulthost_secure is also 8500. It should be 8501(?)

Click WC_default_secure, and then change the port number from 8500 to 8501. The following message appears:

One or more virtual hosts match the previous host name and port combination of “*:8500” and do not match the new combination of “*:8501.” You might need to update the host aliases.
Changes have been made to your local configuration. You can:

• Save directly to the master configuration.
• Review changes before saving or discarding.

The server may need to be restarted for these changes to take effect.

The PSEM profile is stopped and started using the steps shown above.

After stopping PSEM web profile and restarting, the following error appears:

Recover prior changes

Your prior session timed out before the changes could be published to the master configuration. Would you like to recover the changes made in the prior session or work with the master configuration?

Work with the master configuration
Recover changes made in prior session View items with changes

Changed Items Status
cells / PSEMHUB_fsdmoNodeCell / nodes / PSEMHUB_fsdmoNode / serverindex.xml Updated

Also:

Enterprise Applications > Save
Save your workspace changes to the master configuration.

Click Save to update the master repository with your changes.
Click Discard to discard your changes and begin work again using the master repository configuration.
Click Cancel to continue working with your changes.

Total changed documents: 2

Changed Items Status
cells / PSEMHUB_fsdmoNodeCell / nodes / PSEMHUB_fsdmoNode / serverindex.xml Updated
cells / PSEMHUB_fsdmoNodeCell / applications / PSEMHUB.ear / deployments / PSEMHUB / deployment.xml

After saving the master configuration, PSEM was stopped and restarted. The file E:PSOFTFS900webservPSEMHUB_fsdmologsserver SystemOut.log showed:

************ Start Display Current Environment ************
WebSphere Platform 6.1 [ND 6.1.0.3 cf30646.29] running with process name PSEMHUB_fsdmoNodeCellPSEMHUB_fsdmoNodeserver1 and process id 2580
Host Operating System is Windows Server 2003, version 5.2 build 3790 Service Pack 1
Java version = J2RE 1.5.0 IBM J9 2.3 Windows Server 2003 x86-32 j9vmwi3223-20061001 (JIT enabled)
J9VM – 20060915_08260_lHdSMR
JIT – 20060908_1811_r8
GC – 20060906_AA, Java Compiler = j9jit23, Java VM name = IBM J9 VM
was.install.root = E:IBMWebSphereAppServer
user.install.root = E:PSOFTFS900webservPSEMHUB_fsdmo
Java Home = E:IBMWebSphereAppServerjavajre
ws.ext.dirs = E:IBMWebSphereAppServer/java/lib;E:PSOFTFS900webservPSEMHUB_fsdmo/classes;E:IBMWebSphereAppServer/classes;E:IBMWebSphereAppServer/lib;E:IBMWebSphereAppServer/installedChannels;E:IBMWebSphereAppServer/lib/ext;E:IBMWebSphereAppServer/web/help;E:IBMWebSphereAppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime
Classpath = E:PSOFTFS900webservPSEMHUB_fsdmo/properties;E:IBMWebSphereAppServer/properties;E:IBMWebSphereAppServer/lib/startup.jar;E:IBMWebSphereAppServer/lib/bootstrap.jar;E:IBMWebSphereAppServer/lib/j2ee.jar;E:IBMWebSphereAppServer/lib/lmproxy.jar;E:IBMWebSphereAppServer/lib/urlprotocols.jar;E:IBMWebSphereAppServer/deploytool/itp/batchboot.jar;E:IBMWebSphereAppServer/deploytool/itp/batch2.jar;E:IBMWebSphereAppServer/java/lib/tools.jar
Java Library path = E:IBMWebSphereAppServerjavajrebin;.;E:IBMWebSphereAppServerbin;E:IBMWebSphereAppServerjavabin;E:IBMWebSphereAppServerjavajrebin;E:PSOFTFS900binclientwinx86;C:WINDOWSsystem32;C:WINDOWS;C:WINDOWSSystem32Wbem;E:beaTuxedo9.1bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;C:PS_HOMEbinclientwinx86;C:Program FilesMicrosoft SQL Server80ToolsBinn;C:Program FilesMicrosoft SQL Server90Toolsbinn;C:Program FilesMicrosoft SQL Server90DTSBinn;C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDE;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin
************* End Display Current Environment *************
[11/27/08 14:39:35:968 VET] 0000000a ModuleManifes E UTLS0002E: The shared library psSharedLibrary contains a classpath entry which does not resolve to a valid jar file, the library jar file is expected to be found at E:PSOFTFS900webservPSEMHUB_fsdmoinstalledAppsPSEMHUB_fsdmoNodeCellPSEMHUB.earPSIGW.warWEB-INFlibmail.jar.
[11/27/08 14:39:36:093 VET] 0000000a ModuleManifes E UTLS0002E: The shared library psSharedLibrary contains a classpath entry which does not resolve to a valid jar file, the library jar file is expected to be found at E:PSOFTFS900webservPSEMHUB_fsdmoinstalledAppsPSEMHUB_fsdmoNodeCellPSEMHUB.earPSIGW.warWEB-INFlibactivation.jar.

Note that there is no reference to the port number.

The file E:PSOFTFS900webservPSEMHUB_fsdmologsserverstartServer.log showed:

************ Start Display Current Environment ************
Host Operating System is Windows Server 2003, version 5.2 build 3790 Service Pack 1
Java version = J2RE 1.5.0 IBM J9 2.3 Windows Server 2003 x86-32 j9vmwi3223-20061001 (JIT enabled)
J9VM – 20060915_08260_lHdSMR
JIT – 20060908_1811_r8
GC – 20060906_AA, Java Compiler = j9jit23, Java VM name = IBM J9 VM
was.install.root = E:IBMWebSphereAppServer
user.install.root = E:PSOFTFS900webservPSEMHUB_fsdmo
Java Home = E:IBMWebSphereAppServerjavajre
ws.ext.dirs = E:\IBM\WebSphere\AppServer\java\lib;E:\IBM\WebSphere\AppServer\classes;E:\IBM\WebSphere\AppServer\lib;E:\IBM\WebSphere\AppServer\installedChannels;E:\IBM\WebSphere\AppServer\lib\ext;E:\IBM\WebSphere\AppServer\web\help;E:\IBM\WebSphere\AppServer\deploytool\itp\plugins\com.ibm.etools.ejbdeploy\runtime
Classpath = E:PSOFTFS900webservPSEMHUB_fsdmoproperties;E:IBMWebSphereAppServerproperties;E:IBMWebSphereAppServerlibstartup.jar;E:IBMWebSphereAppServerlibbootstrap.jar;E:IBMWebSphereAppServer/lib/j2ee.jar;E:IBMWebSphereAppServer/lib/lmproxy.jar;E:IBMWebSphereAppServer/lib/urlprotocols.jar;E:IBMWebSphereAppServerjavalibtools.jar
Java Library path = E:IBMWebSphereAppServerjavajrebin;.;E:IBMWebSphereAppServerbin;E:IBMWebSphereAppServerjavabin;E:IBMWebSphereAppServerjavajrebin;E:PSOFTFS900binclientwinx86;C:WINDOWSsystem32;C:WINDOWS;C:WINDOWSSystem32Wbem;E:beaTuxedo9.1bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;C:PS_HOMEbinclientwinx86;C:Program FilesMicrosoft SQL Server80ToolsBinn;C:Program FilesMicrosoft SQL Server90Toolsbinn;C:Program FilesMicrosoft SQL Server90DTSBinn;C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDE;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin
Current trace specification = *=info:com.ibm.*=all
************* End Display Current Environment *************

[11/27/08 14:39:29:515 VET] 0000000a ManagerAdmin I TRAS0017I: The startup trace state is *=info:com.ibm.*=all.
[11/27/08 14:39:29:515 VET] 0000000a WsServerContr 1 Executing executeUtilityOnWindows with args: E:PSOFTFS900webservPSEMHUB_fsdmoconfig PSEMHUB_fsdmoNodeCell PSEMHUB_fsdmoNode server1
[11/27/08 14:39:29:515 VET] 0000000a WsServerContr 1 Getting WindowsService obj with: server1 and E:PSOFTFS900webservPSEMHUB_fsdmoconfig PSEMHUB_fsdmoNodeCell PSEMHUB_fsdmoNode server1
[11/27/08 14:39:29:515 VET] 0000000a WindowsServic > getWindowsServiceNameForServer() Entry
[11/27/08 14:39:29:515 VET] 0000000a WindowsServic 1 In executeCommand, args are: E:IBMWebSphereAppServerbinWASService.exe -getServiceName server1 -profilePath E:PSOFTFS900webservPSEMHUB_fsdmo
[11/27/08 14:39:29:531 VET] 0000000a WindowsServic 1 Runtime.exec() returned process java.lang.ProcessImpl@456a456a
[11/27/08 14:39:29:531 VET] 0000000a WindowsServic 1 retCode from childProcess.waitFor() is 0
[11/27/08 14:39:29:531 VET] 0000000a WindowsServic 3 exitCode = 0
[11/27/08 14:39:30:531 VET] 0000000a WindowsServic 1 Trying to new up WindowsService using serverName=server1, winServiceName=null
[11/27/08 14:39:30:531 VET] 0000000a ManagerAdmin I TRAS0018I: The trace state has changed. The new trace state is *=info.
[11/27/08 14:39:30:562 VET] 0000000a AdminTool A ADMU0128I: Starting tool with the PSEMHUB_fsdmo profile
[11/27/08 14:39:30:562 VET] 0000000a AdminTool A ADMU3100I: Reading configuration for server: server1
[11/27/08 14:39:32:828 VET] 0000000a AdminTool A ADMU3200I: Server launched. Waiting for initialization status.
[11/27/08 14:40:41:796 VET] 0000000a AdminTool A ADMU3000I: Server server1 open for e-business; process id is 2580

Solution:

Ensure that the web server is started

References:

http://www-128.ibm.com/developerworks/forums/thread.jspa?threadID=169775&start=15&tstart=0

Integrating UPK With Oracle E-Business Suite Help Menu

This documentation shows how integrate UPK content into the Help menu of Oracle E-Business Suite. Examples are drawn from the VIS4 instance; your instance may vary.

Step 1:        After creating the content in UPK Developer, publish the content to a UPK Player package. From the Tools menu, click Publish Content.

Step 2:        Choose Publish All Modules and click OK.

Step 3:        Check Deployment – Player Package and click Next.

Step 4:        Click Next.

Step 5:        Click Publish.

The modules are published.

Step 6:        In this example, the module is exported to the C:Program FilesUser Productivity KitUPK Developer 27PublishPlayer for Add New Responsibility to Existing User directory.

Rename the output directory to remove spaces.

Step 7:        The published directory (upktest in this example) must be copied onto the server. It must be copied to the $COMMON_TOP/portal/<context name> directory.

For VIS4, the upktest directory and its contents must be copied to:

/u3/oracle/vis4comn/portal/VIS4_appslinux

Step 8:        Copy the odcontenturl.js file in the hemi directory to odcustomurl.js. Modify the ORACLEHELP_URL to point to the old Oracle E-Business Suite help file (use the format “http://<oracle server>:<port> /OA_HTML/jsp/fnd/fndhelp.jsp”):

ORACLEHELP_URL=”http://appslinux.support.com:8004/OA_HTML /jsp/fnd/fndhelp.jsp?dbc=vis4″

The odcontenturl.js is located in /u3/oracle/vis4comn/portal/VIS4_appslinux /upktest/ORACLE/hemi/ directory.

Step 9:        Log on to the VIS4 instance and select the System Administrator responsibility. Navigate to Profile > System. The Find System Profile Values form appears. In the Profile field, enter %Help% and then click Find.

Step 10:   Locate the Applications Help Web Agent profile option.

Enter the following URL in the Site field:

http://appslinux.support.com:8004/upktest/ORACLE/hemi/odhelp.html?dbc=/u3/oracle/vis4appl/fnd/11.5.0/secure/VIS4_appslinux/vis4.dbc

Then click Save.

Step 11:    Finally, log off Oracle Applications and then log back on. When Help is selected, a new link (UPK) appears. When it is clicked, the custom Player content appears.

References:

Content Administration PDF (located in C:Program FilesUser Productivity KitUPK Developer 27docsReference).

    

DDDAUDIT Errors After Running Change Assistant

DDDAUDIT Errors after Partially Running Change Assistant (FSCM MP5)

Problem:

After partially running Change Assistant (FSCM MP5), many errors are appearing on the DDDAUDIT.sql report (e.g. objects are now missing from the database):

PeopleSoft
Report Name :DDDAUDIT APPLICATION DESIGNER/DATABASE AUDIT REPORT Page No : 1
Database Name: Run Date: 11/25/2008
Platform :WINDOWS-NT DBType: Microsoft SQL Server Run Time: 15:57:39
(TABLE-1) SQL Table Names defined in the
Application Designer that are not blank and
not the same as the Record Name: No rows found.

(TABLE-2) SQL Table defined in the
Application Designer and not found in the
Database:
Record Name Ownerid
————— ——-
AE_DETIJ_AET TTS
AE_DETIS_AET TTS
AE_DETW_AET TTS
AE_PEPXPLOD_AET TTS
AM_EXT_AUD_DTL FAM
AM_EXT_AUD_HDR FAM
AM_JE_DTL_TMP FAM
APS8003_RPT FAP
AP_APS8003_AET FAP
AP_DAM_LTD_T FAP
AP_IU_LN2_AET FGL
AP_IU_LN_AET FGL
AP_MTVLN5A_T FAP
BP_ACT2_TAO FGL
BP_ACTFS_TAO FGL
BP_ACT_TAO FGL
BP_APA_S_TAO FAP
BP_APN_S_TAO FAP
BP_APV_S_TAO FAP
BP_AREV_G_TAO FGL
BP_ARM_S_TAO FAR
BP_ARR_S_TAO FAR
BP_ASEXLG_TAO FGL
BP_BDHDR_TAO FGL
BP_BDLN_TAO FGL
BP_BI_S_TAO DBI
BP_BKOUT_TAO FGL
BP_BP_TAO FGL
BP_CF_TAO FGL
BP_CM_S_TAO DCM
BP_EE_TAO FFA
BP_EXCPTN_TAO FGL
BP_EX_S_TAO FEX
BP_FSRC_TAO FGL
BP_GEN_S_TAO FGL
BP_GLB_S_TAO FGL
BP_GL_S_TAO FGL
BP_GM_S_TAO FGM
BP_HR_S_TAO FGL
BP_KKAMT_TAO
BP_LEDGER_TAO FGL
BP_LGRP_TAO FGL
BP_LQDFS_TAO FGL
BP_LQD_TAO FGL
BP_PC1_S_TAO FPC
BP_PC_S_TAO FPC
BP_PFS1_TAO FGL
BP_PFS2_TAO FGL
BP_POA_S_TAO DPO
BP_POC_S_TAO DPO
BP_PO_S_TAO DPO
BP_PRNT_TAO FGL

PeopleSoft
Report Name :DDDAUDIT APPLICATION DESIGNER/DATABASE AUDIT REPORT Page No : 2
Database Name: Run Date: 11/25/2008
Platform :WINDOWS-NT DBType: Microsoft SQL Server Run Time: 15:57:39
(TABLE-2) SQL Table defined in the
Application Designer and not found in the
Database: (continued)
Record Name Ownerid
————— ——-
BP_PST1_TAO FGL
BP_PST2_TAO FGL
BP_REFDBK_TAO FGL
BP_REFD_TAO FGL
BP_RFLDS_TAO FGL
BP_RQN_S_TAO DPO
BP_RQ_S_TAO DPO
BP_TA_S_TAO FEX
BP_XCF2_TAO FGL
BP_XCF_TAO FGL
BP_XLBP_TAO FGL
BS_BLD_PROJ ENV
BS_MRG_PRJ_AET ENV
BS_PRJ_MRG_RN ENV
CA_CH_APS_TA1 FCA
CE_LOP_PROC_T DCM
DEPR_RP43_TMP FAM
DEPR_RP50_TMP FAM
DEPR_RP51_TMP FAM
DIST_LN3_TAO FAM
DIST_LN4_TAO FAM
DP_CALCLIB_RC DDP
DP_DDH_BI_TAO DDP
DP_DDH_CK_TAO DDP
DP_DDH_CP_TAO DDP
DP_DDH_IN_TAO DDP
DP_DDH_KN_TAO DDP
DP_DDH_OM_TAO DDP
DP_DDH_SO_TAO DDP
DP_FCADJHSTAO DDP
DP_FCITEMSDRV DDP
DP_FCITEMSTAO DDP
DP_FCITMDRV_AET DDP
DP_FCITMD_TAO DDP
DP_FCPRDS_TAO DDP
DP_FCWRKQMTAO DDP
EXPLODE_IDS TTS
EXPLODE_IDS_NUM TTS
EXP_CHUNK_TMP TTS
EXP_CTRL TTS
EXP_FIELD_SEQ TTS
EXP_PROJ TTS
EXP_RECDEFN TTS
EXP_RECFIELD TTS
EXP_REQUEST TTS
EXP_REQUEST_OPT TTS
EXP_SEQ TTS
EXP_STMT TTS
EXP_STMT_CHUNK TTS
EXP_TBL TTS
EX_ADVLN_TAO FEX
EX_ADVLSS_TAO FEX
EX_ADV_HDR_TMP FEX
EX_ADV_HDR_TMP2 FEX
EX_BCHK_ERTAO
EX_PYNTFY_TAO FEX
EX_PYNTFY_TBL FEX

PeopleSoft
Report Name :DDDAUDIT APPLICATION DESIGNER/DATABASE AUDIT REPORT Page No : 3
Database Name: Run Date: 11/25/2008
Platform :WINDOWS-NT DBType: Microsoft SQL Server Run Time: 15:57:39
(TABLE-2) SQL Table defined in the
Application Designer and not found in the
Database: (continued)
Record Name Ownerid
————— ——-
EX_STGSHT_TMP FEX
FS_CE_CFS_TAO FGL
FS_CE_CFV_TAO FGL
GBR_RUN_CTL_CIS FAP
GL_ACCT_ENTRY AGC
IN_ALMDMND_AET DIN
IN_DEMAND1_T DPO
IN_RLS_OPCK_TAO DIN
IN_UNDOSDPTAO DIN
IN_UNDOSETTAO DIN
JRNL_IUW2_AET FGL
JRNL_IUWK_AET FGL
KK_DUP_SHDR FGL
KK_SHDR_TAO FGL
OCH_ITLD_TAO DOM
OCH_LOCK_TAO DOM
OMA_LOCK_TAO DOM
OMB_ITLD_TAO DOM
OMB_LOCK_TAO DOM
OMCB_LOCK_TAO DOM
OMD_LOCK_TAO DOM
OMEC_OUTLS_INF DOM
OME_ITLD_TAO DOM
OME_LOCK_TAO DOM
OMH_LOCK_TAO DOM
ORD_HEADER_LOCK DOM
PC_BUD_SM_TMP FPC
PC_OLT_TAO FPC
PG_PNVAT3_TAO FAR
POP_PROJ TTS
POP_SEQ TTS
POP_TBL TTS
PST_APPCT_TMP FAP
PST_WVCH_TMP FAP
RECV_ASN_DIST2 DPO
REC_COUNT TTS
REC_COUNT_WRK2 TTS
REQ_CHG_HDR_T DPO
REQ_CHG_LN_T DPO
REQ_CHG_ORD_TMP DPO
REQ_CHG_SHP_T DPO
REQ_CNCL_CO_TMP DPO
RUN_TDS_ANNEXUR FLC
RUN_TDS_QRETURN FLC
RVL_AR_TAO FAR
SF1219_DTL_TBL FGL
SF1219_SUM_TBL FGL
SF1219_TMP_TBL FGL
SUMLED_REQ_BU FGL
TDS_QRETURN_DTL FLC
TDS_QRETURN_TAO FLC
TDS_QRETURN_TBL FLC
TDS_QRET_NMHDR FLC
TDS_QRET_NUM FLC
TDS_REP_TBL FLC
TT_WRK2 TTS
UPD_QTY_TMP

Solution:

Run Application Designer.

In a new project, click Insert > Definitions Into Project

Search for and insert all Records and Indexes

Click Build > Project

Click Settings. Ensure the following are set:
• Skip table if it already exists
• Recreate view if it already exists
• Recreate index only if modified

Check Create Tables and Create Views

Cloning of Production Instance

#

Step

Estimated duration

1. Prepare the test machine (echo) that shall be used as the new production machine for cloning:Remove any existing E-Business Suite instance on the machine. Ideally, reinstall the operating system, apply any required service packs, install the additional software such as JDK, Visual C++, MKS Toolkit etc. The software should be installed to the same directory paths as those on the production instance.If the test machine will not reinstalled, then remove the Oracle-related keys from the registry.

1 day

2. Carry out the pre-clone steps for the production instance (adpreclone.pl).

½ day

3. Shutdown the production E-Business Suite instance (application and database tier services) and copy the files from the production machine (delta) to the test machine (echo).

1 day

4. Disconnect the production server from the network. Change the name and IP address of the test machine (echo) to that of the production machine (delta). Update the ‘hosts’ file on the new production server, so that it now contains the new IP address and hostname.

1 hour

5. Clone the new production server. Run the clone scripts on the new production server (adcfgclone.pl).

½ day

6. Perform stress-testing of the new server to ensure that it responds suitably to the load.

1 day

7. Backup and test recovery of the instance on another server.

1 day

Please note:

1. Ensure that the Database processes are properly shut down before proceeding to copy the files; if files aren’t copied correctly, the cloning process would not be executed correctly.

2. Do not run the Gather Schema Statistics concurrent job on the new PROD instance.