Integrating FileNet P8 with the J2EE messaging infrastructure

justforregister

• Select the Security tab and add the users as shown in                    Figure 16.

                             
Figure 16. Security
               

justforregister

• Click OK and remember to commit your changes.

             You have now finished configuring the component queue on FileNet P8.
            
Configuring the EJB transport
             If the user needs to use the JMS component queue, complete the following                steps to create a                component manager in the process task manager with EJB transport.
               

• Modify the                        <APPCLIENT_INSTALL_DIR>/properties/sas.client.props file                        to identify the CE host CE boostrap port.
• Set com.ibm.CORBA.loginSource to none as shown in Listing 1.                        
  
  Listing 1. Setting com.ibm.CORBA.loginSource to none
  

  com.ibm.CORBA.securityServerHost=servername com.ibm.CORBA.securityServerPort=2809 com.ibm.CORBA.loginTimeout=300 com.ibm.CORBA.loginSource=none

• Find component manager under Application Engine Node.
• Right-click and select New on the menu, as shown in                            Figure 17.

justforregister

Figure 17. Process task                    manager
                               
               

• Select the region and click OK.
• In the General Tab of the new component manager, remove  *                        from the Queues field, replace it with the new JMSQueue, and click                            Apply, as shown in Figure 18.
• Enter the content engine URL as iiop://servername:2809 and                        complete the other fields, as shown in Figure 18.

justforregister

Figure 18. Component manager
                               
                 

• Select the Required Libraries tab and add entries for the .jar                    files, as shown in Figure 19.

justforregister

Figure 19. Required libraries
                                     
                     

• Remove the wasp.jar from the list.
• Add <APPCLIENT_INSTALL_DIR>\properties
• Add all                        the .jar files in the <APPCLIENT_INSTALL_DIR>\lib directory and                        its sub directories.
• Add all the .jar files in the                        <APPCLIENT_INSTALL_DIR>
• Select the Advanced tab and enter the fields as shown                             in Listing 2.

justforregister

• 
  Listing 2. Advanced tab entries
  

  Registry Port : 32771 Event Port : 32773 JNDI Initial Context Factory : com.ibm.websphere.naming.WsnInitialContextFactory JRE Parameters : [see Listing 3]

• Set the JRE parameters to define the                        following system properties:                        
  
  Listing 3. JRE parameters
  

  filenet.naming.provider.url=iiop://<JMSServer>:<JMSServerBootstrap>      (from serverindex.xml) com.ibm.CORBA.ConfigURL=<APPCLIENT_INSTALL_DIR>/properties/sas.client.props com.ibm.SSL.ConfigURL=<APPCLIENT_INSTALL_DIR>/properties/ssl.client.props java.ext.dirs=<APPCLIENT_INSTALL_DIR>/java/jre/lib/ext; <APPCLIENT_INSTALL_DIR>/lib; <APPCLIENT_INSTALL_DIR>/lib/WMQ/java/lib;<APPCLIENT_INSTALL_DIR>/properties;      <APPCLIENT_INSTALL_DIR>/plugins

            Listing 4 shows an example of what your .jar files might look like.

justforregister

Listing 4. Example .jar files

-Dwasp.location=C:/Program Files/FileNet/AE/Router/../CE_API/wsi -Djava.naming.provider.url=iiop://<jmserver>:<jmsserverbootstrap>      (from serverindex.xml) (such as iiop://<servername>:2809 ) -Dserver.root=C:\Program Files\IBM\WebSphere\AppServer -Dcom.ibm.CORBA.loginSource=none -Dcom.ibm.CORBA.ConfigURL=C:\Program      Files\IBM\WebSphere\AppServer\profiles\AppSrv01\properties\sas.client.props -Duser.install.root=C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01 -Xbootclasspath/p:C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmorb.jar; C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\properties -Djava.ext.dirs=C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ext; C:\Program Files\IBM\WebSphere\AppServer\java\lib; C:\Program Files\IBM\WebSphere\AppServer\classes; C:\Program Files\IBM\WebSphere\AppServer\lib; C:\Program Files\IBM\WebSphere\AppServer\installedChannels; C:\Program Files\IBM\WebSphere\AppServer\lib\ext; C:\Program Files\IBM\WebSphere\AppServer\web\help; C:\Program    Files\IBM\WebSphere\AppServer\deploytool\itp\plugins\com.ibm.etools.ejbdeploy\runtime; C:\Program Files\IBM\WebSphere\AppServer\plugins; C:\Program Files\IBM\WebSphere\AppServer\lib\WMQ\java\lib Preferred JRE path bin : C:\Program Files\IBM\WebSphere\AppServer\java\jre\bin

                                      Select the Java Security tab and add the entries in Listing                        5.                        

Listing 5. Java Security tab entries

java.security.auth.login.config : C:/Program      Files/FileNet/AE/Router/taskman.login.config.websphere java.security.policy : C:/Program Files/FileNet/AE/Router/taskman.policy

justforregister

• The contents of C:/Program Files/FileNet/AE/Router/taskman.login.config.websphere                        are shown in Listing 6.                       
  
  Listing 6. C:/Program Files/FileNet/AE/Router/taskman.login.config.websphere
  

  CELogin {   filenet.vw.server.VWLoginModule required routerurl="region1";   com.filenet.wcm.toolkit.server.operations.util.CELoginModule   required credTag=Clear; }; FileNetP8 {      com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy      required delegate=com.ibm.ws.security.common.auth.module.WSLoginModuleImpl; };

You are now finished configuring the component manager with EJB transport.

justforregister

Understanding JMS                message format and related code
             Now for the most interesting part of this article, it is time to get your hands dirty                with the code. After you write a message driven bean (MDB) and while                deploying on the WebSphere Application Server, you need to provide the JNDI name of the                activation specification that you created under Configuring                    JMS on WebSphere. You do this to activate the MDB once                the process engine tries to execute the component step. The component                integrator service manager posts the actual message, which is part of the                application engine (AE) talking to the component adapter, such as the JMS                adapter.
           The JMS adapter uses the JNDI for the queue connection                factory and for the queue, as shown in Figure 14. The               JMS posts messages to the queue. The process task manager, the component                integrator service manager, and the JMS adapter are part of the                application engine, as shown in Figure 20.
                                    
Figure 20. Sequence diagram for posting a message on queue
                    

justforregister

In JMS, you can post a message to a queue using                ObjectMessage, MapMessage, TextMessage ,                    StreamMessage, or ByteMessage. At first glance,                 ObjectMessage and MapMessage look like the most likely candidates that the JMS                adapter would use to send messages. But a closer look suggests that the                ObjectMessage format can go out of reckoning because the developer needs                to implement a serializable class, which would complicate things for the                MDB developer.                Also notice that the definition of each operation is similar to an                individual method call.
                So you might think the better choice would be MapMessage, because you can make the parameter name into a key and you can make the value for the parameter                be the value for the key. But, TextMessageis actually the better choice, because you can use a self-descriptiveXML format, which defines everything about the contents of the message,as shown in Listing 7.
                    
Listing 7. XML format of text message
<StepElement LaunchedBy="Administrator"
LaunchedOn="20090324T153400Z"
ReceivedOn="20090324T153401Z"
Description=""  WOBName="*"  WOBNumber="582B46B0D1203D4F981F4F2A707963FF"
WorkflowName="CruiseBooking"
WorkflowNumber="582B46B0D1203D4F981F4F2A707963FF"       
WorkClassName="CruiseBooking"
Tag="*"        
RosterName="DefaultRoster"
QueueName="JMSQueue"
CurrentQueueName="JMSQueue"
Operati
CurrentMapName="Workflow"
Excepti
Excepti
IsTracker="false"
Overdue="NotOverdue"
CanReassign="false"
CanViewStatus="false"
CanViewHistory="false"
CanReturnToSource="false">
       
<Originator>
   <Value DistinguishedName="CN=Administrator,CN=Users,DC=ibm,DC=idmdev,DC=com"
                DisplayName="Administrator"
                GUID="S-1-5-21-3351868238-2367661336-251463525-500"
                DomainName="dc=ibm,dc=idmdev,dc=com"
                    IsGroup="false">administrator</Value>

</Originator>
<Responses/>
<Parameters>
   <Parameter Name="cruiseID" AuthoredName="cruiseID" Description="" Type="int"
      IsSystemParameter="false" Mode="in" IsArray="false">
                <Values>
                        <Value>51</Value>
                </Values>
   </Parameter>
   <Parameter Name="orderID" AuthoredName="orderID" Description=""
            Type="int"        IsSystemParameter="false" Mode="in" IsArray="false">
                <Values>
                        <Value>52</Value>
                </Values>
   </Parameter>
   <Parameter Name="passengerName" AuthoredName="passengerName" Description=""
     Type="string" IsSystemParameter="false" Mode="in" IsArray="false">
                <Values>
                <Value>hellodude</Value>
                </Values>
   </Parameter>
   <Parameter Name="passengerID" AuthoredName="passengerID"        Description=""
                Type="int" IsSystemParameter="false"        Mode="in" IsArray="false">
                <Values>
                        <Value>53</Value>
                </Values>
   </Parameter>
</Parameters>
       
</StepElement>