|
|
After you select your task file and application server, then you must set your deployment options for your application. Deployment options do not differ depending on your application server type.
You can also edit existing deployment options from this page, by selecting the packaged application you want to modify and then choosing Edit on the main J2EE Session EJB Deployments page. When you select Edit, existing settings are displayed and can be modified within the wizard user interface.
The task file, application server name, and state management mode are the options you set on the Task File and Application Server page of the New /Edit J2EE Session EJBs Wizard.
Deployment Options
EJB Name: The session EJB name defaults to the name of the task file + state mode + EJB that you selected in the Task File and Application Server page of the wizard, for example, AccountQueryStatefulEJB.
 |
Use Java class naming restrictions when configuring your deployment options. The names you choose for your package, EJB, and connector names determine how you will access the bean from your application. The default names follow the necessary restrictions and will work. |
EJB Description (optional): An optional description of the session EJB. Once entered, this description is available from your application server-specific location.
EJB Package Name: The name used for the deployed package containing the necessary classes to run your application. This name must be different than the class names it contains and different from the EJB name.
EJB JNDI Name: The JNDI (Java Naming and Directory Interfaces) name uniquely identifies the EJB. The name defaults to the EJB default name, in our example, AccountQueryStatefulEJB.
You may want to prepend 'ejb/', 'ejb-' or 'ejb.', (depending on the requirements of your application server), to indicate a sub-section of the JNDI tree.
Connector Name: The J2EE connector name defaults to the name of the task file + connector you selected in the Task File and Application Server page of the wizard. For example, AccountQueryConnector.
Connector Description (optional): An optional description of the connector. Once entered, this description is available from your application server-specific location.
Connector JNDI Name: Set the JNDI name to the location under which you will access the resource adapter ConnectionFactory. The JNDI name uniquely identifies the connector.
You may want to prepend 'eis/', 'eis-' or 'ejb.', (depending on the requirements of your application server), to indicate a sub-section of the JNDI tree.
|
What is a ConnectionFactory? A ConnectionFactory is an object used for creating a resource manager connection and is stored at the JNDI location. |
The JNDI name is the name that your connector uses to reference the ConnectionFactory in a manner specific to the application server you are using.
 |
|
 |
Session EJB Errors |
|
Deploying J2EE Session EJBs |
|
Integrating your J2EE Session EJB with an Application |
|
Using J2EE Architecture |
 |
Synapta Services Builder for CICS Manager Help Links |
 |