• From the menu, select BMC, DevX Data Studio, and select the Rules Repository tab.
• Right-click on the TDPRepos repository and Open Repository.

• Double-click on your Data Privacy Project.

• Click on the Data Elements tab at the bottom.

• In your Project, Click on the Composites tab at the bottom of the screen.

• Click on bottom right Global button under Categories.
• Import Name and Separators categories from Global by clicking Import.

• In the Data Items section in the top right, click on the Global button under Data Items.
• Select Name-First Name, Name-Last Name and Name-Middle Name.

• Scroll down and also select White Space Separator (reducible).
• Click Import.

• Under Composite on the left-hand side click the Add button.

• Give your Composite a name as shown.
• Under Data Item on the left grab Global: Name-First Name and drag to the black box under Structure.
• Line it up on the left of that box until you see the arrows and drop it.

• Drag the White Space Separator to the right of the first name in the Structure box and drop it directly beside the First Name.

• Continue lining up Middle Name, then a Space, then Last Name.

The data in our column or field may or may not contain a Middle Name.
To handle this: 

• Click on the Middle Name in the Structure box.
• Click the Optional box below under the General tab.

• Click on the Second Space in the Structure box and select Optional below.
• Click on Test. at the bottom of the screen

• Type a name into the field to test your newly created Composite definition.
•  Click OK to view your results.

• Click the X to close this box. Click OK to save your Composite Definition.

• Click on the Rules tab at the bottom of the screen.
• Click Add to add a new Rule.

• Type a new Rule name as shown and click Composite for the Create Rule Action.
• Click Next.

• Type in an Action name as shown in the first field.
• Use the drop-down menu for Project Resource and select the Data Element already created for FIRST LAST NAMES.
• Click Next.

• Select your Composite field definition from the drop-down menu.

The different data items will appear below.

• Click on a Data Item and use the drop-down under the Data Element column to match to the correct Data Element.

Since we are not disguising Middle Name or Spaces we will leave those blank.

• Click Finish.

• Click the X in the tab to Close the updated Data Privacy project.

• Select the Data Explorer tab next to the Rules tab.  These are both available within the DevX Data Studio perspective..

• Right click on the FAEXRepos Repository in the left-hand tree view. 
• Select Open.

• Right click on Related Extract and select New.

• Input an Extract name as shown and then click Browse for the Driving Object. 

• Select Database (JDBC) for the Type.
• Use the Host dropdown to select the SQL Server Sample database.
• Type dbo (in lowercase) for the Schema Name.
• You may be prompted for credentials to connect to the database. Enter "testdrive" for the userid and password and click OK.
• Click List beside schema name.

• Select the CONTACT_TABLE from the list and click OK.

• Click Finish.

• Click Browse for the Extract file location. This is where the extract file will be written.

• Navigate to Temporary Files and then click on Select Folder.

• From the Extract Overview screen, select the Data Privacy tab along the bottom of this section.

Here you can select the Disguise Rules already created and saved within your Data Privacy Project. This will determine the data eligible for disguise and the rules to be applied to the data during this extract process.

• Click on the Browse button for Project Name.

• Use the Repository drop-down to select the TDPRepos repository.
• Select your project, or you may use the TEST DRIVE DISGUISE PROJECT for this exercise.
• Click OK.

• Execute by clicking on the Blue Arrow execution button in the top right corner.

• Look in the Console tab for execution information. 
• Double click the Console tab to maximize this view.
• Here you will see number of rows extracted.
• Scroll down to see information on how the data privacy rules were applied to the different columns.

• Double click again on the Console tab to minimize.
• Close the Extract job by clicking on the X in the tab.

• Save the Extract job when prompted.

•  Navigate to the Data Explorer view and right click on Related Loader and select New.

• Name this Load job CONTACT_TABLE_LOAD.
• Click on the Browse button to navigate to the target table to load the data.

• Take the default Type Database and Host of SQL Server Sample and click OK.

• Click Finish to open the Related Loader.

• Under Extracted Data navigate to the recently run extract. 
• Click Browse.

• Select the CONTACT_TABLE_EXTRACT job from the list.
• Click OK.

• From the Overview click on the Objects tab across the bottom of this section.

Here is listed the Source and Target table names. The Source is derived from information in the Extract file, and the target defaults to this same name.

• Right click on Target Name and select Change Target Object Name.

• Change the target table name to CONTACT_TABLE_DIS. 

This table does not exist and will be created during the Load job. 

• Click OK.

• Click on the Field Mappings tab along the bottom of this section.

If the source and target tables are different column mapping can be done here.

• Click on the DDL tab along the bottom of this section.

• Click on the Options tab along the bottom of this section.

Listed are options including for Commits and Discards. 

• Click the Blue execute button in the top right.

• Look in the Console tab for execution information.
• Double click the Console tab to maximize this view.

Here you will see number of rows loaded.

• Double click the Console tab to minimize this view. 
• Close the Load job by clicking the X in the tab. 
• Click Save to save this job in the repository.

• Select the Host Explorer tab.

• Right click on Hosts
• Select Configure
• Click Host Types and check SQLServer Databases.
• Click Apply and Close.

• Expand Hosts
• Expand SQL Server Sample by clicking on the arrow.
• Expand Microsoft SQL Server. 

(If it cannot be expanded, right click on Microsoft SQL Server and select Add Filter. Type "dbo" in lowercase for the Schema and * in the table field.)

• Double click on the CONTACT_TABLE.

• Click Run to open the table in an Edit session

• Double click on CONTACT_TABLE_DIS.

• Click Run to open this table in another tab within the Edit session.

• Place your cursor on the second tab and drag to the right and drop to see the two tables side by side.

Notice the gray line that pops up during the drag.

You can now see the Contact Name column in both tables and see how the Composite rule replaced the original First and Last Names with new values. Note Row 9 had a Middle Name in the original data and that is retained in the new table.

• Scroll to the right for each table to view the Telephone Number columns.

• Close both tables by clicking on the X within the tabs.
• Close all open tabs.