Title: NT Application Server with AS/400 Enterprise Server Setup in Xe
Abstract: Information describing how to add an NT Application Server (sometimes called a Logic Server) to an existing AS/400 Enterprise Server configuration in OneWorld Xe.
Assumptions about Adding a NT Application Server to an Existing Installation Plan
This setup applies only when adding an NT Application Server to an existing AS/400 Enterprise Server configuration in OneWorld Xe. The Application Server has host code and pathcodes only and is used to process UBE's. The AS/400 has the DB2 database used by the Application Server. **
Enterprise Server - Copy the SVM7333 Library
Logon to the AS/400 Enterprise Server as QSECOFR. Copy the SVM7333 library and rename it as APPLIB. The APPLIB library will be the server map for your Application Server.
Deployment Server- Add-on Servers Plan
** Please reference the AS/400 Installation Guide for Xe (Chapter 12) "Adding a Server to an Existing Configuration." **
Make sure you are an administrator to the machine, logon to OneWorld in the planner environment (JDEPLAN) as user JDE. From the 'System Installation Tools Menu' (GH961), double-click 'Add-on Servers Plan' (P98240). On 'Work with Installations Plans,' click 'Add.' A 'OneWorld Information Prompt Warning' window will appear, click 'OK'.
Entering a Plan Description
After starting 'Installation Planner', enter your basic plan information (name of your plan and description). The 'Status' field should be set to 10 (In Planning) and the 'Release' field set to B7333.
Entering A Plan Location
On 'Location Search' select an existing plan location - the location defined during you base installation. Click 'Ok' on the 'Location Revisions' form.
Selecting Additional Server Types
Uncheck the Deployment Server, Data Server, WTS Server and Jas Server boxes, leave the Enterprise Server box checked - this will add your Application Server to your configuration.
Entering Enterprise (Application) Server Information
On the 'Enterprise Server Revisions' form verify the 'Machine Usage' defaulted to 20 (Enterprise Server) and that the 'Location' defaulted to the location that you selected on the 'Location Revisions' form. Then enter in the following information:
Machine Name - NTAPPSVR (The name of your Application Server - the name is case-sensitive and cannot exceed 10 characters)
Description - Enter in a long description of the machine
Release - B7333
Host Type - Click the visual assist button and choose 50 for Intel NT
Port Number - The port number defaults into the field from the JDE.INI file, you will want to use the same port number that your Enterprise Server is using
Logical Machine Name -NTAPPSVR (The name of your Application Server defaults into this field when you enter the host type)
Database Type - Click the visual assist button and choose 'I' for Client Access
Server Map - Defaults to 'NTAPPSVR - B7333 Server Map' (where NTAPPSVR is the name of your Application Server)
Installation Path - The installation directory path to which OneWorld will install on your Application Server.
\jdedwardsoneworld\ddp\b7333
Only the Use Julian Dates, Use Decimal Shift, Support For Updates, and OCM Data Source boxes should be checked.
Entering Enterprise (Application) Server Datasource Information
Choose to enter 'Custom' datasource information (do not take the defaults) for the Application Server you just added. On the 'Data Source Setup' form, for your server map datasource, verify the following fields (remember this is case-sensitive):
Data Source Name -NTAPPSVR - B7333 Server Map (where NTAPPSVR is the name of your Application Server)
Server Name -NTAPPSVR (The name of your Application Server)
Data Source Type - Click the visual assist button and choose 'I' for Client Access
AS/400 Database Name -ENTSVR (The name of your AS/400 Enterprise Server)
Data Library Name - APPLIB (This is your server map library on the AS/400 for your Application Server)
Then select 'Advanced' from the form exit bar and continue verifying the following settings for your server map datasource:
Data Source Use - DB
Data Source Name - NTAPPSVR - B7333 Server Map (where NTAPPSVR is the name of your Application Server)
Data Source Type - I (for Client Access)
Object Owner ID - leaveblank
Library Name - APPLIB
DLL Name - JDBODBC.DLL
Database Name - 'NTAPPSVR - B7333 Server Map' (where NTAPPSVR is the name of your Application Server)
Server Name - NTAPPSVR (The name of your Application Server)
Platform - NTSVR
Only the Use Julian Dates, Use Decimal Shift, Support For Updates, and OCM Data Source boxes should be checked.
Continue entering the rest of your datasources (reference the Xe Installation Reference Guide). After completing your Application serve datasource information you can conclude the Enterprise (Application) Server setup.
Finalizing the Installation Plan
'Installation Planner' automatically finalizes your installation plan and sets your plan status to 20. This signals that several adjustments to OCM mappings and tables are made according to your plan. The following tables are updated when your plan is finalized (F00945, F00942, F98404, F9651, and F984031). Review the 'Validation Planner Report' to confirm that all records were validated. If you encountered any errors, correct them before proceeding.
Enterprise Server - Verify DLL's for APPLIB/F98611
Logon to the AS/400 Enterprise Server as QSECOFR. At the AS/400 command prompt type STRSQL. Enter the following SQL statement:SELECT * FROM APPLIB/F98611. The OMDLLNAME needs to be set to JDBODBC.DLL for your Application Server datasources if not, you will need to fix this to reflect the correct DLL name. The following is an example SQL statement that may be used to change the OMDLLNAME to JDBODBC.DLL:UPDATE APPLIB/F98611 SET "OMDLLNAME" = 'JDBODBC.DLL' WHERE "OMSRVR" = 'ENTSVR' (where ENTSVR is the name of your AS/400 Enterprise Server).
Deployment Server - Verify/Setup Sever Map and Logic Datasource
You will need to verify/setup the ODBC Datasource Administrator and the ODBC datasources within OneWorld (both the Database Data Sources & Logical Data Sources).. Make sure you are an administrator to the machine, logon to OneWorld in the planner environment (JDEPLAN) as user JDE.
ODBC Data Source Administrator
In the 'Windows Control Panel', double-click on 'ODBC Data Sources' and verify the following tabs for each datasource:
NTAPPSVR - B7333 Server Map
General - Data source name: NTAPPSVR - B7333 Server Map, AS/400 System: ENTSVR
Server - Default libraries: APPLIB
Package(s) - Default package library: APPLIB
Translation - Translation: Do Not Translate CCSID 65535
Format - Naming convention: System naming convention (*SYS)
NTAPPSVR
General - Data source name: NTAPPSVR, AS/400 System: ENTSVR
Server - Default libraries: APPLIB
Package(s) - Default package library: APPLIB
Translation - Translation: Translate CCSID 65535
Format - Naming convention: System naming convention (*SYS)
Database Data Sources
From the 'System Administration Tools' menu (GH9011), double-click on the 'Database Data Sources' application. You should see a 'NTAPPSVR - B7333 Server Map' datasource listed (where NTAPPSVR is the name of your Application Server). If you do not have this datasources you will need to add it, otherwise re-verify the following settings:
NTAPPSVR - B7333 Server Map
Data Source Use - DB
Data Source Name -NTAPPSVR - B7333 Server Map (where NTAPPSVR is the name of your Application Server)
Data Source Type - I (for Client Access)
Object Owner ID - leaveblank
Library Name - APPLIB
DLL Name - JDBODBC.DLL
Database Name - NTAPPSVR - B7333 Server Map (where NTAPPSVR is the name of your Application Server)
Server Name - NTAPPSVR(The name of your Application Server)
Platform - NTSVR
Only the Use Julian Dates, Use Decimal Shift, Support For Updates, and OCM Data Source boxes should be checked.
Logical Data Sources
From the 'System Administration Tools' menu (GH9011), double-click on the 'Logical Data Sources' application. Choose the 'System - B7333' datasource. You should have an 'NTAPPSVR' and 'NTAPPSVR - Logic' datasource (where NTAPPSVR is the name of your Application Server). If you are missing any of these datasources you will need to add them, otherwise re-verify the following settings:
NTAPPSVR
Data Source Use - SVR
Data Source Name - NTAPPSVR (where NTAPPSVR is the name of your Application Server)
Data Source Type - Set to 'I' for Client Access
Object Owner ID - leaveblank
Library Name - APPLIB
Library List Name -ENTSVR (The name of your AS/400 Enterprise Server)
DLL Name - JDBODBC.DLL
Database Name - 'NTAPPSVR - B7333 Server Map' (where NTAPPSVR is the name of your Application Server)
Server Name - NTAPPSVR (where NTAPPSVR is the name of your Application Server)
Platform - NTSVR
Only the Use Julian Dates, Use Decimal Shift, and Support For Updates boxes should be checked.
NTAPPSVR - Logic
Data Source Use - SVR
Data Source Name - NTAPPSVR - Logic (where NTAPPSVR is the name of your Application Server)
Data Source Type - I (for Client Access)
Object Owner ID - leaveblank
Library Name - APPLIB
Library List Name -ENTSVR (The name of your AS/400 Enterprise Server)
DLL Name - JDBODBC.DLL
Database Name - 'NTAPPSVR - B7333 Server Map' (where NTAPPSVR is the name of your Application Server)
Server Name - NTAPPSVR (where NTAPPSVR is the name of your Application Server)
Platform - NTSVR
Only the Use Julian Dates, Use Decimal Shift, and Support For Updates boxes should be checked
Deployment Server - Installation Workbench
Make sure you are an administrator to the machine, logon to OneWorld in the planner environment (JDEPLAN) as user JDE. From the 'System Installation Tools Menu' (GH961), double-click 'Installation Workbench' (P9841). Select your application server plan and run the Installation Workbench. When the workbench completes click 'Ok' and close the application.
** Coexistence Warning:When running the Installation Workbench it will sets up default OCM mappings for the F0002, F0021, F0004, F0004D, F0005, F0005D tables which point to the appropriate Control Table library for that environment. With a coexistent setup you will need to change the mappings of these tables to point to the appropriate AS/400 Common Datasource for that environment. **
Application Server -Configuring the Application Server
** Please reference the NT Installation Guide for Xe (Chapter 8) "Installing the Enterprise Server." **
Logon to your Application Server as an Administrator to the machine.
- Create the OneWorld administrator user. From the 'Administrative Tools' program group, run 'User Manager' to create a new user JDE with a password JDE - must be in ALL CAPS.
- Setup and verify the host file. From the Windows NT explorer, access \Winnt\System32\Drivers\Etc\Hosts. For each Enterprise Server and Deployment Server on your network, complete the machine IP address and the machine name.
- Verify that Client Access Express is installed on your Application Server, if not, you will need to install it. Verify that it is at the same release and service pack level as your Deployment Server.
- Verify that you have Microsoft Data Access Component (MDAC) installed - must be at the same level of MDAC as your Deployment Server.
- Map your Application Server to the Deployment Server where the OneWorld base directory exists (for example, D:\b7333)
- Modify the Application Server JDE.INI that is located on the Deployment Server. From Windows NT Explorer, locate the JDE.INI file that will be copied to the Application Server. By default it is located in: \jdedwardsoneworld\b7333\hosts\INTELNT\NTAPPSVR (where 'NTAPPSVR' is the name of your Application sever). Using a text editor, modify the JDE.INI file as follows:
- In the [INSTALL] section, verify that your LocalCodeSet parameter is set to the appropriate value. For appropriate values and code pages, see the 'National Language Support Tables' in the 'Language Process Overview' chapter in the 'Custom Preparation' section in the 'Xe Installation Guide.' These values are set automatically, with the first language installed. For multiple languages, the first language, alphabetically, is the default, and may need to be modified.
- The DefaultEnvironment Parameter in the [SECURITY] section must match a valid environment in the plan (for example, DV7333).
- In the [DB SYSTEM SETTINGS] verify the following settings ('NTAPPSVR' is the name of your Application Server & 'ENTSVR' is the name of your AS/400 Enterprise Server).
Base Datasource=NTAPPSVR - B7333 Server Map
Server=NTAPPSVR
Database=NTAPPSVR - B7333 Server Map
Load Library=JDBODBC.DLL
Library List=ENTSVR
- In the [JDENET_KERNEL_DEF10] set the numberOfAutoStartProcesses=0.
- Save the JDE.INI file, and then close it.
Application Server -Manually Create ODBC Datasources
** Please reference the "Creating Third-Party ODBC Data Sources." section of the NT Installation Guide for Xe and the "Data Source Charts" section of the Xe Reference Guide. **
Signon as the OneWorld NT administrator user JDE and manually create a Client Access ODBC for each datasource. If you are unsure of what datasources need to be created, logon to OneWorld on your Deployment Server and go to the 'System Administration Tools' menu (GH9011) and double-click on 'Database Data Sources' (P986115). From the 'Machine Search & Select' form select your 'NTAPPSVR - Server Map' data source. On the 'Work with Data Sources' form do a 'Find' - these are the datasources that you will need to manually create on your Application Server. You will also need to create an ODBC datasource for 'ENTSVR - B7333 Server Map' (where 'ENTSVR' is the name of the Enterprise Server) that points to the SVM7333 library, and 'NTAPPSVR - B7333 Server Map' datasource that points to the APPLIB on your AS/400 Enterprise Server. These ODBC datasources should be created exactly like the ODBC datasources (for your Application Server) on your Deployment Server.
Application Server - Application Server Setup
The Enterprise (Application) server installation process copies OneWorld system and path code files directly from the NT Enterprise Server CD. Signon as the OneWorld NT administrator user JDE, verify that you have mapped a share to your Deployment Server where the OneWorld base directory exists.
- Insert the NT Enterprise Server Setup CD into the CD drive. Installation Manager starts automatically.
- On the 'Installation Manager,' click on the link to install the Enterprise Server. The 'JDEdwards OneWorld Enterprise Server Setup' form appears, click 'Next.'
- The 'OneWorld Enterprise Server JDE.INI Path' form appears. Enter the path for the Deployment Server where your Application Server JDE.INI file exists, (for example, c:\hosts\INTELNT\NTAPPSVR\JDE.INI/ (where 'NTAPPSVR' is the name of your Application Server).DO NOT provide the path of the Deployment Server JDE.INI. Click 'Next'.
- The 'JDEdwards OneWorld Enterprise Server Setup Type' from appears, choose the setup type as 'Custom' . In the 'JDEdwards Enterprise Install Path' field, use the browse button to choose the directory where you want the files installed on your Application Server. If this directory does not already exist, the setup program will create it for you. Click 'Next.'
- The 'JDEdwards OneWorld Enterprise Server Setup Component Selection' form appears. Verify the appropriate components are installed, and click 'Finish.' The OneWorld Enterprise Server Setup dialog appears as files are loaded.
- When the installation finishes, the OneWorld Enterprise Server Setup dialog tells you whether the installation was successful.
Application Server - Verifying the Installation (PORTTEST)
Logon the Windows NT Application Server, as user JDE. The PORTTEST program initializes a user and an environment (assuming that OneWorld is installed and configured correctly). To verify that OneWorld is installed correctly you must run the PORTTEST program for each environment. Open a DOS command window and enter the following commands:
D: [or the appropriate drive letter]
cd \jdedwardsOneWorld\ddp\b7333\System\Bin32
PORTTEST userid password environment
Where userid is a valid OneWorld user, and password is the password for that user, and environment is the environment you are verifying. These parameters are case sensitive. Enter the PORTTEST command for each environment.
** PORTTEST should display messages indicating the selection of records out of a OneWorld table. If it does not, review the JDE_####.LOG and JDEDEBUG_#### file that was specified in the JDE.INI file on the Application Server. If PORTTEST fails to run, see the "PORTTEST Checklist" in the NT Install Guide for Xe -Chapter 8 for diagnostic assistance. **
Application Server - Starting OneWorld Application Server
After you install OneWorld on the Application Server and have verified a successful install with PORTTEST, you can start the server.Always have the AS/400 Enterprise Server services started before you start your NT Application Server services. Be sure to start Network, and then the Queue services. The JDENET, JDEQUE and the Application Server MUST use the same login.