Setting up a default UDDI node with a default data source

You can create a UDDI node with predetermined property values and an embedded Apache Derby database. You can do this to set up a UDDI registry quickly for test or development purposes.

About this task

When you set up a default UDDI node with a default data source, the mandatory node properties, such as node ID, are set automatically and you cannot change them. You run a single script to create the UDDI database and data source, and to deploy the UDDI registry application. This type of node is suitable for initial evaluation of the UDDI registry and for development and test purposes.

If you want to create a default UDDI node with an embedded Apache Derby database but a different data source, or with a different database, see Setting up a default UDDI node.

If you want to set up a UDDI node with your own properties, including the mandatory node properties, you must set up a customized node. See Configurando um Nó UDDI Customizado.

Procedure

  1. Create the UDDI node by running the wsadmin script uddiDeploy.jacl from the app_server_root/bin directory.

    [AIX Solaris HP-UX Linux Windows]For the UNIX or Linux operating systems, add the .sh suffix to the wsadmin command.

    Use the following syntax:[AIX Solaris HP-UX Linux Windows][IBM i]
    wsadmin [-conntype none] [-profileName profile_name] 
                   -wsadmin_classpath app_server_root/derby/lib 
                   -f uddiDeploy.jacl 
                   node_name 
                   server_name
                   default
    where:
    • -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.
    • -conntype none is optional, and is needed only if the application server is not running.
    • app_server_root is the directory name of the WebSphere® Application Server installation location.
    • node_name is the name of the WebSphere node on which the target server runs. Note that the node name is case sensitive.
    • server_name is the name of the target server that deploys the UDDI registry, for example, server1. The server name is case sensitive.
    • default creates a UDDI node with default policies in an Apache Derby database and data source. This option is specific to the Apache Derby database only and creates everything required to run a UDDI node.
      If the Apache Derby database already exists, you are asked if you want to re-create it. If you choose to re-create the database, the existing database is deleted and a new one is created in its place. If you choose not to re-create the database, the command exits and a new database is not created.
      Note: If the application server has already accessed the existing Apache Derby database, the uddiDeploy.jacl script cannot re-create the database. Use the uddiRemove.jacl script to remove the database, as described in the topic about removing a UDDI registry node, restart the server, and run the uddiDeploy.jacl script again.
    For example, to create a UDDI node named MyNode on a server named server1 when server1 is started, you might enter the following command. Enter the command on a single line.[AIX Solaris HP-UX Linux Windows]
    wsadmin -wsadmin_classpath C:\Progra~1\IBM\WebSphere\AppServer\derby\lib 
    -f uddiDeploy.jacl MyNode server1 default
    [IBM i]
    wsadmin -profileName myProfile -wsadmin_classpath /QIBM/ProdData/WebSphere/
    AppServer/was_version/Base/derby/lib -f uddiDeploy.jacl MyNode server1 default
    To create a UDDI node named MyNode on a server named server1 when server1 is not started, you might enter the following command. Enter the command on a single line.[AIX Solaris HP-UX Linux Windows]
    wsadmin -conntype none -wsadmin_classpath C:\Progra~1\IBM\WebSphere\AppServer\
    derby\lib -f uddiDeploy.jacl MyNode server1 default
    [IBM i]
    wsadmin -conntype none -profileName myProfile -wsadmin_classpath /QIBM/ProdData/
    WebSphere/AppServer/was_version/Base/derby/lib -f uddiDeploy.jacl MyNode server1 default
  2. [AIX][HP-UX][Linux][Solaris]Para um banco de dados DB2®, pare o servidor se ele estiver em execução. Edite o perfil do usuário do DB2 que inicia o o servidor. Modifique o perfil do usuário para executar o script db2profile, que está localizado no diretório-raiz do ID do usuário do DB2 (por exemplo, /home/db2inst1/sqllib/db2profile). Como alternativa, você pode executar o script db2profile manualmente, mas deverá fazer isso toda vez que reiniciar o o servidor. Insira o seguinte comando (há um único caractere de espaço após o ponto neste comando):
    . /home/db2inst1/sqllib/db2profile
  3. Clique em Aplicativos > Tipos de Aplicativos > Aplicativos Corporativos WebSphere para exibir os aplicativos instalados. Inicie o aplicativo de registro UDDI selecionando a caixa de opção junto ao nome do aplicativo e clicando em Iniciar. Como alternativa, se o servidor de aplicativo não estiver em execução ainda, inicie-o. Essa ação inicia automaticamente o aplicativo de registro UDDI. O nó de UDDI agora está ativo.

    Se você reiniciar o aplicativo UDDI ou o servidor de aplicativos, o nó UDDI sempre será reativado, mesmo que o nó tenha sido desativado anteriormente.

  4. Click UDDI > UDDI Nodes > UDDI_node_id to display the properties page for the UDDI registry node. Set Prefix for generated discoveryURLs to a valid URL for your configuration. This property specifies the URL prefix that is applied to generated discovery URLs that are used by the HTTP GET service for UDDI Version 2.

What to do next

Follow the instructions in Using the UDDI registry installation verification test (IVT) to verify that you have successfully set 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_default_install1
Nome do arquivo: twsu_default_install1.html