Migration from Control-M to JobScheduler in a TWS Landscape

SOS Software Gmb

!erlin" German#

Content
$ $ $ $ $ $ $ basic conditions % & %% pre'ious landscape (Control-M) current landscape (JobScheduler) basic data installation migration (o'er'iew) migration (wor*flow)

SOS Software Gmb

!erlin" German#

!asic Conditions %
$ complete replacement of Control-M (incl, ser'er)
o the scheduling software has to be installed on the application ser'er o all scheduling tas*s ha'e to be handled b# JobScheduler

$ TWS is still the enterprise tool for software automation

o %t is necessar# to implement the communication between JobScheduler and TWS o no changes in the TWS en'ironment o the configuration of the TWS -obstreams ha'e to remain unchanged

SOS Software Gmb

!erlin" German#

!asic Conditions %%
$ securit# conditions
o the securit# conditions of the customer ha'e to be considered (e,g, no direct ssh connection to the TWS ser'er)

$ less migration effort

o the effort is /0 da#s

$ cost reduction
o appro1, 203 sa'ings o 4O% 5 6 #ear

SOS Software Gmb

!erlin" German#

8re'ious Landscape (Control-M)

$ 9Logistic Cluster9
o two application ser'er (production & de'elopment) o de'elopment ser'er is fallbac* for production

$ Job scheduling controlled b# Control-M

o o o o one Control-M installation on a separate ser'er no distinction between production & de'elopment Control-M handles the communication with TWS Control-M handles the batch operations for the logistic applications

$ TWS communication controlled b# an TWS agent

o a TWS agent is running on the Control-M ser'er o it handles the communication with the TWS ser'er

SOS Software Gmb

!erlin" German#

8re'ious Landscape (Control-M)

TWS ser'er Control-M ser'er TWS TWSagent agent application ser'er

S;8

TWS TWS

Control-M Control-M

logistic logistic applications applications

SOS Software Gmb

!erlin" German#

Current Landscape (JobScheduler)

$ 9Logistic Cluster9
o Two application ser'ers (production & de'elopment) o <e'elopment ser'er is fallbac* for production

$ Job scheduling controlled b# JobScheduler (JS)

o one instance of JS installed on each application ser'er (production & de'elopment) o JS handles the communication with TWS o JS handles the batch operations of the logistic applications

$ TWS communication controlled b# an TWS agent

o a TWS agent is running on the application ser'er o it handles the communication with the TWS ser'er

SOS Software Gmb

!erlin" German#

Current Landscape (JobScheduler)

6

conman is a command line tool for the TWS agent

TWS ser'er

application ser'er TWS TWSagent agent

webservice

conman 1

S;8

TWS TWS

other othere1ternal e1ternal applications applications

JobScheduler JobScheduler
webservice script

logistic logistic applications applications

SOS Software Gmb

!erlin" German#

!asic <ata
$ configuration of JobScheduler
o o o o o /00 -obs +:0 -ob chains 600 orders TWS communication 'ia TWS agent e1ternal -ob start 'ia Web Ser'ice

$ database
o one database shared b# two instances of JobScheduler (production & de'elopment) o Oracle 66 o :0 G! tablespace

SOS Software Gmb

!erlin" German#

>

!atch %nstallation
$ installation of JobScheduler in batch mode
o configuration files -ust differ in a few parameters (e,g, the ser'er names) o garantee of e1actl# the same installation on all s#stems o eas# to reinstall

SOS Software Gmb

!erlin" German#

60

Migration O'er'iew
$ e1port the Control-M configuration
o Control-M pro'ides its -ob configuration in ?ML o one 1ml file per Control-M table

$ automated migration
o pro'iding a set of ?SLT st#lesheets to handle the migration o controlled b# ;@T o / steps wor*flowA $ configuration $ data collection $ build addtional ressources for JobScheduler $ generating JobScheduler ob-ects $ pro'ide a release 'ersion of the li'e folder $ deplo#ment to the application ser'ers o 5 :3 manual adaption

SOS Software Gmb

!erlin" German#

66

Migration Wor*flow
configure configure configure a file with all CTM tables to migrate create a 9collection9 of the basic data of all -obs create manual JS ob-ects in indi'idual cases adapt the gi'en Control-M data in the 9collection9 e1pand the 9collection9 with sample 9pa#load9 per -ob B automated steps (?LST) collect collect

build build

generate additional JS ob-ects (e,g, s#ncpoint -obs" process classes" loc*s) generate JS ob-ects based on the 9collection9 (-obs" orders" -ob chains) create a local release 'ersion of the li'e folder

generate generate

release release

deplo# deplo#
SOS Software Gmb

deplo# the li'e folder to the application ser'ers

!erlin" German#

6+