ACCEPTED SOLUTION
Accepted Solutions
This is doable.
But we need to know how the publishing job is being triggered.
Does this pertain to ALL publishing jobs including a manual create representation?
I wrote some code that would publish from a workflow and return the results of the job.
In our case we needed to get the published PDF and copy it across the network to a folder but the same technique would apply here. The code still needed to determine if the publishing was successful or not.
In your case you need to go one more step. You need to determine WHY it was unsuccessful. The CAD Worker did not start.
To get to that level of granularity you need to read the log. This is the same log displayed in the WVS Job Monitor.
If you need to republish ONLY if the CAD Worker does not start you can read the log that is displayed in WVS Job Monitor.
Here's an image of a Windchill shell that has run code that gets the publishing job's log and writes the log to the shell.
This is from the same publishing job log shown above. Note the html tags.
If the log contains the error in question such as:
"No worker can be started"
or
"Error, did not find available worker of type"
or whatever you want to trigger the republish then the code republishes the Representable.
BTW I also coded to republish only once. So, only two tries to publish (one initial publish and one republish). You don’t want to get into an infinite loop.
Hopefully this helps.
David
This is doable.
But we need to know how the publishing job is being triggered.
Does this pertain to ALL publishing jobs including a manual create representation?
I wrote some code that would publish from a workflow and return the results of the job.
In our case we needed to get the published PDF and copy it across the network to a folder but the same technique would apply here. The code still needed to determine if the publishing was successful or not.
In your case you need to go one more step. You need to determine WHY it was unsuccessful. The CAD Worker did not start.
To get to that level of granularity you need to read the log. This is the same log displayed in the WVS Job Monitor.
If you need to republish ONLY if the CAD Worker does not start you can read the log that is displayed in WVS Job Monitor.
Here's an image of a Windchill shell that has run code that gets the publishing job's log and writes the log to the shell.
This is from the same publishing job log shown above. Note the html tags.
If the log contains the error in question such as:
"No worker can be started"
or
"Error, did not find available worker of type"
or whatever you want to trigger the republish then the code republishes the Representable.
BTW I also coded to republish only once. So, only two tries to publish (one initial publish and one republish). You don’t want to get into an infinite loop.
Hopefully this helps.
David
As a follow-up to this I wrote a utility that will detect when a publishing job fails.
I wrote it such that ONLY if the failure was due to the CAD Worker not starting a workflow Task is sent to the Admin and the user who initiated the publishing job. Could certainly key of whatever but that seemed to be what this thread is concerned with.
The workflow is about as simple as it gets.
The Task get renamed to include the identity of the object that failed to publish.
This was done to make it easily identified from the Home page.
This task includes the WVS Job Monitor log as well as a link to the Representable object that filed publishing.
This was done to make it as quick and easy as possible to identify the problem.
Some food for thought maybe?
David
