Section 3.9, “Installing the WebSphere Customization Toolbox”.
3.7 Enabling SDK 7.0 on WebSphere Application Server 8.5
Starting with WebSphere Application Server 8.5, SDK 7.0 is supported as an optional feature. The java 1.6 is still the default installation.
Caution:
JD Edwards EnterpriseOne supports WebSphere Application Server 8.5 running with SDK 7.0 only. You must switch the java level after the installation is completed.
You can switch the java level by using the managesdk command. The executable for the managesdk command is located in the bin directory of your profile. For example:
Z:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin
This section discusses how to use the managesdk command for these purposes:
View Available Java Products with Detail Information
Syntax Examples using the managesdk Command
View Available Java Products
Use this command to view the available Java products:
managesdk.bat -listAvailable
The following shows a sample of returned information.
View Available Java Products with Detail Information
Use this command to view the available Java products with detail information:
managesdk.bat -listAvailable -verbose
The following shows sample returned information.
Syntax Examples using the managesdk Command
The following examples demonstrate correct syntax when you run the managesdk command:
managesdk.bat -listAvailable [-verbose]
managesdk.bat -listEnabledProfile -profileName AppSrv01 [-verbose]
managesdk.bat -listEnabledProfileAll [-verbose]
managesdk.bat -enableProfile -profileName AppSrv01 -sdkname 1.7_64 -enableServers
managesdk.bat -enableProfileAll -sdkname 1.7_64 -enableServers
managesdk.bat -getNewProfileDefault [-verbose]
managesdk.bat -setNewProfileDefault -sdkname 1.7_64
managesdk.bat -getCommandDefault [-verbose]
managesdk.bat -setCommandDefault -sdkname 1.7_64
3.8 Switching to SDK 7.0 on WebSphere Application Server 8.5
Caution:
JD Edwards EnterpriseOne supports WebSphere Application Server 8.5 running with SDK 7.0 only. You must switch the java level after the installation is completed.
This section describes these topics:
Section 3.8.1, “Working with the managesdk Command”
Section 3.8.2, “Modify the JD Edwards EnterpriseOne Server Manager Agent with JRE 1.7.0”
3.8.1 Working with the managesdk Command
This section discusses how to use the managesdk command for these purposes:
View List of Available SDK Names
Set the command default to the version 7.0 SDK
Set the New Profile Default to the Version 7.0 SDK
If Profiles Already Exist, Enable the Profiles to use the Version 7.0 SDK
View List of Available SDK Names
Use this command to view a list of available SDK names for the product installation:
managesdk.bat -listAvailable
The following shows sample returned information.
Set the command default to the version 7.0 SDK
Use this command to set the command default to the version 7.0 SDK:
managesdk.bat -setCommandDefault -sdkname 1.7_64
The following shows sample returned information.
Set the New Profile Default to the Version 7.0 SDK
Use this command to set the new profile default to version 7.0 SDK:
managesdk.bat -setNewProfileDefault -sdkname 1.7_64
The following shows sample returned information.
If Profiles Already Exist, Enable the Profiles to use the Version 7.0 SDK
If profiles already exist, use this command to enable the profiles to use the version 7.0 SDK:
managesdk.bat -enableProfileAll -sdkname 1.7_64 -enableServers
The following shows sample returned information.
Note:
To change federated profiles in a Network Deployment installation, the deployment manager must be running. The managesdk command updates the master configuration repository. After the command runs, a synchronization operation must occur before the new SDK can be used for federated profiles.
3.8.2 Modify the JD Edwards EnterpriseOne Server Manager Agent with JRE 1.7.0
Use this procedure to modify the Server Manager Agent with JRE 1.7.0:
Stop the JD Edwards EnterpriseOne Server Manager Agent.
Copy the JRE folder from the JDK 1.7 version to this folder:
\jde_home\SCFHA\jdk
Start the JD Edwards EnterpriseOne Server Manager Agent.
3.9 Installing the WebSphere Customization Toolbox
New tool functionality with IBM WebSphere 8.5 includes the requirement to install the WebSphere Customization Toolbox. This tool aids in configuring your plug-in properly. The WebSphere Customization Toolbox comes from the supplemental software repository that was downloaded, decompressed, and added to the repository list as described in previous procedures in this document.
Start the IBM Installation Manager.
On IBM Installation Manager, click the Install option.
On Install Packages, select packages, select the two check boxes for WebSphere Customization Toolbox and his package and version Version 8.5.x.
Click the Next button.
On Install Packages, review the International Program License Agreement and click the radio button to accept the terms if you want to continue with the installation.
Click the Next button.
On Install Packages, package group, click the radio button entitled: Create a new package group.
In the Installation Directory field, enter an appropriate location to install the WebSphere Customization Toolbox 8.5.
For example:
z:\IBM\WebSphere\Toolbox
Click the Next button.
以下文章點擊率最高
Loading…