Introduction: This document assumes you have a strong understanding of Oneworld and CNC concepts. The Environment and Pathcode created are not suitable for upgrade.
Introduction:
This document details the steps required to create a custom Pathcode and Environment. These steps will create the OCM, Data sources, and physical files needed to run OneWorld.
1.
Create Data base user and files. Listed below are the methods for SQL and ORACLE:
•
For SQL login as system administrator. Open an sQL Query analyzer, past in these scripts being sure to modify drive and file names to match your install.
Use master
Go
CREATE DATABASE JDE_CUSTOM (*JDE_CUSTOM represents name of the custom file)
ON
(NAME = ‘JDE_CUSTOM_Data’, FILENAME =’z:\mssql7data\JDE_CUSTOMdata.mdf’,SIZE=2000,MAXSIZE=2500MB, FILEGROWTH=5MB)
LOGON
(NAME=’JDE_CUSTOM_log’,FILENAME=’z:\mssql7data\JDE_CUSTOMlog.ldf’,SIZE=200, MAXSIZE=250MB, FILEGROWTH=5 MB)
GO
Sp_dboption JDE_CUSTOM,’select into/bulkcopy’,TRUE
Go
CREATE DATABASE JDE_CUS
ON
(NAME=’JDE_CUS_Datta’,FILENAME=’z:\mssql7data\jde_CUSdatta.mdf,SIZE=500, MAXSIZE=600MB, FILEGROWTH=5MB)
LOG ON
(NAME=’JDE_CUS_log’,FILENAME=’z:\mssql7data\jde_CUSlog.ldf’,SIZE=50, MAXSIZE=60MB, FILEGROWTH=5MB)
GO
Sp_dboption JDE_CUS,’select into/bulkcopy’,TRUE
Go
Use JDE_CUS
Grant CREATE TABLE to public
Go
Use jdeb733
Go
Grant CREATE TABLE to public
Go
Sp_addlogin ‘CUSTOM’,’CUSTOM’,JDEB733
Go
Use JDE_Custom
Go
Sp_adduser ‘JDE’,’JDE’,public
Go
Sp_addlogin ‘CUSTOM’,’CUSTOM’, ‘public’
Go
Sp_adduser ‘CUSTOM’,’CUSTOM’,’public’
Go
Use JDEB733
Go
Sp_adduser ‘CUSTOM’,’CUSTOM’, ‘public’
Go
•
For Oracle, run this script in Oracle SQL worksheet. Login as Oracle dba. Be sure to modify drive and file names to match your install. The scripts for creating the tablespaces can be copied from the deployment server. They are stored in
Create tablespace customt
Datafile ‘d:\orajde\custom01.dbf’ size 1300M autoextend on next 1 M maxsize 1500M
Default storage (initial 500000 next 500000 maxextents unlimited pctincrease 0);
Creat tablespace customi
Datafile ‘d:\orajde\customi01.dbf size 350M autoextend on next 1M mazsize 1000M
Default storage (initial 500000 next 500000 maxextents unlimited pctincrease 0);
Create tablespace custdtat
Datafile ‘d:\orajde\custdta01.dbf’ size 200M autoextend on next 1 M maxsize 1000M
Default storage (initial 500000 next 500000 maxextents unlimited pctincrease 0);
Creat tablespace custdtai
Datafile ‘d:\orajde\custdtai01.dbf size 200M autoextend on next 1M mazsize 1000M
Default storage (initial 500000 next 500000 maxextents unlimited pctincrease 0);
Create tablespace custctlt
Datafile ‘d:\orajde\custctl01.dbf’ size 25M autoextend on next 1 M maxsize 1000M
Default storage (initial 500000 next 500000 maxextents unlimited pctincrease 0);
Creat tablespace custctli
Datafile ‘d:\orajde\custctli01.dbf size 25M autoextend on next 1M mazsize 1000M
Default storage (initial 500000 next 500000 maxextents unlimited pctincrease 0);
Create user custom identified by custom
Default tablespace customt
Temporary tablespace TEMPORARY_DATA
Quota unlimited on customt
Quota unlimited on customi
Quota unlimited on TEMPORARY_DATA;
Grant jde_role to custom;
2.
Create Oneworld Data Sources
•
Log in to Oneworld on an Admin workstation
•
Fast path to the GH9011 menu
•
Choose Database datasources
•
Select the system –B733 datasource
•
Copy Business Data –xxxx and rename it to Business Data – CUSTOM. Pay close attention to the object owner ID and the Database name.
•
Copy the remaining Data Sources (Versions, Central Objects, Control Tables and OneWorld local –xxxx). Pay close attention to the object owner ID and the Database name.
•
Create ODBC datasource as prompted (SQL Server)
3.
Copy and existing pathcode
•
Fast Path to GH9053
•
Select Path Code Master
•
Highlight an existing pathcode (xxxxB733) and click copy.
•
Modify the Path Code name, description and Deployment Data Source
4)
Copy an existing Environment
•
Fast path to GH9053
•
Select Environment Master
•
Highlight an existing Environment (xxx733). From the row exit click the Copy Environment
•
Modify Environment Name, Description and Path Code.
•
Enter OL Data Source if prompted.
5)
Copy files on the Enterprise Server and the Deployment Server
•
On the Deployment Server, right click on the path code you wish to copy. Highlight B733 and click paste.
•
Rename the directory to your custom name
•
Modify, under the custom path code, the Package directory as necessary.
•
In the PACKAGE_INF directory, copy and modify an existing package.inf
•
On the enterprise server, copy and existing path code and rename it to your custom name.
6)
Create new OL records
•
Log into OneWorld, fastpath to BV
•
D a find for R989861
•
Double click on the XJDE0001
•
In the Processing Options, set your source PathCode to the PathCode you copied, Target is the New Custom Pathcode.
7)
Generate Server Map OCM (*Note this will configure all environments listed. If you add another environment and don’t want to alter other settings, delete the other enviornments, configure and then readd the environment.)
•
Fast Path to P9654a
•
Click Find. Expand, the Enterprise Server section
•
Highlight your Enterprise Server and click Select
•
From the Form exit, click on Environments
•
Add your custom environment to the list
•
From the form exit, click on the Generate Server Map
8)
Run the appropriate R98403 version
•
Version 21 will copy your Business Data to the new custom Data Source
•
Version 19 will copy your Specs and Versions to the new custom Data Source
•
Version 22 will copy your Control Tables to the new custom Data Source
9)
Test the new environment
•
Run PortTest for the newly created environment. CD to the system\bin32 on the enterprise server from a command prompt.
On the Enterprise Server do the following:
1.
Start, Run, type in the following to get a dos prompt: cmd
2.
Type the letter drive of the jdedwardsoneworld path. Ex: g:
3.
Then type: cd:\jdedwardsoneworld\ddp\b7332\system\bin32
4.
Type, porttest JDE JDE CUSTOM. Case is important, JDE JDE should be replaced with a valid OneWorld username and passworld. Custom should be replaced with the custom environment name.
