This study will demonstrate how Unity Director 14.00 User Interface handles the initial configuration and setup activities users will face when starting to work with this product.
Managed systems - Teradata Database systems managed by Unity Director
Within an EDW user has created a data loading application that needs to be made highly available via Unity Director. There are two sites (local and remote) that host servers connected in HA pair mode: 2 Unity Director servers, 2 managed database systems and monitored by 2 clustered Viewpoint systems.
Configuration and initial steps use case
Purpose: User wants to review initial configuration and start using Unity Director software to manage the data loading application.
Assumptions: Unity Director is already installed in the user environment. Unity Director is sold as staged software installed on Teradata Managed server. Teradata systems Managed by Director existed prior to installing Unity Director and their network configuration was added to Unity Director servers host files.
Review default Unity Director Configuration – look for initial installation architecture, make sure that everything is configured correctly and Unity Director System is ready to start being used.
Start by examining Unity Director Components architecture on Dashboard Components tab – this view shows that users connect to Unity Director TDPID and the requests are routed to database systems. It also presents state and details popup windows for all Unity Director Components (sequencer, dispatcher, watchdog, endpoints and repository) for each site.
View default global settings in Configuration Portlet
Create Data Dictionary for tables representing user application using Unity Director Configuration portlet.
1. Navigate to DD tab and click on plus icon:
2. Click on the newly created dictionary, give it a name, go through 4 steps within the wizard either using step buttons (from 1 to 4) or navigating via ‘back’ and ‘next’ buttons:
a. Scan databases to discover objects on the systems:
b. Select databases used in the application:
c. Scan objects within the selected databases:
d. Select objects that comprise the application:
3. Deploy Data Dictionary:
4. Observe application’s tables in the Deployed Dictionary area:
Please note that users can have multiple dictionaries. Objects are not shared by multiple dictionaries. Deployed Dictionary is a collection of all objects contained in deployed dictionaries. Also if user kept the ‘Auto-select on object scan’ global setting the application will automatically select objects that are identical across Teradata systems.
5. Dealing with errors:
In some cases due to different reasons user has to perform an analysis of errors related to DD objects. Not all errors prevent user from deploying a DD. A typical critical error is related to object definition mismatch across multiple systems. DD tool allows user to view errors and force rescan of objects in question.
6. Dealing with locks:
Unity Director performs its own lock management. It reads locking information during scan and uses this knowledge to process user requests. Users can alter default locking behavior for object that are equal across systems.
7. Exporting and importing:
In some cases, for example when moving from one version to another or when migrating from a different environment user needs to save a DD in the temporary location and put it back. DD tool provides export and import functionality. For importing it analyses which dictionary objects are being imported and allows mapping objects to other existing dictionaries.
Activate Teradata systems on Components view if they are not already active
Review and set routing rules
Step 5: Start application load scripts and begin monitoring Unity Director
In this last step user may go to command line and start a BTEQ or TPT script that would be loading data into managed Teradata systems via Unity Director. After the script has started go to Dashboard Data Synchronization view to check if tables are active. Then go to Sessions view to see sessions created by the load script.
After completing those steps users are ready to start using Unity Director Viewpoint User Interface to monitor and manage their data loads. This study shows how simple it is to get an application up and running with new Unity Director 14.00 product.
I have completed the initial setup , but whenever I am trying to connect to a Teradata system via unity, it throws the following error, I am not sure if I made anything wrong during the setup. All my hosts files are exactly same on all ecosystem components such as viewpoint, unity director, primary and standby td systems.
Error: 3748: Parcel kind or ordering is invalid.
What log file have you found this error in? It may be related to security configuration. Are you using LDAP or IP filters? How do you access the system (i.e. BTEQ etc) and what version of client are you using?