WebSphere Member Manager scripts fail to run due to environment settings

Technote (troubleshooting)


Problem

WebSphere® Member Manager scripts do not run properly in some situations.

Cause

Typically, this occurs because the paths or file locations are not set properly in the environment settings.

NOTE: WebSphere Member Manager was initially available as a component within WebSphere Application Server (WSAS) and the location of the scripts were assumed to be fit in the application server directory structure.


Resolving the problem

The procedure described below was tested in Microsoft® Windows® and AIX® environments. It is also expected to work for iSeries, HP-UX, Linux® and Solaris® operating environments.


In this technote, we assume <WP_root>, <WSAS_root> and <WSAS_profile_root>, respectively, are:
Windows®:

    <WP_root>=C:\WebSphere\PortalServer
    <WSAS_root>=C:\WebSphere\AppServer
    <WSAS_profile_root>=C:\WebSphere\AppServer\profiles\wp_prof

UNIX™:
    <WP_root>=/usr/WebSphere/PortalServer
    <WSAS_root>=/usr/WebSphere/AppServer
    <WSAS_profile_root>/usr/WebSphere/AppServer/profiles/wp_prof

WMM scripts
The WMM scripts referenced below reside in directory "<WP_root>/config/work/wmm/bin". The scripts most frequently used by Portal administrators are:

wmm_encrypt.bat/.sh: Used to encrypt passwords used in WMM configuration files.

attributeLoader.bat/.sh: Used to load custom attributes into WMM DB or LA (LookAside) tables.

updateWmmWASAdminRegistry.bat/.sh: Used to add (modify/delete) WebSphere Application Server console users in wmmWASAdmin.xml when WMMUR is configured.

wmmVersion.bat/.sh: Shows the version of WMM currently installed on the system.


Edit the following files as described below:

setenv.bat/.sh
Note: This is the common setup file all others below will call

1)The correct path to "setupCmdLine.bat/.sh" should be <WSAS_root>/bin in WebSphere Application Server 5.1, and <WSAS_profile_root>/bin in WebSphere Application Server version 6 and above. So the calling line should be:
for WebSphere Application Server 5.1.x,
    Windows
    call <WSAS_root>\bin\setupCmdLine.bat

    UNIX
    <WSAS_root>/bin/setupCmdLine.sh
for WebSphere Application Server 6.0 and above,
    Windows
    call <WSAS_profile_root>\bin\setupCmdLine.bat

    UNIX
    <WSAS_profile_root>/bin/setupCmdLine.sh
Note that different shells in UNIX may have a different "source" command. In Korn shell, it is a period ".". In Bash, use "source".

2) SERVER should be set to "WebSphere_Portal". Replace "@APP_SERVER_NAME@" with "WebSphere_Portal".

3) Set up WP_HOME.
    Windows
    set WP_HOME=<WP_root>
    UNIX
    WP_HOME=<WP_root>
    export WP_HOME

4) The lines for database configuration should be adjusted to the database to which your portal is configured.

wmm_encrypt.bat/.sh:
1) Call common setup script
    Windows
    call setenv.bat

    UNIX
    . ./setenv.sh

2) Since JAVA_HOME was already set, there is no need to set it again.
    Windows
    JAVA_EXE=%JAVA_HOME%\jre\bin\java

    UNIX
    JAVA_EXE=${JAVA_HOME}/jre/bin/java
    export MM_DRIVER JAVA_EXE

3) Use WP_HOME in the CLASSPATH setting. That is, use "WP_HOME" to replace "MM_DRIVER" in "JCP_CP" definition.

4) For WebSphere Application Server version 6 and above, three JAR files should be added to the classpath, utils.jar, emf.jar, and bootstrap.jar, all under directory <WSAS_root>/lib.

attributeLoader.bat/.sh:
1) attributeLoader trace can be put in the same directory
    Windows
    set TRACE_LOG=attrloader.log
    UNIX
    TRACE_LOG=attrloader.log
    export TRACE_LOG

2) "show usage" text had wrong path. It should be
    Windows
    echo Usage: attributeLoader.bat C:\WebSphere\PortalServer\wmmXXattributes.xml where XX is either DB or LA

    UNIX
    echo Usage: attributeLoader.sh /usr/WebSphere/PortalServer/wmm/wmmXXAttributes.xml where XX is either DB or LA
3) For WebSphere Application Server version 6 and above, three JAR files should be added to the classpath, utils.jar, emf.jar, and bootstrap.jar, all under directory <WSAS_root>/lib.

updateWmmWASAdminRegistry.bat/.sh:
1) Comment out "MM_DRIVER". We will use "WP_HOME".

2) In CLASSPATH, wmmclient.jar is not found in the installation, so it should be removed.

3) Correct the variable WMM_UR_FILEREGISTRY, as follows:
    Windows
    set WMM_UR_FILEREGISTRY=%WP_HOME%\wmm\wmmWASAdmin.xml
    UNIX
    WMM_UR_FILEREGISTRY=${WP_HOME}/wmm/wmmWASAdmin.xml

4) Comment out the OPTIONS variable. It is not used.

5) For WebSphere Application Server version 6 and above, three JAR files should be added to the classpath, utils.jar, emf.jar, and bootstrap.jar, all under directory <WSAS_root>/lib.

Cross reference information
Segment Product Component Platform Version Edition
Organizational Productivity- Portals & Collaboration WebSphere Portal End of Support Products AIX, HP-UX, Linux, Solaris, Windows 5.1.0.4, 5.1.0.3, 5.1.0.2, 5.1.0.1, 5.1.0 Enable, Extend

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Portal End of Support Products
WebSphere Portal

Software version:

6.0

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Software edition:

Enable, Extend, Server

Reference #:

1247076

Modified date:

2013-08-03

Translate my page

Machine Translation

Content navigation