Use this task to set the ActivitySession deployment attributes for an enterprise bean to enable the bean to participate in an ActivitySession context and support ActivitySession-based operations.
Why and when to perform this task
You can configure the deployment attributes of an application by using the Deployment Descriptor Editor of WebSphere Studio Application Developer or the Assembly Toolkit.
This topic describes the use of the Assembly Toolkit to configure the ActivitySession deployment attributes. These attributes are in addition to other deployment attributes, like Load at (which specifies when the bean loads its state from the database). This task description assumes that you have an EAR file, which contains an application enterprise bean that can be deployed in WebSphere Application Server. For more details about using the Assembly Toolkit, see Assembling applications with the Assembly Toolkit. For more detail about the fields in the Assembly Toolkit, and for associated task help, see the help information provided with the toolkit.
To set the ActivitySession deployment attributes for an enterprise bean, use the Assembly Toolkit to complete the following steps:
Steps for this task
Note: Ensure that you set the target server as WBI Server Foundation v5.1.
For example, to change attributes of an existing application, use the import wizard to import the EAR file into the Assembly Toolkit. To start the import wizard:
An enterprise bean with this activation policy is activated and passivated as follows:
The ActivityRequiredException exception is javax.rmi.RemoteException.
Any received ActivitySession context is suspended for the duration of the method and resumed after the method ends. The container starts a new ActivitySession before method dispatch and completes it after the method ends.
How the container manages the ActivitySession boundaries when delegating a method invocation depends on both the ActivitySession kind attribute, set here, and the Transaction attribute attribute, as described inConfiguring transactional deployment attributes using the Assembly Toolkit. For more detail about the relationship between these two properties, see Combining transaction and ActivitySession container policies.
Important: Use Run On Server for unit testing only. Assembly Server Toolkit controls the WebSphere Application Server installation and, when an application is published remotely, the Toolkit overwrites the server configuration file for that server. Do not use on production servers.
What to do next
After assembling your application, use a systems management tool to deploy the EAR file onto the application server that is to run the application; for example, using the administrative console as described in Deploying and managing applications.