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


IBM JMS Interface DevelopmentIBM Certification Exams, Stopping and Starting the Queue Manager Building the AUDOperations.jar- IBM JMS Interface Development IBM FileNet 5.5.x Workflow
0 Comments

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 compiled and exported as a jar file

Figure 3-238The Eclipse IDE Java ➤ JAR file export wizard is selected

Figure 3-239The options for exporting the Java JAR file are selected

Figure 3-240The AUDOperations.jardesc file is saved to the Project Source folder

Figure 3-241The Browse command is used to select the path for the .jardesc file

Figure 3-242The MANIFEST.MF generation option is selected and defined for save

Figure 3-243The AUDOperations jar file is exported with compile warnings

The status of the AUDOperations.jar build is shown in Listing 3-11.

An Eclipse AUDOperations.jardesc file was created.

<?xml version=”1.0″ encoding=”UTF-8″ standalone=”no”?>

<jardesc>

<jar path=”/root/eclipse/java-2021-12/eclipse/AUDOperations.jar”/>

<options buildIfNeeded=”true” compress=”true” descriptionLocation=”/AUD_CIOps/src/AUDOperations.jardesc” exportErrors=”true” exportWarnings=”true” includeDirectoryEntries=”false” overwrite=”false” saveDescription=”true” storeRefactorings=”false” useSourceFolders=”false”/>

<storedRefactorings deprecationInfo=”true” structuralOnly=”false”/>

<selectedProjects/>

<manifest generateManifest=”true” manifestLocation=”/AUD_CIOps/bin/MANIFEST.MF” manifestVersion=”1.0″ reuseManifest=”false” saveManifest=”true” usesManifest=”true”>

<sealing sealJar=”false”>

<packagesToSeal/>

<packagesToUnSeal/>

</sealing>

</manifest>

<selectedElements exportClassFiles=”true” exportJavaFiles=”false” exportOutputFolder=”false”>

<file path=”/AUD_CIOps/.classpath”/>

<file path=”/AUD_CIOps/.project”/>

<javaElement handleIdentifier=”=AUD_CIOps/src&lt;com.ibm.filenet.ps.ciops”/>

</selectedElements>

</jardesc>

Listing 3-11The AUDOperations.jardesc file list

Rebuilding the AUDOperations.jar File

To rebuild the AUDOperations.jar file, we can make use of the AUDOperations.jardesc file we created.

NoteMake a backup (if required) of the previous AUDOperations.jar first!

Right-click this AUDOperations.jardesc file in the Project area AUD_CIOPS and select Create Jar from the menu, then click Yes when prompted to overwrite the existing AUDOperations.jar file. (Click OK.)

Copy the compressed AUDOperations.jar file to the Installs folder for import as a System Component Integrator step.

The configuration.properties file contains the following (used for the JUnit test harness).

AUDOperationsTest.CEWsiUrl=http://ecmukdemo6:9080/wsi/FNCEWS40MTOM/

AUDOperationsTest.ConnectionPointName=CP1

AUDOperationsTest.EmailFrom=alan.bluck@asbsoftware.co.uk

AUDOperationsTest.EmailTemplatePath=/AUDIT_TEST/AC.pdf

AUDOperationsTest.EmailTo= alan.bluck@asbsoftware.co.uk

AUDOperationsTest.ObjectstoreName=OS2

AUDOperationsTest.Password=filenet

AUDOperationsTest.TestFolderName=/AUDIT_TEST

AUDOperationsTest.Username=Alan

AUDOperationsTest.WaspLocation=/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/localhostNode01Cell/FileNetEngine.ear/cews.war/WEB-INF/classes/com/filenet/engine/wsi

AUDOperationsTest.WsiJaasConfigFile=/opt/IBM/ECMClient/configure/CE_API/config/jaas.conf.WSI

Listing 3-12The latest configuration.properties JUnit test file parameters


Leave a Reply

Your email address will not be published. Required fields are marked *