On the first page of the wizard, enter a job name that describes a purpose of the job. Choose the 'source' database schema that will serve as a baseline for a comparison job. It can be either a 'live' database schema, as for example, your QA server database schema, or a Server Studio schema snapshot previously created and stored in Sentinel repository. If you want to create a new snapshot at this point, choose Version Snapshot radio button and press Create New Snapshot button. See Version Snapshots topic in the Server Studio help (Help -> Server Studio Help menu) for an additional information on version snapshots functionality.
You can include one or more databases into a single schema audit job. For example, you can create a job that compares all databases on your source Informix server instance to all databases on one or multiple target server instances. This model works well when you have multiple deployment targets for your Informix applications and all targets should have exactly the same schema as a source target.
Press the Next button to define target Informix instances. Select one or more target instances and press the Next button. The third page of the wizard attempts to automatically match selected databases or snapshots on a source Informix instance to databases with the same name on selected target instances. If your target database or databases have different names than a source database name, you can manually specify a target database name for each source database in the Target Database column in the grid.
Press the Next button to define schema comparison options. You can choose to compare only selected group of objects, ignore physical storage properties, such as dbspace names, include or exclude user permissions comparison, etc.
Press the Next button to define how you want to be notified when the differences in schema are found. You can choose to send an email message that can optionally include a schema difference report and a pre-generated synchronization SQL script.
Press the Next button to define a schedule for a newly created job. If you do not define a schedule right away, you still will be able to execute schema audit jobs manually or add the schedule at later time after the job is created.
Press the Next button to define actions that should be taken when the schema audit job fails during execution . Optionally, define actions to be taken when job execution succeeds. For example, you might want to send an email notification when a scheduled schema audit job fails because it cannot establish a connection to a target Informix server. Schema audit job can also execute another job in case of failure and/or success.
After the schema audit job is created on Sentinel server, you can access it in the Sentinel-Automation tab under Sentinel Server -> Change Management -> Schema Audit Jobs folder. If the job was scheduled, it will be executed as per specified schedule. Otherwise, you can execute it manually by selecting the job in the tree and choosing Execute from the mouse popup menu. To edit the job, choose Edit from the mouse popup menu.
All schema difference reports created by a particular schema audit job are available in the job's Properties panel. Alternatively, all difference reports created by all schema audit jobs executed on Sentinel server are available in Sentinel Server -> Change Management -> Schema Audit Reports folder under Sentinel – Automation tab.