weblogic-jws-config.xml Configuration File

The weblogic-jws-config file allows you to configure runtime parameters of web services, both on the development server and production servers. This file is used by JwsCompile when preparing WebLogic Workshop projects for deployment to a production server.

# Elements

The following xml elements may appear in weblogic-jws-config.xml

<config>

The <config> element is the root element of the weblogic-jws-config.xml file. All other elements are children or grandchilden of <config>.

<protocol> (global)

The global <protocol> element appears as the immediate child of the <config> element. The global <protocol> element defines the default exposure protocol for your web application. Unless otherwise specified in the jws-specific <protocol> element, web resources within the web application, including web services, will be exposed on the protocol specified. Possible values are http or https.

<protocol> (jws-specific)

The jws-specific <protocol> element appears as the immediate child of the <jws> element. The jws-specific <protocol> element overrides the value of global <protocol> element. Possible values are http or https.

<hostname>

The <hostname> element specifies the name of the machine where your web application will be deployed.

<http-port>

The <http-port> element specifies which port should be used for http traffic.

<https-port>

The <https-port> element specifies which port should be used for https traffic.

<jws>

The <jws> tag takes a pair of <class-name> / <protocol> elements as children. For example,

<jws>

<class-name>HelloWorld</class-name>

<protocol>http</protocol>

</jws>

<jws>

<class-name>HelloWorldSecure</class-name>

<protocol>https</protocol>

</jws>

Use the <jws>, <class-name> and <protocol> elements to specify the transport protocol for individual web services in a web application.

<class-name>

The <class-name> element is used in conjunction with the <jws> and <protocol> elements to specify the transport protocols of individual web services with a web application. Possible values are the names of web services within the web application. For example, to specify a web service Foo.jws, use <class-name>Foo</class-name>. Values of the <class-name> element are case sensitive.

<transaction-isolation-level>

The <transaction-isolation-level> tag is used to specify the transaction isolation level of the EJB's that back JWS's. The value will of <transaction-isolation-level> be mapped to the EJBs' deployment descriptors during a build. Default settings are TRANSACTION_READ_COMMITTED for a production build (compiling an EAR for deployment) and TRANSACTION_SERIALIZABLE for a non-production build (compiling to run in Test View). Valid values are

TRANSACTION_READ_COMMITTED

TRANSACTION_READ_UNCOMMITTED

TRANSACTION_REPEATABLE_READ

TRANSACTION_SERIALIZABLE

<ejb-concurrency-strategy>

The <ejb-concurrency-strategy> element is used to specify the ejb concurrency strategy of the EJBs that back conversational web services. Valid values are

Exclusive

Database

Optimistic

Default value is Exclusive for non-production builds and Database for production builds. For clustered environments a value of Database is required. Non-clustered environments can use Exclusive.

WebLogic Workshop requires that method invocations on conversational web services occur serially. Serial access is enforced via record locking on the conversation's database record. When SQL Server or Oracle is used as the persistent store for conversation state, record locking is provided by the SQL statements used internally and <ejb-concurrency-strategy> may be set to Optimistic. When PointBase is used as the conversation store, <ejb-concurrency-strategy> must be Exclusive or race conditions may occur in conversation state access.

<file-filter>

The <file-filter> element includes an arbitrary number of child <include-files> and <exclude-files> elements (<include-files> and <exclude-files> elements in turn can include an arbitrary number of child <rule> elements). Use the nested <file-filter><include-files><rule> elements nested to specify files to be included in deployment EARS. Use the nested <file-filter><exclude-files><rule> elements nested to specify files to be excluded from deployment EARS. See the <rule> element for details on including and excluding files from deployment EARS.

<include-files>

Use the <include-files> element to include specific files in deployment EARS. The <include-files> element is a child element to the <file-filter> element. The <include-files> element can have an arbitrary number of child <rule> elements. See the <rule> element for details on including files in deployment EARS.

<exclude-files>

Use the <exclude-files> element to exclude specific files from deployment EARS. The <exclude-files> element is a child element to the <file-filter> element. The <exclude-files> element can have an arbitrary number of child <rule> elements. See the <rule> element for details on excluding files from deployment EARS.

<rule>

Use the <rule> element to specify individual files for exclusion or inclusion from a deployment EAR file. When jwsCompile produces a deployment EAR it checks the weblogic-jws-config.xml file to see which files in the web service project to include and exclude. By default the following file types are excluded from deployment EARS: JWS, CTRL, WSDL, JAVA, JSX, XMLMAP, CLASS. You must explicitly override the default to include these file types in deployment EARS. You can override the default behavior either by including <include-files> and <rule> elements, or by using the -x parameter of the EAR generation tool jwsCompile (see JwsCompile Command for details).

The value of the <rule> element is a file pattern relative to the project root. For example, <rule>/misc/*.txt</rule> can be used to include or exclude all TXT files in the /misc folder from the deployment EAR. The following example shows how to use the <file-filter>, <include-files>, <exclude-files>, and <rule> elements to include and exclude files and file patterns from a deployment EAR:

<file-filter>

<include-files>

<rule>/Services.h</rule>

<rule>/PageBuffer.java</rule>

<rule>/wsdl/StockTrader.wsdl</rule>

</include-files>

<include-files>

<rule>/etc/*</rule>

</include-files>

<exclude-files>

<rule>*.h</rule>

<rule>*.java</rule>

</exclude-files>

</file-filter>

Related Topics

JwsCompile Command