Upload
sanyahv
View
56
Download
5
Tags:
Embed Size (px)
DESCRIPTION
JobScheduler
Citation preview
Migration from Migration from Control-M toControl-M to
JobScheduler in a JobScheduler in a TWS LandscapeTWS Landscape
SOS Software GmbH Berlin, Germany
ContentContent basic conditions I & II previous landscape (Control-M) current landscape (JobScheduler) basic data installation migration (overview) migration (workflow)
SOS Software GmbH Berlin, Germany 2
Basic Conditions IBasic Conditions I
complete replacement of Control-M (incl. server)o the scheduling software has to be installed on the application servero all scheduling tasks have to be handled by JobScheduler
TWS is still the enterprise tool for software automationo It is necessary to implement the communication between JobScheduler and TWSo no changes in the TWS environmento the configuration of the TWS jobstreams have to remain unchanged
SOS Software GmbH Berlin, Germany 3
Basic Conditions IIBasic Conditions II
security conditionso the security conditions of the customer have to be considered
(e.g. no direct ssh connection to the TWS server)
less migration efforto the effort is 60 days
cost reductiono approx. 80% savingso ROI < 1 year
SOS Software GmbH Berlin, Germany 4
Previous Landscape (Control-M)Previous Landscape (Control-M)
'Logistic Cluster'o two application server (production & development)o development server is fallback for production
Job scheduling controlled by Control-Mo one Control-M installation on a separate server o no distinction between production & developmento Control-M handles the communication with TWSo Control-M handles the batch operations for the logistic applications
TWS communication controlled by an TWS agento a TWS agent is running on the Control-M servero it handles the communication with the TWS server
SOS Software GmbH Berlin, Germany 5
Previous Landscape (Control-M)Previous Landscape (Control-M)
application server
logisticapplications
logisticapplications
TWS server
TWSTWSSAP
Control-M server
TWS agentTWS agent
Control-MControl-M
SOS Software GmbH Berlin, Germany 6
Current Landscape (JobScheduler)Current Landscape (JobScheduler)
SOS Software GmbH Berlin, Germany
'Logistic Cluster'o Two application servers (production & development)o Development server is fallback for production
Job scheduling controlled by JobScheduler (JS)o one instance of JS installed on each application server (production & development)o JS handles the communication with TWSo JS handles the batch operations of the logistic applications
TWS communication controlled by an TWS agento a TWS agent is running on the application servero it handles the communication with the TWS server
7
application server
logistic applications
logistic applications
Current Landscape (JobScheduler)Current Landscape (JobScheduler)
TWS server
TWSTWSSAP
TWS agentTWS agent
JobSchedulerJobScheduler
SOS Software GmbH Berlin, Germany 8
webservice
webservice
script
conman1
other external applications
other external applications
1 conman is a command line tool for the TWS agent
Basic DataBasic Data
configuration of JobSchedulero 600 jobso 250 job chainso 100 orderso TWS communication via TWS agento external job start via Web Service
databaseo one database shared by two instances of JobScheduler (production &
development)o Oracle 11o 50 GB tablespace
SOS Software GmbH Berlin, Germany 9
Batch InstallationBatch Installation
installation of JobScheduler in batch modeo configuration files just differ in a few parameters (e.g. the server names)o garantee of exactly the same installation on all systemso easy to reinstall
SOS Software GmbH Berlin, Germany 10
Migration OverviewMigration Overview export the Control-M configuration
o Control-M provides its job configuration in XMLo one xml file per Control-M table
automated migrationo providing a set of XSLT stylesheets to handle the migrationo controlled by ANTo 6 steps workflow:
configuration data collection build addtional ressources for JobScheduler generating JobScheduler objects provide a release version of the live folder deployment to the application servers
o < 5% manual adaption
SOS Software GmbH Berlin, Germany 11
Migration WorkflowMigration Workflow
SOS Software GmbH Berlin, Germany 12
configureconfigure
collectcollect
buildbuild
generategenerate
releaserelease
deploydeploy
configure a file with all CTM tables to migrate
generate JS objects based on the 'collection'(jobs, orders, job chains)
create a 'collection' of the basic data of all jobs create manual JS objects in individual cases adapt the given Control-M data in the 'collection' expand the 'collection' with sample 'payload' per job
generate additional JS objects(e.g. syncpoint jobs, process classes, locks)
create a local release version of the live folder
deploy the live folder to the application servers
= automated steps (X
LST)
Folie 1Folie 2Folie 3Folie 4Folie 5Folie 6Folie 7Folie 8Folie 9Folie 10Folie 11Folie 12