TIBCO ActiveMatrix BusinessWorks Process Monitor Server. Installation

Transcription

1 TIBCO ActiveMatrix BusinessWorks Process Monitor Server Installation Software Release Published: May 2013

2 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-ON FUNCTIONALITY) 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 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 confidential 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 BusinessWorks, TIBCO Rendezvous, TIBCO Administrator, TIBCO Enterprise Message Service, TIBCO InConcert, TIBCO Policy Manager, and TIBCO Hawk 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 identification 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 TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information

3 Contents Important Information... 2 Contents... 3 Installation of TIBCO BWPM Server... 1 Introduction... 1 How to use this document... 1 Related Documentation... 2 Checklist: Planning Your Installation... 2 System Requirements... 2 Preparing for Installation... 6 Preparing Oracle Database System... 6 Preparing Microsoft MS- SQL Server... 6 Preparing TIBCO Enterprise Messaging Service... 7 Preparing Apache Tomcat... 8 Fundamentals BWPM Instance TIBCO BWPM Server TIBCO BWPM Client Installing and Configuring a new BWPM Instance Installing TIBCO BWPM Server Add needed Third- Party- Libraries Setup a new BWPM Instance Updating and Configuring an existing BWPM instance Stop Apache Tomcat Server Remove existing application of TIBCO BWPM Server Start Apache Tomcat Server again Deploy and Start new version of TIBCO BWPM Server Add needed Third- Party- Libraries Clear the cache of the browser Connect to your existing BWPM database again Re- Start all data providers of TIBCO BWPM Server Verify whether your update process was successful... 26

4 Needed Third- Party- Libraries and How to Add Uninstalling TIBCO BWPM Server Stop Apache Tomcat Server Remove existing application of TIBCO BWPM Server Start Apache Tomcat Server again Optional: Drop JMS destinations of BWPM Optional: Drop BWPM database Appendix A: Glossary... 29

5 Installation of TIBCO BWPM Server Introduction This document describes the process for installing and configuring TIBCO BWPM Server. It is recommended to read the entire document before starting installation. Before you begin the installation process, gather information on the needs of your enterprise, and discuss the scope of your deployment. How to use this document This document is divided into the following sections: Introduction gives you an overview of the installation process and instructions to be executed during the installation process. Preparing for Installation walks you through the preparation of all third party prerequisite software. Fundamentals briefly explains the conceptual structure of TIBCO BWPM Server Installing and Configuring a new BWPM Instance walks you through installing and configuring TIBCO BWPM Server. The section includes procedures for determining whether your installation was successful. Updating an existing BWPM Instance explains how to update an existing BWPM Instance to a higher version of TIBCO BWPM Server. Appendice(s): Appendix A: Glossary: TIBCO BWPM related terms and definitions 1

6 Related Documentation More information about TIBCO BWPM Server is available from the following sources: Release Notes: Before you install TIBCO BWPM Server you should read the Release Notes. The Release Notes contain additional information about: any restrictions or known issues any fixes that have been done any other information that was not available when this document was created Checklist: Planning Your Installation Each of the prerequisite steps must be carried out before the installation and each step contains various parameters relevant to your enterprise. All of these requirements will be addressed in upcoming sections of this guide. TIBCO BWPM Server basically requires the following systems installed and running: Oracle Database System 10g (or greater; XE is supported for non- production environments only) TIBCO Enterprise Messaging Service 5.0 (or greater) Apache Tomcat Web Application Server 6.0 (or greater) System Requirements In order to deploy and run TIBCO BWPM Server, your system must meet the following requirements: Hardware Requirements Component Computer and processor Memory Disc space Minimum Requirement A computer with Intel x86, Dual or Quad Core, 32 Bit or 64 Bit, 2 GHz or divergent architecture with comparable performance characteristics 2 GB RAM 100 MB free disc space 2

7 Operating System Requirements Any operating system of the following list is supported: OS Linux Windows Supported version Ubuntu Server for x86 SUSE Linux Enterprise Server (SLES) 10 or 11 for x86 Red Hat Enterprise Linux 5.x, 6.x for x86 Windows Server 2003 Windows Server 2008 / R2 Windows XP Windows Vista Windows 7 Including most recent Service Pack Either 32 bit or 64 bit Solaris AIX HP- UX Others Solaris 10 or greater for x86 AIX 6.1 HP- UX 11i v2 Please contact TIBCO Support for other supported platforms Database Requirements TIBCO BWPM Server requires one of the following Databases. Database Oracle Database 10g or greater Oracle Database 10 XE Remarks No limitations Potential performance and space limitations (for instance partitioning and compress features are not available, and XE instances are restricted in size) Read the Oracle Database documentation for more information. TIBCO Enterprise Messaging Service TIBCO EMS 5.0 or greater is required as messaging platform to be used by TIBCO BWPM Server. Apache Tomcat Apache Tomcat 6.0 or greater is required to host TIBCO BWPM Server Software. 3

8 Web Browser Support The following web browsers are supported: Web browser Microsoft Internet Explorer Mozilla Firefox Supported versions 9 4 or greater, excluding version 12 Additional Software Requirements The following Java libraries must be available in the Apache Tomcat s classpath. Please check the corresponding Apache Tomcat manual for further information. JDBC Driver for Oracle 1 The JDBC Driver for Oracle is not part of the TIBCO BWPM Server Distribution Package. Please go to the Oracle website for downloading ojdbc6.jar. This driver should be made available in the classpath variable of the tomcat server before the BWPM database can be created. JDBC Driver for MS- SQL The JDBC Driver for Microsoft SQL Server is not part of the BWPM Server Distribution Package. Please go to the Microsoft website 2 for downloading sqljdbc4.jar. This driver should be made available in the classpath variable of the tomcat server before the BWPM database can be created. TIBCO EMS Client libraries The following TIBCO EMS client libraries are required by the TIBCO BWPM Server to communicate with the TIBCO EMS server: tibjmsadmin.jar, tibjms.jar, tibcrypt.jar Check your TIBCO EMS installation for those files. Typically they can be found at: <TIBCO_EMS_HOME>/<VERSION>/client For example: c:\tibco\ems\6.1\client 1 edition/jdbc html 2 us/sqlserver/aa aspx 4

9 Other The Java Message Service API must be available on the system. It is located in the file jms.jar, which is a part of your J2EE installation. 5

10 Preparing for Installation In this section you will prepare your environment by installing and configuring all software prerequisites. Preparing Oracle Database System TIBCO BWPM Server requires an Oracle Database to be available within your environment. Required database privileges In order to create the BWPM database objects (tables, views, etc.) the following privileges are required by the database user for installing TIBCO BWPM Server: Permission: CONNECT RESOURCE CREATE VIEW CREATE JOB Type: Role Role System privilege System privilege If your database account has not been provided with these required privileges, the BWPM database cannot be created during the automatic installation procedure. In that case you can let BWPM create an SQL script including all required commands for creating the BWPM database objects. This script can be executed by a DBA. After this has been run, you can continue with configuring the system using the BWPM web interface. Preparing Microsoft MS- SQL Server Prepare your MS SQL Server database by creating an BWPM database (e.g. bwpmdb) and a BWPM database user (e.g. bwpmuser) and set the bwpmuser as owner of bwpmdb. Also make sure, that the user s default schema is set to the correct schema (e.g. bwpm). BWPM requires READ_COMMITTED_SNAPSHOT to be turned on in MS SQL Server. Ask your DBA to execute the following lines: use msdb; ALTER DATABASE [BWPMDB] SET READ_COMMITTED_SNAPSHOT ON; CREATE USER [BWPMUser] FOR LOGIN [BWPMUser]; EXEC sp_addrolemember 'SQLAgentUserRole', [BWPMUser]; GRANT SELECT ON msdb.dbo.sysjobactivity TO [BWPMUser]; GRANT SELECT ON msdb.dbo.sysjobs TO [BWPMUser]; GRANT SELECT ON msdb.dbo.sysjobhistory TO [BWPMUser]; 6

11 GRANT SELECT ON msdb.dbo.sysjobschedules TO [BWPMUser]; GRANT SELECT ON msdb.dbo.sysschedules TO [BWPMUser]; Note: Currently BWPM supports only one database per MS- SQL Server. Preparing TIBCO Enterprise Messaging Service TIBCO BWPM Server requires TIBCO EMS up and running and being available on your network/subnet where you want to use TIBCO BWPM Server. TIBCO BWPM Server will create specific destinations on your TIBCO EMS Server. You need the following information about your TIBCO EMS Server: IP- Address / Server name, Port Number Account (Username, Password) Permissions send / receive, or publish / subscribe on destinations that BWPM requires: Destinations: Privilege required by TIBCO BWPM Server Queues: Topics: <prefix>.event receive Subscribe (, durable) <prefix>.command send publish <prefix>.error send publish Administrative permissions required by BWPM Server are: view- destination view- durable view- server If you plan using JNDI to lookup connection factories, the following information is required in addition: IP- Address / Server name, Port Number of JNDI server JNDI Account (Username, Password) Name of the Connection Factory (for example: QueueConnectionFactory) Authentication Requirements The following administrative permission is required to configure TIBCO EMS during BWPM installation process: Permission: CREATE- DESTINATION Type: Administrative 7

12 If your TIBCO EMS account does not have the CREATE- DESTINATION privilege on the <prefix>.> destination, your TIBCO EMS administrator needs to create the aforementioned destinations for you in advance. Example The following commands will create an EMS User bwpm including permissions to create destinations and send/receive messages from BWMP specific queues. The parent BWPM queue queue.bwpm.> will be created including send/receive permissions to user bwpm. Alse, the required administrative privileges are granted: > > > > > > create user bwpm User to send and receive BWPM messages password=bwpm create queue queue.bwpm.> grant queue queue.bwpm.> user=bwpm receive,view,send grant admin user=bwpm view-destination grant admin user=bwpm view-durable grant admin user=bwpm view-server Preparing Apache Tomcat Apache Tomcat is required by TIBCO BWPM Server as a runtime environment. Before you deploy TIBCO BWPM Server ensure Apache Tomcat is running properly. Memory Requirements of Apache Tomcat TIBCO BWPM Server requires at least 64 MB RAM. Please make sure that the default memory setting in the Apache Tomcat s configuration is set accordingly. It is recommended to extend the maximum heap size to at least 1024 MB. For high performance environments a maximum heap size of at least 4096 MB is recommended. Add the following option to CATALINA_OPTS: - Xmx1024m. CATALINA_OPTS is defined in the tomcat start scripts catalina.sh (for Unix environments) or catalina.bat (for Windows) in the <TOMCAT_HOME>/bin directory. Authentication Requirements If you plan to deploy the TIBCO BWPM Server web application using Tomcat s management interface, you need a user which is member of the following roles: tomcat, manager. You can use the built in user account tomcat for deploying TIBCO BWPM Server, or ask you Apache Tomcat administrator to deploy the web application for you. 8

13 9

14 Fundamentals TIBCO BWPM Server is a web application. Users interact with the application using a web browser. The following picture illustrates the main components of BWPM and their interaction: Webbrowser BWPM Instance HTTP Web-Application Server Presentation Layer BWPM Server Core UI Database Access Layer Data Provider JDBC Database system JMS Log Message Bus JMS BWPM Client Client for BW Client for BW Client for BW BWPM Instance An instance of BWPM represents the combination of various components that are interacting together within one environment. Each BWPM Instance consists of one database system, one or more JMS Server(s), and at least one TIBCO BWPM Server. You can combine several TIBCO BWPM Servers within one BWPM Instance, if load balancing is required. Typically you want to separate your production environment from your non- production environments. In order to do so, you can create for example two different BWPM instances as there are: BWPM TEST and BWPM PROD: 10

15 TEST PROD BWPM Instances TIBCO BWPM Server The TIBCO BWPM Server represents the core components of a BWPM Instance: Webbrowser HTTP Web-Application Server Presentation Layer BWPM Server Core UI Database Access Layer Data Provider JDBC Database system JMS Log Message Bus The TIBCO BWPM Server runs inside Apache Tomcat and interacts in three directions: Log Message Bus: BWPM Server collects log messages from BWPM Clients via JMS. The BWPM destinations on the JMS Server represent the Log Message Bus. BWPM needs to have a defined connection to your JMS Server and a configured BWPM data provider to communicate with the Log Message Bus 11

16 Database system: A relational database system is used to store and retrieve BWPM log information. A defined database connection and a JDBC driver are used to connect to the database. User: A user interacts with TIBCO BWPM Server by using the BWPM GUI via a standard web browser. TIBCO BWPM Client The TIBCO BWPM Client represents a system to be monitored. For example the TIBCO BWPM Client for BW is connected with TIBCO BusinessWorks and sends monitoring information on the Log Message Bus. Log Message Bus JMS BWPM Client Client for BW Client for BW Client for BW 12

17 Installing and Configuring a new BWPM Instance The overall installation process of a new BWPM Instance consists of the following main steps: 1. Install TIBCO BWPM Server a. Deploy TIBCO BWPM Server, represented by a Web Archive File (WAR), on Apache Tomcat. b. Start the application bwpm. 2. Setup a new BWPM Instance a. Log in into BWPM for the first time and create a BWPM Setup User. b. Define a connection to the database and create the BWPM database objects. c. Define a connection to the JMS Server. d. Configure a data provider to use the JMS connection from the previous step. e. Add the configured data provider to the runtime configuration. f. Start the data provider. Installing TIBCO BWPM Server Upload WAR File Start your preferred web browser and open the administration page of Apache Tomcat: This is the Apache Tomcat Homepage. Click on Tomcat Manager to open Tomcat Web Application Manager. 13

18 The Tomcat web Application Manager lets you manage web applications individually: This is the Tomcat Web Application Manager. You can see all deployed applications here. By default there is only the manager application available. Scroll down to upload a WAR file to deploy. Upload and deploy TIBCO BWPM Server: Select the TIBCO BWPM Server WAR file (bwpm.war) and click on deploy. Start application bwpm When you deployed TIBCO BWPM Server successfully, a new application /bwpm appears in the Application List: Click on start, if the newly deployed application has not been started by Tomcat automatically. Add needed Third- Party- Libraries This is described in chapter Needed Third- Party- Libraries and How to Add. Setup a new BWPM Instance The next step is to setup a new BWPM Instance. 14

19 Log in into BWPM for the first time Click on application bwpm or type in your web browser the URL You are now asked to create an account for the TIBCO BWPM Server Setup User: This is the screen of the first start of TIBCO BWPM Server. You are now asked to enter the credentials for creating a new TIBCO BWPM Server Setup User. Create an account for the TIBCO BWPM Server Setup User by specifying a user name and a password. The Setup User has limited access and is only used for setup and configuration purpose. This user account is not permitted to view any log data, but only permitted to setup and administer TIBCO BWPM Server. It is recommended to specify a unique name for the Setup User. By clicking on the login icon the TIBCO BWPM Server Setup User is created and you are logged in. 15

20 Create the BWPM database This is the first time you are logged in into BWPM webui. Since the Setup User is a restricted user to only setup and administer TIBCO BWPM Server, you only have access to the Administration category: This start screen will appear the first time you log in into BWPM webui. You are directed right away to the configuration wizard where you are asked for configuring the connection parameters to the database and for creating the BWPM database objects. JDBC settings Specify the JDBC connection parameters: This is the first step of the configuration wizard. 16

21 Depending on what you choose as Connection Type you will get different parameters to set. You can choose Simple or JDBC_URL which has less options and where you specify most of the options in a text string. The common options are: Attribute JDBC Driver JDBC Driver Class Username Password Database Schema Use Partitions Connection Pool Size Description Name of the JDBC driver. The related driver class is shown automatically after selection of the JDBC driver. This is the name of the database user BWPM will use to interact with. This is the password according to the username above. Name of the database schema True / False. If your Oracle database is enabled for using partitions, it is recommended to set this option to true. Note: Oracle XE does not support partitions; in that case Use Partitions must be disabled. Note: Also in case of MS- SQL partitioning is not supported. This is the connection pool size. Options available only for Connection Type Simple are: Attribute Database Server DB Server Port SID Description Type in the name of the database server or the IP- Address. Number of the port, for Oracle typically This is your Oracle System ID (SID). The following further options are available only for Connection Type JDBC_URL : Attribute JDBC_URL Description This is the JDBC connection string to database. There are different types of URLs; please refer to Oracle s 3 and Microsoft s 4 websites for additional information Examples: Oracle: jdbc:oracle:thin:@localhost:1521:orcl MS SQL Server: 3 Oracle Database URLs and Database settings: 4 Building the Connection URL for MS SQL Server us/library/ms378428%28v=sql.90%29.aspx 17

22 jdbc:sqlserver://localhost:1433;databasename=adventureworks; Click on Test Connection Settings to verify your parameters. If the test was successful, you can save your settings by clicking on Save settings. Click on Next to proceed with the next step. Database setup At this stage you have to enter the configuration parameters of your BWPM database: The second step is about creating the BWPM database. 18

23 Attribute Description BWPM Instance BWPM Admin Admin Password Confirm Password This is the name of your BWPM Instance. Choose a different name for each of your environments (Dev, Test and Prod) This is the name of the administrator of BWPM. The administrator has full access to BWPM and is able to setup BWPM, manage user accounts, and grant access to users/roles. In addition the administrator has full access to any log object / data by default. Password of the administrator Confirm the password Create BWPM database Caution: If there is an existing BWPM installation using the specified schema, all existing data will be lost. There are two ways to create the BWPM database objects after configuration. Either you create the database using the wizard, or you let the wizard create an SQL script that can be executed separately by a DBA. If you want to create the BWPM database directly, click on Create Database. Provide a database account with sufficient privileges in the following dialog to create the database objects: If you want your DBA to create the BWPM database, click on Download file an SQL script will be generated including all commands to create all BWPM database objects. You can handover this script to your DBA for execution. At this stage you need to suspend your configuration work by logging out and resume it after the DBA has executed the SQL script. Create a JMS Connection After the BWPM Database objects have been created successfully, you can now create a connection to your JMS Server. 19

24 In category Administration click on Connections / JMS. As you can see there are two pre- defined connection settings, one for topics and one for queues. Select Connections / JMS from the Administration category to setup a JMS connection. Specify the following information: Attributes Name Provider URL Use JNDI Connection factory Username Password Description Name of the JMS Connection This is the URL of your JMS Server: For JNDI: tibjmsnaming://<servername>:<port> No JNDI: tcp://<servername>:<port> Activate this option, if you want to use JNDI For JNDI specify the connection factory according to your JMS Server This is the JMS user account for BWPM Password of the user Click on Test connection to verify your settings. If the connection could be established successfully, click on Save settings. Create BWPM data provider Based on a JMS connection, a data provider defines the configuration of the Log Message Bus. 20

25 Data Provider Settings Create a data provider: Specify the data provider settings by clicking on Data Provider in the "Administration category. Attributes Name Destination Create destination if not exists Thread Pool Size Data provider class Use durable subscriber JMS Connection Description Name of the data provider Prefix of the destinations Activate this option, if you want to create destinations in your JMS server for BWPM. If unchecked, ask a JMS Server administrator to create the required destinations for you. This setting determines how many messages are executed in parallel. Specifies the class of your data provider. If you selected topics as your preferred type of destinations, you can use an optional durable subscriber. Pick one of the predefined connection types. If you have selected Create destination, if not exists the following dialog prompts you for a JMS server account that has sufficient privileges to create the required destinations: 21

26 Click the Create JMS Destinations button to proceed, or Cancel to return to the previous dialog. Runtime Configuration Go to System Management / Run Config and select the according data provider from the list of available data providers. Click on System Management / Run Config to list all data providers. There are both data providers available within the right list box Available. The left list box Selected is empty at this stage. Select the data provider you have configured before and click on the button < to move this entry into the list of all selected data providers. Afterwards you can start the selected data provider(s) by clicking on (Re)start button. 22

27 Click on Start to (re- )start the data provider(s). 23

28 Determining whether your installation was successful Please follow the instructions below to ensure BWPM is running properly: Verify BWPM Log File for any error or warning messages. In case of an error you have to investigate the cause of the failure and resolve the issue accordingly. Check whether there is a receiver / subscriber registered on the JMS Server destination used by BWPM: <prefix>.event. At least 1 receiver / subscriber should be registered on that destination. In case there is no consumer registered, please check whether the data provider has been started successfully. Try to log in into BWPM webui by using the Administrator account. If log in fails, please check whether the Apache TOMCAT Server has been started successfully. 24

29 Updating and Configuring an existing BWPM instance The overall update process of an existing BWPM Instance consists of the following main steps: 1. Stop Apache Tomcat Server 2. Remove existing application of TIBCO BWPM Server 3. Start Apache Tomcat Server again 4. Deploy TIBCO BWPM Server, represented by a Web Archive File (WAR) 5. Clear browser cache 6. Connect to your existing BWPM database again Please note, that this chapter only describes the general process of updating TIBCO BWPM Server. You have to follow the steps specified in the release notes that are enclosed to each new version of TIBCO BWPM Server. Stop Apache Tomcat Server Shutdown Apache Tomcat Server according to the procedure depending on your operating system. Please refer to the Apache Tomcat User Guide. Remove existing application of TIBCO BWPM Server The following folders of BWPM have to be removed including all sub folders: <CATALINA_BASE>/work/Catalina/localhost/bwpm <CATALINA_BASE>/webapps/bwpm In addition an existing WAR file has to be removed as well: <CATALINA_BASE>/webapps/bwpm.war Start Apache Tomcat Server again Start Apache Tomcat Server according to the procedure depending on your operation system. Please follow the instructions of Apache Tomcat User Guide. 25

30 Deploy and Start new version of TIBCO BWPM Server Upload the new WAR file within Apache Tomcat Manager. Afterwards deploy and start the BWPM application. Add needed Third- Party- Libraries This is described in chapter Needed Third- Party- Libraries and How to Add. Clear the cache of the browser Before you log in into BWPM webui again, you have to clear your browser cache. Connect to your existing BWPM database again Log in into BWPM webui by using your BWPM Setup User. Click on Administration / Connections / JDBC and specify the parameters to connect to your existing BWPM database and save the settings. Please note: Do not create a new BWPM database unless you want to drop all existing BWPM information! Re- Start all data providers of TIBCO BWPM Server Start all data providers again via Administration / System Management / Run Config. If the data providers are stopped, click on the button Start to start them all. Verify whether your update process was successful On the lower left end of the BWPM webui you can verify the new version number of TIBCO BWPM Server that should correspond to the version of the enclosed release notes. Furthermore check the BWPM log file to ensure that BWPM was started successfully: Administration / System Management / Logfile 26

31 Needed Third- Party- Libraries and How to Add Following table summarizes third- party- libraries which are needed: Name Needed for connectivity with Where to get ojdbc6.jar Oracle database Oracle homepage sqljdbc4.jar MS- SQL Server Microsoft homepage tibcrypt.jar TIBCO EMS lib directory of EMS installation tibjms.jar TIBCO EMS lib directory of EMS installation tibjmsadmin.jar TIBCO EMS lib directory of EMS installation jms.jar JMS Server lib directory of EMS installation These jar files must be present in the classpath of Tomcat. The following steps are necessary: 1. Copy these jar files to <CATALINA_HOME>/lib 2. Restart Apache Tomcat. Uninstalling TIBCO BWPM Server If you want to uninstall BWPM from your machine please follow the next steps: 1. Stop Apache Tomcat Server 2. Remove existing application of TIBCO BWPM Server 3. Start Apache Tomcat Server again 4. Optional: delete JMS destinations of BWPM 5. Optional: Drop BWPM database Stop Apache Tomcat Server Shutdown Apache Tomcat Server according to the procedure depending on your operating system. Please refer to the Apache Tomcat User Guide. Remove existing application of TIBCO BWPM Server The following folders of BWPM have to be removed including all sub folders: <CATALINA_BASE>/work/Catalina/localhost/bwpm 27

32 <CATALINA_BASE>/webapps/bwpm In addition the existing WAR file has to be removed as well: <CATALINA_BASE>/webapps/bwpm.war Start Apache Tomcat Server again Start Apache Tomcat Server according to the procedure depending on your operation system. Please follow the instructions of Apache Tomcat User Guide. Optional: Drop JMS destinations of BWPM If you want to cleanup your TIBCO BWPM Server, you can delete the existing destinations only used by BWPM: <prefix>.event <prefix>.command <prefix>.error Optional: Drop BWPM database Optionally you can drop the bwpm- schema owner as the final step. 28

33 Appendix A: Glossary Term Administrator account Data Provider Instance Log Message Bus TIBCO BWPM Client TIBCO BWPM Server Setup User account webui Definition This user is used for administration of the BWPM Instance: User- Management, grant permissions, maintenance, etc. A data provider consists of a connection to a message server and a destination Represents the combination of various components that are interacting together within one environment. The messaging layer between TIBCOP BWPM Client and TIBCO BWPM Server is called Log Message Bus. The recommended messaging system of BWPM is JMS (Java Message Service). The TIBCO BWPM Client is attached to the system of the customer that is be monitored. It gathers logging / monitoring information and sends the data via the BWPM Log Message Bus to TIBCO BWPM Server. This is the server component of BWPM. It receives incoming logging / monitoring information from TIBCO BWPM Clients via JMS and persists those messages in the database. It also contains services for the BWPM web based user interface. Specific user account with limited access to setup and administer the BWPM Instance. This user is used to initial setup a new BWPM Instance. Web based user interface of BWPM. This is the main interface the user can interact with BWPM. 29