Reply To: Automating changes from development to production

[Steve Carter]

I’m currently working on the same thing.  What I decided to tackle first were the changes to the NetConfig (particulary moving of threads).

The script displays prompts for each step.  I first ask for the site, then it will load all of the protocol threads into a list.  The user can either enter a ‘?’ for a list of threads or key in the thread name.  It then determines the protocol of the thread (right now I’m targeting pdl-tcpip threads).  Depending on whether or not it is client or server determines whether or not I prompt for an IP address.

Once the user has entered enough information about the source thread, I then prompt for a production site name.  I pull the NetConfig from the production box back to test as a temp file.  I parse the temp file to make sure the thread they have chosen doesn’t already exist.  I then prompt for the process in which the thread belongs.  Again, the user can enter a ‘?’ for a list of processes.

Once this is complete, I build a file containing the protocol thread information and then push it back to the production box.  I have another script on the prod box that appends it to the NetConfig.

There is a lot of verification going on in the background to prevent typo’s and invalid IP’s, port numbers and overwriting of existing threads.

This script uses the netcfgLoad, etc. to parse the NetConfig’s.

The next piece I’m working on is the DATAXLATE portion for obtaining routes from other threads that route data to the thread that I’m moving.  I haven’t gotten too far into this yet as a few other projects have taken my time.

Shoot me an email if you have any questions.

Hope this helps.

Steve