Starting the PDFRendering Monitor Service

To enable PDF rendering of checked-in documents via the Adlib PDF Enterprise server, Business Administrators must install and run the PDF Rendering Monitoring Service to ensure that submitted PDF rendering jobs are completing successfully. The PDF Rendering Monitoring Service can run on the same server as 3DSpace, 3DPassport, and other services, or it can run on a different physical or virtual server.

See Also
Installing PDF Rendering Service
  1. Depending on whether you are using Linux or Windows, the steps are similar:
    • For Windows, open the startup_pdfr.bat script located in PDFRenderingMonitor/win_b64/code/command/startup_pdfr.bat.
    • For Linux, open the startup_pdfr.sh script located in PDFRenderingMonitor/linux_a64/code/command/startup_pdfr.sh, then follow these steps:
  2. Run either of the following commands depending upon your Operating System: 
    • PDFRenderingMonitor/linux_a64/code/command/startup_pdfr.sh <USER> ‘<CONTEXT>’<SERVICENAME> <SERVICESECRET> <PDFR_URL>
      or 
    • PDFRenderingMonitor/win_b64code/command/startup_pdfr.bat <USER> “<CONTEXT>” <SERVICENAME> <SERVICESECRET> <PDFR_URL>

    where:

    • <USER> is the username of the Document Center Administrator or the Leader.
    • <CONTEXT> is the 'Document Center Administrator.MyCompany.Global' or 'VPLMProjectLeader.MyCompany.Default'. If using Windows, insert "" around Context role.
    • <SERVICENAME> is the name for the service when the input is through 3DPassport.
    • <SERVICESECRET> is issued by 3DPassport.
    • <PDFR_URL> is the URL of the local PDFR TommEE Web Service.

    You should see a response message similar to the following captured in the catalina.out logs found at location: <PDFRenderingMonitor InstallDirectory>/<OS Name>/code/tomee/logs. 

    Has been redirected. Last Redirect URL: https://<hostname>/3DSpace/?ticket=ST-64-zywytVolfQoA0Je9oa5f-cas
Successfully initialized Adlib Job Management Service1
Initialize
Settings.MetadataListcom.dassault_systemes.enovia.jobmanagementservice.
ArrayOfMetadata@3c9bfddc   
com.dassault_systemes.enovia.jobmanagementservice.ProcessRulesResponse2@56aaaecd
Successfully intialized as an Adlib component
< Processing the Jobs :: >
< Processing the Jobs :: >
    The < Processing the Jobs :: > message will repeat on a 3 second interval.

    The output it will provide directly in the command window will be 

    -bash-4.1$ ./PDFRenderingMonitor/linux_a64/code/command/startup_pdfr.sh docmanager 'Document Center Administrator.MyCompany.GLOBAL' PDFRService de99c2b5-c09c-4c01-8a2c-ac72c0b9314a http://localhost:9080

Starting Up PDFR Tomcat .. it appears not to be running
Using CATALINA_BASE:   /RTV/R421/PDFRenderingMonitor/linux_a64/code/tomee
Using CATALINA_HOME:   /RTV/R421/PDFRenderingMonitor/linux_a64/code/tomee
Using CATALINA_TMPDIR: /RTV/R421/PDFRenderingMonitor/linux_a64/code/tomee/temp
Using JRE_HOME:        /RTV/R421/PDFRenderingMonitor/linux_a64/code/serverjre/jre
Using CLASSPATH:       /RTV/R421/PDFRenderingMonitor/linux_a64/code/tomee/bin/
bootstrap.jar:/RTV/R421/PDFRenderingMonitor/linux_a64/code/tomee/bin/tomcat-juli.jar 
Using CATALINA_PID:    /RTV/R421/PDFRenderingMonitor/linux_a64/code/tomee/tomcat.pid
Tomcat started.
Now Waiting for Tomcat to start.....
Now Starting via PDFRIgnition main()
PDFR Service is not currently Running, so trying to start it
PDFRIgnition:  Returned Status PDFR Start Service Call: Started
PDFRIgnition:  ---> EXPECTED STATUS: Started
PDFRIgnition:  Returned Status PDFR Second Service Call: Running
PDFRIgnition:  ---> EXPECTED STATUS: Running
---->>>>>PDFRIgnition Final Reported Status: Running

  3. To enable tracing, make the following change in the PDF Rendering Monitoring Service script:

    • On Linux: Uncomment the following line: export TRACES=on
    • On Windows: Change set TRACES=off to set TRACES=on because it is configured off by default.

    The scripts are located:

    • On Linux: ../PDFRenderingMonitor/linux_a64/code/command/startup_pdfr.sh
    • On Windows: ..\PDFRenderingMonitor\win_b64\code\command\startup_pdfr.bat

  4. To stop the monitoring process and tomcat service, you can run a shutdown script located at
    • On Linux: ../PDFRenderingMonitor/linux_a64/code/command/shutdown_pdfr.sh
    • On Windows: ..\PDFRenderingMonitor\win_b64\code\command\shutdown_pdfr.bat

When the PDF Monitoring Service successfully authenticates with the 3DEXPERIENCE server and also with Adlib PDF Enterprise server, it logs the number of jobs it has received from the 3DSpace server. It also polls the Adlib PDF Enterprise server for the current status of each of those jobs. It coordinates the release of both successful and failed PDF rendering jobs with the Adlib PDF Enterprise server. For successful PDF rendering jobs, it submits a check-in request for the generated PDF file to the 3DSpace server. For failed PDF rendering jobs, it notifies the 3DSpace server of the failure.

Note: If the PDF Rendering Monitoring service is not running, but PDF rendering is enabled, any successfully generated PDF files will not be checked in by the 3DSpace server and users will not be notified if the PDF file failed to be generated.