Presently I am working Translation Service of Teamcenter. Though to share my learning experience with you people. Translation service comes as a Dispatcher Service under teamcenter installation. Translation service is nothing but to translate one file format to other. For example Doc to PDF. The broader task any translation are as follows.
a) Extract Data from Teamcenter.
b) Execute Translation.
c) Load translated result to teamcenter.
Hence the Dispatcher Service of teamcenter has three main components.
1) Scheduler
2) Module
3) Dispatcher Client
There is one more component called Dispatcher Admin which is basically used for Admin activity and it is optional component. Each of the above three component run independently and can be run as service or in console. Each component can be run in different server. As name suggests scheduler manage the whole framework by interacting between Module and Dispatcher client. Dispatcher Client component basically manage extract and loading of data. Module does actual translation. The below diagram depict the Translation Frame work.
Dispatcher Client is the front end of Dispatcher Framework which basically interacts with Teamcenter through SOA for translation request. Teamcenter required to be configuring through ETS preferences for new translation services and object type on which this service is valid. Once the request is received to Dispatcher Client, it processes the request and put all extracted files required to be translated in to directory called staging directory. Staging directory is required to be configured during Dispatcher Service Installation. In staging directory a unique subfolder is created for each request by Dispatcher client based on Task ID generated during user request in Teamcenter. Once Dispatcher client completes the extract, it inform scheduler for translation processing. Scheduler in turn informs Module to start processing the task. Module translate the file and put the output in staging directory. Once completed schedule ping the Dispacher client which load translated file back to Teamcenter.
Siemens PLM provide lot of out of box translation service which required to be make active. In next blog I will provide more detail about each component and there configuration.
See Also :
Configuring Translator
Customizing Translation Services
a) Extract Data from Teamcenter.
b) Execute Translation.
c) Load translated result to teamcenter.
Hence the Dispatcher Service of teamcenter has three main components.
1) Scheduler
2) Module
3) Dispatcher Client
There is one more component called Dispatcher Admin which is basically used for Admin activity and it is optional component. Each of the above three component run independently and can be run as service or in console. Each component can be run in different server. As name suggests scheduler manage the whole framework by interacting between Module and Dispatcher client. Dispatcher Client component basically manage extract and loading of data. Module does actual translation. The below diagram depict the Translation Frame work.
Dispatcher Client is the front end of Dispatcher Framework which basically interacts with Teamcenter through SOA for translation request. Teamcenter required to be configuring through ETS preferences for new translation services and object type on which this service is valid. Once the request is received to Dispatcher Client, it processes the request and put all extracted files required to be translated in to directory called staging directory. Staging directory is required to be configured during Dispatcher Service Installation. In staging directory a unique subfolder is created for each request by Dispatcher client based on Task ID generated during user request in Teamcenter. Once Dispatcher client completes the extract, it inform scheduler for translation processing. Scheduler in turn informs Module to start processing the task. Module translate the file and put the output in staging directory. Once completed schedule ping the Dispacher client which load translated file back to Teamcenter.
Siemens PLM provide lot of out of box translation service which required to be make active. In next blog I will provide more detail about each component and there configuration.
See Also :
Configuring Translator
Customizing Translation Services
Thanks Manoj Sir,its really interesting and good way to Transfer your experience to make our knowledge increase .
ReplyDeleteHello Sir,
ReplyDeleteHow can we display a JPEG image in the TcR&A report. JPG image file is available in Teamcenter as a Dataset under some custom Item object i look for Generating Report Through TcRA 8.3
Actually i want to Generating Report Through TcRA 8.3 (Teamcenter Reporting & Analytics) on the connection of TcUA 8.3 ( Teamcenter Unified )
Example :-
1. In TcUA 8.3 There is Business Object called " Item "
2. Item have Dataset ( .JPG pic ) which is from out of box of Teamcenter
Requirement :-
I need to Generating Report Through TcRA 8.3 of That Item which include .JPEG pic also
i Have used dataset.UID and type should be IMAGE as Attribute from TcR&A ,But its not work.
so please help me out from this Problem
Thanks & Best Regards
Awanish kumar
Yes i am totally agreed with this article and i just want say that this article is very nice and very informative article.I will make sure to be reading your blog more. You made a good point but I can't help but wonder, what about the other side? !!!!!!THANKS!!!!!!
ReplyDeletehttp://www.profi-fachuebersetzung.de/
Hello Sir,
ReplyDeleteI am not able to login to TCAR 2007 SR1M mapper, the login page itself is not opening. In server log file it is throwing some error as:
64488552 [AJPRequestHandler-RMICallHandler-6-Thread-376] FATAL apiCategory - Exception
com.eqtechnologic.eqube.eQDbException: Exception Occurred While Executing The Query
( DbError is 942:ORA-00942: table or view does not exist )
Query is : SELECT * FROM FEATURE_SUPPORT
at com.eqtechnologic.eqube.s.a(Unknown Source)
at com.eqtechnologic.eqube.s$a.do(Unknown Source)
at com.eqtechnologic.eqube.s$a.run(Unknown Source)
16/06/15 08:29:53 com.eqtechnologic.eqube.eQDbException: Exception Occurred While Executing The Query
( DbError is 942:ORA-00942: table or view does not exist )
Query is : SELECT * FROM FEATURE_SUPPORT
16/06/15 08:29:53 at com.eqtechnologic.eqube.s.a(Unknown Source)
16/06/15 08:29:53 at com.eqtechnologic.eqube.s$a.do(Unknown Source)
16/06/15 08:29:53 at com.eqtechnologic.eqube.s$a.run(Unknown Source)
64488552 [AJPRequestHandler-RMICallHandler-6] ERROR apiCategory - Other Exception occurred while executing query.
16/06/15 08:29:53
***EMS Not Enabled****
com.eqtechnologic.eqube.eQDbException: Exception Occurred While Executing The Query
( DbError is 942:ORA-00942: table or view does not exist )
Query is : SELECT * FROM FEATURE_SUPPORT
16/06/15 08:29:53 ***
Error while initializing Mapper
Our DB team have restarted the servers recently and we also restarted the TCAR and license servers after that, issue is persisting.
Appreciate, if you could highlight some clues to rectify this issue.
Thanks and Regards
Asgar Ali
Really a good article. much informative.
ReplyDeleteNice post it is very helpful for me I have some important information in your blog its very helpful for me.
ReplyDeleteArabic Translation Services
Thanks for your great info about the topic of blog commenting. It’s really helpful for me. Thanks for sharing these great insights.
ReplyDeleteVoice Over Artist In Delhi | Translation Services In Pune | Indian Languages Translator | English To Kannada Translation |Certified Translation Services In Pune | Translation Companies In Hyderabad