# Automating the Manager features
All actions usually performed in the Manager user interface (until the distribution of a model), can be automated in a scripting file. All sources and targets supported by the Manager are also supported in the script file.
## About this task
The actions to be automated in the script file are the following:
* starting and stopping database journalization,
* creating and deleting an environment,
* creating and deleting a model,
* adding and deleting tables,
* creating and deleting a target,
* starting, stopping and terminating the distribution of a model,
* performing a load recovery on the distribution.
## Procedure
1. To create the script file, open a .txt file.
2. Feed it according to the following commands and their syntax:
Information noteNote: You can add as many commands as you like in the same script file (for example, connecting to various source databases and creating various distributions is possible). You can also create one script file for each source type. It depends on your needs.
| Command | Description | Details and Syntax |
| --- | --- | --- |
| : comment line | | ``` :this is a comment line ```
or
``` : this is a comment line ``` |
| connect source | To connect the source database | Type entry is one among the databases supported as source (AS400, MS SQL Server, Oracle, OpenEdge, PostgreSQL, MySQL, MariaDB).
Three different commands are used:
For AS400 IBMi source:
connect IpAddress/AS400/
For MS SQL Server and Oracle sources:
connect IpAddress/Type/Instance
For MariaDB, MySQL, PostgreSQL and OpenEdge sources:
where storage\_path is the folder located on the same machine as the engine, used for the storage of .JRN files. |
| select-env | To select an environment | Use this command only if you want to use an environment that is already created in the Manager.
``` select-env envid ``` |
| create env | To create and select an environment
Default value is used if no parameter is specified | ``` create-env envid EnvType := 2 :0 = Production 'default :1 = Test :2 = Training :3 = Model :4 = Deployment Description := SFEnvirt Training 01 Hold := 0 :0 = False :default :1 = True SrcId := S01 Tempo := 1 Retry := 5 end-create ``` |
| create metadata | To create metadata for this environment | Mainly for the JSON variables used for streaming sources (Kafka, Kinesis, Snowflake). The JSON script is then included in the create model command.
``` select-env envid create-metadata #variable1# := metavalue1 #variable2# := metavalue2 #variable3# := metavalue3 end-create ``` |
| select model | To select a model | ``` select-env envid select-model grpid ``` |
| create model | To create and select a model
Default value is used if no parameter is specified | AS400 source
``` begin-script-where :Some query after where clause SALESNUM = '1' AND PROMOKEY > 10 end-script-where ``` |
| add transformation to the table | To add the transformation to the selected table | First, use the selection commands:
if I.SALESNUM = '1' Then O.PROMOKEY = 1 O.SALESNUM = I.SALESNUM Endif end-transformation ```
DCL lines are the default ones. They will appear in the list if no other declaration is entered.
If you want to add another DCL than the
default ones, you can write it in the transformation block.
The default DCL lines are automatically removed from the list and only your new lines are taken into account.
Information noteNote: Between begin-transformation and end-transformation, comments are
marked with /\* only. |
| stop distribution | To stop the distribution of the model | ``` select-env envid select-target tgtid stop-distribution grpid ``` |
| kill distribution | To terminate the distribution of a model | ``` select-env envid select-target tgtid kill-distribution grpid ``` |
| delete distribution | To delete the distribution of a model | ``` select-env envid select-target tgtid delete-distribution grpid ``` |
| delete target | To delete a target | ``` select-env envid delete-target tgtid ``` |
| delete model | To delete a model | ``` select-env envid delete-model grpid ``` |
| delete table | To delete a table | ``` select-env envid select-model grpid delete-table tableid ``` |
| delete environment | To delete an environment | ``` delete-env envid ``` |
| stop journalization | To stop journalizing a database | ``` dejournalise dbid ``` |
3. Save the file.
4. Launch a command prompt and enter the following commands:
>cd TalendChangeDataCaptureDestinationPath. Press Enter.
DDmanager -cicd "ScriptFilePath". Press Enter.
## Results
Distributions are created as they were declared in the script file.
If you want to view the result: launch the Manager and subscribe to the source, then connect to it. For more information, see [Managing sources subscription and connection](https://help.qlik.com/talend/en-US/change-data-capture-user-guide/7.3/managing-sources). To start the replication process, follow [Operating and supervising a replication](https://help.qlik.com/talend/r/en-US/7.3/change-data-capture-user-guide/operation-of-replication) section.
To check the logs after the start of the script, open DDMGRAUTO.log file located in DestinationPath repository (the same repository as the Manager .exe file).
To plan when to launch all replications, you can configure the Scheduler (see [Starting Replications Automatically](https://help.qlik.com/talend/r/en-US/7.3/change-data-capture-user-guide/starting-replications-automatically)).
### In this section
* [Script file samples](https://help.qlik.com/talend/en-US/change-data-capture-user-guide/7.3/script-file-samples)