Disabling WAS Global Security

If you want to turn off WAS Global Security, run the disable-security task. To enable WAS Global Security that has been disabled, run the enable-security-ldap or enable-security-cur tasks.

To run the disable-security task, complete the following steps:

  1. Edit the /qibm/userdata/webas5/base/<instance>/portalserver5/config/wpconfig.properties file and enter the values appropriate for the environment.
    Note the following:

    • Do not change any settings other than those specified in these steps. For instructions on working with these files, see Configuration properties reference for a complete properties reference, including default values.

    • You can also modify the wpconfig.properties file locally on the iSeries system by entering the following on an OS/400 command line: 

      EDTF '/qibm/userdata/webas5/base/<instance>/portalserver5/config/wpconfig.properties'

    • Some values, shown in italics below, might need to be modified to the specific environment.

    Section Property Value
    Portal configuration properties PortalAdminId

    Description: The user ID for the WebSphere Portal administrator.

    Recommended Value: uid=<portaladminid>,o=default organization

    Default value: <none>

    PortalAdminIdShort

    Description: The short form of the user ID for the WebSphere Portal administrator, as defined in the PortalAdminId property.

    Recommended value: <portaladminid>

    Default Value: <none>

    PortalAdminPwd

    Description: The password for the WebSphere Portal administrator, as defined in the PortalAdminId property.

    Recommended value: No recommended value for this property

    Default Value: <none>

    PortalAdminGroupId

    Description: The group ID for the group to which the WebSphere Portal administrator belongs.

    Recommended Value: cn=wpsadmins,o=default organization

    Default Value: <none>

  2. Enter the following command to run the configuration task: 

    WPSconfig.sh disable-security

    Check the output for any error messages before proceeding with any additional tasks. If any the configuration task fails, verify the values in the /qibm/userdata/webas5/base/<instance>/portalserver5/config/wpconfig.properties file.

  3. Change to the directory /qibm/proddata/webas5/pme/bin.

  4. Enter the following command: 

    startServer -instance <instance> <app_server>

    where instance is the name of the WAS instance, and app_server is the name of the application server. Note: The default name of the application server is the instance name.

 

See also