Creating new Environment!

Would anyone have a detailed & modified step-by-step procedure of creating a New Environment? I would really appreciate it if I could get hold of it!

Rgds
Nailesh Mascarenhas
OW Xe SP 17 Update 3
Windows 2000 Advanced Server / TS / Citrix MetaFrame XP
MS SQL 2000

Nailesh,

Do you need to create a new pathcode, too or are you going to be using an
existing one?

Andy



Rgds
Nailesh Mascarenhas
OW Xe SP 17 Update 3
Windows 2000 Advanced Server / TS / Citrix MetaFrame XP
MS SQL 2000






Consultant with clients
at B7331 - Xe
Various Deployment Servers, Citrix and JAS

Hey Andy,

Thankz for replying quickly. Yeah, I need to create a new pathcode as well. I have a document from the KG site titled 'Creating an Electronic Software Update Path Code and Environment in OneWorld® Xe'. It is not in depth & it covers MS SQL 7.0 & not SQL 2000.

Hope to hear from you soon!

I beg to differ. If you download the Word file that is linked to that KG document, it is quite detailed, with many steps supported by screen shots. And even though it is SQL 7 instead of SQL 2000, the SQL statements should still work fine.

For another perspective, try looking for document #OTI-01-0056.

I used the "Creating a Custom Path Code and Environment that can be upgraded or updated" (OTI-01-0056) and the steps worked out great for us. I highly recommend this document.

One thing that got missed out of this document was the ESU history tables.

Basically if you copy a PathCode with ESUs applied to a new PathCode, the new PathCode won't have the ESU history against it.

To get around this do the following procedure, (This is a excert from a doument I wrote for a client on the AS400 platform for a PY7333 to PD7333 copy, but you get the general idea...)

ESU History Tracking:

Two files in the JDEB7.MDB file on the deployment server need to have records copied namely R9671 and R9672 so that the ESU history is copied from PY7333 to PD7333.

Copy F9671 and F9672 in SYS7333 to F9671WK and F9672WK respectively, with no data.

Enter the following and run the following SQL commands;
For F9671:
Insert into sys7333.F9671WK select * from
sys7333.F9671 where SDSUDFUT2 = ‘PY7333’
Update sys7333.F9671WK set SDSUDFUT2 = ‘PD7333’
Delete from sys7333.f9671 where SDSUDFUT2 = ‘PD7333’
Insert into sys7333.F9671 select * from sys7333.F9671WK
For F9672:
Insert into sys7333.F9672WK select * from ys7333.F9672 where SUPATHCD = ‘PY7333’
Update sys7333.F9672WK set SUPATHCD = ‘PD7333’
Delete from sys7333.f9672 where SUPATHCD = ‘PD7333’
Insert into sys7333.F9672 select * from F9672WK

Copy them to JDEPLAN.
Sign into the deployment server in the JDEPLAN environment
Enter Batch Versions and Search on R98403
Select Version IGP0001 (Copy ESU History – System to Planner)
Processing Options:
1 Blank
2 OneWorld Local
3 2
4 System – B7333
5 Blank
6 1
7 A
8 Blank
9 Blank
Data Selection
Where ‘Object Name’ = F9671, F9672
Run it locally, records will copy from System to Planner.

Regards