Creating Test Batch Files
JD Edwards EnterpriseOne Tools Configurable Network Computing Implementation Guide
Denote whether a customer's object will be merged with the JD Edwards
EnterpriseOne object This option can be set at the path code level so that all objects
checked into that path will carry the same merge option as the path code.
Specify the release number as defined by the release master.
Deployment Data Source
Specify the data source if the primary data source or if the data item in the primary
data source cannot be located.
Determine how to create the serve path. Valid options are:
1 or Y
Creates the paths using relative paths. Enter a double slash (||) rather than a
specific drive followed by a single slash (\).
0 or N
Creates the path using the actual drive letter.
The description that appears in the Z record of a SAR when OMW enters information
into that record.
B.6 Creating Test Batch Files
This section discusses how to create test batch files.
B.6.1 Creating Test Batch Files
To create test batch files:
Using a text editor such as Notepad, remark out all lines in the LOADALL and
JDESET files and format a test set in the same format as the production set.
Copy the LOADPROD to a LOADTEST.BAT file, and change the appropriate
parameters to the ones you created in the JDESET.BAT file.
Run the LOADALL.BAT batch application.
Add the data sources you need in the current plan's planner environment.
For logical data sources, you will probably want Business Data Test, Central
Objects Test, JD Edwards EnterpriseOne Local Test, and Control Tables Test.
Make sure the deployment server source matches the Central Objects Data
source and the LOADALL specifications that you entered.
B.7 Updating Server Map Tables with the New Environment
This section discusses how to update server map tables with the new environment