Dispatcher Client

CMM supports Teamcenter Dispatcher Client (formerly called Translation Services) to allow you to distribute the migration process to a server pool. For information on installing and configuring the Dispatcher Client, see the Teamcenter Help. Dispatcher Client is supported only by CMM, not by NXM. The following configuration options are added to CMM to support Dispatcher Client.

• You can submit CMM tasks to Teamcenter Client Dispatcher. This functionality is available both interactively using the CMM menu and in batch mode using CMMBatch.
• You can submit single or multiple items in a Teamcenter Client Dispatcher translation session using the CMM menu or CMMBatch.
• Thousands of items can be queued simultaneously.
• Migrations are performed on server hardware, instead of user desktop computers.
• You can achieve consistent results from all migrations, because CMM option files are used on the server machine. This prevents users from using unique options on their local machines.
• This is the most efficient way to perform a large-scale migration. When using the Dispatcher Client, you should plan your migration carefully. Because of the power of running large numbers of migrations simultaneously with administrative ownership on a server, you should plan your migration in detail.
• Plan your migration to avoid collisions of the same items being accessed by multiple migrations.
• Using the Dispatcher Client requires a higher level of knowledge of Teamcenter. Configuration guide

Configuration guide Setting up CMM for Dispatcher Client After CMM has been installed, there are additional setup steps that are required. You must set the Teamcenter preferences and setup access control for the dispatcher (client) proxy user. By default, this user is dcproxy. Teamcenter preferences for Dispatcher Client There are several preferences that you must set in Teamcenter to use CMM with the Dispatcher Client. You can do this manually or use Teamcenter functionality to import the preferences as described in the Teamcenter documentation. The preferences should be imported as site-wide and should be merged with existing preferences. The file to import is \Dispatcher\ETSCMMPreference_merge.xml. Setting access control If you choose to have the migrated data owned by the original CAD user, you must create the correct access rules. These rules allow CMM to change the NX part's dataset owner to the CAD user, instead of keeping it as the dispatcher(client) proxy user. If you use a workflow process that involves statuses, you may need to make sure that these rules are above your status rules in the rule tree.

• From Access Manager, add the following rule to the rule tree under Has Class: (POM_application_object)→Working Condition = Has Class Value = DispatcherRequest ACL Name = DispatcherRequest ACE Type of Accessor = User ACE ID of Accessor = ETS Proxy User ID ACE Privilege = Write ACE Privilege Value = Grant ACE Privilege = Delete ACE Privilege Value = Grant ACE Privilege = Change Ownership ACE Privilege Value = Grant
• Add ETS Proxy user ID to (POM_application_object)→Working: Condition = Has Class Value = POM_application_object ACL Name = Working ACE ID of Accessor = ETS Proxy User ID ACE Privilege = Write ACE Privilege Value = Grant ACE Privilege = Delete ACE Privilege Value = Grant ACE Privilege = Change Ownership ACE Privilege Value = Grant Configuration guide

Configuration guide Running more than one CMM translator module on a single machine To enable running more than one CMM translator module on a single machine, ensure the Teamcenter setting IIOP_SERVER_ACTIVATION is set to PER_CLIENT. This is done through the Teamcenter Environment Manager (TEM). Note that for some source CAD systems, you need to allow multiple sessions of the CAD system to run simultaneously on the same machine. Other CAD systems do not support running multiple, simultaneous sessions on one machine. Running Dispatcher and the CMM translator on different machines Many users choose to have the Dispatcher process running on a different machine than where CMM is installed. In this case, the automated CMM install process cannot update all of the Dispatcher configurations. If you choose to have the Dispatcher running on a different machine from where the CMM modules run, perform the following: 1. Copy the CMMETSTaskPrep.jar file from the CMM installation directory to the %DISPATCHER_ROOT%\DispatcherClient\lib directory. Ensure you choose the correct CMMETSTaskPrep.jar file for your Teamcenter release. The .jar files are found in the \dispatcher directory. 2. Modify the %DISPATCHER_ROOT%\DispatcherClient\conf\Service.properties file to add ETSCMMService at the end of the first import line in the file. Using different settings for Dispatcher translations In the Dispatcher Client, the CMM migration services are called:

• cmmcadtonx_direct
• cmmcadtonx1_direct
• cmmcadtonx2_direct
• cmmcadtonx3_direct While they all use the same CMM services to perform data migration, they can be setup to use different option files and different translation priorities. Each translator has two preference settings that control its behavior. The option that corresponds to the translator is numbered using the same number as the translator. To control which option file is used by each translator, set the following Teamcenter options:
• CMM_cadtonx_optionFile
• CMM_cadtonx1_optionFile
• CMM_cadtonx2_optionFile
• CMM_cadtonx3_optionFile Similarly, the translation priority and allowed dataset types can be set for each translator using the following Teamcenter options:
• ETS.DATASETTYPES.SIEMENS.CMMCADTONX_DIRECT
• ETS.DATASETTYPES.SIEMENS.CMMCADTONX1_DIRECT
• ETS.DATASETTYPES.SIEMENS.CMMCADTONX2_DIRECT
• ETS.DATASETTYPES.SIEMENS.CMMCADTONX3_DIRECT Configuration guide

Configuration guide I-deas specific setup for Dispatcher I-deas has an 80 character limit for the path and file name. Since CMM uses I-deas in its migration process, the path to the Dispatcher staging location must be much shorter than 80 characters. We recommend that you limit it to 10 characters at the most. CATIA V4 setup for Dispatcher CATIA V4 data uses .model files. These model files may represent a large number of individual parts. The Convert Model to Single Part setting in CMM allows you to control whether the .model files get migrated as a single part or are separated into individual NX parts for each part in the model file. If you choose to separate the CATIA model into individual NX parts, large numbers of new items could be created. By default, all of these items are put into the user's Newstuff folder. This is particularly important when you are running many migrations at the same time through the Dispatcher Client. When Teamcenter tries to place very large numbers of items from different processes into the Newstuff folder, a performance bottleneck can occur. To avoid this, create the following Teamcenter preferences as User preferences for the Dispatcher Client migration user: WsolnsertNoSelectionsPref=3 WsolnsertSelectionsPref=4 Submitting translations to Dispatcher There are several ways to submit translations to Dispatcher. Teamcenter provides the ability to submit translations through workflows or from the Translation menu in the Teamcenter portal. These two methods let you submit one dataset at a time to the translator. If the dataset has children, such as drawings and assemblies, those children are also migrated. CMM provides the Submit to Dispatcher command in both the Teamcenter CMM menu and through CMMBatch. The advantage of using the Submit to Dispatcher command is that you can submit multiple datasets to a single Dispatcher translation. This provides significant throughput improvement because CMM services are only started one time for each translation session. For example, if you want to translate 100 parts, using Submit to Dispatcher groups all 100 parts into a single translation, so the services are only started once. Using the Translation menu in the Teamcenter portal to submit 100 parts creates 100 different translation sessions. Performance enhancements When Dispatcher is installed, a Translation menu is added to let you submit translations. You can use this menu to submit one item per translation session by selecting the dataset to translate. If you select a part, this means that only one part is migrated in the session. Since CMM starts up several services for each session, that may take as long as two minutes on some machines, so migrating one part at a time may add two minutes to each part migration. When considering thousands of parts, this can add up to a large amount of time. One performance improvement is to submit large numbers of items to a single Dispatcher session using the CMM command Submit to Dispatcher, or by using the CMMBatch –submit option. When you submit using the CMM menu, you can multi-select items at the item revision level. You don't need to drill down to the dataset. Then you can use the Submit to Dispatcher command to migrate them all in one Dispatcher session. Configuration guide

Configuration guide When you submit using CMMBatch, you need to create a selection file that contains the list of items to migrate. If you have this list already, it can be converted to the required format. You also need to create a login file. Examples of these files and their formats can be created using the CMM menu command Save Selection for Batch. You need to edit the login file to include the user's password. It can then be referenced from CMMBatch. You should be able to group 500 or more parts into one Dispatcher session using this method instead of using the Dispatcher Translation command, which limits you to one per session. You may want to start small and scale up to identify a good number for each session. When you migrate many assemblies or drawings through different Dispatcher sessions, you may run into collisions because the assemblies or drawings use the same child parts. It is important that you understand the hierarchy of your data to minimize this occurrence. In addition, you may find that it is a best practice to migrate all of your parts first. When you do this, you can set the CMM option Skip Check Out Reused Status to limit the reused items that are checked out during a migration. If you set the value to ++PendingRepair, no previously migrated items are checked out. However, there could be possible problems when using this method where people are using these items and updating them during your migration process. If you don't control access to items that are being migrated and allow them to be changed during the migration process, you may get unexpected results. Understanding your results Using Dispatcher to do your migrations can generate large amounts of data very quickly. You need to be prepared to review these results and act on needed re-migrations or repairs. All of the CMM tools for reporting can be used for migrations through Dispatcher. However, the Report Statistics tool may be the most helpful in understanding where you need to start further investigation of your results. The Reporting→Report Statistics command on the CMM menu generates a spreadsheet-ready, tab-delimited file that lists the results for each top level item migrated during a selected time period. You can quickly learn the migration directory, migration status, and top-level results of a migration. This enables you to determine the migration sessions that need further investigation. You can then use the more detailed CMM reporting tools. Configuration guide

Configuration guide