Creating a Workflow Subscription on a New Audit Report Document Event- IBM JMS Interface Development IBM FileNet 5.5.x Workflow

The Target Object store, OS2, with a Workflow Definition document class (AUD_JMSMessage.pep file) is used to run the Workflow we created, after a new Audit Report document is created in ... Read MoreRead More

0 Comments

IBM Process Designer Component Queue Configuration- IBM JMS Interface Development IBM FileNet 5.5.x Workflow

After the parameters for the AUD_Operations have been configured using the IBM FileNet Content Engine acce web administration tool, the Workflow Component Queues have to be configured using the IBM ... Read MoreRead More

0 Comments

FileNet Workflow System Component AUDOperations.jar Deployment- IBM JMS Interface Development IBM FileNet 5.5.x Workflow-2

a) In the object store navigation pane, click the Administrative ➤ Workflow System ➤ Isolated Regions folder and click the isolated region that you want to modify. Figure 3-259The New ... Read MoreRead More

0 Comments

FileNet Workflow System Component AUDOperations.jar Deployment- IBM JMS Interface Development IBM FileNet 5.5.x Workflow-1

Create a new Component Queue, AUD_Operations, in the Workflow System: a) Log in to the FileNet Administration Console for Content Engine (acce) web application configuration tool. Figure 3-244The acce administration ... Read MoreRead More

0 Comments

Building the AUDOperations.jar- IBM JMS Interface Development IBM FileNet 5.5.x Workflow

Next, we need to export the Java program in the AUDOperations.jar file with the exposed methods we wish to call from our IBM Process Designer Workflow. Figure 3-237The AUDOperations.java is ... Read MoreRead More

0 Comments

AUDOperations Rebuild and Deploy .jar: Final Prebuild Test- IBM JMS Interface Development IBM FileNet 5.5.x Workflow

The following Test output was output after adding the log4j.xml and log4j.dtd files from the Audit Event Handlers Java project we covered in Chapter 2. Configuration property file search order: ... Read MoreRead More

0 Comments

Second Run of the AUDOperationsTest.java JUnit for JMS Messaging- IBM JMS Interface Development IBM FileNet 5.5.x Workflow-3

// define the name of the QueueManager //String qManager = “wasadm”; // and define the name of the Queue //String qName = “AUDQAR”; // Put the message to the queue ... Read MoreRead More

0 Comments

Second Run of the AUDOperationsTest.java JUnit for JMS Messaging- IBM JMS Interface Development IBM FileNet 5.5.x Workflow-2

public VWAttachment[] getFolderDocuments(VWAttachment folderAttachment ) throws Exception { Folder folder = getFolderFromAttachment(folderAttachment); DocumentSet containedDocuments = getContainedDocuments(folder); Iterator<?> iterator = containedDocuments.iterator(); ArrayList<VWAttachment> containedDocumentList = new ArrayList<VWAttachment>(); while ( iterator.hasNext() ) { ... Read MoreRead More

0 Comments

Second Run of the AUDOperationsTest.java JUnit for JMS Messaging- IBM JMS Interface Development IBM FileNet 5.5.x Workflow-1

The second run of the JUnit test is more successful. The console screen output in Figure 3-232 is from the Eclipse IDE JUnit run of the AUDOperationsTest.java Class. This shows ... Read MoreRead More

0 Comments

Error Log Location- IBM JMS Interface Development IBM FileNet 5.5.x Workflow

The error logs can be located on the ecmukdemo6 IBM MQ series 9.2.5 server in the following location. Figure 3-195The error logs are found located in the /var/mqm/errors subfolder com.ibm.mq.jms.MQQueue ... Read MoreRead More

0 Comments