Applying 64-bit Component to the Deployment Server

Configure Server Password

On the Server Manager Management Console, select the Server Manager Users in the CONFIGURE section of the tab on the left.
In the Server Manager User Authentication section, verify that the Primary Security Server is the Enterprise Server that is being used as the Security Server. Also, verify that the Outgoing JDENET Port value is the same as the value in the jde.ini file.
Click the Save button.
Click the Management Dashboard link.
From the Select Instance drop-down menu, select the Home Management Console option.
In the Configuration section of the tab on the left, click JDBJ Database Configuration.
Enter the required values in the JDBJ Bootstrap Datasource field in this window.
Note: Click the information icon next to the text box for more information about the jde.ini section that contains this information. Do not use the jde.ini file of the Deployment Server. Navigate to the OneWorld Client Instal\misc path, and then use the jde.ini file located in this path for the information. Do not enter any values in the JDBJ Connection Pools section. The values in the JDBC Drivers section are auto-populated.
In the Oracle Database Settings section, make sure that the path in the Location field points to the location of the console. For example:
```
 /slot/ems6282/oracle/Middleware/jde_home_
          1/SCFMC/targets/home/config/tnsnames.ora
```
In the File Content field for the Oracle Database, add the content in the TNSNAMES.ora file of your Database. You can leave the field blank when connecting to a Microsoft SQL server or an AS400 Database.
Example 1: Navigate to the path: C:\Oracle\E1Local\NETWORK\ADMIN. Copy the section for the database that you are using for EnterpriseOne. Paste the content in the File Content field.
Example 2: Copy and paste the following section for the database that you are using for EnterpriseOne:
ems6282 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = den60212jems)(PORT = 1603)) ) (CONNECT_DATA = (SID = ems6282) (SERVER = DEDICATED) ) )
ORACLR_CONNECTION_DATA = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521)) ) (CONNECT_DATA = (SID = CLRExtProc) (PRESENTATION = RO) ) )
Click the Save button.
Log-off and back in to Server Manager.

Changing the Component for the Deployment Server

Click Manage Dashboard.
Click the Deployment Server managed instance
Click the Change button under Software Component Version.
Select the … 9.2.3.0 x64 … component.
Select Component Download for Multi-foundation Only.
Click the Change Component button.
The system will prompt for a database username and password. Enter the appropriate credentials.

Server Manager will inform you that it has detected a 64-bit component and that it will automatically be installed as a multi-foundation directory.
Click the OK button.
Note:
Server Manager might, depending on the session state, prompt again for the database user and password.
Enter the 64-bit JRE location and click OK.
Note:
Nothing is visibly different in Server Manager with the component change. The tools release reported is still 9.2.3 x86.

Viewing the New Foundation Directory

On the Deployment Server navigate to: ..\JDE\DEP\JDEdwards\E920 directory

A new foundation directory has been created called foundation_9.2.3.0_X64 and will be used for all 64-bit builds. The directory contains all artifacts required for a foundation.
Close the Windows Explorer window.
Sign-in to the Server Manager console, and access the Deployment Server.

Viewing the New Foundation Details

Launch JD Edwards EnterpriseOne on the Deployment Server.
Enter GH9083 in the Fast Path and press Enter.
Under Package and Deployment Tools, click Package Assembly.
Click Foundation Items from the Form menu.
Click Find on Work With Foundation Items.
Select the foundation record for …x64.

You see the details of the new foundation that was created for the 64-bit foundation on the Deployment Server.