Installation and Configuration Guide

Procedure 3.1. Install Open JDK on Red Hat Enterprise Linux

1. Subscribe to the Base Channel

   Obtain the OpenJDK from the RHN base channel. (Your installation of Red Hat Enterprise Linux is subscribed to this channel by default.)

2. Install the Package

   Use the yum utility to install OpenJDK: yum install java-1.7.0-openjdk-devel

3. Verify that OpenJDK is Now Your System Default

   To ensure that the correct JDK is set as the system default, login as root and run the alternatives command: /usr/sbin/alternatives --config java
   Select /usr/lib/jvm/jre-1.6.0-openjdk/bin/java
   Set javac /usr/sbin/alternatives --config javac
   Select /usr/lib/jvm/java-1.6.0-openjdk/bin/java

Procedure 3.2. Installing Apache Ant on Red Hat Enterprise Linux

1. Download Apache Ant

   Open a terminal and input this command: sudo yum install ant-trax

2. Install Apache Ant

   Enter Y when prompted to do so by the installer.

3. Add the ANT_HOME Environment Variable

   1. vi ~/.bash_profile.
   2. Add the following line:

   export ANT_HOME=/FILEPATH/ant

   Copy to Clipboard Toggle word wrap
   where filepath is the directory in which Apache Ant was installed. Save and exit vi.

   Example 3.1. 

   export ANT_HOME=/opt/apache-ant-1.8.2

   Copy to Clipboard Toggle word wrap

4. Append the Ant installation's bin directory to the Path environmental variable.

   1. vi ~/.bash_profile.
   2. Add the following line and then save and exit vi:

   export PATH=$PATH:$ANT_HOME/bin

   Copy to Clipboard Toggle word wrap

5. Test the installation

   Go back to your terminal and run ant -version. The output should resemble the following:

   [localhost]$ ant -version
   Apache Ant(TM) version 1.8.2 compiled on July 6 2011
   

   Copy to Clipboard Toggle word wrap

Procedure 3.3. Installing Apache Ant on Microsoft Windows

1. Download Apache Ant

   Download the latest Apache Ant binary release from http://ant.apache.org/.

2. Extract Apache Ant

   Extract the files to a preferred installation location such as:

   • c:\Program Files\Apache\Ant\

3. Add the ANT_HOME Environment Variable

   1. Click on the Start Menu.
   2. Open the Control Panel.
   3. Select System → Advanced → Environment Variables
   4. Create a new variable called ANT_HOME.
   5. Configure the ANT_HOME variable so that it points to the Apache Ant directory.

4. Append the bin directory of the Ant installation to the Path environmental variable.

   1. Click on the Start Menu.
   2. Open the Control Panel.
   3. Select System → Advanced → Environment Variables → System Variables
   4. Edit the PATH variable and append the text:

   ;%ANT_HOME%\bin

   Copy to Clipboard Toggle word wrap

5. Test the installation

   Run ant -version in a command line terminal. The version number should appear.

Procedure 4.1. Task:

1. Browse to https://access.redhat.com and click the Log in link in the top right corner. Enter your credentials and click Log In.
   Result:

   You are logged into RHN and you are returned to the main web page at https://access.redhat.com.

2. Navigate to the Downloads page.

   Use one of the following options to navigate to the Downloads page.
   • Click the Downloads link in the top navigation bar.
   • Navigate directly to https://access.redhat.com/downloads/.

3. Select the product and version to download.

   Use one of the following ways to choose the correct product and version to download.
   • Step through the navigation one level at a time.
   • Search for your product using the search area at the top right-hand side of the screen.

4. Download the appropriate file for your operating system and installation method of choice.

   Depending on the product you choose, you may have the choice of a Zip archive, RPM, or native installer for a specific operating system and architecture. Click either the file name or the Download link to the right of the file you want to download.

Procedure 4.2. Verify the Downloaded File

1. To verify that a file downloaded from the Red Hat Customer Portal is error-free, whilst still on the portal site, go to that package's Software Details page. Here you will find MD5 and SHA256"checksum" values that you will use to check the integrity of the file.
2. Open a terminal window and run either either the md5sum or sha256sum command, supplying the filename of the downloaded ZIP as an argument. The program will output the checksum value for the file.
3. Compare the checksum value returned by the command to the corresponding value displayed on the Software Details page for the file.

   Note

   Microsoft Windows does not come equipped with a checksum tool. Users of that operating system will have to download a third-party product instead.

Procedure 5.1. Installation

1. Extract the installation directory by running unzip soa-p-VERSION.zip.
2. Open the user account settings file in your text editor: vi SOA_ROOT/jboss-as/server/default/conf/props/soa-users.properties.
   The contents of this file using the following syntax: username=password.

   #admin=admin
   

   Copy to Clipboard Toggle word wrap
   Confirm that the security roles for your admin account are enabled by removing a leading hash character, if it is present.

   Warning

   Because this account is not secure and the password can be easily guessed, use admin=admin for test purposes only. Do not use admin as a password on production systems as this may compromise security.
3. Save the file and exit vi.
4. Open the security permissions file in your text editor: vi SOA_ROOT/jboss-as/server/default/conf/props/soa-roles.properties.

   #admin=JBossAdmin,HttpInvoker,user,admin
   

   Copy to Clipboard Toggle word wrap
   Confirm that the security roles for your admin account are enabled by removing a leading hash character, if it is present.
5. Save the changes to the file and exit vi.

Procedure 5.2. Installation

1. Extract the soa-p-VERSION.zip using the ZIP tool of your choice.
2. Confirm that the security roles for your admin account are enabled by removing a leading hash character, if it is present.

   Warning

   Because this account is not secure and the password can be easily guessed, use admin=admin for test purposes only. Do not use admin as a password on production systems as this may compromise security.
3. Save the file and exit Notepad.
4. Open SOA_ROOT\jboss-as\server\default\conf\props\soa-roles.properties in Notepad.

   #admin=JBossAdmin,HttpInvoker,user,admin
   

   Copy to Clipboard Toggle word wrap
   Remove the hash to enable the security permissions for your admin account.
5. Save the file and exit Notepad.

Procedure 6.1. Start the JBoss Enterprise SOA Platform

• Start the SOA server in a server window

  • Red Hat Enterprise Linux

    1. Open a terminal and navigate to the bin directory by entering the command cd SOA_ROOT/jboss-as/bin.
    2. Enter ./run.sh to start the SOA server. (Because you are not specifying a server profile, "default" will be used.)

  • Microsoft Windows

    1. Open a terminal and navigate to the bin directory by entering the command chdir SOA_ROOT\jboss-as\bin.
    2. Enter run.bat to start the SOA server. (Because you are not specifying a server profile, "default" will be used.)

Procedure 6.4. Stop the JBoss Enterprise SOA Platform Server

• Stop the SOA server

  Press ctrl-c in the server window (the terminal window where the SOA server was started).

Procedure 7.1. Add a New User

1. Open the soa-users.properties file in a text editor: vi SOA_ROOT/jboss-as/server/PROFILE/conf/props/soa-users.properties. Add the user's name and password on a new line, using this syntax: username=password.
   Here is an example for a user with the login name "Harold":

   harold=@dm1nU53r
   

   Copy to Clipboard Toggle word wrap

   Note

   Any line in this file that begins with a hash (#) is ignored. (You can use this convention to temporarily disable a user account.)
2. Save the changes to the file and exit the text editor.
3. Open the soa-roles.properties file in a text editor: vi SOA_ROOT/jboss-as/server/PROFILE/conf/props/soa-roles.properties. Add the user and the roles you wish to assign to them on a new line, using this syntax: username=role1,role2,role3.

   harold=JBossAdmin,HttpInvoker,user,admin
   

   Copy to Clipboard Toggle word wrap

   Note

   You can assign any number of roles. Note that a user must be assigned the JBossAdmin, HttpInvoker, user and admin roles in order to be able to log into the server consoles.

   Any line in this file that begins with a hash (#) is ignored. You can use this convention to temporarily disable user roles.
4. Save the changes to the file and exit the text editor.

Procedure 7.2. Disable a User's Account

1. Open the soa-users.properties file in a text editor: vi SOA_ROOT/jboss-as/server/PROFILE/conf/props/soa-users.properties. Either delete the entire line containing the user's name and password or simply put a hash (#) in front of it to "comment it out."
   Here is an example for a user with the login name "Harold":

   #harold=@dm1nU53r
   

   Copy to Clipboard Toggle word wrap
2. Save the changes to the file and exit the text editor.

1. Back Up Your Server Profile

   Make a copy of the server profile for which you plan to configure your database as the Database Configuration Tool modifies the configuration settings. cp -R SOA_ROOT/jboss-as/server/Profile /path/to/backup/folder.

2. Running the Database Configuration Tool

   Change to the directory containing the Database Configuration script: cd SOA_ROOT/jboss-as/tools/schema

3. Run Ant

   Run the ant command to launch the script.

4. Enter Data

   Following the prompts, enter the following information as it is requested:
   • the type of database being used,
   • the name of the database,
   • the host name or IP Address of the database,
   • the TCP port being used for the database,
   • the user name needed to access the database, and
   • the password for this user account.

   Note

   You could also add these values directly to the build.properties file (found in the same directory) before running the script. The Database Schema Tool will not prompt you for these properties if it finds you have already added them to the file.

Procedure 9.1. Task

1. Open the global configuration file in a text editor: vi SOA_ROOT/jboss-as/server/PROFILE/deployers/esb.deployer/jbossesb-properties.xml.
2. Scroll down to the "registry" section and alter the settings as you wish.

   <properties name="registry">
     <property name="org.jboss.soa.esb.registry.implementationClass"
       value="org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl"/>
     
     <property name="org.jboss.soa.esb.registry.factoryClass"
       value="org.apache.ws.scout.registry.ConnectionFactoryImpl"/>
     
     <property name="org.jboss.soa.esb.registry.queryManagerURI"
       value="org.apache.juddi.v3.client.transport.wrapper.UDDIInquiryService#inquire"/>
     
     <property name="org.jboss.soa.esb.registry.lifeCycleManagerURI"
       value="org.apache.juddi.v3.client.transport.wrapper.UDDIPublicationService#publish"/>
     <property name="org.jboss.soa.esb.registry.securityManagerURI"
       value="org.apache.juddi.v3.client.transport.wrapper.UDDISecurityService#secure"/>
     
     <property name="org.jboss.soa.esb.registry.user" value="root"/>
     <property name="org.jboss.soa.esb.registry.password"	value="root"/>
     
     <property name="org.jboss.soa.esb.scout.proxy.uddiVersion" value="3.0"/>
     <property name="org.jboss.soa.esb.scout.proxy.uddiNameSpace" value="urn:uddi-org:api_v3"/>
     
     <property name="org.jboss.soa.esb.scout.proxy.transportClass"
       value="org.apache.ws.scout.transport.LocalTransport"/>
     <!-- specify the interceptors, in order -->
     <property name="org.jboss.soa.esb.registry.interceptors"
     value="org.jboss.internal.soa.esb.services.registry.InVMRegistryInterceptor, org.jboss.internal.soa.esb.services.registry.CachingRegistryInterceptor"/>
     <!-- The following properties modify the cache interceptor behaviour -->
     <property name="org.jboss.soa.esb.registry.cache.maxSize" value="100"/>
     <property name="org.jboss.soa.esb.registry.cache.validityPeriod" value="600000"/>
     
     <!-- Organization Category to be used by this deployment. -->
     <property name="org.jboss.soa.esb.registry.orgCategory"         
     value="org.jboss.soa.esb.:category"/>
   </properties>
   

   Copy to Clipboard Toggle word wrap
3. Save the file and exit.

Procedure 9.2. Task

1. Open the global configuration file in a text editor: vi SOA_ROOT/jboss-as/server/PROFILE/deployers/esb.deployer/jbossesb-properties.xml.
2. Scroll down to the "registry" section and alter the settings like this:

   <properties name="registry">
   
   	    <property name="org.jboss.soa.esb.registry.implementationClass" 				    
   	    value="org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl"/>
   
   	    <property name="org.jboss.soa.esb.registry.factoryClass" 					
   	    value="org.apache.ws.scout.registry.ConnectionFactoryImpl"/>
   
       	<property name="org.jboss.soa.esb.registry.queryManagerURI" 				
       	value="org.apache.juddi.registry.local.InquiryService#inquire"/>
   
       	<property name="org.jboss.soa.esb.registry.lifeCycleManagerURI" 
       	value="org.apache.juddi.registry.local.PublishService#publish"/>
   
       	<property name="org.jboss.soa.esb.registry.securityManagerURI" 
       	value="org.apache.juddi.registry.local.SecurityService#secure"/>
   
       	<property name="org.jboss.soa.esb.registry.user" value="jbossesb"/>
       	<property name="org.jboss.soa.esb.registry.password" value="password"/>
       	
       	<property name="org.jboss.soa.esb.scout.proxy.transportClass" 				                                    
       	value="org.apache.ws.scout.transport.LocalTransport"/>
   
   </properties>
   

   Copy to Clipboard Toggle word wrap
3. Save the file and exit.

Procedure 9.3. Task

1. Open the global configuration file in a text editor: vi SOA_ROOT/jboss-as/server/PROFILE/deployers/esb.deployer/jbossesb-properties.xml.
2. Scroll down to the "registry" section and alter the settings like this:

   <properties name="registry">
     <property name="org.jboss.soa.esb.registry.implementationClass"
       value="org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl"/>
   
     <property name="org.jboss.soa.esb.registry.factoryClass"
       value="org.apache.ws.scout.registry.ConnectionFactoryImpl"/>
   
     <property name="org.jboss.soa.esb.registry.queryManagerURI"
       value="jnp://localhost:1099/InquiryService?org.apache.juddi.registry.rmi.Inquiry#inquire"/>
   
     <property name="org.jboss.soa.esb.registry.lifeCycleManagerURI"
       value="jnp://localhost:1099/PublishService?org.apache.juddi.registry.rmi.Publish#publish"/>      
     <property name="org.jboss.soa.esb.registry.securityManagerURI"
       value="jnp://localhost:1099/PublishService?org.apache.juddi.registry.rmi.Publish#publish"/>
     
     <property name="org.jboss.soa.esb.registry.user" value="jbossesb"/>
     <property name="org.jboss.soa.esb.registry.password" value="password"/>
         
     <property name="org.jboss.soa.esb.scout.proxy.transportClass"
       value="org.apache.ws.scout.transport.RMITransport"/>
   </properties>
   

   Copy to Clipboard Toggle word wrap
3. Save the file and exit.
4. Open the web.xml file in your text editor.
5. Configure it like this:

   <!--  uncomment if you want to enable making calls in juddi with rmi  -->
     <servlet>
     	<servlet-name>RegisterServicesWithJNDI</servlet-name>
     	<servlet-class>org.apache.juddi.registry.rmi.RegistrationService</servlet-class>
     	<load-on-startup>1</load-on-startup>
     </servlet>
   

   Copy to Clipboard Toggle word wrap
6. Save the file and exit.
7. Open the jUDDI configuration file in a text editor: vi SOA_ROOT/jboss-as/server/standard/deploy/juddi-service.sar/juddi.war/WEB-INF/juddi.properties.
8. Configure it like this:

   # JNDI settings (used by RMITransport)
   java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
   java.naming.provider.url=jnp://localhost:1099
   java.naming.factory.url.pkgs=org.jboss.naming
   

   Copy to Clipboard Toggle word wrap
9. Save the file and exit.
10. Add scout-client.jar to the RMI client's class-path.

1. For a local application, open the global configuration file in a text editor: vi SOA_ROOT/jboss-as/server/PROFILE/deployers/esb.deployer/jbossesb-properties.xml.
2. Scroll down to the "registry" section and alter the local settings like this:

   <properties name="registry">
   	<property name="org.jboss.soa.esb.registry.implementationClass" 
   value="org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl"/>
   
   	<property name="org.jboss.soa.esb.registry.factoryClass"
   value="org.apache.ws.scout.registry.ConnectionFactoryImpl"/>
   
       	<property name="org.jboss.soa.esb.registry.queryManagerURI"
   value="org.apache.juddi.registry.local.InquiryService#inquire"/>
   
       	<property name="org.jboss.soa.esb.registry.lifeCycleManagerURI"
   value="org.apache.juddi.registry.local.PublishService#publish"/>
   
       	<property name="org.jboss.soa.esb.registry.securityManagerURI"
   value="org.apache.juddi.registry.local.SecurityService#secure"/>
   
       	<property name="org.jboss.soa.esb.registry.user" value="jbossesb"/>
       	<property name="org.jboss.soa.esb.registry.password" value="password"/>
       	
       	<property name="org.jboss.soa.esb.scout.proxy.transportClass" 
   value="org.apache.ws.scout.transport.LocalTransport"/>
   </properties>
   

   Copy to Clipboard Toggle word wrap
3. Save the file and exit.
4. For a remote application, open the global configuration file in a text editor: vi SOA_ROOT/jboss-as/server/PROFILE/deployers/esb.deployer/jbossesb-properties.xml.
5. Scroll down to the "registry" section and alter the remote method invocation settings like this:

   <properties name="registry">
   	<property name="org.jboss.soa.esb.registry.implementationClass"
   value="org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl"/>
   
   	<property name="org.jboss.soa.esb.registry.factoryClass"
   value="org.apache.ws.scout.registry.ConnectionFactoryImpl"/>
   
       	<property name="org.jboss.soa.esb.registry.queryManagerURI"
   value="jnp://localhost:1099/InquiryService?org.apache.juddi.registry.rmi.Inquiry#inquire"/>
   
       	<property name="org.jboss.soa.esb.registry.lifeCycleManagerURI"
   value="jnp://localhost:1099/PublishService?org.apache.juddi.registry.rmi.Publish#publish"/>
   	
       	<property name="org.jboss.soa.esb.registry.user" value="jbossesb"/>
       	<property name="org.jboss.soa.esb.registry.password" value="password"/>
       	
       	<property name="org.jboss.soa.esb.scout.proxy.transportClass"
   value="org.apache.ws.scout.transport.RMITransport"/>
   </properties>
   

   Copy to Clipboard Toggle word wrap
6. Save the file and exit.
7. Point the host names of the queryManagerURI and lifeCycleManagerURI classes to the host on which the jUDDI Registry is running (this is also where the local is running). Note that the local application needs to have access to a naming service.
8. Use these settings to register the application:

   //Getting the JNDI setting from the config
   Properties env = new Properties();
   env.setProperty(RegistryEngine.PROPNAME_JAVA_NAMING_FACTORY_INITIAL,factoryInitial);
   env.setProperty(RegistryEngine.PROPNAME_JAVA_NAMING_PROVIDER_URL, providerURL);
   env.setProperty(RegistryEngine.PROPNAME_JAVA_NAMING_FACTORY_URL_PKGS,
     factoryURLPkgs); 
   
   InitialContext context = new InitialContext(env);
   Inquiry inquiry = new InquiryService();
   log.info("Setting " + INQUIRY_SERVICE + ", " + inquiry.getClass().getName());
   mInquery = inquiry;
   context.bind(INQUIRY_SERVICE, inquiry);
   Publish publish = new PublishService();
   log.info("Setting " + PUBLISH_SERVICE + ", " + publish.getClass().getName());
   mPublish = publish;
   context.bind(PUBLISH_SERVICE, publish);
   

   Copy to Clipboard Toggle word wrap
9. Include the scout-client.jar file on the RMI client's class-path.

Procedure 9.4. Task

1. Shut down the RMI service by "commenting out" the web.xml file's RegisterServicesWithJNDI servlet.
2. Deploy the juddi.war archive.
3. Configure the data-source.
   Here are some sample properties:

   <properties name="registry">
   	<property name="org.jboss.soa.esb.registry.implementationClass" 				
   	value="org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl"/>
   
   	<property name="org.jboss.soa.esb.registry.factoryClass" 					
   	value="org.apache.ws.scout.registry.ConnectionFactoryImpl"/>
   
      	<property name="org.jboss.soa.esb.registry.queryManagerURI" 				
      	value="http://localhost:8080/juddi/inquiry"/>
   
      	<property name="org.jboss.soa.esb.registry.lifeCycleManagerURI" 				
      	value="http://localhost:8080/juddi/publish"/>	
   
      	<property name="org.jboss.soa.esb.registry.user" value="jbossesb"/>
      	<property name="org.jboss.soa.esb.registry.password" value="password"/>
      	
      	<property name="org.jboss.soa.esb.scout.proxy.transportClass" 				
      	value="org.apache.ws.scout.transport.AxisTransport"/>
   </properties>
   

   Copy to Clipboard Toggle word wrap

Procedure 9.5. Task

1. Open a web browser session and go to the jUDDI Console at http://localhost:8080/uddi-console/. Log in as root.
2. Click "Publisher".
3. From the Publisher ID list, click on the username.
4. Select the "Is Admin" checkbox.

Procedure 9.6. Task

1. Launch JBoss Developer Studio
2. Go to JBoss Central screen
3. Download the plug-ins you require to do your SOA development work.

Procedure 10.1. Task

1. Choose a specific JAXR implementation.
2. Set the property to configure the class. (Because the JBoss Enterprise SOA Platform uses Apache Scout by default, this property is set to the Scout factory class, namely org.apache.ws.scout.registry.ConnectionFactoryImpl.)
3. Configure the JAXR implementation by providing it with the Registry's location. Do so by editing org.jboss.soa.esb.registry.queryManagerURI, org.jboss.soa.esb.registry.lifeCycleManagerURI and org.jboss.soa.esb.registry.securityManagerURI.

Procedure 10.2. Task

• Write a new SystinetRegistryImplemtation class and provide a reference to it from within this property.

Procedure 10.3. Task

1. Edit the node definition file: vi SOA_ROOT/jboss-as/server/PROFILE/deploy/jbossesb.sar/esb.juddi.client.xml
2. Use the node settings to select which transport to use:

   <node>
   	    <!-- required 'default' node -->
   	    <name>default</name> 
   	    <description>Main jUDDI node</description>
   	    <properties>
   	<property name="serverName" value="localhost" />
   		<property name="serverPort" value="8880" />
   	    </properties>
   	    <!-- JAX-WS Transport
        <proxyTransport>org.apache.juddi.v3.client.transport.JAXWSTransport</proxyTransport>
   	    <custodyTransferUrl>http://${serverName}:${serverPort}/juddiv3/services/custody-transfer?wsdl</custodyTransferUrl>
       <inquiryUrl>http://${serverName}:${serverPort}/juddiv3/services/inquiry?wsdl</inquiryUrl>
       <publishUrl>http://${serverName}:${serverPort}/juddiv3/services/publish?wsdl</publishUrl>
       <securityUrl>http://${serverName}:${serverPort}/juddiv3/services/security?wsdl</securityUrl>
       <subscriptionUrl>http://${serverName}:${serverPort}/juddiv3/services/subscription?wsdl</subscriptionUrl>
       <subscriptionListenerUrl>http://${serverName}:${serverPort}/juddiv3/services/subscription-listener?wsdl</subscriptionListenerUrl>
   	   <juddiApiUrl>http://${serverName}:${serverPort}/juddiv3/services/juddi-api?wsdl</juddiApiUrl>
   	    -->
   	   <!-- In VM Transport Settings 
       <proxyTransport>org.jboss.internal.soa.esb.registry.client.JuddiInVMTransport</proxyTransport>
       <custodyTransferUrl>org.apache.juddi.api.impl.UDDICustodyTransferImpl</custodyTransferUrl>
   	    <inquiryUrl>org.apache.juddi.api.impl.UDDIInquiryImpl</inquiryUrl>
   	    <publishUrl>org.apache.juddi.api.impl.UDDIPublicationImpl</publishUrl>
       <securityUrl>org.apache.juddi.api.impl.UDDISecurityImpl</securityUrl>
       <subscriptionUrl>org.apache.juddi.api.impl.UDDISubscriptionImpl</subscriptionUrl>
       <subscriptionListenerUrl>org.apache.juddi.api.impl.UDDISubscriptionListenerImpl</subscriptionListenerUrl>
   	   <juddiApiUrl>org.apache.juddi.api.impl.JUDDIApiImpl</juddiApiUrl>
    	-->
   	<!-- RMI Transport Settings -->
   <proxyTransport>org.apache.juddi.v3.client.transport.RMITransport</proxyTransport>
   	<custodyTransferUrl>/juddiv3/UDDICustodyTransferService</custodyTransferUrl>
   	<inquiryUrl>/juddiv3/UDDIInquiryService</inquiryUrl>
   	<publishUrl>/juddiv3/UDDIPublicationService</publishUrl>
   <securityUrl>/juddiv3/UDDISecurityService</securityUrl>
   <subscriptionUrl>/juddiv3/UDDISubscriptionService</subscriptionUrl>
   <subscriptionListenerUrl>/juddiv3/UDDISubscriptionListenerService</subscriptionListenerUrl>
   <juddiApiUrl>/juddiv3/JUDDIApiService</juddiApiUrl>
   <javaNamingFactoryInitial>org.jnp.interfaces.NamingContextFactory</javaNamingFactoryInitial>
   	<javaNamingFactoryUrlPkgs>org.jboss.naming</javaNamingFactoryUrlPkgs>
   	<javaNamingProviderUrl>jnp://localhost:1099</javaNamingProviderUrl>
   	</node>
   

   Copy to Clipboard Toggle word wrap
3. By default, the Remote Method Invocation (RMI) settings are enabled. To switch transports, comment those ones out and enable the ones you want to use.
4. Save the file and exit.

Procedure 10.4. Task

1. Check that the transportClass is set to LocalTransport in the uddi.xml file.
2. Configure the uddi.xml file to utilize the Registry's transports (these being InVM, RMI and WS, respectively). The file is located in SOA_ROOT/jboss-as/server/all/deploy/jbossesb.sar/esb.juddi.client.xml
3. Create a schema in the jUDDI registry by adding the jbossesb publisher to it.

   Note

   The product/install/jUDDI-registry directory contains database-create scripts for most common databases. These files are located in SOA_ROOT/jboss-as/server/PROFILE/deploy/jbossesb-registry.sar/juddi-sql.

   Note

   The system can generate the database automatically if the user has been granted permission to create tables. (The Registry can create a database of any type for which there exists an associated Hibernate dialect.)
4. Check that the SOA_ROOT/jboss-as/server/default/deploy/jbossesb-registry.sar/esb.juddi.xml and SOA_ROOT/jboss-as/server/all/deploy/jbossesb.sar/esb.juddi.client.xml exist. These files contain the Registry's configuration settings.

   Note

   If you want the software to communicate with another UDDI registry, use Apache Scout's JAXR transports. There are four implementations of this class and they are also based on SOAP, SAAJ, RMI and Embedded Java.
5. If you decide to change the transport, always change the query and life-cycle uniform resource indicators as well. Here is sample code that demonstrates how to do so:

   SOAP
   queryManagerURI	http://localhost:8080/juddi/inquiry
   lifeCycleManagerURI	http://localhost:8080/juddi/publish
   transportClass		org.apache.ws.scout.transport.AxisTransport
   
   RMI
   queryManagerURI 	jnp://localhost:1099/InquiryService?org.apache.juddi.registry.rmi.Inquiry#inquire
   lifeCycleManagerURI 	jnp://localhost:1099/PublishService?org.apache.juddi.registry.rmi.Publish#publish
   transportClass		org.apache.ws.scout.transport.RMITransport
   
   Local
   queryManagerURI	org.apache.juddi.registry.local.InquiryService#inquire
   lifeCycleManagerURI	org.apache.juddi.registry.local.PublishService#publish
   transportClass		org.apache.ws.scout.transport.LocalTransport
   

   Copy to Clipboard Toggle word wrap

1. Open the global configuration file in a text editor: vi SOA_ROOT/jboss-as/server/PROFILE/deployers/esb.deployer/jbossesb-properties.xml.
2. Modify the org.jboss.soa.esb.registry.interceptors properties.
3. Save the file and exit.

Procedure 11.1. Task

• Integration is turned on by default. To confirm this, open vi SOA_ROOT/jboss-as/server/PROFILE/deploy/riftsaw.sar/bpel.properties.xml and ensure that is set as follows: bpel.uddi.registration=true.

Procedure 11.2. Task

1. Open the esb.juddi.client.xml file in your text editor: vi SOA_ROOT/jboss-as/server/PROFILE/deploy/jbossesb.sar/esb.juddi.client.xml
2. Configure the settings. For example:

   </nodes>
      <clerks registerOnStartup="false">
         <clerk name="SOAExample" node="default" publisher="root" password="root"/>
      </clerks>
      </manager>
   </uddi>
   

   Copy to Clipboard Toggle word wrap
3. Save the file and exit.
4. Put another copy of the file in here (the files must always correspond: SOA_ROOT/jboss-as/server/PROFILE/deploy/jbossesb-registry.sar/juddi_custom_install_data/
5. Save the file and exit.

Procedure 12.1. Task

1. Go to the HornetQ Directory: cd SOA_ROOT/jboss-as/extras/hornetq.

2. Deploy It

   Run ant.

Procedure 12.2. Task

1. Configure the JMS Provider

   To configure JBoss Messaging, open the configuration file in a text editor: vi jboss-esb.xml.
2. Modify these settings:

   jndi-URL="localhost”
   	jndi-context-factory="org.jnp.interfaces.NamingContextFactory"
   	connection-factory="ConnectionFactory"
   	destination-type="queue"
   	destination-name="queue/myqueue"
   

   Copy to Clipboard Toggle word wrap

   Important

   Always include the jboss-messaging-client.jar file on the class-path. (This file is found in the SOA_ROOT/jboss-as/client/jboss-messaging-client.jar archive.)

   Note

   If you want to use load balancing and fail-over capabilities, you must configure JBoss Messaging for clustering. This functionality is constantly evolving. To learn how to configure it, please consult the JBoss Messaging documentation.
3. Check that JBoss Messaging's Service Binding Manager configuration matches that found in the SOA_ROOT/seam/bootstrap/deploy/remoting-service.xml file.

Procedure 12.3. Task

1. Copy the IBM Websphere wmq.jmsra.rar file to the JBoss Enterprise SOA Platform: cp wmq.jmsra.rar SOA_ROOT/jboss-as/server/PROFILE/deploy/
2. Copy the IBM Websphere com.ibm.mqetclient.jar to the JBoss Enterprise SOA Platform: cp com.ibm.mqetclient.jar SOA_ROOT/jboss-as/lib/.
3. Open run.conf in your text editor: vi SOA_ROOT/jboss-as/bin/run.conf
4. Add this setting by modifying the JAVA_OPTS in run.conf:

   JAVA_OPTS="-DtraceEnabled=true -DtraceDestination=wmq_jca.trc 
       -DtraceLevel=10 -DlogWriterEnabled=false"
   

   Copy to Clipboard Toggle word wrap
5. Save the file and exit.
6. Open the jboss-esb.xml file in your text editor: vi SOA_ROOT/jboss-as/server/PROFILE/deploy/jbossesb.esb/META-INF/jboss-esb.xml
7. Add these settings:

   <jms-jca-provider name="WMQ-JCA" connection-factory="MyAppXAConnectionFactory"
   adapter="wmq.jmsra.rar"
          jndi-URL="10.12.10.110:1414/CH1"
          jndi-context-factory="com.ibm.mq.jms.context.WMQInitialContextFactory">
       <property name="max-xa-sessions-per-connection" value="1" />
   <jms-bus busid="quickstartEsbChannel">
     <jms-message-filter dest-type="QUEUE" dest-name="Q1" transacted="true"/>
   </jms-bus>
   <activation-config>
        <property name="queueManager" value="QM1" />
        <property name="channel" value="CH1" />
        <property name="hostName" value="10.12.10.110" />
        <property name="port" value="1515" />
        <property name="transportType" value="CLIENT" />
        <property name="useJNDI" value="false" />
   </activation-config>
   </jms-jca-provider>
   

   Copy to Clipboard Toggle word wrap
8. Save the file and exit.
9. Run crtmqm -q QM1
10. Run strmqm QM1

    define channel (CH.1) chltype (RCVR) trptype (TCP)
    start channel (CH.1)
    define qlocal (Q1)
    define listener(QM1.LISTENER) trptype(TCP) port(30001) ipaddr(10.12.58.110)
    start listener (QM1.LISTENER)
    

    Copy to Clipboard Toggle word wrap

Procedure 12.4. Task

1. Run this command: /opt/mqm/java/bin/JMSAdmin -v

        
   java -Dcom.ibm.msg.client.commonservices.log.outputName=$MQ_JAVA_DATA_PATH/log -Dcom.ibm.msg.client.commonservices.trace.outputName=$MQ_JAVA_DATA_PATH/trace -DMQJMS_INSTALL_PATH=$MQ_JAVA_INSTALL_PATH com.ibm.mq.jms.admin.JMSAdmin $*
   

   Copy to Clipboard Toggle word wrap
2. Open JMSAdmin.config in your text editor: vi JMSAdmin.config
3. Edit the file as per this sample code:

        
   INITIAL_CONTEXT_FACTORY=com.ibm.mq.jms.context.WMQInitialContextFactory
   
   PROVIDER_URL=localhost:30002/SYSTEM.DEF.SVRCONN
   
   SECURITY_AUTHENTICATION=none
   

   Copy to Clipboard Toggle word wrap

   Note

   If you have a listener on a different port, use it instead. (The default is 1414).
4. Save the file and exit.
5. Define objects with these commands: InitCtx> def cf(ConnectionFactory) qmgr(QM1) tran(CLIENT) host(10.12.58.105) BROKERQMGR(QM1) and InitCtx> def qcf(QueueConnectionFactory) qmgr(QM1) tran(CLIENT) host(10.12.58.105)
6. If you are having problems with JMSAdmin, troubleshoot the logs: less /var/mqm/errors/AMQERR01.LOG and less /var/mqm/qmgrs/QUEUE MANAGER NAME/errors/AMQERR01.LOG

   Note

   For more information, refer to http://www.ibm.com/developerworks/websphere/techjournal/0502_woolf/0502_woolf.html.

Procedure 12.5. Task

1. Configure the Adapter

   The adapter name is wmq.jmsra.rar. Copy this file into the JBoss Enterprise SOA Platform's SOA_ROOT/jboss-as/server/PROFILE/deploy directory.

2. Check the Context Factory

   Ensure that the initial context factory is com.ibm.mq.jms.context.WMQInitialContextFactory.

3. Configure the QueueManager

   Ensure that the queueManager configuration is in the <activation-config>. You will need to configure a queue manager in your own Websphere MQ installation. (Note that all of your destination queues are configured in your queue manager.)

4. Configure the Channel

   Ensure that the channel configuration is in the <activation-config> property.

   Note

   You can configure a queue manager to use a number of different types of channel. Clients connect through server connection channels. A default server connection channel (SYSTEM.DEF.SVRCONN), is added as part of the Websphere MQ installation but it is a good idea to also create your own dedicated channels, especially if you are using extended (XA) transactions.

5. Configure the transportType

   Edit the transportType. The configuration for this is in the <activation-config> property. Websphere MQ supports two transport types ( Client and Binding).

6. Edit the Settings

   Open the configuration file in a text editor and edit it.
   Here is an example of a <jms-jca-provider> configuration. It shows how to set a gateway provider configuration:

   <jms-jca-provider adapter="wmq.jmsra.rar" connection-factory="MyAppXAConnectionFactory" jndi-context-factory="com.ibm.mq.jms.context.WMQInitialContextFactory" name="WMQ-JCA">
   	<property name="max-xa-sessions-per-connection" value="1"/>
   		<jms-bus busid="quickstartGwChannel">
   		<jms-message-filter dest-name="QUEUE1_JMS" dest-type="QUEUE" transacted="true"/>
   		</jms-bus>
   			<activation-config>
   				<property name="queueManager" value="TQM"/>
   				<property name="channel" value="Q1CONN"/>
   				<property name="hostName" value="localhost"/>
   				<property name="port" value="1414"/>
   				<property name="transportType" value="CLIENT"/>
   			</activation-config>
   </jms-jca-provider>
   

   Copy to Clipboard Toggle word wrap

   Note

   It is actually the <jms-listener> configuration that determines the gateway/message-aware characteristics of a listener. However, as far as Websphere MQ is concerned, this is only of use as a gateway listener provider. In other words, this configuration would not work as a message-aware listener for Websphere MQ. This is because it does not specify an appropriate JNDI provider URL (as used by the ServiceInvoker) for routing ESB messages to the destinations (buses) defined on the provider.

7. Configure the JCA Adapter

   The <activation-config> configures the JCA adapter so that it obtains messages from the destinations. It does not determine how messages are to be delivered to the destinations. Here is an example of a configuration that could be used as a message-aware listener's provider:

   <jms-jca-provider adapter="wmq.jmsra.rar" connection-factory="MyAppXAConnectionFactory" jndi-URL="localhost:1414/CHANX" jndi-context-factory="com.ibm.mq.jms.context.WMQInitialContextFactory" name="WMQ-JCA">
   	<property name="max-xa-sessions-per-connection" value="1"/>
   		<jms-bus busid="quickstartEsbChannel">
   			<jms-message-filter dest-name="QUEUE2_JMS" dest-type="QUEUE" transacted="true"/>
   		</jms-bus>
   	<activation-config>
   		<property name="queueManager" value="TQM"/>
   		<property name="channel" value="Q2CONN"/>
   		<property name="hostName" value="localhost"/>
   		<property name="port" value="1414"/>
   		<property name="transportType" value="CLIENT"/>
   	</activation-config>
   </jms-jca-provider>
   

   Copy to Clipboard Toggle word wrap

8. Creating a Standard JMS Provider

   The settings for creating a standard JMS provider configuration are similar:

   <jms-provider connection-factory="MyAppConnectionFactory" jndi-URL="localhost:1414/CHAN1" jndi-context-factory="com.ibm.mq.jms.context.WMQInitialContextFactory" name="JMS">
   	<jms-bus busid="quickstartGwChannel2">
   		<jms-message-filter dest-name="QUEUE3_JMS" dest-type="QUEUE"/>
   	</jms-bus>
   </jms-provider>
   

   Copy to Clipboard Toggle word wrap

   Note

   With the standard provider, there is neither an adapter nor any <activation-config> configurations. Listeners receiving messages from the destinations defined in a standard provider do not use a JCA Adapter Inflow to obtain the messages. Instead, they need to use JNDI to find the destination and obtain the messages. This means that, for Websphere MQ, the jndi-URL must always be specified (remember that for JCA it is only required for destinations that service a Message-Aware listener).

9. Save

   Save the file and exit.

Procedure 12.6. Task

1. Edit the JMSRouter Configuration

   Open the JMSRouter's configuration file in a text editor and modify the settings in your jboss-esb.xml. Here is an example of a JMSRouter configuration for routing messages to Websphere MQ from inside an ESB action pipeline:

   <action class="org.jboss.soa.esb.actions.routing.JMSRouter" name="routeToORDERSQueue">
   	<property name="jndi-context-factory" value="com.ibm.mq.jms.context.WMQInitialContextFactory"/>
   	<property name="jndi-URL" value="wmqserver:1414/CHANX"/>
   	<property name="connection-factory" value="WMQConnectionFactory"/>
   	<property name="jndiName" value="ORDERS"/>
   </action>
   

   Copy to Clipboard Toggle word wrap

2. Save

   Save the file and exit.

Procedure 12.7. Task

1. Edit the jms-jca-provider Configuration

   Edit the jboss-esb.xml file in a text editor. Here is how the jms-jca-provider configuration would look for an Extended Transaction Client configuration. (In this example, the XA Connection Factory that has been configured in the WMQ JNDI namespace is called WMQXAConnectionFactory.)

   Note

   Inflow related configurations (adapter, <activation-config> etc) were intentionally omitted as they are not relevant to the Extended Client configuration:

   <jms-jca-provider name="WMQ" connection-factory="WMQXAConnectionFactory"
   	jndi-URL="wmqserver:1414/CHANXA_SEND"
   	jndi-context-factory="com.ibm.mq.jms.context.WMQInitialContextFactory">
   		<property name="max-xa-sessions-per-connection" value="1" />
   			<jms-bus busid="ordersGwChannel">
   			<jms-message-filter dest-type="QUEUE" dest-name="ORDERS" transacted="true"/>
   			</jms-bus>
   				<activation-config>
   					<!--
   					Used by inflow... not relevant to client
   					See section on JMS and JCA.
   					-->
   		</activation-config>
   </jms-jca-provider>
   

   Copy to Clipboard Toggle word wrap

2. Configuring for Use with the JMSRouter

   This example shows how to use the same XA Connection Factory on the JMSRouter:

   <action name="routeToORDERSQueue" class="org.jboss.soa.esb.actions.routing.JMSRouter">
   <property name="jndi-context-factory"
   value="com.ibm.mq.jms.context.WMQInitialContextFactory"/>
   <property name="jndi-URL" value="wmqserver:1414/CHANXA_SEND"/>
   <property name="connection-factory" value="WMQXAConnectionFactory"/>
   <property name="jndiName" value="ORDERS"/>
   <property name="max-xa-sessions-per-connection" value="1"/>
   <!-- etc... -->
   </action>
   

   Copy to Clipboard Toggle word wrap

   Important

   An important point to note about Websphere MQ and XA is that it does not support both getting and putting messages concurrently on the same Queue Manager Channel. For this reason, it is a good idea to configure a dedicated channel for each component that gets or puts messages into a Websphere MQ destination in the context of XA transactions.
3. Set the max-xa-sessions-per-connection property in jboss-esb.xml to 1.

4. Save

   Save the file and exit.
5. Configure a dedicated queue manager channel for each component that obtains or sends messages to a Websphere MQ destination.
6. Make sure the GET and PUT properties on each of the Websphere MQ destinations are not set to Inhibit. (This can be happen when the destination is created and it results in the ESB being unable to obtain or send messages.)

Procedure 12.8. Task

1. Navigate to the bin directory: cd /opt/mqm/java/bin.
2. Launch JMSAdmin.
3. Use this program to administer your JNDI settings and obtain a ConnectionFactory for Plain JMS interactions.

   Note

   For more information about using JMSAdmin, refer to http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp.

Procedure 12.9. Task

1. Make a queue manager called QM1: crtmqm -q QM1
2. Start runmqsc: runmqsc QM1
3. Input the following settings when prompted:

   define channel (CH.1) chltype (RCVR) trptype (TCP)
   start channel (CH.1)
   define qlocal (Q1)
   define listener(QM1.LISTENER) trptype(TCP) port(30001) ipaddr(10.12.58.110)
   start listener (QM1.LISTENER) 
   (end)
   

   Copy to Clipboard Toggle word wrap
4. Exit the program.
5. Copy com.ibm.mqetclient.jar from your Websphere MQ installation to your server: cp com.ibm.mqetclient.jar SOA_ROOT/jboss-as/PROFILE/lib/
6. Copy wmq.jmsra.ivt.ear from your Websphere MQ installation to your server: cp wmq.jmsra.ivt.ear SOA_ROOT/jboss-as/server/PROFILE/deploy
7. Copy wmq.jmsra.rar from your Websphere MQ installation to your server: cp wmq.jmsra.rar SOA_ROOT/jboss-as/server/PROFILE/deploy
8. Create a data source file in a text editor (be sure to change the IP address to that of your WSMQ server): vi SOA_ROOT/jboss-as/server/PROFILE/deploy/wsmq-ds.xml
   Here is a sample configuration:

   <?xml version="1.0" encoding="UTF-8"?>
   
    
   
   <connection-factories>
     <!-- connection factory definition -->
     <tx-connection-factory>
   
    
   
       <jndi-name>IVTCF</jndi-name>
       <xa-transaction />
       <rar-name>wmq.jmsra.rar</rar-name>
   
    
   
       <connection-definition>
         javax.jms.ConnectionFactory
       </connection-definition>
   
    
   
       <config-property name="channel" type="java.lang.String">SYSTEM.DEF.SVRCONN</config-property>
       <config-property name="hostName" type="java.lang.String">
         10.12.58.110
       </config-property>
       <config-property name="username" type="java.lang.String">mqm</config-property>
       <config-property name="password" type="java.lang.String">mqm</config-property>
       <config-property name="port" type="java.lang.String">30001</config-property>
       <config-property name="queueManager" type="java.lang.String">QM1</config-property>
       <config-property name="transportType" type="java.lang.String">CLIENT</config-property>
   
    
   
       <security-domain-and-application>JmsXARealm</security-domain-and-application>
     </tx-connection-factory>
   
    
   
     <!-- admin object definition -->
     <mbean code="org.jboss.resource.deployment.AdminObject"
         name="jca.wmq:name=ivtqueue">
   
    
   
       <attribute name="JNDIName">
         IVTQueue
       </attribute>
       <depends optional-attribute-name="RARName">
         jboss.jca:service=RARDeployment,name='wmq.jmsra.rar'
       </depends>
       <attribute name="Type">javax.jms.Queue</attribute>
   
    
   
       <attribute name="Properties">
         baseQueueManagerName=QM1
         baseQueueName=Q1
       </attribute>
     </mbean>
   </connection-factories>
   

   Copy to Clipboard Toggle word wrap
9. Save the file as and exit your text editor.
10. Launch a web browser and go to http://localhost:8080/WMQ_IVT/.
    This brings up the IVT ("Install Verification Test").
11. Run the normal test and the transactional test.

    Note

    For more information, refer to http://www.ibm.com/developerworks/websphere/library/techarticles/0710_ritchie/0710_ritchie.html.