Deploying the UDDI registry application

You deploy a UDDI registry application as part of setting up a UDDI node. You can use a supplied script, the administrative console, or wsadmin scripting commands.

Before you begin

Before you deploy a UDDI registry application, you must create the database and data source for the UDDI registry.

About this task

Use this task as part of setting up a default UDDI node or setting up a customized UDDI node. You can deploy a UDDI registry application in two ways:
  • You can use a script that performs all the necessary steps.

    This script deploys the UDDI registry to a server that you specify.

  • You can use the administrative console. You deploy the UDDI registry application, the uddi.ear file, then complete additional steps, as described later in this topic. Alternatively, you can follow the same procedure using wsadmin scripting commands.

Procedure

  1. Optional: To deploy a UDDI registry application using the supplied script:
    1. [IBM i]Start a Qshell session by entering the STRQSH command from the IBM® i command line.
    2. Run the uddiDeploy.jacl wsadmin script as shown, from the app_server_root/bin directory.
      [AIX][HP-UX][Linux][Solaris]Note: For the UNIX or Linux operating systems, add the .sh suffix to the wsadmin command.
      [AIX Solaris HP-UX Linux Windows][IBM i]
      wsadmin [-conntype none] [-profileName profile_name] -f uddiDeploy.jacl 
              node_name server_name
      The attributes of the command are as follows:
      • -conntype none is optional, and is needed only if the application server is not running.
      • -profileName profile_name is optional, and is the name of the profile in which the UDDI application is deployed. If you do not specify a profile, the default profile is used.
      • node_name is the name of the WebSphere® Application Server node on which the target server runs. The node name is case sensitive.
      • server_name is the name of the target server on which you want to deploy the UDDI registry, for example, server1. The server name is case sensitive.
      [AIX Solaris HP-UX Linux Windows]For example, to deploy UDDI on the node MyNode and the server server1 on a Windows system, assuming that server1 is already started:
      wsadmin -f uddiDeploy.jacl MyNode server1
      [IBM i]For example, to deploy UDDI on the node MyNode and the server server1, assuming that server1 is already started:
      wsadmin -f uddiDeploy.jacl MyNode server1
  2. Optional: To deploy a UDDI registry application using the administrative console, use the following steps.
    1. Install the UDDI application (the uddi.ear file) to the server that you require.
    2. Click Applications > Application Types > WebSphere enterprise applications > uddi_application > [Detail Properties] Class loading and update detection.
    3. Ensure that Class loader order is set to Classes loaded with local class loader first (parent last).
    4. Ensure that WAR class loader policy is set to Single class loader for application.
    5. Click Apply, then save your changes to the master configuration.

What to do next

Continue setting up the UDDI node.

Ícone que indica o tipo de tópico Tópico de Tarefa



Ícone de registro de data e hora Última atualização: July 9, 2016 5:26
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-base-dist&topic=twsu_uddi_deploy
Nome do arquivo: twsu_uddi_deploy.html