Adding a new Environment

hkpolarbear

Active Member
I have currently the CRP environment (PY7333) running. Central Objects on the Deployment Server, Business Data on an AS400 coexistent with World. I have my data sources Business Data - CRP and AS400 Common - CRP pointing to the right libraries on the AS400.

If I want to create a duplicate environment say PZ7333 and I want it sharing pathcode, central objects with PY7333 except Business Data - CRP and AS400 Common - CRP which point to a different library respectively on the AS400, is that possible ? and how can I do it easily ?

Regards,

Conrad
 

vap

Active Member
Conrad,

Have a look at CNC Implementation, page 100. Below is a brief set of
steps, which assumes at least a limited degree of understanding of CNC.
1. Create ODBC datasources (in Windows Control Panel), pointing to your
new libraries (if they don't exist already)
2. Create OneWorld Database Datasources both for [System - B7333] and
[(EnterpriseServer) - B7333 Server Map], menu GH9011, app P986115,
ZJDE0002 (just copy existing ones, change the name of DS and Database
Name = new ODBC DS)
3. Go to GH9053, Environment Master (P0094), right click, prompt for
Processing Options values, change Copy OCM = 1. Select Copy Environment
from Row menu. Change the name of your new environment.
4. Go to GH9011, Object Configuration Manager (P986110). Change the
mappings for your environment both [System - B7333] and
[(EnterpriseServer) - B7333 Server Map]. It is a little tedious, you may
run an SQL query on SYS7333.F986101 and SVM7333.F986101.

Regards,
Vladimir Ponomarev
B7332, XE (mostly XE at the moment); SQL 7.0, Oracle 8.1.5; Wintel, HP
(mostly Wintel);
A little bit of World A73 Cum10
 

hkpolarbear

Active Member
Re: RE: Adding a new Environment

Thanks for your info.

I have done these processes before but I just cannot list out all the required steps in advance and chain them together or decide which one to do first.

What about package creation ? A different package is required to be deployed in this case for different ODBC setup on the client. Otherwise it will be tedious to create and modify for each client.
Correct me if I am wrong.

Thanks,

Conrad
 

vap

Active Member
RE: RE: Adding a new Environment

Well, Conrad,

Have not thought about deploying to workstations. :-(
If you wish to go JDE way - you can deploy just foundation package (you
might need to amend \\(EnterpriseServer)\B7333\Client\ODBCDataSource.inf
manually, i'm not sure if it's updated automatically, but think not).
I would prefer a simple reg file - export
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\odbc.ini, edit it to leave only new DS,
and then import it on your workstations.

Regards,
Regards,
Vladimir Ponomarev
B7332, XE (mostly XE at the moment); SQL 7.0, Oracle 8.1.5; Wintel, HP
(mostly Wintel);
A little bit of World A73 Cum10
 

hkpolarbear

Active Member
Re: RE: RE: Adding a new Environment

That is a very good idea. I have never thought of that. Can I just get the odbc.ini file in my developer's workstation and then make a copy to every workstation so they will have all the new ODBC setup ?

I never touched registry. Can you explain your process of reg export and how is it different from me just copying the odbc.ini file to the workstations ?

Thanks a lot.

Conrad

OneWorld XE SP15.1
COexistency with World A73Cum11
 

vap

Active Member
RE: RE: RE: Adding a new Environment

Conrad,

I do not know anything about copying odbc.ini. I think that it's a
legacy file, and not sure if it is used by NT.

I must confess that I'm strongly NT-oriented, it might not work for
Win9* or Me. Copying registry:
1. Go to Start, Run...
2. Enter regedit
3. Open menu File -> Export Registry File
4. In [File name] enter file name :). In [Export range] select
[Selected branch] and enter "HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\odbc.ini"
(without quotes).
5. Save
6. Find the file in Explorer. Right click on it, select Edit.
7. It will look something like this:
-
REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\odbc.ini\1]
1=1
2=2
3=3

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\odbc.ini\2]
1=1
2=2
3=3
-
Delete the values, which are not related to your Datasources. Let's say,
if you only need DS 2, the edited file should look like this:
-
REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\odbc.ini\2]
1=1
2=2
3=3
-
8. Go to your client machine, left double click on the file. You need
local Admin or Power User rights.

If you have Win2k station, registry file will look slightly different.
If you are to install it on NT, replace the first line with "REGEDIT4"
and save as non-Unicode file.

Regards,
Regards,
Vladimir Ponomarev
B7332, XE (mostly XE at the moment); SQL 7.0, Oracle 8.1.5; Wintel, HP
(mostly Wintel);
A little bit of World A73 Cum10
 
Top