Tib Amx Administration Tutorials

7/28/2019 Tib Amx Administration Tutorials

1/78

TIBCO ActiveMatrix

BPMAdministration Tutorials

Software Release 1.3

March 2012


2/78


3/78

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR

BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ONFUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT

LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE

AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE

IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED

DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE

FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE

AGREEMENT, THE LICENSE(S) LOCATED IN THE LICENSE FILE(S) OF THE SOFTWARE. USE OF THIS

DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE

ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.

This document contains confdential information that is subject to U.S. and international copyright laws and treaties. No part

of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.

TIBCO, The Power of Now, TIBCO ActiveMatrix, and TIBCO Enterprise Message Service are either registered trademarks

or trademarks of TIBCO Software Inc. in the United States and/or other countries.

EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems,

Inc. in the U.S. and other countries.

All other product and company names and marks mentioned in this document are the property of their respective owners and

are mentioned for identifcation purposes only.

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING

SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE

README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM

PLATFORM.

THIS DOCUMENT IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,

INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A

PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES

ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN

NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES

IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.

THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY,

BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO

ANY RELEASE NOTES AND "READ ME" FILES.

Copyright (c) 2005-2012 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confdential Information

TIBCO ActiveMatrix BPM Administration Tutorials


4/78


5/78

Contents

Preface..................................................................................................7

Changes from the Previous Release of this Guide..................................................................8

TIBCO Product Documentation................................................................................................9

Other TIBCO Product Documentation....................................................................................10

Third-Party Documentation....................................................................................................11

Typographical Conventions....................................................................................................12

Connecting with TIBCO Resources........................................................................................15

Chapter 1 Overview.........................................................................17

Chapter 2 Tutorial Prerequisites ...................................................19

Set Up the Runtime Environment...........................................................................................20

Create a UDDI Server in Administrator..................................................................................21

Configure Administrator Command-Line Properties..............................................................22

Set Up the Service Invocation Environment...........................................................................23

Chapter 3 How to Configure Logging............................................25

Create a Logging Appender...................................................................................................26

Navigate to a Logging Configurations List..............................................................................27

Create a Logging Configuration.............................................................................................28

Apply a Logging Configuration...............................................................................................29

Chapter 4 How to Deploy and Run the Hello World Application...31

Complete Hello World Prerequisites.......................................................................................32

Create the Hello World Application.........................................................................................33

Create an HTTP Connector Resource Template....................................................................34

Create and Install the HTTP Connector Resource Instance..................................................35

Distribute the Hello World Application....................................................................................36

Deploy and Start the Hello World Application.........................................................................37Generate the Hello World WSDL File.....................................................................................38

Invoke the Hello World Service..............................................................................................39

How to View the Hello World Service in the UDDI Server .....................................................40

Chapter 5 How to Deploy and Run the Enhanced Hello World Application.41

Complete Enhanced Hello World Prerequisites.....................................................................42

Deploy and Start the Date Manager Application....................................................................43


TOC | 5


6/78

Create the Hello World Application.........................................................................................44



Create and Install the HTTP Client Resource Instance..........................................................47

Distribute the Enhanced Hello World Application...................................................................48

Deploy and Start the Enhanced Hello World Application.......................................................49

Generate the Hello World WSDL File.....................................................................................50Invoke the Hello World Service..............................................................................................51

Chapter 6 How to Deploy and Run the Phonebook Application..53

Complete Phonebook Prerequisites.......................................................................................54

Create the Phonebook Application.........................................................................................55



Create and Install the JDBC Shared Resource Instance.......................................................58

Distribute the Phonebook Application....................................................................................59

Deploy and Start the Phonebook Application.........................................................................60

Generate the Phonebook WSDL File.....................................................................................61

Invoke the Phonebook Service...............................................................................................62

Chapter 7 How to Deploy and Run the Hello World Web Application.63

Complete Hello World Web Application Prerequisites............................................................64

Create the Hello World Web Application................................................................................65



Distribute the Hello World Web Application............................................................................68

Deploy and Start the Hello World Web Application................................................................69

Invoke the Hello World Web Application.................................................................................70

Chapter 8 How to Deploy and Run the Content-Based Routing Mediation Application.71

Create the Routing and Target Service Mediation Applications.............................................72

Create HTTP Connector Resource Templates.......................................................................73

Create and Install Resource Instances..................................................................................74

Distribute the Routing and Target Service Applications..........................................................75

Deploy and Start the Routing and Target Service Applications..............................................76Generate the Routing WSDL File...........................................................................................77


6 | TOC


7/78

Preface

TIBCO ActiveMatrix BPM is a scalable and extensible platform for developing, deploying, and managing applications

that conform to a service-oriented architecture.



8/78

Changes from the Previous Release of this Guide

This section itemizes the major changes from the previous release of this guide.


8 | Preface


9/78

TIBCO Product Documentation

The following documents form the TIBCO ActiveMatrix BPM documentation set:

Concepts: Read this manual before reading any other manual in the documentation set. This manual describes

terminology and concepts of the TIBCO ActiveMatrix platform. The other manuals in the documentation set assume

you are familiar with the information in this manual. Development Tutorials: Read this manual for a step-by-step introduction to the process of creating, packaging, and

running composites in TIBCO Business Studio.

Composite Development: Read this manual to learn how to develop and package composites.

Java Component Development: Read this manual to learn how to confgure and implement Java components.

Mediation Component Development: Read this manual to learn how to confgure and implement Mediation

components.

Mediation API Reference: Read this manual to learn how to confgure and implement Mediation components.

Web Application Component Development: Read this manual to learn how to confgure and implement Web

Application components.

Administration Tutorials: Read this manual for a step-by-step introduction to the process of creating and starting the

TIBCO ActiveMatrix runtime, starting TIBCO ActiveMatrix servers, and deploying applications to the runtime.

Administration: Read this manual to learn how to manage the runtime and deploy and manage applications.

Solutions: Read this manual to learn how to perform tasks that span the design and administration tools.

Installation and Confguration: Read this manual to learn how to install TIBCO ActiveMatrix BPM software and

create and upgrade runtime objects.

Release Notes: Read this manual for a list of new and changed features, steps for migrating from a previous release,

and lists of known issues and closed issues for the release.

The documentation for the following features is installed separately:

TIBCO ActiveMatrix Implementation Type for C++

TIBCO ActiveMatrix Binding Type for EJB

TIBCO ActiveMatrix Binding Type for Adapters


Preface | 9


10/78

Other TIBCO Product Documentation

You may fnd it useful to read the documentation for the following TIBCO products:

TIBCO Enterprise Message Service


10 | Preface


11/78

Third-Party Documentation

Service Component Architecture

Service Assembly Model V1.00

Policy Framework V1.00

Transaction Policy V1.00 Java Component Implementation V1.00

Java Common Annotations and APIs V1.00

Java EE Integration V1.00

JMS Binding V1.00

World Wide Web Consortium Web Services

WSDL 1.1

SOAP 1.1

Web Services Addressing

OASIS

Web Services Reliable Messaging 1.2

UDDI Version 3

Internet Engineering Task Force

SMTP RFC 5321

LDAP RFC 4510

Java Community Process

JDBC 4.0

JMS 1.1

Hibernate


Preface | 11
http://www.osoa.org/download/attachments/35/SCA_AssemblyModel_V100.pdf?version=1http://www.osoa.org/download/attachments/35/SCA_Policy_Framework_V100.pdf?version=1http://www.osoa.org/download/attachments/35/SCA_TransactionPolicy_V1.0.pdf?version=1http://www.osoa.org/download/attachments/35/SCA_JavaComponentImplementation_V100.pdf?version=1http://www.osoa.org/download/attachments/35/SCA_JavaAnnotationsAndAPIs_V100.pdf?version=1http://www.osoa.org/download/attachments/35/SCA_JAVAEE_Integration_V100.pdf?version=1http://www.osoa.org/download/attachments/35/SCA_JMSBinding_V100.pdf?version=2http://www.w3.org/TR/wsdlhttp://www.w3.org/TR/2000/NOTE-SOAP-20000508/http://www.w3.org/Submission/ws-addressing/http://docs.oasis-open.org/ws-rx/wsrm/200702http://www.oasis-open.org/specs/index.php#uddiv2http://tools.ietf.org/html/rfc5321http://tools.ietf.org/html/rfc4510http://jcp.org/en/jsr/detail?id=221http://jcp.org/en/jsr/detail?id=914http://www.hibernate.org/http://www.hibernate.org/http://jcp.org/en/jsr/detail?id=914http://jcp.org/en/jsr/detail?id=221http://tools.ietf.org/html/rfc4510http://tools.ietf.org/html/rfc5321http://www.oasis-open.org/specs/index.php#uddiv2http://docs.oasis-open.org/ws-rx/wsrm/200702http://www.w3.org/Submission/ws-addressing/http://www.w3.org/TR/2000/NOTE-SOAP-20000508/http://www.w3.org/TR/wsdlhttp://www.osoa.org/download/attachments/35/SCA_JMSBinding_V100.pdf?version=2http://www.osoa.org/download/attachments/35/SCA_JAVAEE_Integration_V100.pdf?version=1http://www.osoa.org/download/attachments/35/SCA_JavaAnnotationsAndAPIs_V100.pdf?version=1http://www.osoa.org/download/attachments/35/SCA_JavaComponentImplementation_V100.pdf?version=1http://www.osoa.org/download/attachments/35/SCA_TransactionPolicy_V1.0.pdf?version=1http://www.osoa.org/download/attachments/35/SCA_Policy_Framework_V100.pdf?version=1http://www.osoa.org/download/attachments/35/SCA_AssemblyModel_V100.pdf?version=1


12/78

Typographical Conventions

Table 1: General Typographical Conventions

UseConvention

TIBCO products are installed into an installation environment. A product installed into an installation

environment does not access components in other installation environments. Incompatible products

TIBCO_HOME

ENV_NAMEand multiple instances of the same product must be installed into different installation environments.

An installation environment consists of the following properties:

Name Identifes the installation environment. The name is appended to the name of Windows

services created by the installer and is a component of the path to the product shortcut in the

Windows Start > All Programs menu. This name is referenced in documentation as ENV_NAME.

Path The folder into which the product is installed. This folder is referenced in documentation

as TIBCO_HOME. For example, on Windows systems the default value is C:\Program

Files\tibco\amx-3.

A TIBCO confguration folder stores confguration data generated by TIBCO products.Confguration data can include sample scripts, session data, confgured binaries, logs, and so on.

CONFIG_HOME

This folder is referenced in documentation as CONFIG_HOME. On Windows platforms, the default

location of the folder is userHome\Application Data\amx-3\data.

Code font identifes commands, code examples, flenames, pathnames, and output displayed in a

command window. For example:

code font

Use MyCommand to start the foo process.

Code example:

public class HelloWorldImpl extends AbstractHelloWorldImpl {...

public HelloResponseDocument sayHello(HelloRequestDocumentfirstName) {

...System.out.println("--> Generating Java Hello Component

Response...");

String name =firstName.getHelloRequest()==null||firstName.getHelloRequest().

equals("")?"Friend":firstName.getHelloRequest();HelloResponseDocument resp =

HelloResponseDocument.Factory.newInstance();resp.setHelloResponse("Hi " + name + "! " + "This is the Java

component.\n");

System.out.println("--> Java Hello Component Response: \n\t\t"+

resp.getHelloResponse());...

}}

CONFIG_HOME/admin/enterpriseName/samples/remote_props.properties

Output example:

C:\Program Files\tibco\amx-3\studio\3.5\eclipse>amx_eclipse_ant.exe-buildfile "C:/helloworld1/build.xml" -data "C:/hws"Buildfile: C:/helloworld1/build.xml

createApplicationDAA:[sds.createDAA] Waited for 47ms for workspace refreshes after building


12 | Preface


13/78

UseConvention

features.

all:BUILD SUCCESSFUL

BUILD SUCCESSFULTotal time: 2 minutes 18 seconds

Bold code font is used in the following ways:bold code font

In procedures, to indicate what a user types. For example: Type admin.

In large code samples, to indicate the parts of the sample that are of particular interest.

In command syntax, to indicate the default parameter for a command. For example, if no

parameter is specifed, MyCommand is enabled:

MyCommand [enable | disable]

Italic font is used in the following ways:italic font

To indicate a document title. For example: See TIBCO BusinessWorks Concepts.

To defne new terms. For example: A portal page may contain several portlets. Aportletis a

mini-application that runs in a portal.

To indicate a variable in a command or code syntax that you must replace. For example:

MyCommand pathname.

Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C.Key combinations

Key names separated by a comma and space indicate keys pressed one after the other. For example:

Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, for example, an

additional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to apply the information

provided in the current section to achieve a specifc result.

The warning icon indicates the potential for a damaging situation, for example, data loss or

corruption if certain steps are taken or not taken.

Table 2: Syntax Typographical Conventions

UseConvention

An optional item in command syntax.[ ]

For example:

MyCommand [optional_parameter] required_parameter

A logical OR that separates multiple items of which only one may be chosen.|

For example, you can select only one of the following parameters:

MyCommand param1 | param2 | param3

A logical group of items in a command. Other syntax notations may appear within each logical

group.

{ }


Preface | 13


14/78

UseConvention

For example, the following command requires two parameters, which can be either the pair param1

and param2, or the pair param3 and param4.

MyCommand {param1 param2} | {param3 param4}

In the next example, the command requires two parameters. The frst parameter can be either

param1 or param2 and the second can be either param3 or param4:

MyCommand {param1 | param2} {param3 | param4}

In the next example, the command can accept either two or three parameters. The frst parameter

must be param1. You can optionally include param2 as the second parameter. And the last parameter

is either param3 or param4.

MyCommand param1 [param2] {param3 | param4}


14 | Preface


15/78

Connecting with TIBCO Resources

How to Join TIBCOmmunity

TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts, a place to share and access

the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety ofresources. To register, go to http://www.tibcommunity.com .

How to Access All TIBCO Documentation

After you join TIBCOmmunity, you can access the documentation for all supported product versions here:

http://docs.tibco.com/TibcoDoc.

How to Contact TIBCO Support

For comments or problems with this manual or the software it addresses, please contact TIBCO Support as follows:

For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site:

http://www.tibco.com/services/support If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a username and password. If you do not have a username, you can request one.


Preface | 15
http://www.tibcommunity.com/http://docs.tibco.com/TibcoDochttp://www.tibco.com/services/supporthttps://support.tibco.com/https://support.tibco.com/http://www.tibco.com/services/supporthttp://docs.tibco.com/TibcoDochttp://www.tibcommunity.com/


16/78


17/78

Chapter

1Overview

These tutorials demonstrate how to deploy and run SOA applications developed in TIBCO Business Studio in TIBCO

ActiveMatrix Administrator and send SOAP requests from the TIBCO Business Studio Web Services Explorer.

Tutorial Facts lists the location of the sample projects, the names of the deployed applications, and the ports of the HTTP

connector resources used by the applications. . Before proceeding with a tutorial, complete the steps in Tutorial Prerequisites

on page 19.

Table 3: Tutorial Facts

PortsDeployed ApplicationsSample Project LocationTutorial

9095helloworld1TIBCO_HOME/amx/1.3/samples

/java/helloworld1.zip

Hello World

9096helloworld2TIBCO_HOME/amx/1.3/samples/java/helloworld2.zipEnhanced Hello World

9097datemanager

9098phonebookTIBCO_HOME/amx/1.3/samples/java/phonebook.zipPhonebook

9099helloworldTIBCO_HOME/amx/1.3/samples/amx_it_webapp/helloworld.zipHello World Web

Application

8777querygdsTIBCO_HOME/amx_it_mediation/3.2/samples/ContentBasedRoutingContent-Based Routing

8666targetserviceTIBCO_HOME/amx_it_mediation/3.2/samples/TargetService



18/78


19/78

Chapter

2Tutorial Prerequisites

Topics

Set Up the Runtime Environment

Create a UDDI Server in Administrator

Configure Administrator Command-Line Properties

Set Up the Service Invocation Environment



20/78

Set Up the Runtime Environment

About this task

Procedure

1. Create and start a TIBCO ActiveMatrix Administrator server as described in the installation manual for your product.

When you create the Administrator server, create a development node and accept the default values for the environment

and node names.

2. Invoke the TIBCO ActiveMatrix Administrator GUI. The URL is

http://machinename:port//amxadministrator/loginForm.jsp, where machinename is the machine on which you

created Administrator server and port is the port on which Administrator clients access the Administrator server .

3. Log in with the credentials you specifed when you created the Administrator server.

After successful login, Administrator displays the Welcome screen.

4. If you want to register deployed services in a UDDI registry, install and start TIBCO ActiveMatrix Runtime UDDI

Server.


20 | Tutorial Prerequisites


21/78

Create a UDDI Server in Administrator

Procedure

1. In the Administrator GUI, select Infrastructure > Servers.

2.Click .

The New Server dialog displays.

3. In the Name feld, type SOAUDDI.

4. In the Type feld, ensure that UDDI is selected.

5. In the UDDI Server Type feld, select TIBCO.

6. In the Hostname/IP feld, type the name of the host on which the UDDI server is running.

7. In the Port feld, type 58080.

8. In the Username and Password felds, type admin and admin.

9. Click the Test Connection button.

10. In the Publication Business drop-down list, type Services deployed in TIBCO ActiveMatrix.11. Check the Automatic Publication checkbox.

12. ClickSave.

ResultsWhen you deploy an application, Administrator will publish the endpoints exposed by the application in the UDDI

server.


Tutorial Prerequisites | 21


22/78

Configure Administrator Command-Line Properties

Procedure

1. In a terminal window, open CONFIG_HOME/ admin/enterpriseName/samples/remote_props.properties

in a text editor.

a) Replace the host portion of the value of the adminURL property with the host on which the Administrator server

is running.

b) Replace the port portion of the value of the adminURL property with the port on which the Administrator server

is running.

c) Replace the username and password properties with the credentials you specifed when you created the

Administrator server.

2. Save the properties fle.


22 | Tutorial Prerequisites


23/78

Set Up the Service Invocation Environment

About this task

Create a project in TIBCO Business Studio to contain the concrete WSDL fles of deployed service bindings. To test a

deployed service, you open the concrete WSDL fle in the TIBCO Business Studio Web Services Explorer and generateSOAP requests.

Procedure

1. Start TIBCO Business Studio.

2. Select File > New > Project....

The New Project wizard displays.

3. Select General > Project and clickNext >.

4. In the File name feld, type ConcreteWSDLs and clickFinish.

A general project named ConcreteWSDLs displays in the Project Explorer view.


Tutorial Prerequisites | 23


24/78


25/78

Chapter

3How to Configure Logging

Topics

Create a Logging Appender

Navigate to a Logging Configurations List

Create a Logging Configuration

Apply a Logging Configuration



26/78

Create a Logging Appender

Procedure

1. Select Shared Objects > Logging Appenders.

2.Click .

The Add Logging Appenders dialog displays.

3. In the Name column, type a name for the appender.

4. In the Type drop-down list, select an appender type.

Clear Text File - Appends events to a fle in clear text format.

CBE XML File - Appends events to a fle in Common Base Event (CBE) format.

JMS - Append events to a log service.

Appender-specifc felds display.

5. Fill in the felds and clickSave.

The appender is added to the Logging Appenders table and is selected.

Results


26 | How to Configure Logging
http://www.eclipse.org/tptp/platform/documents/resources/cbe101spec/CommonBaseEvent_SituationData_V1.0.1.pdfhttp://www.eclipse.org/tptp/platform/documents/resources/cbe101spec/CommonBaseEvent_SituationData_V1.0.1.pdf


27/78

Navigate to a Logging Configurations List

Procedure

1. Navigate to a list of hosts, nodes, or applications.

2. Click a host, node, or application.

3. Click the Confguration tab.

4. Click the Logging Confgurations link.

The logging confgurations table for the host, node, or application displays.


How to Configure Logging | 27


28/78

Create a Logging Configuration

Procedure

1. Navigate to a logging confgurations list.

2. ClickAdd.

A row is added to the list.

3. In the Logger Name column, type a logging confguration name.

4. In the Additivity column, select an additivity.

5. ClickAdd Child.

A row is added to the list.

6. In the Level column, select a logging level.

7. In the Appender column, select an appender.

8. ClickSave.

9. Optionally, clickApply.


28 | How to Configure Logging


29/78

Apply a Logging Configuration

Procedure

1. Select the object for which logging is being confgured.

2. Navigate to a logging confgurations list and click a logging confguration.

3. ClickApply.


How to Configure Logging | 29


30/78


31/78

Chapter

4How to Deploy and Run the Hello World Application

This how-to describes how to deploy and run the Hello World application in TIBCO ActiveMatrix Administrator.

Topics

Complete Hello World Prerequisites

Create the Hello World Application

Create an HTTP Connector Resource Template

Create and Install the HTTP Connector Resource Instance

Distribute the Hello World Application Deploy and Start the Hello World Application

Generate the Hello World WSDL File

Invoke the Hello World Service

How to View the Hello World Service in the UDDI Server



32/78

Complete Hello World Prerequisites

Procedure

In TIBCO Business Studio, create a distributed application archive (DAA) by following the instructions in the How

To Create and Package a Hello World Application TIBCO Business Studio cheat sheet or extract

jv.helloworld1.soa/Deployment Artifacts/jv.helloworld1.soa.daa from helloworld1.zip.


32 | How to Deploy and Run the Hello World Application


33/78


Procedure

1. ClickApplications.

The Applications list displays.

2.Click .

The Application Setup wizard displays.

3. In the Application Name feld, type helloworld1.

4. In the Environment Name drop-down list, select DevEnvironment.

5. Click the Upload a DAA fle radio button.

6. ClickNext.

7. Click the Browse button next to the Upload DAA feld.

8. Navigate to the folder containing the fle jv.helloworld1.soa.daa, click the DAA, and clickOpen.

9. ClickNext three times.

10. ClickSave And Exit.

The helloworld1 application is added to the Applications list with Runtime State Not Deployed.


How to Deploy and Run the Hello World Application | 33


34/78


Procedure

1. Select Shared Objects > Resource Templates.

2.Click .

The Add Resource Template dialog displays.

3. In the Name feld, type hello1Connector.

4. In the Type drop-down list, select HTTP Connector.

The HTTP connector confguration felds display.

5. Accept the default Machine Name.


7. ClickSave.




35/78


Procedure

1. Select Infrastructure > Hosts.

2. In the Hosts list, clickSystemHost.

The host details display below the list.

3. Click the Resource Instances tab.

The All Instances list displays.

4. ClickNew.

The New Resource Instances dialog displays.

5. In the resource templates list at the top, click the hello1Connector row. The Instance Name feld is set to

hello1Connector.

6.In the Available Nodes list at the bottom, clickDevNode and click .

The node moves to the Selected Nodes list.

7. ClickSave and Close.The hello1Connector resource instance is added to the All Instances table with status NOT_INSTALLED. The Install

Resource Instances dialog displays with the hello1Connector clicked.

8.Click .

The Resource Instances list displays.

9. Click until the status changes to Running.




36/78

Distribute the Hello World Application

Procedure


2. In the Applications list, clickhelloworld1.

3. Click the Distribution tab.

4. Clickhelloworld1.

5.In the Available Nodes list, clickDevNode and click .


6. ClickSave.




37/78

Deploy and Start the Hello World Application

Procedure

1. ClickDeploy.

The application is deployed and started. If you have completed Create a UDDI Server in Administrator on page 21,

the WSDL fle is published in the UDDI server.

2. Click to refresh the display.

The Runtime State changes to Starting and the Action History changes to In Progress (Deploy).


The Runtime State changes to Running and the Action History changes to Deploy with Start Successful.




38/78


Procedure


2. Expand the helloworld1 node.

3. Click the HelloWorldPT service.

The service details display on the right.

4. Click the Bindings link.

The service's binding details display.

5. In the list of bindings, expand HelloWorld1SOAP.

The list of nodes on which the binding is deployed displays below.

6. In the node list, clickDevNode.

The Generate WSDL button activates.

7. ClickGenerate WSDL.

The WSDL document representing the deployed service displays.

8. Save the WSDL fle with the name helloworld1.wsdl in the ConcreteWSDLs project in TIBCO Business Studio.




39/78


Procedure

1. In TIBCO Business Studio, right-clickConcrete WSDLs/helloworld1.wsdl and select Web Services > Test

with Web Services Explorer.

The WSDL fle opens in the Web Services Explorer.

2. In the Navigator pane, expand the HelloWorld1SOAP node.

3. Click the sayHello node.

The Invoke a WSDL Operation displays on the right with the newly created endpoint selected in the Endpoints

drop-down list.

4. In the Actions pane, type Jimin the HelloRequest feld.

5. ClickGo.




40/78

How to View the Hello World Service in the UDDI Server

Procedure

1. Start the TIBCO ActiveMatrix UDDI Service Console GUI.

The Services Deployed in TIBCO ActiveMatrix business displays in the Service Console.

2. ClickDetails.

The details of the Services deployed in TIBCO ActiveMatrix business display.

3. In tree on the left, expand the helloworld1-HelloWorldPT node and click the binding template key under the node.

In the right pane, the General Information tab of the Binding Template displays the service access point

http://0.0.0.0:9095/helloWorldPT/.




41/78

Chapter

5How to Deploy and Run the Enhanced Hello WorldApplication

This how-to describes how to deploy and run the enhanced Hello World application in TIBCO ActiveMatrix Administrator.

Topics

Complete Enhanced Hello World Prerequisites

Deploy and Start the Date Manager Application




Create and Install the HTTP Client Resource Instance

Distribute the Enhanced Hello World Application

Deploy and Start the Enhanced Hello World Application





42/78

Complete Enhanced Hello World Prerequisites

Procedure

1. In TIBCO Business Studio, create a distributed application archive (DAA) by following the instructions in the How

To Enhance the Hello World Application TIBCO Business Studio cheat sheet or extract

jv.helloworld2.soa/Deployment Artifacts/jv.helloworld2.soa.daa from helloworld2.zip.

2. Extract datemgr_build.xml, datemgr_data.xml, and jv.datemanager.soa.daa from

jv.datemanager.soa/Deployment Artifacts/ from helloworld2.zip.

3. Edit datemgr_build.xml and replace all instances ofC:/amx-3/tibco/cfgmgmtwith the path of your

CONFIG_HOMEdirectory. Set the file attribute of the import element to

TIBCO_HOME/administrator/3.1/bin/taskdef.xml.


42 | How to Deploy and Run the Enhanced Hello World Application


43/78

Deploy and Start the Date Manager Application

Procedure

In a TIBCO ActiveMatrix terminal window, run ant -f datemgr_build.xml.

Buildfile: datemgr_build.xmlupload.daa:[AMXAdminTask] INFO - Processing 1 objects[AMXAdminTask] INFO - Uploading DAA...[AMXAdminTask] INFO - DAA location: jv.datemanager.soa.daa[AMXAdminTask] INFO - Successfully added Application Template 'jv.datemanager.soa'(version: '1.0.0.201005041043') to the Administrator Staging Area[AMXAdminTask] INFO - Successfully added Feature 'jv.datemanager.soa.customfeature.id'(version: '1.0.0.201005041043') to the Administrator Staging Area

create.app:[AMXAdminTask] INFO - Processing 1 objects[AMXAdminTask] INFO - Adding application...[AMXAdminTask] INFO - Successfully added Application 'datemanager'map.app.to.node:[AMXAdminTask] INFO - Processing 1 objects

[AMXAdminTask] INFO - Mapping application to nodes...[AMXAdminTask] INFO - Successfully mapped application 'datemanager' to node 'DevNode'

create.rt:[AMXAdminTask] INFO - Processing 1 objects[AMXAdminTask] INFO - HttpConnector Resource template created with nameDateMgrConnectorTemplate and Id 29create.ri:[AMXAdminTask] INFO - Processing 1 objects[AMXAdminTask] INFO - Adding Resource Instances...[AMXAdminTask] INFO - Resource Instance datemgrConnector created on Node DevNodeinstall.ri:[AMXAdminTask] INFO - Processing 1 objects[AMXAdminTask] INFO - Start to install Resource Instance 'datemgrConnector'[AMXAdminTask] INFO - Resource Instance Install finished successfullydeploy.app:

[AMXAdminTask] INFO - Processing 1 objects[AMXAdminTask] INFO - Deploying application...[AMXAdminTask] INFO - Successfully deployed Application 'datemanager': Deploymentsucceeded for application 'datemanager' at 05/03/10 4:04 PM[AMXAdminTask] INFO - .[AMXAdminTask] INFO - Application Deploy with Start finished successfully

all:

BUILD SUCCESSFUL


How to Deploy and Run the Enhanced Hello World Application | 43


44/78


Procedure


The Applications list displays. The datemanager application appears in the list with Runtime State Running.

2.Click .


3. In the Application Name feld, type helloworld2.



6. ClickNext.


8. Navigate to the folder containing the fle jv.helloworld2.soa.daa, click the DAA, and clickOpen.

9. ClickNextfve times.


The helloworld2 application is added to the Applications list with Runtime State Not Deployed.




45/78


Procedure

Follow the steps in Create an HTTP Connector Resource Template on page 34. In the Name feld, type

hello2Connector. In the Port feld, type 9096.




46/78


Procedure

Follow the steps in Create and Install the HTTP Connector Resource Instance on page 35. Use the template

hello2Connector.




47/78

Create and Install the HTTP Client Resource Instance

Procedure

Follow the steps in Create and Install the HTTP Connector Resource Instance on page 35. Use the

HttpClient_DateManagerSOAP template.




48/78

Distribute the Enhanced Hello World Application

Procedure

Follow the steps in Distribute the Hello World Application on page 36. Click the helloworld2 application and the

jv.helloworld2.soa component.




49/78

Deploy and Start the Enhanced Hello World Application

Procedure

1. ClickDeploy.










50/78


Procedure

Follow the steps in Generate the Hello World WSDL File on page 38. Click the HelloWorld2SOAP binding and

name the WSDL fle helloworld2.wsdl.




51/78


Procedure

Apply the steps in Invoke the Hello World Service on page 39 to helloworld2.wsdl.

The Status pane displays a response of the form:

HelloResponse (string): Hi Jim! This is the Java component.The current time is 2009-11-19 16:32:57.337.




52/78


53/78

Chapter

6How to Deploy and Run the Phonebook Application

This how-to describes how to deploy and run the Phonebook web application in TIBCO ActiveMatrix Administrator.

Topics

Complete Phonebook Prerequisites

Create the Phonebook Application



Create and Install the JDBC Shared Resource Instance Distribute the Phonebook Application

Deploy and Start the Phonebook Application

Generate the Phonebook WSDL File

Invoke the Phonebook Service



54/78

Complete Phonebook Prerequisites

Procedure

1. In TIBCO Business Studio, create a distributed application archive (DAA) by following the instructions in the How

to Create and Package the Phonebook Application TIBCO Business Studio cheat sheet or extract

jv.phonebook.soa/Deployment Artifacts/jv.phonebook.soa.daa from phonebook.zip.

2. Download HyperSQL Database Engine version 1.8.1.2 from

http://sourceforge.net/projects/hsqldb/fles/hsqldb/hsqldb_1_8_1/hsqldb_1_8_1_2.zip/download.

3. Unpackhsqldb-1.8.1.2.zip.

4. Change to the server directory: cd hsqldb/bin.

5. Start the HyperSQL database server: java -cp ../lib/hsqldb.jar org.hsqldb.Server.

The server outputs:

> java -cp ../lib/hsqldb.jar org.hsqldb.Server[Server@83cc67]: [Thread[main,5,main]]: checkRunning(false) entered[Server@83cc67]: [Thread[main,5,main]]: checkRunning(false) exited[Server@83cc67]: Startup sequence initiated from main() method

[Server@83cc67]: Loaded properties from [C:\Documents andSettings\sbodoff\Desktop\hsqldb\hsqldb\bin\server.properties][Server@83cc67]: Initiating startup sequence...[Server@83cc67]: Server socket opened successfully in 78 ms.[Server@83cc67]: Database [index=0, id=0, db=file:test, alias=] opened sucessfully in468 ms.

[Server@83cc67]: Startup sequence completed in 546 ms.[Server@83cc67]: 2010-05-04 14:06:10.923 HSQLDB server 1.8.1 is online[Server@83cc67]: To close normally, connect and execute SHUTDOWN SQL[Server@83cc67]: From command line, use [Ctrl]+[C] to abort abruptly


54 | How to Deploy and Run the Phonebook Application
http://sourceforge.net/projects/hsqldb/files/hsqldb/hsqldb_1_8_1/hsqldb_1_8_1_2.zip/downloadhttp://sourceforge.net/projects/hsqldb/files/hsqldb/hsqldb_1_8_1/hsqldb_1_8_1_2.zip/downloadhttp://sourceforge.net/projects/hsqldb/files/hsqldb/hsqldb_1_8_1/hsqldb_1_8_1_2.zip/downloadhttp://sourceforge.net/projects/hsqldb/files/hsqldb/hsqldb_1_8_1/hsqldb_1_8_1_2.zip/download


55/78

Create the Phonebook Application

Procedure



2.Click .


3. In the Application Name feld, typephonebook.



6. ClickNext.


8. Navigate to the folder containing the fle jv.phonebook.soa.daa, click the DAA, and clickOpen.

9. ClickNext four times.


The phonebook application is added to the Applications list with Runtime State Not Deployed. The specifed resource

templates are imported into the Administrator database.


How to Deploy and Run the Phonebook Application | 55


56/78


Procedure


phonebookConnector. In the Port feld, type 9098.




57/78


Procedure


phonebookConnector.




58/78

Create and Install the JDBC Shared Resource Instance

Procedure

Follow the steps in Create and Install the HTTP Connector Resource Instance on page 35. Use the template hsqldb

and specify the instance name hsqldb.




59/78

Distribute the Phonebook Application

Procedure

Follow the steps in Distribute the Hello World Application on page 36. Click the phonebook application and the

jv.phonebook.soa component.




60/78

Deploy and Start the Phonebook Application

Procedure

1. ClickDeploy.










61/78

Generate the Phonebook WSDL File

Procedure

Follow the steps in Generate the Hello World WSDL File on page 38. Click the PhonebookPT service, click the

PhonebookSOAP binding, and name the WSDL fle phonebook.wsdl.




62/78

Invoke the Phonebook Service

Procedure

1. Apply the steps in Invoke the Hello World Service on page 39 to phonebook.wsdl.

2. Click the addPhone node. In the Actions pane, enter values in the felds frstName: Joe, lastName: Doe, and phone:

111-1111.

The Status pane displays:

AddPhoneResponseentryId (string): 0

3. Click the getPhone node.

4. In the Invoke a WSDL Operation pane on the right, click the Add link next to the frstName feld.

A new row is added below the feld.

5. Type Joe in the empty row.

6. ClickGo.

The Status pane displays:

GetPhoneResponseoutentryId (string): 0

firstName (string): Joe

lastName (string): Doe

phone (string): 111-1111




63/78

Chapter

7How to Deploy and Run the Hello World Web Application

This how-to describes how to deploy and run the Hello World web application in TIBCO ActiveMatrix Administrator.

Topics

Complete Hello World Web Application Prerequisites

Create the Hello World Web Application



Distribute the Hello World Web Application Deploy and Start the Hello World Web Application

Invoke the Hello World Web Application



64/78

Complete Hello World Web Application Prerequisites

Procedure

In TIBCO Business Studio, create a distributed application archive (DAA) by following the instructions in the How

To Create and Package a Hello World Web Application TIBCO Business Studio cheat sheet or extract

webapp.helloworld.soa/Deployment Artifacts/webapp.helloworld.soa.daa from

helloworldwebapp.zip.


64 | How to Deploy and Run the Hello World Web Application


65/78

Create the Hello World Web Application

Procedure



2.Click .


3. In the Application Name feld, type helloworldwebapp.



6. ClickNext.


8. Navigate to the folder containing the fle webapp.helloworld.soa.daa, click the DAA, and clickOpen.


10. ClickSave and Exit.

webapp.helloworld.soa is added to the Applications list with Runtime State Not Deployed.


How to Deploy and Run the Hello World Web Application | 65


66/78


Procedure


WebAppHttpConnectorTemplate. In the Port feld, type 9099.




67/78


Procedure


WebAppHttpConnectorTemplate and specify the instance name webAppHttpConnector.




68/78

Distribute the Hello World Web Application

Procedure

Follow the steps in Distribute the Hello World Application on page 36. Click the helloworldwebapp application

and the webapp.helloworld.soa component.




69/78

Deploy and Start the Hello World Web Application

Procedure

1. ClickDeploy.










70/78

Invoke the Hello World Web Application

Procedure

In a browser, open the location: http://localhost:9099/helloworld/sayHello?frstName=Jim.

The response is: Hi Jim! This is the Web App component.




71/78

Chapter

8How to Deploy and Run the Content-Based RoutingMediation Application

This how-to describes how to deploy and run the content-based routing mediation application in TIBCO ActiveMatrix

Administrator.

Topics

Create the Routing and Target Service Mediation Applications

Create HTTP Connector Resource Templates

Create and Install Resource Instances

Distribute the Routing and Target Service Applications

Deploy and Start the Routing and Target Service Applications

Generate the Routing WSDL File



72/78

Create the Routing and Target Service Mediation Applications

Procedure


2.Click .


3. In the Application Name feld, type querygds.



6. ClickNext.


8. Navigate to

TIBCO_HOME\amx_it_mediation\3.3\samples\ContentBasedRouting\mediation.querygds.route.soa\Deployment

Artifacts\, clickmediation.querygds.route.daa, and clickOpen.



The querygds application is added to the Applications list with Runtime State Not Deployed and the resource templates

used by the application are added to the database.

11. Repeat steps 2 through 10 for the target service application. Name the application targetservice and use the DAA

TIBCO_HOME\amx_it_mediation\3.3\samples\TargetService\targetservice.soa\Deployment

Artifacts\targetservice.mediationsamples.daa.

The targetservice application is added to the Applications list with Runtime State Not Deployed.


72 | How to Deploy and Run the Content-Based Routing Mediation Application


73/78

Create HTTP Connector Resource Templates

Procedure

1. Select Shared Objects > Resource Templates.

2.Click .

3. In the Name feld, type httpConnector.

4. In the Type drop-down list, select HTTP Connector.

5. Accept the default Machine Name.


7. ClickSave.

8. Repeat the preceding steps for a template named httpConnectorTargetService with port 8666.


How to Deploy and Run the Content-Based Routing Mediation Application | 73


74/78

Create and Install Resource Instances

Procedure

1. Select Infrastructure > Hosts.

The Hosts list displays.

2. Click the Resource Instances tab.

The All Instances list displays.

3. ClickNew.

The New Resource Instances dialog displays.

4. In the Resource Templates list, click the httpConnector row.

The Instance Name feld is set to httpConnector.

5.In the Available Nodes list at the bottom, clickDevNode and click .


6. ClickSave and Close.

The httpConnector resource instance is added to the All Instances table with status NOT_INSTALLED.

7.Click the row containing httpConnector and click .

The Action History changes to In Progress (Install).

8. Click until the status changes to Running.

9. Repeat the preceding steps to create and install resource instances from the following resource templates:

httpConnectorTargetService

HttpClient_querygds.soap.binding

HttpClient_querygdsasia.soap.binding

HttpClient_querygdseurope.soap.binding

HttpClient_querygdsus.soap.binding




75/78

Distribute the Routing and Target Service Applications

Procedure


2. In the Applications list, clickquerygds.

3. Click the Distribution tab.

4.In the Available Nodes list, clickDevNode and click .


5. ClickSave.

6. Repeat the preceding steps for the targetservice application.




76/78

Deploy and Start the Routing and Target Service Applications

Procedure

1. In the Applications list, select querygds and targetservice.

2. ClickDeploy.

The applications are deployed and started.








77/78

Generate the Routing WSDL File

Procedure


2. Expand the querygds node.

3. Click the QueryGDS service.

The service details display on the right.

4. Click the Bindings link.

The service's binding details display.

5. In the list of bindings, expand SOAPService_Binding1.

The list of nodes on which the binding is deployed displays below.

6. In the node list, clickDevNode.

The Generate WSDL button activates.

7. ClickGenerate WSDL.

The WSDL document representing the deployed service displays.

8. Save the WSDL fle with the name QueryGDS_gen.wsdlin the ConcreteWSDLs project in TIBCO Business Studio.




78/78

Date post:	03-Apr-2018
Category:	Documents
Upload:	215prasad
View:	228 times
Download:	0 times