Sun ONE logo      Previous      Contents      Index      Next     

Sun ONE Portal Server 6.2 Installation Guide

Appendix C
IBM WebSphere Application Server

Sun™ ONE Portal Server 6.2 can be deployed on an WebSphere Application Server 4.0.5 Advanced Edition using it as its web application container.

Renaming an IBM WebSphere Application Server Instance

To install the Portal Server, the application server instance to which you install must already exist. You can create a new application server instance or use an existing instance; however, the instance name must not contain a space.

The default instance name for IBM WebSphere Application Server is called “Default Instance.” If this instance is not being used for other purposes, you can deploy Sun ONE Portal Server to this instance, but you must change the instance name to something that does not include a space.

To rename an IBM WebSphere Application Server instance:

Note

The admin server instance must be running.

The IBM WebSphere Application Server instance should not be running.

  1. Access the WebSphere administration console by running.

    2. /opt/WebSphere/AppServer/bin/adminclient.sh

  2. Expand the tree under Nodes to access the application server instance settings . For example:
    1. Select Nodes.
    2. Select Application Server.
    3. Select Default Server.
  3. In the Application Server field, change the instance name to one without a space, for example Default_Server.
  4. Select Apply.
  5. Regenerate the WebSphere plugin.
    1. Right click on the deploy node.
    2. In the menu, select Regen Webserver Plugin.
  6. Stop the node.
  7. Restart the node.

If you want to create a new instance for deploying the portal server, use the Create Application Server wizard in the administration console before starting the portal server install.

To create a new instance:

  1. Open the admin console. For example, to start the console installed in the default base directory of /opt, type:

    2. /opt/WebSphere/AppServer/bin/adminclient.sh

  2. Click Console, Wizards, and Create Application Server.
  3. On the Specifying Application Server Properties page, enter the following:

    4. Application Server: new_instance_name

    Node to install server on: node_name

    where node_name is the machine name on which the application server is installed.

  4. Click Next and Finish.

Setting the Cookie Encoding Values

The com.iplanet.am.cookie.encode property in the AMConfig.properties file should be set to “true” when the target web container is BEA WebLogic Server or WebSphere Application Server. This is necessary because WebLogic does not automatically encode cookie values set by web applications.

Setting com.iplanet.am.cookie.encode to “true” under WebLogic and WebSphere will prevent characters like the comma, semi-colon and white space to be set in cookie values by Sun ONE Identity Server without being escaped or encoded. When characters such as comma, semi-colon and white space are set as cookie values directly without being encoded or escaped, some web browsers will not parse the cookie value correctly. Thus, the application will receive corrupted cookie values in subsequent requests.

When the target web container is WebLogic, edit the AMConfig.properties file and set the value of the com.iplanet.am.cookie.encode property to true.



Previous      Contents      Index      Next     

Copyright 2003 Sun Microsystems, Inc. All rights reserved.