You can use the WebLogic Server Administration Console to view, modify, and when necessary persist deployment descriptor elements. Some descriptor element changes take place dynamically at run time without requiring the resource adapter to be redeployed. Other descriptor elements require redeployment after changes are made. To use the WebLogic Server Administration Console to configure a resource adapter, open Deployments and click the name of the deployed resource adapter.
Use the Configuration tab to change the configuration of the resource adapter and the other tabs to control, test, or monitor the resource adapter. Dynamic reconfigurable configuration properties are described in Section 5. At run time, after you update the dynamically configurable properties on any of these adapter component beans, you must update the adapter to put changes into effect. Updating the adapter is a relatively lightweight operation during which WebLogic Server modifies the run-time bean instances without interfering with active connection pools or admin objects that do not have configuration updates.
You do not need to update the adapter immediately. However, changes to properties on adapter component beans do not go into effect unless the beans are dynamically updated or the resource adapter is restarted. The resource adapter should be designed carefully with regard to support for dynamic changes to its properties during run time. Depending on the services provided by the resource adapter, it might be critically important that some properties should never be reconfigured when the adapter is running; for example, the listen address and port number of a resource adapter used for the EIS connection any reconfiguration of those properties should require the adapter to be shut down and restarted.
WebLogic Server does not impose any requirements on an adapter component bean with regard to whether specific properties may or may not be designated as dynamically reconfigurable. It is entirely for the adapter developer to decide which adapter component beans support dynamic update and which do not. Using the WebLogic Server Administration Console, you can modify the following configuration parameters on those beans dynamically, without requiring the resource adapter to be redeployed:.
If a resource adapter is deployed in WebLogic Server without a weblogic-ra. However, this automatically generated weblogic-ra. WebLogic Server instead generates internal data structures that correspond to default information in the weblogic-ra. For a 1. The Link-Ref mechanism was introduced in the 8. However, the Link-Ref mechanism is still supported in this release for 1. To use the Link-Ref mechanism, use the ra-link-ref element in your resource adapter's weblogic-ra.
The deprecated and optional ra-link-ref element allows you to associate multiple deployed resource adapters with a single deployed resource adapter. In other words, it allows you to link reuse resources already configured in a base resource adapter to another resource adapter, modifying only a subset of attributes. The ra-link-ref element enables you to avoid - where possible - duplicating resources such as classes, JARs, image files, and so on. Any values defined in the base resource adapter deployment are inherited by the linked resource adapter, unless otherwise specified in the ra-link-ref element.
If you use the optional ra-link-ref element, you must provide either all or none of the values in the pool-params element. The pool-params element values are not partially inherited by the linked resource adapter from the base resource adapter. Assign the max-capacity element the value of 0 zero. This allows the linked resource adapter to inherit its pool-params element values from the base resource adapter.
Assign the max-capacity element any value other than 0 zero. The linked resource adapter will inherit no values from the base resource adapter. If you choose this option, you must specify all of the pool-params element values for the linked resource adapter. For further instructions on editing the weblogic-ra. The bean validation configuration file can be specified for a resource adapter module regardless of whether the resource adapter is deployed independently as a standalone RAR or as part of an enterprise application EAR.
If no bean validation configuration file is specified for an adapter module, WebLogic Server uses a default bean validation configuration to validate the resource adapter module. For these approaches, the contract specifies a listener mechanism to notify the resource adapter that the thread has completed its operation. The resource adapter can also specify the execution context for the thread, and the work management contract controls the context in which the thread executes.
The work management contract between the application server and a resource adapter enables a resource adapter to do a task, such as communicating with the EIS or delivering messages, by delivering Work instances for execution. A generic work context mechanism also enables an application server to support message inflow and delivery schemes. It also provides a richer contextual Work execution environment to the resource adapter while still maintaining control over concurrent behavior in a managed environment.
The Connector Architecture defines the following outbound contracts, system-level contracts between an application server and an EIS that enable outbound connectivity to an EIS. The connection management contract supports connection pooling, a technique that enhances application performance and scalability. Connection pooling is transparent to the application, which simply obtains a connection to the EIS.
The transaction management contract extends the connection management contract and provides support for management of both local and XA transactions. A local transaction is limited in scope to a single EIS system, and the EIS resource manager itself manages such a transaction.
An XA transaction or global transaction can span multiple resource managers. This form of transaction requires transaction coordination by an external transaction manager, typically bundled with an application server.
The resource adapter can also specify the execution context for the thread, and the work management contract controls the context in which the thread executes. The work management contract between the application server and a resource adapter enables a resource adapter to do a task, such as communicating with the EIS or delivering messages, by delivering Work instances for execution. A generic work context contract enables a resource adapter to control the contexts in which the Work instances that it submits are executed by the application server's WorkManager.
A generic work context mechanism also enables an application server to support message inflow and delivery schemes. It also provides a richer contextual Work execution environment to the resource adapter while still maintaining control over concurrent behavior in a managed environment. The Connector Architecture defines the following outbound contracts, system-level contracts between an application server and an EIS that enable outbound connectivity to an EIS.
The connection management contract supports connection pooling, a technique that enhances application performance and scalability. Connection pooling is transparent to the application, which simply obtains a connection to the EIS. The transaction management contract extends the connection management contract and provides support for management of both local and XA transactions. A local transaction is limited in scope to a single EIS system, and the EIS resource manager itself manages such a transaction.
An XA transaction or global transaction can span multiple resource managers. This form of transaction requires transaction coordination by an external transaction manager, typically bundled with an application server. However, to avoid introducing errors, use a tool designed for XML editing. You can also edit most elements of the files using the WebLogic Administration Console.
When editing or creating XML deployment files, it is critical to include the correct schema header for each deployment file. The header refers to the location and version of the schema for the deployment descriptor. Although this header references an external URL at java.
Table shows the entire schema headers for the ra. XML files with incorrect header information may yield error messages similar to the following, when used with a utility that parses the XML such as ejbc :. The contents and arrangement of elements in your deployment descriptor files must conform to the schema for each file you use. The following links provide the public schema locations for deployment descriptor files used with WebLogic Server:.
You can use the Administration Console to view, modify, and when necessary persist deployment descriptor elements. Some descriptor element changes take place dynamically at runtime without requiring the resource adapter to be redeployed. Other descriptor elements require redeployment after changes are made.
To use the Administration Console to configure a resource adapter, open Deployments and click the name of the deployed resource adapter. Use the Configuration tab to change the configuration of the resource adapter and the other tabs to control, test, or monitor the resource adapter.
For information about using the Administration Console, see Configure Resource Adapter Properties in the console help. Using the Administration Console, you can modify the following weblogic-ra.
0コメント