Windows: Upgrade the SDK

Start with IBM WebSphere Portal Combined Cumulative Fix 05, we can change the SDK Java Technology Edition from version 7.0 to version 7.1.

Ensure that IBM WebSphere Application Server and WebSphere Portal are installed with SDK version 7.0.

Prerequisites

Windows: Prepare the operating system

Windows: Prepare the Installation Manager

Windows: Run the installation program

Windows: Next steps

1. Start the IBM Installation Manager.

2. Install IBM WebSphere SDK Java Technology Edition version 7.1.

3. Read the following information before running the managesdk task:

   • For stand-alone environments: Stop the profile server (node) before running the managesdk command.

   • For clustered environments:

     • If the profile is a federated node of a deployment manager, ensure that the deployment manager is running before running the managesdk command to update the profile.

     • Stop all the nodes.

     • Ensure that the node agent for each node is started.

     • When we enable the SDK for a node, run the managesdk command from the /bin directory to which the node belongs. We can also run the command from the /bin directory of the profile containing the node to update.

     • A connection to the deployment manager must exist with a supported connector protocol in the following order of preference:

       • SOAP

       • Inter-Process Communications (IPC)

       • Remote Method Invocation (RMI)

       If the SOAP protocol is enabled, the managesdk command uses the SOAP protocol. If the SOAP protocol is not enabled but the IPC protocol is enabled, the command uses the IPC protocol. If the SOAP and IPC protocol are not enabled, then the command uses the RMI protocol.

     • We must provide the administrative user name and password with the managesdk command for each profile containing a federated node or deployment manager node in a cell with security enabled. If we do not specify the -user and -password parameters, the managesdk command might fail or stop processing.

     • When we enable the SDK for a deployment manager, only the deployment manager server is enabled. None of the managed nodes of the deployment manager are enabled to use the specific SDK.

4. Open a command prompt and change to the APPSERVER_ROOT/bin directory.

5. Enable all existing profiles to use the new SDK version:

   Go to managesdk command for information about the managesdk commands.

   • Windows: managesdk.bat -enableProfileAll -sdkname 1.7.1_64 -enableServers

6. Run the following commands to make the new SDK version the new default:

   • Windows: managesdk.bat -setCommandDefault -sdkname 1.7.1_64

     managesdk.bat -setNewProfileDefault -sdkname 1.7.1_64

7. Repeat these steps on each node in the environment.

Parent topic: Windows: Install WebSphere Portal and Web Content Manager

Previous topic: Windows: Next steps