Administration of CORBA Applications


	BEA Home \| Events \| Solutions \| Partners \| Products \| Services \| Download \| Developer Center \| WebSUPPORT
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| Download Documentation \| Contact \| Glossary

\| WebLogic Server Doc Home \| WTC Administration Guide \| Previous Topic \| Next Topic \| Contents \| View as PDF

Note: For more information on CORBA applications, see Tuxedo CORBA.

The following sections provide information on how to administer and configure the WebLogic Tuxedo Connector to support Tuxedo CORBA clients and services.

How to Configure WebLogic Tuxedo Connector for CORBA Service Applications

Note: For more information on how to configure your XML configuration file, see The WebLogic Tuxedo Connector XML Configuration File.

This section provides information on how to configure your XML configuration file to support a call to a Tuxedo CORBA server from a WebLogic Server EJB. Use the following steps to modify the BDMCONFIG section of your XML configuration file:

Configure a T_DM_LOCAL_TDOMAIN section for your WebLogic Server domain.
Configure a T_DM_REMOTE_TDOMAIN section for your Tuxedo CORBA domain.
Configure a T_DM_IMPORT section.
- Set ResourceName to "//domain_id" where domain_id is DOMAINID specified in the Tuxedo UBBCONFIG file. The maximum length of this unique identifier for CORBA domains is 15 characters and includes the //.
- Set LocalAccessPoint to the value of the LocalAccessPoint element of the T_DM_REMOTE_TDOMAIN.
- RemoteAccessPointList to the value of the AccessPointId element of the T_DM_REMOTE_TDOMAIN.

For information on how to develop client applications that call a Tuxedo CORBA service using a WebLogic Server EJB, see the WebLogic Tuxedo Connector Programmer's Guide.

Example XML Configuration File

The following XML configuration file provides an example of how to configure the WebLogic Tuxedo Connector to a TUXEDO CORBA server.

Listing 4-1 Example XML Configuration File for a CORBA Server Application

<?xml version="1.0"?>

<!DOCTYPE WTC_CONFIG SYSTEM 
"http://www.bea.com/servers/wls610/dtd/wtc_config.dtd">

<!--Java and XML-->
          <WTC_CONFIG>
          <BDMCONFIG>
	                    <T_DM_LOCAL_TDOMAIN AccessPoint="examples">
		                              <WlsClusterName>Coolio</WlsClusterName>
		                              <AccessPointId>examples</AccessPointId>
		                              <Type>TDOMAIN</Type>
		                              <Security>NONE</Security>
		                              <ConnectionPolicy>ON_DEMAND</ConnectionPolicy>
		                              <BlockTime>30</BlockTime>
		                              <NWAddr>//localhost:20304</NWAddr>
		                    	</T_DM_LOCAL_TDOMAIN>
	                    <T_DM_REMOTE_TDOMAIN AccessPoint="TUXDOM">
		                              <LocalAccessPoint>examples</LocalAccessPoint>
		                              <AccessPointId>TUXDOM</AccessPointId>
		                              <Type>TDOMAIN</Type>
		                              <NWAddr>//localhost:20305</NWAddr>
			                    </T_DM_REMOTE_TDOMAIN>
	                    <T_DM_IMPORT
		                              ResourceName="//simpapp"
		                              LocalAccessPoint="examples"
		                              RemoteAccessPointList="TUXDOM">
	                    </T_DM_IMPORT>
</BDMCONFIG>
</WTC_CONFIG>

How to Administer and Configure WebLogic Tuxedo Connector for Inbound RMI/IIOP

This section provides information on how to administer your application environment and configure your XML configuration file to enable Tuxedo CORBA objects to invoke upon EJBs deployed in WebLogic Server using the RMI/IIOP API.

Configuring the XML Configuration file

Note: For more information on how to configure your XML configuration file, see The WebLogic Tuxedo Connector XML Configuration File.

This section provides information on how to configuring the WebLogic Tuxedo Connector to enable Tuxedo CORBA objects to invoke upon EJBs deployed in WebLogic Server using the RMI/IIOP API. Use the following steps to modify the BDMCONFIG section of your XML configuration file:

Configure the T_DM_LOCAL_TDOMAIN section for your WebLogic Server domain
Configure the T_DM_REMOTE_TDOMAIN section for your Tuxedo CORBA domain

Administering the Tuxedo Application Environment

Note: For more information on how to configure your Tuxedo application environment, see Tuxedo Administration Topics.

You must perform some additional steps when configuring your Tuxedo application environment.

Set the TOBJADDR for your environment.
Example: //<hostname>:2468
Register WebLogic Server (WLS) Naming Service in the Tuxedo domain's CosNaming namespace by entering the following command:
cnsbind -o ior.txt WLS

The ior.txt file contains the URL of the WebLogic Server's domain Naming Service.

Listing 4-2 ior.txt File for iiop.ejb.stateless.server.tux Tuxedo Client Example

corbaloc:tgiop:examples/NameService

How to Configure WebLogic Tuxedo Connector for Outbound RMI/IIOP

Note: For more information on how to configure your XML configuration file, see The WebLogic Tuxedo Connector XML Configuration File.

This section provides information on how to configure your XML configuration file to enable WebLogic Server EJBs to invoke upon Tuxedo CORBA objects using the RMI/IIOP API. Use the following steps to modify the BDMCONFIG section of your XML configuration file:

Configure the T_DM_LOCAL_TDOMAIN section for your WebLogic Server domain.
Configure a T_DM_REMOTE_TDOMAIN section for your Tuxedo CORBA domain. Outbound RMI/IIOP requires two additional elements: FederationURL and FederationName.
- Set FederationURL to the URL for a foreign name service that is federated into the JNDI. This must be the same URL used by the EJB to obtain the initial context used to access the remote Tuxedo CORBA object.
- Set FederationName to the symbolic name of the federation point.

Note: For more information, see FederationURL and FederationName.

Configure a T_DM_IMPORT section.
- Set ResourceName to "//domain_id" where domain_id is DOMAINID specified in the Tuxedo UBBCONFIG file of the remote Tuxedo domain where the object is deployed. The maximum length of this unique identifier for CORBA domains is 15 characters including the //.
- Set LocalAccessPoint to the value of the LocalAccessPoint element of the T_DM_REMOTE_TDOMAIN.
- RemoteAccessPointList to the value of the AccessPointId element of the T_DM_REMOTE_TDOMAIN.
- Optional. Specify the transaction timeout value.

For information on how to develop applications that use RMI/IIOP to call a Tuxedo service using a WebLogic Server EJB, see the WebLogic Tuxedo Connector Programmer's Guide at http://download.oracle.com/docs/cd/E13222_01/wls/docs61/wtc_atmi/index.html.

Example XML Configuration File

The following XML configuration file provides an example of how to configure the WebLogic Tuxedo Connector for outbound RMI/IIOP.

Listing 4-3 Example XML Configuration File for Outbound RMI/IIOP

<?xml version="1.0"?>

<!DOCTYPE WTC_CONFIG SYSTEM 
"http://www.bea.com/servers/wls610/dtd/wtc_config.dtd">

<!--Java and XML-->
<WTC_CONFIG>
<BDMCONFIG>
          <T_DM_LOCAL_TDOMAIN AccessPoint="examples">
		                    <WlsClusterName>Coolio</WlsClusterName>
		                    <AccessPointId>examples</AccessPointId>
		                    <Type>TDOMAIN</Type>
		                    <Security>NONE</Security>
		                    <ConnectionPolicy>ON_DEMAND</ConnectionPolicy>
		                    <BlockTime>30</BlockTime>
		                    <NWAddr>//127.0.0.1:5000</NWAddr>
	          </T_DM_LOCAL_TDOMAIN>	
          <T_DM_REMOTE_TDOMAIN>
	                    <T_DM_REMOTE_TDOMAIN AccessPoint="TDOM1">
		                    <LocalAccessPoint>examples</LocalAccessPoint>
		                    <AccessPointId>TDOM1</AccessPointId>
                    		<Type>TDOMAIN</Type>
		                    <FederationURL>corbaloc:tgiop:simpapp/NameService</FederationURL>
				                    <FederationName>tuxedo.corba.remote</FederationName>
                    <NWAddr>//127.0.0.1:4000</NWAddr>
	          </T_DM_REMOTE_TDOMAIN>
          	<T_DM_IMPORT
		                    ResourceName="//simpapp"
		                    LocalAccessPoint="examples"
		                    RemoteAccessPointList="TDOM1">
		                    <TranTime>600</TranTime>
	          </T_DM_IMPORT>
</BDMCONFIG>
</WTC_CONFIG>