VERIFIED SOLUTION i

Manually execute EngageOne Generate using EngageOne Server Incident Archive resources

Operating System: Windows Server
Steps:

1. Run EngageOne Generate outside of EngageOne® Server and add diagnostics such as Trace options and <Message> Diagnostics.
2. Open the Incident Archive logs in EngageOne® Server located in <EngageOneServer install location>\active-drive\incident-archive\dca\daily folder and open the incident log.
3. Example of the Incident log is shown below:

Incident Archive error logs: 
Error occurred during document compostion!

 StartUp Command Lines: 
C:\PB\batch\bin\doc1gen\win\doc1gen , mode=D , MMGX , <server>CommandQueue=HOST:localhost:58142 , ecp=C:\PB\batch\bin\doc1gen\win/doc1ecp
 Server Commands: 
S 1528985072218
X <Input>MiniDeviceHip='\\PB\active-drive2\2018-06-06\1924.hip'
X <Input>MiniDeviceHip='\\PB\active-drive2\2018-06-06\2365.hip'
X <Input>CampaignMessages='\\PB\active-drive2\2018-06-08\2790.him'
X <Input>CampaignMessages='\\PB\active-drive2\2018-06-08\2792.him'
X <RunTime>ComponentPath=C:\PB\batch\cache\Trigger-1212383141834632\activeContents
X <NeutralOutput>TempFileMask=C:\Users\PB\Local\Temp\onhtmp1528985072221_64_21_%1
X <Advanced>OutputMetricsFile=C:\Users\PB\Temp\journal1210923712471438-21-1.xml
X <EngageOne>ManifestFile=C:\PB\batch\cache\Trigger-1212383141834632\hips\2807.xml
N 'C:\PB\batch\cache\Trigger-1212383141834632\hips\1234.hip'
F C:\Users\PB\Temp\journal1210923712471438-21-1.xml
I 0 C:\PB\batch\cache\Trigger-1212383141834632\records\record-0.xml
P P PBPDF=C:\PB\Output\ManualRun.pdf

3. Copy the “MiniDeviceHIP” resources from the daily folder into a separate sub-directory in the local machine.
4. Copy the Message HIM “CampaignMessage” resources from the daily folder into a separate sub-directory in the local machine.
5. Copy the Active content resources from the daily folder into a separate sub-directory in the local machine.
6. Specify the “<Output> Label in OPS File by using the 'P' parameter from the above Incident logs.
7. Specify the “<Input>DataInput” value in OPS File by using the 'I' parameter from the above Incident logs.
8. The Main Publication (Template) HIP e.g 1234.hip by using the 'N' parameter from the above Incident logs needs to be referenced when running EngageOne Generate via the command line.
9. To run EngageOne Generate, Open Command prompt and browse to <EngageOneDesigner install location>\Designer\Client type doc1gen 1234.hip ops=ops.ops
10. OPS File example: 

<Input>
MinideviceHIP=miniHIP\*.HIP
CampaignMessages=miniHIM\*.HIM
DataInput=record-1.xml                           ;Note this section is used to specify the input files to be read at runtime.

<RunTime>
ComponentPath=ActiveContent\             ;Note the Active Contents are the numbered files without an extension.

<EngageOne>
ManifestFile=2807.xml                            ;Note this section is used to reference the manifest file created from the Incident Archive.

<Output>
PBPDF=ManualRun.pdf                          ;Note this section is used to specify the name of the output datastream file.

<trace>
Outputfile=trace.txt
TraceLevel=complete
supportTrace=on                                     ;Note this section creates the trace output file and trace level controls the amount of output information.

<NeutralOutput>
TempFileMask=temp_ManualRun_%1  ;Note the Generate Neutral Output Temporary file used to hold the intermediate composed Neutral pages before being written to final neutral ONH file.

<Messages>
MessageProcessing=Yes                       ;Note this allows details for message rejections to be output. The default is No.

<Advanced>
OutputMetricsFile=ManualRun-Metrics.xml   ;Note the intermediate EngageOne XML file for the intermediate “EngageOne Structured Journal” output before being written to the final Generate Output file.

11. Review the trace logs.
UPDATED:  October 2, 2018