TIBCO ActiveMatrix® BPM SOA Administration … › pub › › activematrix_bpm ›...

TIBCO ActiveMatrix® BPM SOAAdministration TutorialsSoftware Release 2.1.0February 2013

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED ORBUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ONFUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOTLICENSED 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 LICENSEAGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THEREIS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYEDDURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSEFILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSEAGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THISDOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTEACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.

This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No partof 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 trademarksor 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 andare mentioned for identification purposes only.

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATINGSYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THEREADME FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEMPLATFORM.

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 APARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGESARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED INNEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGESIN 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 TOANY RELEASE NOTES AND "READ ME" FILES.

Copyright (c) 2005-2013 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information

TIBCO ActiveMatrix BPM SOA Administration Tutorials

Contents

Preface..................................................................................................7Changes 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 ...................................................19Set 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............................................25Create 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...31Complete 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.........................................................................37

Generate 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.41Complete Enhanced Hello World Prerequisites.....................................................................42

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


TOC | 5

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.....................................................................................50

Invoke the Hello World Service..............................................................................................51

Chapter 6 How to Deploy and Run the Phonebook Application..53Complete 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.63Complete 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.71Create 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..............................................76

Generate the Routing WSDL File...........................................................................................77


6 | TOC

Preface

TIBCO ActiveMatrix® BPM is a scalable and extensible platform for developing, deploying, and managing applicationsthat conform to a service-oriented architecture.


Changes from the Previous Release of this Guide

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


8 | Preface

TIBCO Product Documentation

The following documents form the TIBCO ActiveMatrix® BPM documentation set:

• SOA Concepts: Read this manual before reading any other manual in the documentation set. This manual describesterminology and concepts of the TIBCO ActiveMatrix platform. The other manuals in the documentation set assumeyou 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, andrunning 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 configure and implement Java components.• Mediation Component Development: Read this manual to learn how to configure and implement Mediation

components.• Mediation API Reference: Read this manual to learn how to configure and implement Mediation components.• Web Application Component Development: Read this manual to learn how to configure and implement Web

Application components.• SOA 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.• SOA 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 Configuration: 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

Other TIBCO Product Documentation

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

• TIBCO Enterprise Message Service™


10 | Preface

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=1

http://www.osoa.org/download/attachments/35/SCA_Policy_Framework_V100.pdf?version=1

http://www.osoa.org/download/attachments/35/SCA_TransactionPolicy_V1.0.pdf?version=1

http://www.osoa.org/download/attachments/35/SCA_JavaComponentImplementation_V100.pdf?version=1

http://www.osoa.org/download/attachments/35/SCA_JavaAnnotationsAndAPIs_V100.pdf?version=1

http://www.osoa.org/download/attachments/35/SCA_JAVAEE_Integration_V100.pdf?version=1

http://www.osoa.org/download/attachments/35/SCA_JMSBinding_V100.pdf?version=2

http://www.w3.org/TR/wsdl

http://www.w3.org/TR/2000/NOTE-SOAP-20000508/

http://www.w3.org/Submission/ws-addressing/

http://docs.oasis-open.org/ws-rx/wsrm/200702

http://www.oasis-open.org/specs/index.php#uddiv2

http://tools.ietf.org/html/rfc5321

http://tools.ietf.org/html/rfc4510

http://jcp.org/en/jsr/detail?id=221

http://jcp.org/en/jsr/detail?id=914

http://www.hibernate.org/

Typographical Conventions

Table 1: General Typographical Conventions

UseConvention

TIBCO products are installed into an installation environment. A product installed into an installationenvironment 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 Identifies the installation environment. The name is appended to the name of Windowsservices created by the installer and is a component of the path to the product shortcut in theWindows 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 documentationas TIBCO_HOME. For example, on Windows systems the default value is C:\ProgramFiles\tibco\amx-3.

A TIBCO configuration folder stores configuration data generated by TIBCO products.Configuration data can include sample scripts, session data, configured binaries, logs, and so on.

CONFIG_HOME

This folder is referenced in documentation as CONFIG_HOME. On Windows platforms, the defaultlocation of the folder is userHome\Application Data\amx-3\data.

Code font identifies commands, code examples, filenames, pathnames, and output displayed in acommand window. For example:

code font

• Use MyCommand to start the foo process.• Code example:

public class HelloWorldImpl extends AbstractHelloWorldImpl {... public HelloResponseDocument sayHello(HelloRequestDocument firstName) { ... 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

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 specified, 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 define new terms. For example: A portal page may contain several portlets. A portlet is 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, anadditional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to apply the informationprovided in the current section to achieve a specific result.

The warning icon indicates the potential for a damaging situation, for example, data loss orcorruption 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 logicalgroup.

{ }


Preface | 13

UseConvention

For example, the following command requires two parameters, which can be either the pair param1and param2, or the pair param3 and param4.

MyCommand {param1 param2} | {param3 param4}

In the next example, the command requires two parameters. The first parameter can be eitherparam1 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 first parametermust be param1. You can optionally include param2 as the second parameter. And the last parameteris either param3 or param4.

MyCommand param1 [param2] {param3 | param4}


14 | Preface

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 accessthe 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/TibcoDoc

http://www.tibco.com/services/support

https://support.tibco.com

Chapter

1Overview

These tutorials demonstrate how to deploy and run SOA applications developed in TIBCO Business Studio in TIBCOActiveMatrix 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 HTTPconnector resources used by the applications. . Before proceeding with a tutorial, complete the steps in Tutorial Prerequisiteson page 19.

Table 3:Tutorial Facts

PortsDeployedApplications

Sample Project LocationTutorial

9095helloworld1TIBCO_HOME/amx/2.1/samples /java/helloworld1.zipHello World

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

9097datemanager

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

9099helloworldTIBCO_HOME/amx/2.1/samples/amx_it_webapp/helloworld.zipHello World WebApplication

8777querygdsTIBCO_HOME/amx_it_mediation/3.2/samples/ContentBasedRoutingContent-BasedRouting

8666targetserviceTIBCO_HOME/amx_it_mediation/3.2/samples/TargetService


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


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 environmentand node names.

2. Invoke the TIBCO ActiveMatrix Administrator GUI. The URL ishttp://machinename:port//amxadministrator/loginForm.jsp, where machinename is the machine on which youcreated Administrator server and port is the port on which Administrator clients access the Administrator server .

3. Log in with the credentials you specified 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 UDDIServer.


20 | Tutorial Prerequisites

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 field, type SOAUDDI.

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

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

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

7. In the Port field, type 58080.

8. In the Username and Password fields, 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. Click Save.

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


Tutorial Prerequisites | 21

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 serveris running.

b) Replace the port portion of the value of the adminURL property with the port on which the Administrator serveris running.

c) Replace the username and password properties with the credentials you specified when you created theAdministrator server.

2. Save the properties file.


22 | Tutorial Prerequisites

Set Up the Service Invocation Environment

About this task

Create a project in TIBCO Business Studio to contain the concrete WSDL files of deployed service bindings. To test adeployed service, you open the concrete WSDL file 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 click Next >.

4. In the File name field, type ConcreteWSDLs and click Finish.A general project named ConcreteWSDLs displays in the Project Explorer view.


Tutorial Prerequisites | 23

Chapter

3How to Configure Logging

Topics

• Create a Logging Appender• Navigate to a Logging Configurations List• Create a Logging Configuration• Apply a Logging Configuration


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 file in clear text format.– CBE XML File - Appends events to a file in Common Base Event (CBE) format.– JMS - Append events to a log service.

Appender-specific fields display.

5. Fill in the fields and click Save.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.pdf

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 Configuration tab.

4. Click the Logging Configurations link.The logging configurations table for the host, node, or application displays.


How to Configure Logging | 27

Create a Logging Configuration

Procedure

1. Navigate to a logging configurations list.

2. Click Add.A row is added to the list.

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

4. In the Additivity column, select an additivity.

5. Click Add 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. Click Save.

9. Optionally, click Apply.


28 | How to Configure Logging

Apply a Logging Configuration

Procedure

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

2. Navigate to a logging configurations list and click a logging configuration.

3. Click Apply.


How to Configure Logging | 29

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


Complete Hello World Prerequisites

Procedure

In TIBCO Business Studio, create a distributed application archive (DAA) by following the instructions in the HowTo Create and Package a Hello World Application TIBCO Business Studio cheat sheet or extractjv.helloworld1.soa/Deployment Artifacts/jv.helloworld1.soa.daa from helloworld1.zip.


32 | How to Deploy and Run the Hello World Application

Create the Hello World Application

Procedure

1. Click Applications.The Applications list displays.

2.Click .The Application Setup wizard displays.

3. In the Application Name field, type helloworld1.

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

5. Click the Upload a DAA file radio button.

6. Click Next.

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

8. Navigate to the folder containing the file jv.helloworld1.soa.daa, click the DAA, and click Open.

9. Click Next three times.

10. Click Save 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

Create an HTTP Connector Resource Template

Procedure

1. Select Shared Objects > Resource Templates.

2.Click .The Add Resource Template dialog displays.

3. In the Name field, type hello1Connector.

4. In the Type drop-down list, select HTTP Connector.The HTTP connector configuration fields display.

5. Accept the default Machine Name.


7. Click Save.



Create and Install the HTTP Connector Resource Instance

Procedure

1. Select Infrastructure > Hosts.

2. In the Hosts list, click SystemHost.The host details display below the list.

3. Click the Resource Instances tab.The All Instances list displays.

4. Click New.The New Resource Instances dialog displays.

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

6.In the Available Nodes list at the bottom, click DevNode and click .The node moves to the Selected Nodes list.

7. Click Save and Close.The hello1Connector resource instance is added to the All Instances table with status NOT_INSTALLED. The InstallResource Instances dialog displays with the hello1Connector clicked.

8.Click .The Resource Instances list displays.

9. Click until the status changes to Running.



Distribute the Hello World Application

Procedure

1. Click Applications.

2. In the Applications list, click helloworld1.

3. Click the Distribution tab.

4. Click helloworld1.

5.In the Available Nodes list, click DevNode and click .The node moves to the Selected Nodes list.

6. Click Save.



Deploy and Start the Hello World Application

Procedure

1. Click Deploy.The application is deployed and started. If you have completed Create a UDDI Server in Administrator on page 21,the WSDL file 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).

3. Click to refresh the display.The Runtime State changes to Running and the Action History changes to Deploy with Start Successful.



Generate the Hello World WSDL File

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, click DevNode.The Generate WSDL button activates.

7. Click Generate WSDL.The WSDL document representing the deployed service displays.

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



Invoke the Hello World Service

Procedure

1. In TIBCO Business Studio, right-click Concrete WSDLs/helloworld1.wsdl and select Web Services > Testwith Web Services Explorer.The WSDL file 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 Endpointsdrop-down list.

4. In the Actions pane, type Jim in the HelloRequest field.

5. Click Go.



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. Click Details.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 pointhttp://0.0.0.0:9095/helloWorldPT/.



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 the Hello World Application• Create an HTTP Connector Resource Template• Create and Install the HTTP Connector Resource Instance• Create and Install the HTTP Client Resource Instance• Distribute the Enhanced Hello World Application• Deploy and Start the Enhanced Hello World Application• Generate the Hello World WSDL File• Invoke the Hello World Service


Complete Enhanced Hello World Prerequisites

Procedure

1. In TIBCO Business Studio, create a distributed application archive (DAA) by following the instructions in the HowTo Enhance the Hello World Application TIBCO Business Studio cheat sheet or extractjv.helloworld2.soa/Deployment Artifacts/jv.helloworld2.soa.daa from helloworld2.zip.

2. Extract datemgr_build.xml, datemgr_data.xml, and jv.datemanager.soa.daa fromjv.datemanager.soa/Deployment Artifacts/ from helloworld2.zip.

3. Edit datemgr_build.xml and replace all instances of C:/amx-3/tibco/cfgmgmt with the path of yourCONFIG_HOME directory. Set the file attribute of the import element toTIBCO_HOME/administrator/3.1/bin/taskdef.xml.


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

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 Areacreate.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 name DateMgrConnectorTemplate 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': Deployment succeeded 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

Create the Hello World Application

Procedure

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


3. In the Application Name field, type helloworld2.



6. Click Next.


8. Navigate to the folder containing the file jv.helloworld2.soa.daa, click the DAA, and click Open.

9. Click Next five times.

10. Click Save And Exit.The helloworld2 application is added to the Applications list with Runtime State Not Deployed.




Procedure

Follow the steps in Create an HTTP Connector Resource Template on page 34. In the Name field, typehello2Connector. In the Port field, type 9096.




Procedure

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



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 theHttpClient_DateManagerSOAP template.



Distribute the Enhanced Hello World Application

Procedure

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



Deploy and Start the Enhanced Hello World Application

Procedure






Generate the Hello World WSDL File

Procedure

Follow the steps in Generate the Hello World WSDL File on page 38. Click the HelloWorld2SOAP binding andname the WSDL file helloworld2.wsdl.



Invoke the Hello World Service

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.



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 an HTTP Connector Resource Template• Create and Install the HTTP Connector Resource Instance• 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


Complete Phonebook Prerequisites

Procedure

1. In TIBCO Business Studio, create a distributed application archive (DAA) by following the instructions in the Howto Create and Package the Phonebook Application TIBCO Business Studio cheat sheet or extractjv.phonebook.soa/Deployment Artifacts/jv.phonebook.soa.daa from phonebook.zip.

2. Download HyperSQL Database Engine version 1.8.1.2 fromhttp://sourceforge.net/projects/hsqldb/files/hsqldb/hsqldb_1_8_1/hsqldb_1_8_1_2.zip/download.

3. Unpack hsqldb-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 and Settings\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 in 468 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/download

Create the Phonebook Application

Procedure



3. In the Application Name field, type phonebook.



6. Click Next.


8. Navigate to the folder containing the file jv.phonebook.soa.daa, click the DAA, and click Open.

9. Click Next four times.

10. Click Save And Exit.The phonebook application is added to the Applications list with Runtime State Not Deployed. The specified resourcetemplates are imported into the Administrator database.


How to Deploy and Run the Phonebook Application | 55


Procedure

Follow the steps in Create an HTTP Connector Resource Template on page 34. In the Name field, typephonebookConnector. In the Port field, type 9098.




Procedure

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



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 hsqldband specify the instance name hsqldb.



Distribute the Phonebook Application

Procedure

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



Deploy and Start the Phonebook Application

Procedure






Generate the Phonebook WSDL File

Procedure

Follow the steps in Generate the Hello World WSDL File on page 38. Click the PhonebookPT service, click thePhonebookSOAP binding, and name the WSDL file phonebook.wsdl.



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 fields firstName: 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 firstName field.A new row is added below the field.

5. Type Joe in the empty row.

6. Click Go.The Status pane displays:

GetPhoneResponseoutentryId (string): 0

firstName (string): Joe

lastName (string): Doe

phone (string): 111-1111



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• Create an HTTP Connector Resource Template• Create and Install the HTTP Connector Resource Instance• Distribute the Hello World Web Application• Deploy and Start the Hello World Web Application• Invoke the Hello World Web Application


Complete Hello World Web Application Prerequisites

Procedure

In TIBCO Business Studio, create a distributed application archive (DAA) by following the instructions in the HowTo Create and Package a Hello World Web Application TIBCO Business Studio cheat sheet or extractwebapp.helloworld.soa/Deployment Artifacts/webapp.helloworld.soa.daa fromhelloworldwebapp.zip.


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

Create the Hello World Web Application

Procedure



3. In the Application Name field, type helloworldwebapp.



6. Click Next.


8. Navigate to the folder containing the file webapp.helloworld.soa.daa, click the DAA, and click Open.


10. Click Save 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


Procedure

Follow the steps in Create an HTTP Connector Resource Template on page 34. In the Name field, typeWebAppHttpConnectorTemplate. In the Port field, type 9099.




Procedure

Follow the steps in Create and Install the HTTP Connector Resource Instance on page 35. Use the templateWebAppHttpConnectorTemplate and specify the instance name webAppHttpConnector.



Distribute the Hello World Web Application

Procedure

Follow the steps in Distribute the Hello World Application on page 36. Click the helloworldwebapp applicationand the webapp.helloworld.soa component.



Deploy and Start the Hello World Web Application

Procedure






Invoke the Hello World Web Application

Procedure

In a browser, open the location: http://localhost:9099/helloworld/sayHello?firstName=Jim.The response is: Hi Jim! This is the Web App component.



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 ActiveMatrixAdministrator.

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


Create the Routing and Target Service Mediation Applications

Procedure



3. In the Application Name field, type querygds.



6. Click Next.


8. Navigate toTIBCO_HOME\amx_it_mediation\3.3\samples\ContentBasedRouting\mediation.querygds.route.soa\Deployment

Artifacts\, click mediation.querygds.route.daa, and click Open.


10. Click Save And Exit.The querygds application is added to the Applications list with Runtime State Not Deployed and the resource templatesused 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 DAATIBCO_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

Create HTTP Connector Resource Templates

Procedure

1. Select Shared Objects > Resource Templates.

2.Click .

3. In the Name field, type httpConnector.

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

5. Accept the default Machine Name.


7. Click Save.

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

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. Click New.The New Resource Instances dialog displays.

4. In the Resource Templates list, click the httpConnector row.The Instance Name field is set to httpConnector.

5.In the Available Nodes list at the bottom, click DevNode and click .The node moves to the Selected Nodes list.

6. Click Save 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



Distribute the Routing and Target Service Applications

Procedure


2. In the Applications list, click querygds.

3. Click the Distribution tab.

4.In the Available Nodes list, click DevNode and click .The node moves to the Selected Nodes list.

5. Click Save.

6. Repeat the preceding steps for the targetservice application.



Deploy and Start the Routing and Target Service Applications

Procedure

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

2. Click Deploy.The applications are deployed and started.





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, click DevNode.The Generate WSDL button activates.

7. Click Generate WSDL.The WSDL document representing the deployed service displays.

8. Save the WSDL file with the name QueryGDS_gen.wsdl in the ConcreteWSDLs project in TIBCO Business Studio.



TIBCO ActiveMatrix® BPM SOA Administration … › pub › › activematrix_bpm ›...

Documents

Transcript of TIBCO ActiveMatrix® BPM SOA Administration … › pub › › activematrix_bpm ›...