Deprovisioning datasets
To deprovision the datasets follow the steps provided here.
To deprovision datasets
-
Navigate to the Workflows tab and select IBM RACF Datasets.
-
Click Add synchronization step.
-
Click Deprovision and then click Next.
-
From the Source connected system section and click Specify.
-
Select your SQL Server Connector and click Finish.
-
Select Source object is deleted or is out of synchronization scope option in the Deprovision target objects if section.
- Optionally, configure the Source object meets the following criteria.
-
Click Next.
-
In the Target connected system field, click Specify and then locate your IBM RACF connector and click Finish.
-
The object type in the Target object system field is populated automatically by Synchronization service to racfDataset.
-
Click Next.
- Select Delete target object.
- Click Finish to complete the synchronization.
Running TSO command
The IBM RACF connector can be used to run any command in the Time Sharing Option (TSO) environment on the target IBM mainframe. The LDAPX exit must be installed and configured for this functionality to be supported.
Working with TSO command
The TSO command is run using an ARSS synchronization step to create an object of type ldapxtsocmd on the target IBM RACF system and supplying the name of the TSO command or script to be run in the attribute racfprogrammername. When the step is run, the IBM RACF connector intercepts the create command and instead sends an LDAP search command with the required parameters via the LDAP protocol.
The LDAPX exit intercepts this request, extracts the TSO command information and runs the command. The LDAP response is constructed, containing the results obtained from running the command. The IBM RACF connector receives this LDAP response, extracts the results and saves them in a text file that can be examined later.
No object is created during the synchronization step so it can be run indefinitely, each time executing the TSO command stored in the racfprogrammername attribute from the same or any other synchronization step.
The following example shows a method of issuing a TSO command using synchronisation from Active Directory (AD).
-
Using Active Directory Users and Computers create a container in AD that can be filtered on by the ARSS. For example, create an organisational unit container called TSO Commands.
-
Create a dummy computer object within this container with name TSOCMD and description field set to the string STATUS. The TSO command STATUS will return the current system status.
-
Create a workflow called Run TSO Command.
-
Within this workflow, create a synchronization step item as follows:
-
Synchronization step type: Create
-
Source object: Active Directory, specified container as created above, name starts with TSOCMD.
-
Target connector: IBM RACF
-
Object type: ldapxtsocmd
-
Mapping: from AD Description attribute to IBM RACF racfprogrammername attribute
-
Save the step.
-
Run the synchronization step. There should be one item to be created with the following properties:
objecttype: ldapxtsocmd
racfprogrammername: STATUS
-
Perform the synchronization step.
-
The LDAP command will be sent and interpreted by the LDAPX exit to run the TSO command.
-
Once complete, the synchronization step will show as being successful.
-
The output from running the command can be found in the following text file:
<ARSS installation folder>\SyncService\TSOCommandOutput\YYDDMM.txt, where, YYMMDD represents the date when the command was run.
-
The text file will contain the output returned from IBM RACF having run the STATUS command.
-
Multiple commands run on the same day will have their output appended to the same daily text file.
Working with MySQL database
This section describes how to create or modify a connection to MySQL database so that Synchronization Service could work with data in that data system.
To create a connection to MySQL database, you need to use Synchronization Service in conjunction with a special connector called MySQL Connector. This connector is included in the Synchronization Service package.
The MySQL database Connector supports the following features:
Table 68: Supported features
Bidirectional synchronization
Allows you to read and write data in the connected data system. |
Yes |
Delta processing mode
Allows you to process only the data that has changed in the connected data system since the last synchronization operation, thereby reducing the overall synchronization operation time. |
No |
Password synchronization
Allows you to synchronize user passwords from an Active Directory domain to the connected data system. |
Yes |
In this section:
For instructions on how to rename a connection, delete a connection, modify synchronization scope for a connection, or specify password synchronization settings for a connection, see Synchronization Service Administration Guide.