Adding Business Logic
At run time, you can add your own logic for each activity.
- For a synchronous activity, add your business logic in the [ActivityName]SynchronousActivity class.
- For an asynchronous activity, add your business logic in the [ActivityName]AsynchronousActivity class.
- For a process starter activity or a signal-in activity, add your business logic in the [ActivityName]EventSource class.
Before you begin
Ensure that you have generated a palette and activities of the plug-in, as described in Defining a Palette and Adding and Configuring Activities.
- Procedure
- In the parent TIBCO Business Studio with the running platform selected, click .
- In the "Create, manage, and run configurations" dialog box, double-click
Eclipse Application in the left panel to create a new Eclipse application.
You can also use an existing Eclipse application.
- Click Debug to launch a child TIBCO Business Studio configured with the bw-runtime platform.
- In the child TIBCO Business Studio, click
to import the model and runtime bundles and features:
- In the Select dialog box, expand the General folder and select Existing Projects into Workspace. Click Next.
- In the Import Projects dialog box, click Browse to locate the project folder that contains the plug-in project.
- Click Deselect All, and then select the runtime and model bundles and features. Click Finish.
The runtime and model bundles are loaded in the child TIBCO Business Studio.
- Click the runtime bundle, and then click the
src folder to add the business logic.
Plain Ordinary Java Object (POJO) class is supported for implementation of source code. You can assign values to POJO classes, and output is automatically generated.
See Runtime Class Specification and Runtime Bundle for more details.
- If you have specified multiple faults when configuring activities at design time, BusinessWorks Plug-in Development Kit only generates the first fault schema at run time. You have to add other faults manually at run time:
- Expand the runtime bundle and find the src folder.
- Expand the com.company_name.bw.palette.palette_name.runtime.fault package.
- In the com.company_name.bw.palette.palette_name.runtime.fault package, make a copy of the fault_nameFault.java file.
- Open the copied file and build the other faults by using the private <N, A> N constructErrData () method and the public QName getFaultElementQName() method.
