I've been trying to get the dispatcher run on our test system.
tried to install all three components but were somewhat overwhelmed by the setup preferences neccecary to fill out.
Hope I did the setup correct, but it's likely I missed something.
We are working with a 4-tier TCRS 11.3 setup.
I modified the installation trough TEM to install Dispatcher.
There are two main issue right now:
Other issue that seems like an indication of some configuration errors is that I can't shutdown the dispatcher client (both service and cmd). Shows an error and wont stop and/or start without a server reboot.
What i've done so far (after installing dispatcher):
I'm stuck and do'nt know what to look for right now.
Attached you'll find the log files and screenshots.
Solved! Go to Solution.
Problem1: To see the translation menu in RAC, install feature "Dispatcher Client for Rich Client" via TEM.
Problem 2: Make sure the access rule for your dispatcher user is created as mentioned in doc (see below)
After installation, you must add a rule to the access rule tree permitting the translation service proxy user to update attributes of a DispatcherRequest object. If this access rule is not created correctly, the dispatcher client reports errors.
Log on to the Teamcenter rich client as a system administrator.
Open Access Manager.
In Access Manager, add the following rule to the rule tree under Has Class (POM_application_object)→Working:
Condition =Has Class
ACL Name =DispatcherRequest
ACE Type of Accessor =User
ACE ID of Accessor =DC-Proxy-User-ID
ACE Privilege =Write
ACE Privilege Value =Grant
ACE Privilege =Delete
ACE Privilege Value =Grant
This rule applies only to the standard Access Manager rule tree. If custom rules are specified for the installation, your custom rules must be modified to provide the equivalent access of this rule. The DC-Proxy-User must be the same user that was specified during installation using the Teamcenter Environment Manager installation tool.
Thanks for the fast reply!
I have "Dispatcher Client for Rich Client" installed already.
Access rule was automatically created on install.
Do you have any other directions?
Okey, finally got a chance to continue this implementation and added the ACL.
Started the CMD dispatcher services.
Retried starting translation trough CMD.
Result is a different error stating the dataset could not be found.
D:\PLM\TCRS112\tc_menu>DISPATCHER_create_rqst -i="1000051" -r="-" -dn="Translate Test001" -dt="MS WordX" -dv=2 -pr=1 -pn="SIEMENS" -tn="tozipfile" DISPATCHER_create_rqst ( May 15 2017 16:39:53 ) version number NOT specified, using latest Could not find dataset <TranslateTest001>, version 2 Dispatcher create request FAILED ( -4 )
Searched for any info on error -4 but did not manage to find it.
Tried to not specify a dataset version but same error, got the current version form the dataset properties found in the RAC. Perhaps still a ACL problem?
This may not be the problem, but you have a space in your -dt argument; "MS WordX". While this is the display name of the dataset type its real name is "MSWordX".
That did the trick!
Got a new zip dataset in the item revision containing the docx.
Will create a different thread to get the Translate button in RAC visible.
To inform others, no need for new thread, found the solution here
It's a TC RapidStart installation, so the command is disabled by default.
To enable it in the RAC, open the "Command suppression" application:
After setting the "Translate..." command to "Show", it shows up:
And it works!