dispatcher_create_rqst

Provides the ability to create a dispatcher request using command line arguments. Note This utility is a sample utility to be used with datasets. It limits the number of translation arguments to 3. If you need more functionality, you can write a custom ITK using the sample code located in DISP_ROOT\DispatcherClient\sample\utilities\dispatcher_create_rqst_itk_main.cxx. Syntax The syntax of the dispatcher_create_rqst utility has two forms: dispatcher_create_rqst -i=item-ID -r=revision-ID [-rn=relation] -dn=dataset-name [-dv=dataset-version-number] -dt=dataset-type-name -pr= 1 | 2 | 3] -pn=translator-provider-name -tn=service-name -ty=type-string [-ta1=translation-argument1 [-ta2=translation-argument2 [-ta3=translation-argument3]]] [-u=user-id -p=password | -pf=password-file -g=group] -verbose | -debug] OR dispatcher_create_rqst -f=path-name -dt=dataset-type-name -pr= 1 | 2 | 3] -pn=service-provider-name -tn=service-name -ty=type-string [-u=user-id -p=password | -pf=password-file -g=group] -verbose | -debug] Arguments Note If a relation is not specified, the IMAN_specification relation is used. -u Specifies the user ID. This is generally a user with administration privileges. Note If Security Services single sign-on (SSO) is enabled for your server, the -u and -p arguments are authenticated externally through SSO rather than being authenticated against the Teamcenter database. If you do not supply these arguments, the utility attempts to join an existing SSO session. If no session is found, you are prompted to enter a user ID and password. -p Specifies the password. This argument is mutually exclusive with the -pf argument. -pf Specifies the password file. For more information about managing password files, see Manage password files. This argument is mutually exclusive with the -p argument. -g Specifies the group associated with the user. If used without a value, the user's default group is assumed. -i Specifies the item. -r Specifies the item revision. -rn Specifies the relation name to be used to find the dataset for the given item revision. This argument is optional. If the relation is not specified, the value of IMAN_specification is used. -dn Specifies the dataset name. This argument is optional. -dv Specifies the dataset version number. This argument is optional. If no version number is specified, the specific version that is the latest is used. If a version number is specified, and the version is the latest, only the latest version is used. Consider the following example. A dataset has the following versions: Dataset with version number Description 006122/000 This is the latest version and also the same as version 2. 006122/000:1 This is version one. 006122/000:2 This is version two and the latest specific version. Consider the following values of the –dv argument: -dv=1: The version 006122/000:1 is used. -dv=2: The version 006122/000 is used because when you specify the latest version in the –dv argument the latest version is used. No value specified: The version 006122/000:2 is used because when you do not specify a version in the –dv argument, the latest specific version is used. -dt Specifies the type of the dataset to be translated -pr Specifies the translation priority. Accepted values are 1, 2, or 3 corresponding to low, medium and high translation scheduler priority. -pn Specifies the name of the translator provider, for example, Siemens. -tn Specifies the name of the translator service, for example ideastojt. -ty Specifies the type name, for example COMMANDLINE. -verbose Provides additional information. This argument is optional. -f Specifies an input file used to create one or more dispatcher requests. This argument is used in lieu of the item, revision, relation name, dataset name, and dataset version arguments. This argument is optional. The format for the input file is as follows: Copy ,,[relation name],[dataset name], [version number] Note Commas are required. -ta1 Specifies a translation argument. Environment As specified in Setting up a Teamcenter command-line environment. Files As specified in Log files produced by Teamcenter. Restrictions None. Examples To create a dispatcher request for the latest version of the I-deas part dataset related to the Block/A item revision, enter the following command on a single line: Copy dispatcher_create_rqst -u=user_name -p=user_name -g=dba -i=Block -r=A -dt=IdeasPart -pr=2 -pn=Siemens -tn=ideastojt -ty=COMMAND_LINE To create a dispatcher request for version 2 of the Block/A item revision, enter the following command on a single line: Copy dispatcher_create_rqst -u=user_name -p=user_name -g=dba -i=Block -r=A -dv=2 -dt=IdeasPart -pr=2 -pn=Siemens -tn=ideastojt -ty=COMMAND_LINE To create two Siemens Digital Industries Software ideastojt dispatcher requests with a priority of 2: One request for the latest version of the Block dataset, an IdeasPart or IdeasAssembly type dataset, associated with item revision Block/A by an IMAN_specification relation; One for the latest version of the Asm dataset, an IdeasPart or IdeasAssembly type dataset associated with item revision Asm/A by an IMAN_specification relation, enter the following command on a single line: Copy dispatcher_create_rqst -u=user_name -p=user_name -g=dba -f=ctrl -dt=IdeasPart,IdeasAssembly -pr=2 -pn-Siemens -tn=ideastojt -ty=COMMAND_LINE The lines in the input file are: Copy Block,A,,Block, Asm,A,,Asm, Note All parts in the file are subject to the same translation, because the translator is specified on the command line. Related Topics Dispatcher ─ Deployment and Administration