Process classes are Controller classes used to implement all the process flows by calling the business objects. Basically, they are used to implement any batch, background or interactive process in the system. We also use EJBs (Stateless Session Beans) for the process classes as well to implement the process functionality.
What does this section cover?
Creating the Process Classes
In this example, we are going to implement a process class that will create a number of installed items. All process classes should be placed under com.crm.process.* named packages, extend either com.crm.process.CRMProcess or one of its subclasses and follow this naming convention: CRMProcess<classname>Bean.java. Classes created for processes handled by the scheduler should extend com.crm.process.CRMProcessRunBean.
Implementing the Process Flow
To implement the desired process flow we add the corresponding methods.
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(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
For more information on creating custom process classes, go to Customise Existing Business Logic.
To start implementing the view layer, go to Developing the View layer