Creating the Process Classes

In this example, we are going to implement a process class that will create a number of installed items. . The first thing to do is to create an EJB that will handle our process class. In order to create our class we must first decide the name of the package to place it in. Based on the business structure, the respective packages should be created. Based on CRM.COM naming conventions, all process classes are stored in the All process classes should be placed under com.crm.process.* named packages, extend either com.crm.process package. Based on the module we are implementing, further packages are then created in here.

In this case, we will create the package .CRMProcess or one of its subclasses  and follow this naming convention: CRMProcess<entityname>Bean.java. Classes created for processes handled by the scheduler should extend com.crm.process.inventory that will contain the module's process classes, and create the CRMProcessInstalledItemBean.java class. CRMProcessRunBean.

Note that on EJB creation, we also specify the super class of the class we are creating, depending on the business logic of our class. In this case we select the com.crm.process.CRMProcess as the super class.

...

Implementing the Process Flow

To implement the desired process flow we add the corresponding methods.

    /**
     * Creates a number of installed items.
     * 
     * @param numberOfInstalledItems - the number of installed items to construct
     * @return a list of installed items
     * @throws Exception
     */
    public ArrayList<CRMDO> createInstalledItems(Integer numberOfInstalledItems) throws Exception {
    	
    	ArrayList<CRMDO> installedItems = new ArrayList<CRMDO>();
    	
    	for (int i=0; i<numberOfInstalledItems; i++)
    	{
    		CRMDOInstalledItem installedItem = (CRMDOInstalledItem)installedItemBean.construct();
    		
    		installedItem.setSerialNumber(newGuid());
    		
    		installedItem = (CRMDOInstalledItem)installedItemBean.validateAndSave(installedItem);
    		
    		installedItems.add(installedItem);
    	}
    	
    	return installedItems;
    }
  

Note that our method does not contain any complex business logic. In short, it executes a loop and for each iteration, it uses the business logic provided by the installedItemBean  installedItemBean(com.crm.businessobject.inventory.CRMBOInstalledItemBean) business object and sets a new serial number on the data objects returned. When the loop completes, it returns a list of the installed item data objects created.

EJB Binding File

In order for the EJB class to be bound to the WebSphere Application Server, it must be specified in the ibm-ejb-jar-bnd.xml binding file 

<ejb-jar-bnd>
    ...
	<!-- CRMProcess > inventory -->
	<session name="CRMProcessInstalledItemBean" simple-binding-name="ejb/CRMProcessInstalledItem" />
	...
</ejb-jar-bnd>

For more information on creating custom process classes, go to Customize existing business logic. 

To start implementing the view layer, go to Developing the View layer