Properties for EAServer Component Generator: Components tab
Description
Specify properties for the component selected in the Objects
to deploy box.
Options
Objects to deploy
Select the check box next to the name of a custom class user
object to specify that you want to deploy it. Select the object
to set its properties in the Properties for selected object group
box.
Component name
Displays the name of the component selected in the Specify
properties for list box.
Component type
Select a component type from the drop-down list:
|
Type |
Description |
|---|---|
|
Standard |
The default. Selecting Standard enables |
|
Shared |
Select to create a component that will |
|
Service |
Select to create a component that performs |
Transaction support
Select how the component supports transactions:
|
Level |
Description |
|---|---|
|
Not Supported |
The component’s methods never |
|
Supports Transaction |
The component can execute in the context |
|
Requires Transaction |
The component always executes in a transaction. When |
|
Requires New Transaction |
Whenever the component is instantiated, |
Roles required
If you want to associate one or more security roles with the component
selected in the Set properties for box, type the names of the roles, one
on each line.
Automatic demarcation/deactivation
Specifies whether the component is wrapped by an EJB stateful
session bean to allow stateful behavior. Select the check box to
have EAServer wrap the component with a stateless session bean. In
business methods, stateful CORBA components must call the transaction state
primitive methods to indicate the session state. For example, completeWork or rollbackWork ends
the session and deactivates the component instance. Selecting the
check box sets the component’s tx_vote property
to false.
Instance pooling
Check to specify that an instance of the component is always
pooled after each client use. When this box is checked, the CanBePooled
event is not triggered for the component.
If you do not check the Automatic Demarcation/Deactivation
check box, instances are pooled when the component calls the SetComplete
(or SetAbort) method of the TransactionServer context object. If
you check the Automatic Demarcation/Deactivation check
box, instances are pooled after each method invocation.
Do not check the Support Instance Pooling box if you want
to specify whether the instance should be pooled using the CanBePooled
event. When this box is not checked, the CanBePooled event is triggered
after each client use.
Thread safe
Check to set the com.sybase.jaguar.component.thread.safe property
to TRUE. This property displays in EAServer Manager as the Concurrency
option on the Instances tab of the component’s Properties
dialog box. The preferred value for this property depends on whether
the component is a standard, shared, or service component.
Each instance of a PowerBuilder component executes in its
own session, and each session can only support one thread of execution.
Therefore a single PowerBuilder component instance cannot simultaneously
execute multiple client requests.
For standard components, this box is checked by default, allowing
multiple instances of a component to handle client requests, thereby
improving performance.
For shared components, this box is disabled and is not checked,
because only one instance of the component should be active at any
time and therefore only one thread can be executed.
For service components, the box is not checked by default,
but becomes checked if you change Create Instances to 2 or more.
Remote debugging
Check to enable remote debugging of this component. Checking
this box does not add any specific debugging information to the component.
Component timeout
Specify how long an active component instance can remain idle
between method calls before being automatically deactivated. The default
is 0, which means the instance is not automatically deactivated.
When specifying timeouts, a resolution of 5 seconds is recommended.
Service instances
Specify how many instances of a service component can be active.