Business Enterprise Server Installation Guide. Version 3.5

Transcription

1 Business Enterprise Server Installation Guide Version 3.5 July 31, 2012

2 Copyright Copyright Interlink Software Services, Ltd., as an unpublished work. All rights reserved. Interlink Software Services, the Interlink Software Services Logo, and all other Interlink Software Services product or services names are registered trademarks of Interlink Software Services, Ltd. Interlink Software Enterprise Dashboard Studio/Business Service Dashboard contains Star Tree from Inxight Software, Inc. Copyright All rights reserved. Star Tree is a registered trademark of Inxight Software, Inc. Star Tree is protected by one or more of the following United States patents: 5,590,250; 5,619,632; 6,108,698; 6,300,957; 6,377,259; 6,654,761. Inxight is a registered trademark of Inxight Software, Inc. All other third party logos, and product and trade names are trademarks or registered trademarks of their respective companies. Restricted Rights Legend Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS or subparagraphs (c)(1) and (2) of the Commercial Computer Software Restricted Rights at 48 CFR , as applicable. Contacting Interlink Software Services, Ltd. You can contact Interlink Software Services, Ltd. by telephone, e mail, and fax. To access information about the company, its products, and its services, go to Main Telephone Number +44(0) Customer Support Telephone Number +44(0) Facsimile Telephone Number +44(0) ii Business Enterprise Server Installation Guide

3 Contacting Customer Support You can obtain technical support by using online support from the Interlink Software Services Web site. Before contacting Customer Support, gather the information outlined in Reporting a Problem. Online Support Technical support is available 24 hours a day, seven days a week by accessing the Support web page at From the Support web page, you can search a database for problems similar to yours for possible solutions download software updates and product documentation find the most current information about Interlink Software products find contact information, including e mail address, fax numbers, and telephone numbers Reporting a Problem Before you contact Customer Support, help us by providing the circumstances under which the problem occurred and if the problem can be reproducible. The following information is needed: Product information Operating environment Sequence of events Product name Product version License details System type Hardware configuration Operating system and version Related software installed Any recent changes made to your system Messages received from operating system Feature used when problem occurred Commands or options that you used including the specific syntax of commands Resulting error messages from product When you report the problem, assign one of the following business impact severity levels: 1 Product is unusable, is critical to business operations, and requires an immediate solution 2 Product is usable but severely limited, the feature that is not working is impacting business operations 3 Product is usable and the feature that is not working is not critical to business operations 4 Product is usable and problem is not impacting business operations Business Enterprise Server Installation Guide iii

4 iv Business Enterprise Server Installation Guide

5 Table of Contents Preface xv How This Book Is Organised xvi Related Documentation xvii Online Books xvii Conventions xviii Chapter 1 Overview What is Business Enterprise Server? Components of a Business Enterprise Server System Optional Business Enterprise Server Products and Components Interlink Software Services Integration for Agentless Monitoring Interlink Software Services Integration for AlarmPoint Interlink Software Services Integration for AutoOPERATOR Interlink Software Services Integration for BMC Event Manager Interlink Software Services Integration for BMC PATROL Enterprise Manager Interlink Software Services Integration for BMC Performance Manager. 6 Interlink Software Services Integration for Business Enterprise Server.. 6 Interlink Software Services Integration for the Business Enterprise Server Interface Interlink Software Services Integration for HP Network Node Manager. 6 Interlink Software Services Integration for HP OpenView IT/Operations. 6 Interlink Integration for HP OVOW Interlink Software Services Integration for HP Service Manager Interlink Software Services Integration for IBM Tivoli Enterprise Console 7 Interlink Software Services Integration for IBM Tivoli Monitoring Interlink Software Services Integration for IBM Tivoli Netcool/OMNIbus 7 Interlink Software Services Integration for IBM Websphere MQ Interlink Software Services Integration for mailx Interlink Software Services Integration for Microsoft Operations Manager 8 Interlink Software Services Integation for Microsoft System Center Operations Manager Business Enterprise Server Installation Guide v

6 Table of Contents Interlink Software Services Integration for NetIQ AppManager Interlink Software Services Integration for Oracle Database Interlink Software Services Integration for Oracle Enterprise Manager.. 9 Interlink Software Services Integration for Quest Foglight Interlink Software Services Integration for Remedy AR System Interlink Software Services Integration for SNMP Interlink Software Services Integration for Sun Management Center... 9 Interlink Software Services Integration for Web Services Business Enterprise Server Reporting Business Enterprise Server Third Party Software Where to Go from Here Chapter 2 Preparing for Installation Business Enterprise Server File Systems and Directories Business Enterprise Server Database Adaptive Server DB Preparation Checklist Ensuring That the Host Meets the System Requirements Business Enterprise Server Requirements Business Service Dashboard Requirements LDAP Authentication Requirements Business Enterprise Server Console Allocating Disk Space and Devices Allocating Raw Devices for the Sybase Database Enabling Large File Support Distributing Sybase Files and Databases in a SAN Environment Creating the Sybase Installation Directory Creating the Business Enterprise Server Administration User Accounts and Group Changing Ownership and Group Permission on the Sybase Installation Directory Changing Write Permission for /var/tmp Setting a File Size Security Limit Changing Kernel Configuration Parameters Increasing the Number of Processes per User in AIX Setting Up the Kernel Parameters for Solaris Setting Asynchronous I/O in AIX Limiting the Number of Threads per Process Setting TCP Node Layer Acknowledgement Rebooting to Implement System Changes Mounting a CD ROM Drive Mounting a Local CD ROM Drive Mounting a Remote CD ROM Drive Upgrading to Business Enterprise Server Upgrading from POWERpack 3.0 or vi Business Enterprise Server Installation Guide

7 Table of Contents Upgrading from Business Enterprise Server 3.2 or Upgrading from Business Enterprise Server 3.4 to Retrieving Installation and Configuration Software for Sybase ASE and Business Enterprise Server Retrieving Sybase ASE Software and License Extracting the Business Enterprise Server Distribution Software Migrating from Business Enterprise Server 3.4 to Migrating to Business Enterprise Server Backing Out of Migration to Business Enterprise Server Where to Go from Here Chapter 3 Installing the Database Before You Begin Methods for Initial Installation of Sybase ASE Installing Sybase ASE Post Installation Tasks Setting Your Environment Variables Verifying Server Execution and Connection Changing Ownership and Group Permission on the Sybase Installation Directory Improving Performance Using Cache and Multiple Engines Adjusting Shared Memory in Solaris Where to Go from Here Installing and Preparing the DB2 UDB for Business Enterprise Server Installing the DB2 Universal Database Creating a Database Instance, Fenced User, and Administration Server.. 55 Creating Symbolic Links to the DB2 UDB Product Libraries and Include Files. 58 Configuring the Instance Owner to Run db2cshrc Verifying the Installation of DB2 UDB Creating a DB2 Database for Business Enterprise Server Where to Go from Here Chapter 4 Installing the Business Enterprise Server Establishing a Link between the /usr Directory and Java Starting the Business Enterprise Server Installation Configuring the Supporting Database for the Business Enterprise Server. 65 Configuring Sybase for the Business Enterprise Server Configuring DB2 for the Business Enterprise Server Installing the Business Enterprise Server Where to Go from Here Chapter 5 Finalising Installation and Starting the Business Enterprise Server Changing Ownership and Group Permission on Sybase Obtaining and Installing Your License Key Obtaining the License Key Business Enterprise Server Installation Guide vii

8 Table of Contents Installing the License Key Modifying the Number of User Connections Adjusting AlertServer Memory Allocation Defining Authentication for the Business Service Dashboard Admin Console 74 Modifying the Apache/Tomcat Communication Port Creating a Microsoft.NET Security Policy Adding a Policy Manually Adding a Policy Using the Distribution Package Defining the Business Enterprise Server on the Business Service Dashboard Host Systems Defining a Business Enterprise Server in the Hosts File Defining the Business Enterprise Server in the Intranet Zone for Internet Explorer Testing the Business Enterprise Server Starting the Business Enterprise Server Starting the Business Service Dashboard and Displaying the Alert View 84 Sending a Sample Message to the Business Enterprise Server Verifying the Sample Messages are Displaying in the Alert View Ensuring All Processes Are Running Verifying All Processes Are Running Changing the Default System Administrator Password Setting Up User Environments for the Business Enterprise Server Configuring Business Enterprise Server to Use https Generating the SSL Certificate Configure Business Enterprise Server to Use Port Configuring Apache to Use Secure Communication Testing the https Protocol Configuration Installing and Configuring User Defined Servlets Installing and Configuring a Standalone Apache Server Adding Entries to the hosts Files on Each Server Updating the Backend Apache Server on the Business Enterprise Server.. 97 Installing the Apache Server Software on the Proxy Server Restarting the Backend Apache Server on the Business Enterprise Server. 98 Starting the Apache Server on the Proxy Server Testing the URL Connections to the Business Enterprise Server and Proxy Server Applying Patches to the Business Enterprise Server Viewing Your Build Version Applying Patches to the Business Enterprise Server Verifying Business Enterprise Server Component Versions Retrieving Component Versions from the Business Enterprise Server Where to Go from Here viii Business Enterprise Server Installation Guide

9 Table of Contents Chapter 6 Installing the Business Enterprise Server Console Installing the Database Client DB2 Client Settings for the Business Enterprise Server Multiple DB2 Client Business Enterprise Server Definitions Starting the Business Enterprise Server Console Installation Changing Database Client Driver DLL Settings Changing the Default Sybase Driver DLL Setting for International Characters Changing the Oracle Driver DLL Settings Launching the Business Enterprise Server Console Showing the Business Enterprise Server Console Hiding the Business Enterprise Server Console Launching the Business Enterprise Server Console Manually Setting the Application to Stay on Top Launching SMART Modules from the Business Enterprise Server Console 111 Managing Business Enterprise Server Connections Defining a Host Name to the Business Enterprise Server Console Adding a Business Enterprise Server Connection Definition Deleting a Business Enterprise Server Connection Definition Verifying Business Enterprise Server Console Component Versions Retrieving Component Versions from the Business Enterprise Server Console Uninstalling the Business Enterprise Server Console Where to Go from Here Appendix A Changing the Business Enterprise Server Database Administrator Password 117 Ascertaining the Main Business Enterprise Server Database Administrator Account Changing the Business Enterprise Server Database Password within the Business Service Dashboard Stopping All Business Enterprise Server Processes Changing the Database Administrator Password Encrypting and Storing the New Database Password Appendix B Business Enterprise Server Communication Ports Appendix C Modifying a Non Clustered Installation of Business Enterprise Server for a Clustered Environment 125 Index Business Enterprise Server Installation Guide ix

10 Table of Contents x Business Enterprise Server Installation Guide

11 List of Figures Figure 1 Example ppuserauth.cfg File Figure 2 Example of Business Enterprise Server State Table Figure 3 Windows System Tray Figure 4 Business Enterprise Server Console Drop Down Menu Figure 5 Business Enterprise Server Console Toolbar Business Enterprise Server Installation Guide xi

12 List of Figures xii Business Enterprise Server Installation Guide

13 List of Tables Table 1 Business Enterprise Server System Components Table 2 Business Enterprise Server Third Party Software Table 3 Business Enterprise Server Default File Systems and Directories Table 4 Preparation Checklist for Sybase Supporting Database Table 5 Preparation Checklist for DB2 Supporting Database Table 6 Business Enterprise Server Requirements Table 7 Business Service Dashboard Requirements Table 8 Business Enterprise Server Console Requirements Table 9 Recommended Minimum Disk Space Requirements Table 10 Kernel Configuration Parameter Tasks Table 11 Solaris Kernel Parameters for DB2 UDB Table 12 Solaris Kernel Parameters for Sybase Table 13 Sybase Environment Variables Table 14 Tasks to Install and Prepare the DB2 UDB for Business Enterprise Server 53 Business Enterprise Server Installation Guide xiii

14 List of Tables xiv Business Enterprise Server Installation Guide

15 Preface This book provides detailed instructions on how to install the Business Enterprise Server product. This book is intended for the following groups of users: System administrators who have a working knowledge of Unix and Microsoft Windows operating environments and are responsible for maintaining systems and applications in an enterprise environment Database administrators who have a working knowledge of Sybase Adaptive Server Enterprise and Oracle and are responsible for setting up, configuring, and maintaining databases Business Enterprise Server Installation Guide xv

16 Preface How This Book Is Organised The Business Enterprise Server Installation Guide is organised as follows: Chapter Chapter 1, Overview Chapter 2, Preparing for Installation Chapter 3, Installing the Database Chapter 4, Installing the Business Enterprise Server Chapter 5, Finalising Installation and Starting the Business Enterprise Server Chapter 6, Installing the Business Enterprise Server Console Appendix A, Changing the Business Enterprise Server Database Administrator Password Appendix B, Business Enterprise Server Communication Ports Appendix C, Modifying a Non Clustered Installation of Business Enterprise Server for a Clustered Environment Description Introduces you to the Business Enterprise Server product System requirements that must be met for installation and the tasks that you must accomplish before installing the Business Enterprise Server product Instructions for installing and configuring the Sybase ASE server that is used as the Business Enterprise Server database Instructions for installing the Business Enterprise Server on a Unix host Instructions for completing post installation tasks and testing the Business Enterprise Server Instructions for installing the Business Enterprise Server Console in the Microsoft Windows environment Instructions for changing the password for the main Business Enterprise Server database administrator account Lists the port numbers that are used on the Business Enterprise Server Instructions for modifying specific files within the Business Enterprise Server to move to a clustered installation of Business Enterprise Server xvi Business Enterprise Server Installation Guide

17 Preface Related Documentation In addition to this book and the Business Enterprise Server online help, you can find useful information in the Business Enterprise Server Application and Middleware Integration Guide Business Enterprise Server Automated Notification Integration Guide Business Enterprise Server Automation Guide Business Enterprise Server Distributed Systems Monitoring Tools Integration Guide Business Enterprise Server Enterprise Console Integration Guide Business Enterprise Server Help Desk Integration Guide Business Enterprise Server Integration Guide Business Enterprise Server Integration Release Notes Business Enterprise Server Network Management Systems Integration Guide Business Enterprise Server Protocols and Services Integration Guide Business Enterprise Server Quick Command Reference Guide Business Enterprise Server Release Notes Business Enterprise Server SMARTSla Getting Started Guide Business Enterprise Server Technical Bulletins Business Enterprise Server User Guide Business Enterprise Server Reporting Getting Started Guide Enterprise Dashboard Studio Getting Started Guide Resilient Server for Business Enterprise Server Getting Started Guide Resilient Server for Business Enterprise Server Release Notes Service Configuration Manager Release Notes Service Configuration Manager User Guide Service Modelling Guide Online Books Online versions of the printed guides are available in Portable Document Format (PDF) files. These can be found on the product CD in the Documentation folder. You can view them, print them, or copy them to your computer by using the Acrobat Reader 3.0 or later. Note: To view the PDF files, you need to install (the free) Acrobat Reader onto your system. A copy of this product can be found on the product CD in the Acrobat Reader folder. Business Enterprise Server Installation Guide xvii

18 Preface Conventions The following conventions are used in this book: All syntax, operating system terms, and literal examples are presented in this typeface. In instructions, - boldface type highlights interface or keyboard options that you select; for example, click Next instructs you to click the Next button on a user interface or press Enter to depress the Enter key - enter the following command specifies to type the text shown in the line directly below and to depress the Enter key The symbol => connects items in a menu sequence. For example, Actions=>Create Test instructions you to choose the Create Test command from the Actions menu. In syntax, - path names or system messages, italic text represents a variable, as shown in the following example: The table table_name is not available. system/instance/file_name - vertical bars ( ) separating items indicates that you must choose one item; for example, you can chose a, b, or c a b c - ellipsis (...) indicates that you can repeat the preceding item or items as many times as necessary - square brackets ( [] ) around an item indicate that the item is optional xviii Business Enterprise Server Installation Guide

19 1 1 Overview 1 This chapter introduces you to the Business Enterprise Server product. Topics included are as follows: What is Business Enterprise Server? Components of a Business Enterprise Server System Optional Business Enterprise Server Products and Components Business Enterprise Server Third Party Software Where to Go from Here Business Enterprise Server Installation Guide 1

20 Overview What is Business Enterprise Server? In many organisations, fault management for network, systems, and applications is much less efficient than it could be. Information technology (IT) providers often find it a challenge to keep up with the large quantities of events and performance metrics that must be monitored throughout an ever changing enterprise infrastructure, let alone relate these technology events to the business services they impact. There have been software tools and management platforms that enable events from disparate technologies to be consolidated onto a pane of glass for some time, the Manager of Manager (MOM) products, frameworks, and SNMP managers have all offered this capability to varying degrees of success. However the market place has suffered from a lack of a sound, proven, low to no maintenance event and service management methodology with supporting tools. Based on concepts from the ITIL Service Delivery, Service Level Management discipline, Interlink Software has developed the Business Enterprise Server, a set of software tools that fuse real time event management and service level management. Business Enterprise Server provides the automated service impact analysis of technology events wherever they originated, network, systems, applications etc. This valuable facility enables IT providers to focus on critical, service threatening faults immediately, and often without the need for manual intervention. How do we do it? By automatically associating the real time events with relevant service definition, and service level agreement (SLA) information stored throughout your enterprise whether it resides in an ASCII file, an Asset data store, DB2 on the mainframe, or wherever. In this way Business Enterprise Server determines how technology faults will impact business processes, services, and customers all driven by your existing Service definition and SLA information. 2 Business Enterprise Server Installation Guide

21 Overview Components of a Business Enterprise Server System A single Business Enterprise Server system consists of a database server, the core services that run as daemons, an http Web server, message channels, and a Business Enterprise Server Console. A publish/subscribe message hub is implemented in Java. The following table identifies the main components. Table 1 Business Enterprise Server System Components Component Message Channel AlertServer EventDaemon Dbi BESApi ppmd Description Process by which Business Enterprise Server collects messages from managed sources and creates alerts Main process within Business Enterprise Server that distributes alerts received from the message channels to the Business Enterprise Server clients suppresses, creates, or changes alerts based on defined correlation criteria manages the impact of technology alerts and tracks the alerts against service level agreements saves alerts to a file to ensure that no alerts are lost if one or more clients of AlertServer is unavailable Client of the AlertServer that provides synchronisation between alerts generated by Business Enterprise Server and any connected third party systems (for example, Tivoli Enterprise Console or HP Network Node Manager) Client of the AlertServer that stores alerts in the Business Enterprise Server database and updates alert records in the Business Enterprise Server database Interface between the Business Enterprise Server (Unix code) and the Business Enterprise Server clients (Microsoft Windows Graphical User Interface) such as the Business Service Dashboard and the Business Enterprise Server Console Monitors the Business Enterprise Server message channels and Business Enterprise Server daemons by retrieving the running pid and checking it every second If a message channel or daemon stops running outside a requested stop, ppmd restarts the process within a specified number of seconds. Business Enterprise Server Installation Guide 3

22 Overview Table 1 Business Enterprise Server System Components (Continued) Component Business Enterprise Server Console Business Service Dashboard Description Graphical user interface that you use to define rules that process collected messages and create alerts define enrichment policies that allow you to add meaningful information to alerts define correlation pathways that automatically close sympathetic alerts that are a result of another alert define service level agreements that identify the underlying technology of which a service is composed and the impact the alerts have on the service define automation policies that automate tasks in the Business Enterprise Server environment Graphical user interface that you use to define users and user groups add, modify, and delete message channels view alerts and their the impact on defined service level agreements Optional Business Enterprise Server Products and Components Interlink Software offers several additional products that collect messages or events from other systems provide automated notification provide interfaces to other products, such as help desk software provide reports on the performance of a service These include, but are not limited to, the products identified in the following sections. Interlink Software Services Integration for Agentless Monitoring Interlink Software Services Integration for Agentless Monitoring enables a remote system to share information with Business Enterprise Server by way of executing commands or scripts on the remote system using the SSH or SCP protocol or RSH and RCP protocol. Business Enterprise Server recognises the information collected by the script or command, stores the information in the Business Enterprise Server database, and creates an alert in Business Enterprise Server that represents the information. 4 Business Enterprise Server Installation Guide

23 Overview Interlink Software Services Integration for AlarmPoint The Invoq Systems AlarmPoint product is an automated voice/telephone notification system which we have integrated with Business Enterprise Server. Invoq Systems AlarmPoint provides the ability to disseminate critical business information to the appropriate people quickly when a problem occurs by way of SMS messages, voice telephone, pager, e mail, or fax. Interlink Software Services Integration for AutoOPERATOR The integration between AutoOperator and the Business Enterprise Server enables the sharing of information between Business Enterprise Server and the BMC Software MAINVIEW AutoOPERATOR product. The integration is accomplished by the installation of components in the Business Enterprise Server and MAINVIEW environments. Interlink Software Services Integration for BMC Event Manager Interlink Integration for BEM is a bidirectional integration between the Business Enterprise Server and the BMC Event Manager. When an event is opened in the BMC Event Manager, the event is forwarded to the Business Enterprise Server and a corresponding alert is created that represents the BMC Event Manager event. When a BMC Event Manager alert is assigned, annotated, or closed in the Business Enterprise Server, the originating event in the BMC Event Manager is updated to reflect the action taken (assigned, annotated, and closed). Likewise, when an action is taken on the originating event in the BMC Event Manager, an updated event is collected from the BMC Event Manager and the corresponding alert in the Business Enterprise Server is updated to reflect the action. Interlink Software Services Integration for BMC PATROL Enterprise Manager Interlink Software Services Integration for PATROL EM enables PATROL Enterprise Manager (PATROL EM) to share events with Business Enterprise Server. Events are collected from the PATROL EM server and are processed by Business Enterprise Server and a corresponding alert is created in Business Enterprise Server. When a user performs an operation on an event in PATROL EM, the corresponding alert in Business Enterprise Server reflects the operation; likewise, when an operation is performed on an alert in Business Enterprise Server that corresponds to an event in PATROL EM, the event in PATROL EM reflects the operation. Business Enterprise Server Installation Guide 5

24 Overview Interlink Software Services Integration for BMC Performance Manager This bidirectional integration allows Business Enterprise Server to gather information from BMC Software Performance Manager Agents (formerly named PATROL Agents) running on managed systems. Connections are established via the Performance Manager API. Each event generated by Business Enterprise Server that originated from a Performance Manager Agent contains the application, instance, and parameter from the originating event. Interlink Software Services Integration for Business Enterprise Server The Interlink Software Services Integration for Business Enterprise Server is a bidirectional integration that enables the forwarding of alerts between primary and secondary Business Enterprise Servers. Alerts are synchronized with open, close, add note, acknowledge, assign and any update field events. Any action taken on an alert on the primary or secondary server creates an action event that is passed to the reciprocating server. Interlink Software Services Integration for the Business Enterprise Server Interface Interlink Integration for the Business Enterprise Server Interface enables users and other programs to create alerts in the Business Enterprise Server. The alerts are standardised using the common alert format (CAF). Interlink Software Services Integration for HP Network Node Manager This integration enables the HP NNM Server to share information with Business Enterprise Server. Business Enterprise Server recognises the NNM event, stores the event information in the database and creates an alert in Business Enterprise Server that represents the NNM event. Interlink Software Services Integration for HP OpenView IT/Operations The integration between HP/OpenView IT/Operations and Business Enterprise Server enables the HP OpenView IT/Operations (ITO) product to share events with Business Enterprise Server. ITO events are displayed as alerts in Business Enterprise Server. When an event is opened and acknowledged in ITO the same state is reflected in its corresponding alert in Business Enterprise Server. If an ITO alert is closed in Business Enterprise Server, its corresponding event is closed in ITO. 6 Business Enterprise Server Installation Guide

25 Overview Interlink Integration for HP OVOW Interlink Integration for HP OVOW enables bidirectional integration between HP OpenView Operations for Windows (hereinafter referred to as HP OVOW) and the Business Enterprise Server. Any alert updated in either application is automatically forwarded to its reciprocating application to update its corresponding alert. Interlink Software Services Integration for HP Service Manager HP Service Manager (formerly known as Peregrine Systems Service Center) is a problem management solution that enables users to track and resolve service requests that Interlink Software has integrated with the Business Enterprise Server. Problems identified in Business Enterprise Server are passed to the Service Manager as action requests for tracking and resolution. As an action request is updated or resolved in Service Manager, the corresponding alert in Business Enterprise Server is updated. Updates in Business Enterprise Server such as notations and closures to the original alert can be synchronised back to Service Manager. Interlink Software Services Integration for IBM Tivoli Enterprise Console The Interlink Integration for IBM Tivoli Enterprise Console integrates Business Enterprise Server with the Tivoli Management Environment (TME). Interlink Integration for IBM Tivoli Enterprise Console provides you with the ability to use the Business Service Dashboard and the Tivoli Enterprise Console (TEC) to monitor and manage alerts and events, with common attributes represented consistently across both consoles. Interlink Software Services Integration for IBM Tivoli Monitoring Interlink Integration for ITM is a unidirectional integration that enables the sharing of event information displayed in the Tivoli Enterprise Portal with Business Enterprise Server. Business Enterprise Server recognises an event retrieved from an ITM system and stores the event information in the Business Enterprise Server database and creates an associated alert that represents the ITM event which is displayed in the Business Service Dashboard. Interlink Software Services Integration for IBM Tivoli Netcool/OMNIbus This integration provides integration between the Business Enterprise Server and Netcool. When an event in Netcool occurs, the event is forwarded to the Business Enterprise Server and is processed as an alert in the Business Enterprise Server environment. When an action occurs against the alert associated with a Netcool event, the action is forwarded to Netcool and the event is updated to reflect the action taken in the Business Enterprise Server environment. Business Enterprise Server Installation Guide 7

26 Overview Interlink Software Services Integration for IBM Websphere MQ Interlink Software Services Integration for IBM Websphere MQ is a unidirectional connection between the IBM Websphere MQ environment to the Business Enterprise Server environment. Interlink Software Services Integration for mailx This integration enables you to automate e mail notification for alerts in the Business Enterprise Server by sending an e mail with the alert details by way of mailx. Interlink Software Services Integration for Microsoft Operations Manager This integration enables the Microsoft Operations Manager (MOM) to forward alerts to Business Enterprise Server. Any alert updated in MOM is automatically forwarded to Business Enterprise Server and the corresponding alert in Business Enterprise Server is updated accordingly. Interlink Software Services Integation for Microsoft System Center Operations Manager 2007 Interlink Integration for SCOM enables the Microsoft System Center Operations Manager (SCOM) to forward alerts to Business Enterprise Server. Any alert updated in SCOM is automatically forwarded to Business Enterprise Server and the corresponding alert in Business Enterprise Server is updated accordingly. Interlink Software Services Integration for NetIQ AppManager The integration between the NetIQ AppManager and Business Enterprise Server enables the forwarding of events between applications. When an event is forwarded from one application to another, its associated alert within the respective application (NetIQ AppManager or Business Enterprise Server) is updated to reflect the state of the event that is forwarded. Interlink Software Services Integration for Oracle Database Interlink Integration for Oracle Database is a unidirectional integration between an Oracle database and Business Enterprise Server that enables forwarding of alerts from an Oracle database to the Business Enterprise Server. 8 Business Enterprise Server Installation Guide

27 Overview Interlink Software Services Integration for Oracle Enterprise Manager Interlink Software Services Integration for Oracle Enterprise Manager receives alert data from a JMS server from which the Oracle Enterprise Manager forwards the alert data. The integration between Oracle Enterprise Manager and Business Enterprise Server is unidirectional. Interlink Software Services Integration for Quest Foglight Interlink Integration for Quest Foglight provides bi directional integration between Quest Foglight and the Business Enterprise Server using Foglight s web service. Any action taken on an a Folight alert in the Business Enterprise Server is forwarded to Foglight to synchronise the events and alerts between the two applications. Interlink Software Services Integration for Remedy AR System Remedy AR System is a problem management solution that enables users to track and resolve service requests that Interlink has integrated with Business Enterprise Server. Problems identified in Business Enterprise Server are passed to Remedy as action requests for tracking and resolution. As an action request is updated or resolved in Remedy AR System, the corresponding alert in Business Enterprise Server is updated. Interlink Software Services Integration for SNMP The integration between SNMP and Business Enterprise Server enables SNMP trap messages to be displayed in the Business Enterprise Server as alerts. The integration product receives and decodes SNMP traps. A program called iss_snmplistener, which is a component of the integration for SNMP, expands the range of SNMP traps that can be received by Business Enterprise Server by loading third party MIBs. Interlink Software Services Integration for Sun Management Center Interlink Integration for Sun Management Center provides bidirectional integration between the Sun Management Center (SMC) and Business Enterprise Server. Interlink Integration for SMC retrieves events from the Sun Management Center (SMC) environment and creates alerts in the Business Enterprise Server for display in the Business Enterprise Server environment. When an action occurs against an alert associated with a SMC event, whether in SMC or Business Enterprise Server, the action is forwarded to the reciprocating environment (SMC to Business Enterprise Server or Business Enterprise Server to SMC) and the event is updated to reflect the action taken in the SMC or Business Enterprise Server environment. Business Enterprise Server Installation Guide 9

28 Overview Interlink Software Services Integration for Web Services Interlink Software Services Integration for Web Services enables communication by way of HTTP between an application and the Business Enterprise Server that is not platform dependent. Any application that can communicate by way of HTTP can create, assign, close, and add notes to an alert in the Business Enterprise Server environment. Business Enterprise Server Reporting A Business Enterprise Server client that enables operations staff, support staff, business users, and customers to view historical reports on the availability of end to end services regardless of the underlying technologies and managed platforms deployed throughout an enterprise organisation. Business Enterprise Server Third Party Software Business Enterprise Server includes several third party software packages in its distribution. Table 2 lists the third party software included in Business Enterprise Server. Table 2 Business Enterprise Server Third Party Software Third Party Software Sybase Adaptive Server Enterprise (32 bit Version) uni REXX 2.99a and Interlink Function Set Version Apache Tomcat Expat Description Data store for configuration and run time data of the Business Enterprise Server system and its integration products Scripting language used for automated operations and other purposes Business Enterprise Server provides APIs for database access. Web server for supporting the Business Service Dashboard Application server for supporting the Business Service Dashboard Fast, non validating, stream oriented XML parsing library that is required by the XML Parser Perl extension 10 Business Enterprise Server Installation Guide

29 Overview Table 2 Business Enterprise Server Third Party Software (Continued) Third Party Software Perl and extensions DBI 1.601, DBD DB2 1.1, DBD Sybase 1.08, Expect 1.21, IO tty 1.07, Net Telnet 3.03, PathTools 3.27, Sybperl 2.18, XML Parser 2.36, and Proc Background 1.08 Description Programming language used to create customisation programs and for the operation of Business Enterprise Server TCL/TK and extension TIX Note: If you do not want to use the Sybase Adaptive Server Enterprise as your underlying database, you can obtain a copy of the DB2 Enterprise Server from IBM. Any of the following the IBM DB2 Enterprise Server Editions are supported by Business Enterprise Server: 8.1 FixPack FixPak Fixpack 3 Where to Go from Here Programming language used to create customisation programs and for the operation of Business Enterprise Server For instructions on preparing a host system prior to installing the Business Enterprise Server product, go to Chapter 2, Preparing for Installation. Business Enterprise Server Installation Guide 11

30 Overview 12 Business Enterprise Server Installation Guide

31 2 1 Preparing for Installation 2 This chapter provides the system requirements that must be met for installation and the tasks that you must accomplish before installing the Business Enterprise Server product. The Business Enterprise Server product consists of the following components: Database Server (Sybase ASE or DB2) Business Enterprise Server Business Enterprise Server Console Sybase ASE or DB2 is used as the Business Enterprise Server database. Sybase ASE is included in the Business Enterprise Server package that you received; DB2 must be obtained from International Business Machines (IBM). Note: [SYBASEDIR] refers to the users chosen installation directory for Sybase. Installation path on pg22 is shown for example purposes only. Topics included are as follows: Business Enterprise Server File Systems and Directories Business Enterprise Server Database Preparation Checklist Ensuring That the Host Meets the System Requirements Allocating Disk Space and Devices Creating the Sybase Installation Directory Creating the Business Enterprise Server Administration User Accounts and Group..25 Changing Ownership and Group Permission on the Sybase Installation Directory...28 Setting a File Size Security Limit Changing Kernel Configuration Parameters Limiting the Number of Threads per Process Setting TCP Node Layer Acknowledgement Rebooting to Implement System Changes Mounting a CD ROM Drive Migrating from Business Enterprise Server 3.4 to Retrieving Installation and Configuration Software for Sybase ASE and Business Enterprise Server Where to Go from Here Business Enterprise Server Installation Guide 13

32 Preparing for Installation Business Enterprise Server File Systems and Directories In a new installation, the Business Enterprise Server files (that is, all the binaries and libraries) are stored in the default file systems and directories listed in Table 3. Table 3 Business Enterprise Server Default File Systems and Directories Default File System /opt/iss [SYBASEDIR]/data [SYBASEDIR] /home /var/spool/iss /var/log/iss Contains Binaries and libraries pertaining to Business Enterprise Server and product options including third party installed software (such as uni REXX) Database devices that you store in a file system Adaptive Server executable files Home directories for Business Enterprise Server users Messages logged by Business Enterprise Server Business Enterprise Server Database The Business Enterprise Server can use the Sybase Adaptive Server Enterprise (hereinafter referred to as the Adaptive Server) Version or the IBM DB2 as its underlying database. Adaptive Server In a new Business Enterprise Server installation using the Adaptive Server, the installation program builds the Adaptive Server system databases and then the Business Enterprise Server database. The Adaptive Server system databases consist of the master database, the model database, the sybsystemprocs database, and the tempdb database. The Adaptive Server system databases consist of the master database, the model database, the sybsystemprocs database, and the tempdb database. 14 Business Enterprise Server Installation Guide

33 Preparing for Installation DB2 By default, Adaptive Server stores the master, model, and tempdb databases on the master device (you can choose to store the tempdb database on a separate device during installation). For further information about these databases, refer to the Sybase Adaptive Server Enterprise documentation at The Business Enterprise Server database is called the ppdb database. You can store the ppdb database on a separate device from the master device or on the same device. Devices are also required for the transaction log segment and the database dump device. Each component of the database requires a device to be allocated. The device can be a raw device or a Unix file system. In the case of the dump device, the device can be a tape drive or a Unix file system. For detailed space requirements and the recommended storage devices, see Allocating Disk Space and Devices on page 21. If you are installing Business Enterprise Server with DB2 as the supporting database, you must create a database. For information on space requirements; see Allocating Disk Space and Devices on page 21 database specific requirements; see Creating a DB2 Database for Business Enterprise Server on page 60 Preparation Checklist Before starting the Business Enterprise Server Unix server installation program, you need to prepare the server for installation. If you decide to add more than one Business Enterprise Server, each server needs the same requirements identified as the single server used in the initial installation. Use Table 4, Preparation Checklist for Sybase Supporting Database, on page 16 and Table 5, Preparation Checklist for DB2 Supporting Database, on page 16 to identify the tasks that you must complete on the host server before installing Business Enterprise Server using Sybase ASE or DB2 as the supporting database. Business Enterprise Server Installation Guide 15

34 Preparing for Installation Platform Table 4 Preparation Checklist for Sybase Supporting Database Task AIX Sun Description Go to 1 x x Ensure that the host machine meets the minimum system requirements Table 5 Preparation Checklist for DB2 Supporting Database page 17 2 x x Allocate disk space and devices page 21 3 x x Create a [SYBASEDIR] directory page 25 4 x x Create Unix user accounts and group definitions for Business Enterprise Server administration 5 x x Change ownership and group permission on the [SYBASEDIR] directory page 25 page 28 6 x x Change write permission on the /var/tmp directory page 28 7 x Set a file size in the /etc/security/limits file page 28 8 x Change kernel configuration parameters page 29 9 x x Limit the number of threads per process page X Set TCP Node Layer Acknowledgement to immediate page x x Reboot to implement system changes page x x Mount a CD ROM drive for the installation CD page 33 Task Description Go to 1 Ensure that the host machine meets the minimum system requirements page 17 2 Allocate disk space and devices page 21 3 Create Unix user accounts and group definitions for Business Enterprise Server administration page 25 4 Change kernel configuration parameters page 29 5 Limit the number of threads per process page 32 6 Set TCP Node Layer Acknowledgement to immediate page 32 7 Reboot to implement system changes page 32 8 Mount a CD ROM drive for the installation CD page Business Enterprise Server Installation Guide

35 Preparing for Installation Ensuring That the Host Meets the System Requirements This section identifies the requirements that a host system must meet before installing the Business Enterprise Server product. Ensure that the machine on which you plan to install Business Enterprise Server meets the minimum hardware and software requirements defined in the following sections and any additional information contained in the Business Enterprise Server Release Notes. Business Enterprise Server Requirements Use Table 6 to identify the requirements that must be met for the host system on which you are installing the Business Enterprise Server. Table 6 Business Enterprise Server Requirements Resource Platform Minimum Requirements Sun or IBM system with dual 600 MHz processor 2GB RAM 40GB free disk space Operating system Solaris When Sybase ASE is the underlying database, Solaris must be version 9 or higher Solaris 9 must be a full installation with the libiconv and libgcc files installed and the following patches applied: Solaris 10 must be a full installation at patch level with libgcc files installed See Installing Solaris on page 18 and Installing libiconv and libgcc Files on page 19 AIX Version 5.3 at TechLevel 06 and higher, including AIX Partition Mobility Version 6.1 Business Enterprise Server Installation Guide 17

36 Preparing for Installation Table 6 Business Enterprise Server Requirements (Continued) Resource Minimum Requirements Third party software If the host will have the IBM DB2 Enterprise Edition as the underlying database for the Business Enterprise Server, you can use any of the following IBM DB2 Enterprise Server Editions: 8.1 FixPack FixPack Fixpack 3 Installing Solaris For Solaris, use Java Runtime Environment (JRE) 1.5 or higher The Java runtime software is contained on your operating system distribution set. For AIX, use Java Runtime Environment 1.5 or higher Note: Java 1.5 is also referred to as Java 5.0. Interlink Software recommends that you do not install the Java Development Kit (JDK) instead of the JRE. Installing the JDK enables debug mode that produces a vast amount of verbose output and could fill up the file system, causing problems with the operating system which could lead to downtime for a production Business Enterprise Server system. For customers operating in environments that are affected by Daylight Savings Time, upgrade your Java environment based on your locale and Java version by March 11, For U.S. time zones and Sun Java 5.0, upgrade to Java 5.0, Update 6 Brazil, Western Australia, Canada, Bermuda time zones and IBM Java 5.0, upgrade to Java 5.0 SR4 For additional information on Daylight Savings Time, go to for Solaris and DST_Java.html for AIX. The Business Enterprise Server requires a full installation of the Solaris 2.9 operating environment. If you have not already installed Solaris 9, during installation select the following option in the Select Solaris Cluster Configuration dialog box: - Entire Solaris Software Group plus OEM If you have already installed Solaris, enter the following command to check the contents of the CLUSTER file to determine if a complete installation occurred. cat /var/sadm/system/admin/cluster 18 Business Enterprise Server Installation Guide

37 Preparing for Installation The following response is displayed: CLUSTER=SUNWCxxx The variable SUNWCxxx can be any of the following values: - SUNWCREq Core Solaris Software Group - SUNWCuser End User Solaris Software Group - SUNWCprog Developer Solaris Software Group - SUNWCall Entire Solaris Software Group - SUNWCXall Entire Solaris Software Group Plus OEM If the value is not SUNWCXall, you must reinstall Solaris. Installing libiconv and libgcc Files This version of Business Enterprise Server searches for the following files in the /usr/local/lib directory which are not present in some of the Solaris 9 and 10 Sparc environments. libiconv files for the Solaris 9 and 10 libgcc files for the Solaris 10 To resolve the issue, create a /usr/local/lib directory and retrieve the libiconv 1.14 and libgcc files from the sunfreeware web site. To Obtain the libiconv 1.14 and libgcc Files Step 1 Open a command window on the server and enter the following command to display the Solaris Sparc version that you are running. Step 2 Step 3 Step 4 Step 5 uname a Open a browser and type the following URL to go the sunfreeware web site. In the list on the right side of the window, select your Solaris Sparc operating environment to display a list of the packages available for retrieval. Scroll down the list until you find the libiconv 1.14 or libgcc link and select it. Scroll down the page to find the appropriate file and follow the directions as noted by the web site for retrieving the file for installation on the Business Enterprise Server. For Solaris Sparc Retrieve this file 9 libiconv 1.14 sol9 sparc local.gz 10 libiconv 1.14 sol10 sparc local.gz libgcc sol10 sparc local.gz Business Enterprise Server Installation Guide 19

38 Preparing for Installation Business Service Dashboard Requirements Use Table 7 to determine the requirements that must be met for the PC on which you intend to execute the Business Service Dashboard. Table 7 Business Service Dashboard Requirements Resource Requirements Hardware Minimum 1GB RAM single 3 GHz processor Browser Runtime environment Recommended 2GB RAM Dual core processor Internet Explorer 7 or higher The following operating systems support Internet Explorer 7.0 or higher: Microsoft Windows XP with SP1 or higher Microsoft Windows Vista with SP1 or higher Microsoft Windows Server 2003 with SP1or higher Microsoft Windows Server 2008 with SP1 or higher Business Service Dashboard provides two sets of standard views that graphically portray the status of your enterprise. One set uses Java and the other uses the.net Framework. If you want to see the standard views that use Java, you must have a copy of the Microsoft Virtual Machine or the Sun Microsystems Java Virtual Machine Go to to obtain a copy of the Sun Microsystems Java Virtual Machine if it is not already installed on your system..net Framework, you are required to install the.net Framework 2.0 with Service Pack 2 or higher Redistributable Package and the Microsoft Visual J# Version 2.0 Redistributable Package and the Trust Interlink Certificate The.NET Framework and the Microsoft Visual J# Redistributable Packages can be obtained from the Microsoft web site; go to The Trust Interlink Certificate can be obtained from the Interlink Software website. Note: If you install.net Framework Version 3.5 Service Pack 1, the ServiceLayout_NET view becomes unusable because the nodes are not layered correctly because of a bug in the Microsoft product. Use Version 2.0 with Service Pack 2 to circumvent this issue until such time as the bug has been resolved due to Version 3.0 does not contain the code for Version 2.0 Service Pack 2 which resolved previously known issues with.net Framework. For information on the bug, go to dbackid= Business Enterprise Server Installation Guide

39 Preparing for Installation LDAP Authentication Requirements If you plan on using an LDAP server to authenticate Business Service Dashboard users, you must install a third party software package on the authenticating server that supports the LDAP v3 or higher protocol such as OpenLDAP freeware or Microsoft Active Directory. Interlink Software is not responsible for maintenance of the LDAP directory structure. LDAP authenticated users must be added into the Business Enterprise Server database by way of the Business Service Dashboard Admin Console so that the abilities of the users such as displaying views and performing operator actions for the authenticated user are stored in the Business Enterprise Server database. Business Enterprise Server Console Use Table 8 to identify the requirements that must be met for each host system on which you are installing the Business Enterprise Server Console. Table 8 Business Enterprise Server Console Requirements Resource Platform Operating system Description PC with Pentium III class processor 512MB RAM 200MB free disk space Screen resolution 1024 x 768 c:\temp directory Microsoft Windows 2000 with SP1, SP2, SP3 and SP4 installed Microsoft Windows XP; SP1 and SP2 installed Microsoft Windows 2003; SP1 and SP2 installed Allocating Disk Space and Devices Before installation, ensure that the necessary space and devices are available for the Business Enterprise Server file systems and the Business Enterprise Server database. The total disk space required for both file systems and database devices when all devices are stored on the same disk are shown in Table 9 on page 22. The database is installed on the Business Enterprise Server host where the primary installation occurs and is also referred to as the database server. All database devices must be stored on the database server. Business Enterprise Server Installation Guide 21

40 Preparing for Installation If you are installing for the Business Enterprise Server a supporting database of DB2, only the first four entries in Table 9 apply Sybase ASE database, all entries in Table 9 apply including the subsequent subsections Table 9 Recommended Minimum Disk Space Requirements File System Space Required Comments / 1GB 380MB for /opt/iss Root and swap directories /home /usr /opt Adaptive Server master, model and tempdb databases Sybase stored procedures Business Enterprise Server database (ppdb) 20MB per user 450MB 600MB Raw device or file system 30MB for master and model Raw device or file system 100MB Raw device or file system 3GB Adaptive Server system databases and the Business Enterprise Server database can reside on the same device. For optimum performance, place the Adaptive Server system databases and the Business Enterprise Server database on separate physical devices. Do not place the stored procedures database in the same file system as the Adaptive Server distribution (example: /opt/sybase/) If you use a raw device for both the Adaptive Server master database and the stored procedures database, do not locate the stored procedures database on the same raw device as the master database. For optimum performance, place the ppdb on a dedicated device Before configuring the file system for the ppdb, see Enabling Large File Support on page Business Enterprise Server Installation Guide

41 Preparing for Installation Table 9 Recommended Minimum Disk Space Requirements (Continued) File System Space Required Comments Business Enterprise Server transaction log (ppdbtransactionlog) Database dump device Raw device or file system 25% of the ppdb database size Tape drive or file system See comments Note: The Business Enterprise Server installation changes the Adaptive Server dsync setting to enabled for database devices that are initialised on Unix file systems. Enabling dsync ensures that data is written to the disk immediately and not buffered by the Unix file system. When dsync is disabled, data recovery on the device cannot be ensured. Allocating Raw Devices for the Sybase Database To avoid data loss, place the transaction log and the ppdb on separate devices If the transaction log shares space with the Business Enterprise Server database, recovery from a database full condition is not possible without loss of data. Do not store the transaction log on a temporary device. If you define ppdump as a disk device, allocate sufficient space in the directory for the ppdump device to handle the Adaptive Server master database stored procedures database Business Enterprise Server database Before configuring the file system for ppdump, see Enabling Large File Support on page 24. The Adaptive Server database optionally requires a raw device on the host machine where it is installed. You can distribute the master database, the Business Enterprise Server (ppdb) database, the stored procedures database (sybsystemprocs), and the Business Enterprise Server (ppdbtransactionlog) transaction log segment to one or more disk devices, as long as all disk partitions reside on the same host machine. To distribute the Adaptive Server master database, the ppdb database, and the ppdb Business Enterprise Server Installation Guide 23

42 Preparing for Installation transaction log segment over several devices on the same host, Interlink Software recommends the devices are spread across different file systems or physical disks. Note: When you use a raw device, the first 512 bytes must be reserved for the operating system. The operating system uses the reserved space for recording information about the raw device, such as the creation date, mirrored copies, and possible mount points in the journaled file system. Warning: The Adaptive Server system databases cannot be stored on a Network File System (NFS). Once you initialise a raw device for the Adaptive Server, that device cannot be used for any other purpose. For complete information about allocating disk resources for the database, review the Sybase Adaptive Server Enterprise installation and system administration documentation. Enabling Large File Support Files larger than 2GB in the AIX environment require that you enable Large File Support for the journaled file system. The file system where you plan on installing the database (for example, [SYBASEDIR]) and the file system that will be used as the dump device (for example, /opt/ppdump) must have Large File Support. Large File Support can only be enabled when you define the journaled file system. If you have already defined a file system larger than 2GB that does not have Large File Support enabled, refer to 1.ibm.com/support/docview.wss?uid=isg1pTechnote0448 for instructions on how to enable Large File Support. Distributing Sybase Files and Databases in a SAN Environment If you plan on distributing the Sybase ASE files and databases in a SAN environment, you must conform to the following requirements: Sybase files (for example, ASE15 and errorlog) reside on a single disk partition that is mounted using TCP. Sybase databases (for example, master and ppdb) reside on a separate disk partition that is mounted using UDP. The two disk partitions can be on the same physical disk but must have separate names. 24 Business Enterprise Server Installation Guide

43 Preparing for Installation Creating the Sybase Installation Directory When you install Sybase ASE on your host system, you must have a default directory in which to install defined on the host system. The installation script defines /opt/sybase as the recommended directory for installation. The default directory is used for installation whether you specify raw devices or files systems for your database structure. To Create the Sybase Installation Directory As user root, enter the following command: mkdir [SYBASEDIR] Creating the Business Enterprise Server Administration User Accounts and Group Before you install Business Enterprise Server, you must create the following user group and users: A Unix user group named ppusers and a Unix user account named ppadmin for running and administering Business Enterprise Server The ppadmin user account performs all Business Enterprise Server functions. Restrict account access to customisers and administrators. For further information, see Managing User Access in the Business Enterprise Server User Guide. Note: During installation of the Business Enterprise Server with a DB2 database, the ppadmin user is added to the DB2 install user group. A Unix user account named sybase (the default) for accomplishing Adaptive Server database tasks, such as restarting the database You can create this user account using the default account name sybase or you can use an account name of your choice. Business Enterprise Server Installation Guide 25

44 Preparing for Installation To Create the Business Enterprise Server Administration User Accounts and Group Step 1 As user root, define a ppusers group with the following properties: Property Value Group Name ppusers Group ID Number between 100 to (the default is 100) Step 2 Define a ppadmin Unix user account with the following properties: Property User Name User ID Shell Home Group ID Group Name Value ppadmin Number ranging from 199 to (the installation default is 199) Choose a number that is not currently used and is valid for your operating system. Path to the default login shell: /bin/csh for C shell /bin/ksh for Korn shell, /bin/sh for Bourne shell Full path of the home directory for ppadmin (the installation default is /home/ppadmin) Notes: Uncomment any auto mount of /home from the system. The /home directory for ppadmin will be created during installation, if it does not already exist. If your user management facility does not allow a user account to be created without a /home directory, create an empty home directory for ppadmin. Group ID number assigned to the ppusers group ppusers 26 Business Enterprise Server Installation Guide

45 Preparing for Installation Step 3 Define an Adaptive Server Unix user account with the following properties: Property User Name User ID Shell Home Group ID Group Name Value sybase Number ranging from 198 to (the installation default is 198) Choose a number that is not currently used and is valid for your operating system. Path to the default login shell, /bin/csh for C shell Full path of the home directory for the Adaptive Server account (the installation default is /opt/sybase) Note: The home directory for the Adaptive Server user account will be created during installation, if it does not already exist. If your user management facility does not allow a user account to be created without a home directory, create an empty home directory for the Adaptive Server user account. Group ID assigned to the ppusers group ppusers Step 4 Step 5 Set the password for ppadmin. Note: The password must be a minimum of 6 characters and contain alpha and numeric characters (for example, pass58wd). If you are defining for your supporting database DB2, proceed to Changing Kernel Configuration Parameters on page 29 Sybase, perform Step 5 If you are defining Sybase as your supporting database, prevent users from logging in to the Adaptive Server user account by locking password entry to the account. When the password for the sybase account is locked, you must use su from root to enter it. As user root in Solaris, enter passwd l sybase AIX, lock the account using the SMIT tool Business Enterprise Server Installation Guide 27

46 Preparing for Installation Changing Ownership and Group Permission on the Sybase Installation Directory After you have created the users, you must change the ownership and group permission for the installation directory to reflect the ASE user and group permission that you created, so that the ASE Server install does not fail. To Change Ownership and Group Permission As user root, enter the following command: chown R sybase:ppusers [SYBASEDIR] Changing Write Permission for /var/tmp You must ensure that user ppadmin has write permission on /var/tmp. If write permission is not given, the BESApi function will fail and a couldn t create error file for command: no such file or directory error message will be written to the POWERpack_Log file. The following is an example command that can be issued as user root to give write permission to all users. If you do not want to grant permission to all users, use the appropriate command that meets your security requirements. chmod 777 /var/tmp Setting a File Size Security Limit Installation of Sybase ASE and Business Enterprise Server in the AIX environment requires that you set a file size in the /etc/security/limits file. Specify a size of any by defining a value of 1 for the fsize parameter. You can specify that the file size be limited to a specific user or to all users. If you choose to limit the file size to specific users, create an fsize entry for the following users: root sybase ppadmin 28 Business Enterprise Server Installation Guide

47 Preparing for Installation The following example is an excerpt of the default section of /etc/security/limits file showing the fsize parameter defined as 1: default: fsize = -1 core = cpu = -1 data = rss = stack = nofiles = 2000 Changing Kernel Configuration Parameters IBM recommends the following parameters be set in the kernel for an AIX 5.3 operating environment in which Business Enterprise Server executes: Kernel parameter Value minfree 960 maxfree 1728 minperm% 5 maxperm% 90 maxclient% 90 lru_file_repage 0 strict_maxclient 1 To run Business Enterprise Server effectively in the AIX and Solaris environments, some kernel configuration parameters must be adjusted. Perform the appropriate tasks for your operating system to adjust the parameters. After you adjust all kernel configuration parameters, you must reboot the system (see Rebooting to Implement System Changes on page 32). Table 10 Kernel Configuration Parameter Tasks System Task Go to AIX Increase the number of processes per user page 30 Solaris Setting Up the Kernel Parameters for Solaris page 30 AIX Set Asynchronous I/O page 31 Business Enterprise Server Installation Guide 29

48 Preparing for Installation Increasing the Number of Processes per User in AIX To run Business Enterprise Server effectively in the AIX environment, you must increase the number of processes allowed for each user to at least 200. You can increase the number of processes by using the procedures that follow or you can allow the installation program to update them automatically. To Increase Number of Processes per User in AIX Step 1 Step 2 As user root, enter the following command: chdev l sys0 a maxuproc= 200 When all tasks in this chapter are complete, reboot the system as directed in Rebooting to Implement System Changes on page 32. Setting Up the Kernel Parameters for Solaris Step 1 Step 2 As user root, back up /etc/system according to your installation policies. Open the /etc/system file and add the appropriate entries using the kernel parameter values defined in Table 11 or Table 12 on page 31 and the following syntax: set kernel_parameter = value Table 11 Solaris Kernel Parameters for DB2 UDB Physical Memory Kernel Parameter MB MB MB 512+ MB msgsys:msginfo_msgmax msgsys:msginfo_msgmnb msgsys:msginfo_msgmap msgsys:msginfo_msgmni msgsys:msginfo_msgssz msgsys:msginfo_msgtql msgsys:msginfo_msgseg shmsys:shminfo_shmmax shmsys:shminfo_shmseg shmsys:shminfo_shmmni semsys:semnifo_semmni semsys:seminfo_semmap Business Enterprise Server Installation Guide

49 Preparing for Installation Table 11 Solaris Kernel Parameters for DB2 UDB (Continued) Physical Memory Kernel Parameter MB MB MB 512+ MB semsys:seminfo_semmns semsys:seminfo_semmnu semsys:seminfo_semume Table 12 Solaris Kernel Parameters for Sybase Kernel Parameter Minimum Value Step 3 Save the file. Step 4 Proceed to Rebooting to Implement System Changes on page 32 Setting Asynchronous I/O in AIX Setting the Asynchronous I/O to Available in AIX is required for proper operation of the Adaptive Server. To Set the Asynchronous I/O in AIX Step 1 Step 2 Step 3 Step 4 shmsys:shmino_shmmax msgsys:msginfo_msgmax msgsys:msginfo_msgmnb msgsys:msginfo_msgmni 50 msgsys:msginfo_msgtql 500 As user root, using the System Management Interface Tool (SMIT), navigate to Devices, select Asynchronous I/O, and then select Change/Show Characteristics of Asynchronous I/O. At the State to be configured at the system restart prompt, click List and select Available. Click OK and exit SMIT. When all kernel configuration changes are complete, reboot the system as directed in Rebooting to Implement System Changes on page 32. Business Enterprise Server Installation Guide 31

50 Preparing for Installation Limiting the Number of Threads per Process Each instance of the Business Service Dashboard has its own set of threads for sending/receiving alerts from the AlertServer. Check your operating system settings to ensure that there are no limits imposed on the number of threads per process; if limits are imposed, amend as needed. Setting TCP Node Layer Acknowledgement TCP Node Layer Acknowledgement specifies whether acknowledgment is sent immediately on receipt of data. Acknowledgement must be set for immediate to ensure minimal delay of message processing at the message channel. To Set the TCP Node Layer Acknowledgement Step 1 Step 2 As user root, open a command window on the AIX system and enter the following command to determine the acknowledgement setting: no a grep nodelay Perform the appropriate action based on your results: If output returns tcp_nodelayack = 1 tcp_nodelayack = 0 Do this action No change is necessary Enter the following command to change the setting to immediate: no p o tcp_nodelayack=1 Rebooting to Implement System Changes You must reboot the host after changing kernel parameters. To reboot the host so that all kernel changes take effect, refer to the appropriate procedure below. To Reboot an AIX or Solaris Host As user root, enter the following command: reboot 32 Business Enterprise Server Installation Guide

51 Preparing for Installation Mounting a CD ROM Drive The Business Enterprise Server installation requires a CD ROM drive to be mounted. Instructions for mounting a local CD ROM and a remote CD ROM follow. Mounting a Local CD ROM Drive Step 1 Step 2 As user root on the Business Enterprise Server database server, enter the following command to create a /cdrom directory. mkdir /cdrom Issue the appropriate command to mount the CD ROM drive. Operating system AIX Solaris Command example In AIX, some configurations can use a variation of cd0; to determine the variation on the target system, use SMIT. mount v cdrfs r /dev/cd0 /cdrom In some Solaris systems, devices are mounted automatically by vold so a mount command is not required. mount F hsfs o ro /dev/dsk/c0t6d0s0 /cdrom or mount F hsfs o ro /dev/sr0 /cdrom Some configurations can use a variation of c0t6d0s0 or sr0. Mounting a Remote CD ROM Drive Step 1 Step 2 Step 3 As user root on the remote system, mount the CD ROM drive using the steps in Mounting a Local CD ROM Drive. Export the device (CD ROM drive) for an NFS mount. Refer to your operating system documentation for the correct command. As user root on the local system, verify that a mount point (such as /mnt) exists; if not, enter the following command to create one. mkdir /mnt Business Enterprise Server Installation Guide 33

52 Preparing for Installation Step 4 Mount the remote system /cdrom directory by entering the following command: mount type_option remote_host:/cdrom /mnt Where: type_option indicates an NFS type mount; refer to your operating system documentation for the correct option remote_host is the name of the remote system Upgrading to Business Enterprise Server 3.5 If you are upgrading to Business Enterprise Server 3.5 from a previous version, refer to the appropriate section. Upgrading from POWERpack 3.0 or 3.1 Due to the numerous changes to the underlying database and the structure of the Business Enterprise Server environment, you must contact Interlink Software to transition from POWERpack to the Business Enterprise Server. Upgrading from Business Enterprise Server 3.2 or 3.3 Business Enterprise Server, Version 3.5 includes a new version of Tomcat and Apache. If you modified the Apache configuration file (httpd.conf) in version 3.2 or 3.3 above the initial setup, the modifications are not migrated during upgrade. The httpd.conf file, however, is archived during the upgrade process so that you can view the file and add the modifications to the new httpd.conf file. The version 3.2 or 3.3 archived httpd.conf file is located in the apache/conf_x.x directory after upgrade; the variable x.x is either 3.2 or 3.3. The version 3.5 httpd.conf file is located in the $PPHOME/eScape/apache/conf directory. If the underlying database for Business Enterprise Server is Sybase ASE, you must migrate the Version 3.2 or 3.3 data to Version Business Enterprise Server Installation Guide

53 Preparing for Installation Upgrading from Business Enterprise Server 3.4 to 3.5 If the underlying database for Business Enterprise Server is DB2, the Business Enterprise Server 3.5 installation provides the upgrade process Sybase ASE, you must migrate the Version 3.4 data to Version 3.5 The process of migration is the backing up of the database and the requisite configuration files on a 3.4 system and restoring the database and configuration files to a 3.5 system and then upgrading to meet the 3.5 changes Retrieving Installation and Configuration Software for Sybase ASE and Business Enterprise Server Included with the Business Enterprise Server, Version 3.5 product is the Business Enterprise Server CD. The CD contains the following files: File Sybase/OS/ase1503_OS_2.tgz Sybase/OS/number.lic BES.tar Description Compressed file containing installation and configuration software for Sybase ASE, Version License file that is to be used to license Sybase ASE during installation Compressed file containing installation and configuration software for Business Enterprise Server, Version 3.5 Where OS is the operating system (for example, AIX or SunOS) number is the serial number for the license Retrieving Sybase ASE Software and License During the retrieval process you will perform the following actions: Copy the software and license from the CD on to a temporary directory on the host machine where the installation is to occur Uncompress and untar the Sybase installation file Business Enterprise Server Installation Guide 35

54 Preparing for Installation To Retrieve Sybase ASE Software and License from the Business Enterprise Server CD Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Insert the Business Enterprise Server CD into the CD ROM drive and change to the CD ROM drive. Open a command window and change to the Sybase/OS directory; the variable OS is AIX or Solaris. Perform the following actions: 3.A Copy the ase1503_os_2.tgz file into a directory from which you want to install Sybase; the variable OS is the designation for the operating environment (for example, solsparc32 or aix64). 3.B Copy the number.lic file into the same directory where you placed the ase1503_os_2.tgz file; the variable number is the serial number for the license. Enter the following command to uncompress the Sybase software installation file. gzip d ase1503_os_2.tgz The variable OS is the designation for the operating environment. Enter the following command to untar the Sybase software installation file. tar xvpif ase1503_os_2.tar The variable OS is the designation for the operating environment. Note: The use of the i flag for untarring the software ignores any checksum errors and is required. Remove the.tgz and.tar files which are no longer needed by entering the following commands: rm ase1503_os_2.tgz rm ase1503_os_2.tar Extracting the Business Enterprise Server Distribution Software During the extractions process you will perform the following actions: Copy from the Business Enterprise Server CD the distribution software from the Business Enterprise Server Untar the distribution software Before proceeding, ensure any previous Business Enterprise Server installation directories are moved or removed. 36 Business Enterprise Server Installation Guide

55 Preparing for Installation To Extract the Distribution Software Step 1 Step 2 Step 3 Step 4 Copy the file BES.tar file to a directory on your system other than /tmp or /opt. The directory should be on a file system with sufficient free space to extract the tar file and backup your existing configuration. Interlink Software recommends that you use a file system with a minimum 800MB of free space do not use /tmp on Solaris because it is a volatile directory Change to user root. Untar the distribution software by entering the following command: tar xvpf BES.tar During the untarring process, the version and build number of Business Enterprise Server is displayed (for example, BES ). Write down the build and version number, you will use it during the installation of Business Enterprise Server 3.5. Remove the BES.tar file that is not longer needed by entering the following command: rm BES.tar Migrating from Business Enterprise Server 3.4 to 3.5 You can perform the migration from Version 3.4 to 3.5 using the same host system (local migration) or two host systems (remote migration). Depending on the migration route that you choose, the following tasks are accomplished: Local Remote Tasks x x Retrieving migration data from the source system x x Migration data is transferred from the 3.4 system to the target 3.5 system Existing versions of Business Enterprise Server and Sybase ASE are uninstalled Note: If Business Enterprise Server Reporting or Resilient Server is installed using the same underlying database, it too is uninstalled. Ensure that the files for both products are backed up before proceeding with the migration. x x Sybase ASE and Business Enterprise Server 3 5 are installed Business Enterprise Server Installation Guide 37

56 Preparing for Installation Local Remote Tasks x x Migration data is loaded from the package file on to the Business Enterprise Server 3.5 system x x Upgrade process is executed which modifies the migrated data to meet the new functionality that is available in Business Enterprise Server 3.5 During the migration process, you will be prompted to perform manual tasks (such as installing Sybase ASE and installing the Business Enterprise Server) in conjunction with the migration script to complete the migration process. All actions taken are written to the BES 3.5.number/Migrate/ Log/Setup.log file; the variable number is the build number you wrote down during the retrieval process of the Business Enterprise Server 3.5 distribution software; see Retrieving Installation and Configuration Software for Sybase ASE and Business Enterprise Server on page 35. Interlink Software recommends that migration be performed between two systems. If you prefer to perform migration using the same system, Interlink Software recommends that the amount of disk space be equal to the same size as the database plus 500MB (250MB for the configuration files and 250MB for Reporting and Resiliency Server). For example, if 2GB of disk space is allocated for the database, then 2.5 GB disk space is needed). Migrating to Business Enterprise Server 3.5 Step 1 Step 2 If you are performing a local migration, open a command window on the Business Enterprise Server 3.4 system and log in as user root remote migration, open a command window on the system where Business Enterprise Server 3.5 is to be installed and log in as user root. Retrieve the migration distribution software: 2.A Enter the following command to move to the directory in which migration distribution software is located. cd BES 3.5.number The variable number is the build number you wrote down during the retrieval process of the Business Enterprise Server 3.5 distribution software (for example, 0002). 2.B Extract the Migrate.tar file by entering the following command: gzip d Migrate.tar.gz 38 Business Enterprise Server Installation Guide

57 Preparing for Installation Step 3 Step 4 Step 5 2.C Untar the migration software by entering the following command: tar xvpf Migrate.tar Start the migration script: 3.A Enter the following command to move to the directory in which migration script resides. cd BES 3.5.number/Migrate The variable number is the build number you wrote down during the retrieval process of the Business Enterprise Server 3.5 distribution software (for example, 0002). 3.B Enter the following command to start the migration script../runsetup The Welcome BES Migration Setup text is displayed and you are prompted to specify a policy selection. Select the appropriate policy by typing 1 for migrating locally or 2 for migrating remotely. If you typed 1, a package file is created by way of the Source Configuration Extractor and the tasks that are performed for creating the packaged are shown in the command window; proceed to Step 6 on 40. If you typed 2, copy the Package.tar.gz file to the source system (3.4) and proceed to Step 5. Note: The file system where you place the Package.tar.gz file must have sufficient free space to perform a full PPConfig backup. Retrieve migration data from the source system: 5.A Open a command window on the Business Enterprise Server 3.4 system and log in as user root. 5.B Move to the directory in which you place the Package.tar.gz file. 5.C Enter the following command to uncompress the Source Package software file. gzip d Package.tar.gz 5.D Enter the following command to untar the Source Package software file. tar xpf Package.tar 5.E Enter the following command to move to the directory in which the package software resides. cd Package Business Enterprise Server Installation Guide 39

58 Preparing for Installation Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 5.F Enter the following command to execute the Source Configuration Extraction script../runsrccfgext 5.G When the extraction is complete, move all files in the Package/data directory to the BES 3.5.number/Migrate/Package/data directory on the Business Enterprise Server 3.5 system. 5.H Proceed to Step 8. When prompted to place the new Business Enterprise Server license file, move the license file to the directory specified and press Enter. Remove Sybase ASE and Business Enterprise Server: 7.A When prompted to back up the existing Sybase ASE database, type Y to back up the database; otherwise, type N. If you typed Y, the tasks performed to back up of the database are displayed in the command window. 7.B When prompted to confirm the removal of Sybase ASE and Business Enterprise Server, type Y to proceed; otherwise, type N. If you typed Y, the tasks performed to remove Sybase ASE and Business Enterprise Server are displayed in the command window. When prompted to install Sybase ASE: 8.A Install Sybase ASE using the instructions defined in Chapter 3, Installing the Database. 8.B After the installation is complete, press Enter. When prompted to install Business Enterprise Server: 9.A Install Business Enterprise Server using the instructions defined in Chapter 4, Installing the Business Enterprise Server. Note: Ensure that you allocate the same size or greater for Sybase devices and databases as detailed in the BES 3.5.number/ Migrate/Package/data/dbState.txt file. 9.B When the installation of Business Enterprise Server is complete, type N to continue with the migration process and skip the reboot process. Warning: Typing Y causes a reboot and aborts the migration process. When prompted to proceed with upgrading Business Enterprise Server, press Enter. When the upgrade process is complete, type N to continue with the migration process and skip the reboot. Warning: Typing Y causes a reboot and aborts the migration process. 40 Business Enterprise Server Installation Guide

59 Preparing for Installation Backing Out of Migration to Business Enterprise Server 3.5 You can back out of the migration and return your system to its previous state manually by removing the new versions of Business Enterprise Server and Sybase ASE and reinstalling your previous versions. To Back Out of Migration Step 1 Step 2 Step 3 As user root, perform the following actions to remove Business Enterprise Server 3.5 and Sybase ASE. 1.A Enter the following command to move to the directory where the Business Enterprise Server distribution software is located. cd BES 3.5.number The variable number is the build number you wrote down during the retrieval process of the Business Enterprise Server 3.5 distribution software (for example, 0002). 1.B Enter the following command to execute the de installation script../uninstall 1.C Enter the following command to change to user root. su root 1.D Enter the following command to move to the top of the directory structure. cd.. 1.E Enter the following command to remove Sybase ASE. rm fr sybase 1.F Enter the following command to return to your original user login. exit Install Sybase ASE and Business Enterprise Server 3.4 using the instructions defined in the Business Enterprise Server, Version 3.4 Installation Guide. Install the latest Business Enterprise Server 3.4 patch using the instructions defined in the Business Enterprise Server, Version 3.4 Installation Guide and ensure that the database devices and database match exactly as defined in the BESversion_number/Migrate/Package/data/dbState.txt file. Business Enterprise Server Installation Guide 41

60 Preparing for Installation Step 4 Step 5 Step 6 Step 7 Step 8 Shut down Business Enterprise Server leaving Sybase ASE active: 4.A As user ppadmin, enter the following command to shut down the Business Enterprise Server. ppstop n Shutdown 4.B As user root, enter the following command to shut down the Apache server: rc.ppwc stop Enter the following command to untar the Config.tar file. tar xpf BESversion_number/Migrate/Package/data/Config.tar Enter the following command to untar the Backup.tar file. tar xpf BES version_number/migrate/work/backup.tar Enter the following commands to move the interfaces and Sybase.cfg files to the [SYBASEDIR] directory. mv f BESversion_number/Migrate/Package/data/interfaces [SYBASEDIR] mv f BESversion_number/Migrate/Package/data/Sybase.cfg [SYBASEDIR] As user root, enter the following command to restart the Business Enterprise Server. $PPHOME/bin/ppServer start Where to Go from Here For instructions on initially installing the Sybase Adaptive Server on a host system, go to Chapter 3, Installing the Database initially configuring the DB2 database and installing the Business Enterprise Server, go to Chapter 4, Installing the Business Enterprise Server finalising the installation of Business Enterprise Server after migration, go to Chapter 5, Finalising Installation and Starting the Business Enterprise Server 42 Business Enterprise Server Installation Guide

61 3 1 Installing the Database 3 This chapter provides instructions for installing and configuring the Sybase ASE server or the DB2 server that is used as the Business Enterprise Server database. Note: [SYBASEDIR] refers to the users chosen installation directory for Sybase. Topics included are as follows: Before You Begin Methods for Initial Installation of Sybase ASE Installing Sybase ASE Post Installation Tasks Where to Go from Here Installing and Preparing the DB2 UDB for Business Enterprise Server Creating a Database Instance, Fenced User, and Administration Server Creating Symbolic Links to the DB2 UDB Product Libraries and Include Files Creating a DB2 Database for Business Enterprise Server Where to Go from Here Business Enterprise Server Installation Guide 43

62 Installing the Database Before You Begin The Sybase ASE server was shipped with your Business Enterprise Server CD. Before proceeding with the installation, be sure that you do the following actions: Perform the pre installation tasks defined in the Business Enterprise Server Release Notes, Version 3.5 Set your DISPLAY variable and issued an xhost + command as user root Are logged in as user sybase Create a [SYBASEDIR]/data directory if you plan on using file systems instead of raw devices for your database structure Note: If you will be installing in a clustered environment, install Sybase ASE using the cluster name. Make a note of the cluster name for you will be prompted for the cluster name during the installation of the Business Enterprise Server; see Starting the Business Enterprise Server Installation on page 62. Methods for Initial Installation of Sybase ASE You can use any of the following install methods to install the Sybase server: Use InstallShield to install the servers and customise the servers for a production environment Fully customising a server at installation time reduces the need to make changes later. Use this method to license your Adaptive Server optional features during the installation process. Use the Resource file: first, use the InstallShield to install the server components on to the hard drive, then run the srvbuildres utility to install and configure Adaptive Server and Backup Server for additional sites that require identical servers. The resource file also allows installation in environments in which X Windows is not available. You cannot install Monitor Server and XP Server using resource files. Use the installation utility, asecfg, in the $SYBASE/$SYBASE_ASE/bin directory to configure a new server, upgrade your existing server, and change the default language of the server. Note: This manual assumes you are going to use the InstallShield to install the Sybase ASE server. 44 Business Enterprise Server Installation Guide

63 Installing the Database Installing Sybase ASE Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Change to user root. Move to the directory in the Sybase ASE installation software resides by entering the following command: cd installation_directory The variable installation_directory is the directory in which you untarred the ase1503_os_2.tar file. If you are running the installation from a system (PC or Unix system) connected to the host, set the display environment variable by entering the following command: setenv DISPLAY host:0 The variable host is the name or the IP address of the host to which you are connected. Start the Sybase ASE installation by entering the following command:./setup Messages are displayed indicating the initialisation of the InstallShield Wizard, searching for the Java Virtual Machine, and the start of InstallShield Wizard to install Sybase ASE. When the wizard is installed, a Welcome screen is displayed. Click Next to proceed with the installation. Install Sybase Adaptive Server using the instructions in the Sybase Installation Guide for Adaptive Server Enterprise and the following information When prompted to define the install directory define install type specify where the license will be obtained Do this action Select the default directory. Note: if you previously defined a directory in Creating the Sybase Installation Directory on page 25, it becomes the default. If the directory does not exist, specify that the directory be created. Select Typical Select Specify license keys and click Browse and navigate to the appropriate distributed license based on your operating system. The license key is located in the installation directory where you placed the ase1503_os_2.tgz from the Business Enterprise Server CD. Business Enterprise Server Installation Guide 45

64 Installing the Database When prompted to Do this action Step 7 define edition type specify license type configure e mail alerts remember the password configure new servers specify configuration type define configuration information for the Adaptive Server define configuration information for the Backup Server If you skipped the licensing task earlier, specify licensing information by placing the.lic file in $SYBASE/SYSAM2 0/licenses directory. You will find a copy of Sybase license certificate contained in the Business Enterprise Server CD box set and instructions where the.lic file is located. Step 8 Proceed to Post Installation Tasks on page 47. From the Product Edition drop down list, select Enterprise Edition. Select AC : OEM Application Deployment CPU License. Select No. Select No. Uncheck all components except the following components: Adaptive Server Backup Server Select Custom configure Adaptive Server and Backup Server and Custom configure Backup Server. From the ASE Page Size drop down list, select 16K. Ensure that Mixed is selected in the Application Type drop down list. All other attributes can be default or custom configured. Note: If you want to change a numeric value that defines size, do not use a value lower than the default value. All attributes can be default or custom configured. 46 Business Enterprise Server Installation Guide

65 Installing the Database Post Installation Tasks After the completing the installation process, you have a minimally configured Adaptive Server. This section describes post installation tasks to administer Adaptive Server. Setting Your Environment Variables During the installation process, the Studio Installer generates C shell and Bourne shell files containing environment variables. These files are located in $SYBASE/SYBASE.sh $SYBASE/SYBASE.csh If you install multiple versions of Adaptive Server, or if you intend to access different Adaptive Servers on your network, you may want to change the environment variables. Table 13 lists the Sybase environment variables that are set. Table 13 Sybase Environment Variables Variable SYBASE SYBASE_ASE SYBASE_OCS PATH Description Path of the Sybase installation directory The installation program sets up the variable SYBASE to point to the release directory specified during installation. Defines the installation directory of Adaptive Server components Defines the installation directory of Open Client Directory path on which to search for executable files The Sybase executable files are located in the installed component s /bin directory. Environment variables are set in the user environment either interactively or by including them in the user.login and.cshrc files (for C shell) or.profile file (for Bourne shell). When you use the setup files SYBASE.csh or SYBASE.sh, the following paths are added to the beginning of the PATH environment variable: $SYBASE/$SYBASE_ASE/bin:$SYBASE/$SYBASE_OCS/bin LD_LIBRARY_PATH specifies which directory to search for executable files. The Sybase executable files are located in the installed component s /bin directory. When using the source file SYBASE.csh or SYBASE.sh, the following paths are added to the beginning of the LD_LIBRARY_PATH environment variable: $SYBASE/$SYBASE_ASE/lib:$SYBASE/$SYBASE_OCS/lib: etc. Business Enterprise Server Installation Guide 47

66 Installing the Database Setting Environment Variables Using the Bourne Shell Open a command window and enter the following command:. SYBASE.sh Setting Environment Variables Using the C Shell Open a command window and enter the following command: source SYBASE.csh Verifying Server Execution and Connection For each server, verify that the server is running and that you can connect to the server. You can use isql or dsedit to test your connections; instructions for using isql are included. Verifying That the Server Is Running For each server, at the Unix prompt, enter one of the following commands: $SYBASE/$SYBASE_OCS/bin/isql Usa P Sserver_name The variable server_name is the name of the server you want to check. If the server is running, the isql prompt 1> is displayed. $SYBASE/$SYBASE_ASE/install/showserver The showserver command displays all Adaptive Server related processes that are on the system. Verifying Your Connection to a Server Using isql Step 1 At the command prompt, enter the following command: isql Usa Ppassword Sserver_name Define password as the sa password server_name as the name of the Adaptive Server The 1> command prompt is displayed if the login is successful. 48 Business Enterprise Server Installation Guide

67 Installing the Database Step 2 Step 3 If you want to display the Adaptive Server version number, perform the following steps: 2.A At the 1> prompt, enter the following command: 2.B At the 2> prompt, enter the following command: go The Adaptive Server version number is displayed followed by the 1> prompt. The output should show Adaptive Server at version Exit Sybase by entering the following command: quit Changing Ownership and Group Permission on the Sybase Installation Directory After you installed Sybase ASE, you must reset the ownership and group permission for the [SYBASEDIR] directory so that the Business Enterprise Server install does not fail. To Change Ownership and Group Permission As user root, enter the following command: chown R sybase:ppusers [SYBASEDIR] Improving Performance Using Cache and Multiple Engines Depending on your system setup, you can dedicate memory and engines to Sybase to perform event processing and enrichment. Event processing is the collection of events by the message channel and the creation of the alerts that are distributed to the Business Enterprise Server clients (such as the database, AlertServer, and so on). Enrichment is the adding of meaningful information to alerts and the execution of the service policy that maps the underlying technology to a service within event processing. If the system on which Sybase ASE is being installed has plenty of memory, you can set up Sybase to use cache to improve enrichment performance (for example, if you have 16GB RAM, you can specify that 1GB is used by Sybase for enrichment). Business Enterprise Server Installation Guide 49

68 Installing the Database When a system has more than one single core CPU or one or more CPUs running multiple cores, you can setup Sybase to use more than the single default engine to process events that are collected from the message channels. An engine can be equated to a CPU core. Interlink Software recommends that the number of engines do not exceed half of the available cores, with a minimum of one (for example, if you have two single core CPUs, only one engine is designated; likewise, if you have a single CPU with eight cores, you can designate up to four engines). The remaining cores are reserved for other processes on the system such as the operating environment and so on. You can, however, specify that additional engines can be used for processing under special circumstances, such as bringing a system online for maintenance. The additional cores are not automatically used by Sybase but are defined to Sybase in advance and started at the time of the need by way of cron or some other user action. The number of engines cannot exceed the total number of cores (for example, if you have two single core CPUs, you cannot define three engines). You specify the use of cache and engines by modifying the SYBASE.cfg file which defines the parameters under which SYBASE executes. For information on event processing, refer to Chapter 2, Collecting Messages from Managed Sources an Chapter 3, Building Rules for Message Processing in the Business Enterprise Server User Guide enrichment, refer to Chapter 4, Enriching Alerts with Meaningful Information in the Business Enterprise Server User Guide service policies, refer to the Business Enterprise Server SMARTSla Getting Started Guide To Specify Cache and Engine Usage for Sybase ASE Step 1 Step 2 Open a command window on the Sybase ASE system and move to the following directory: cd [SYBASEDIR]/ASE version Define version as the version of Sybase Using a text editor open the SYBASE.cfg file. 50 Business Enterprise Server Installation Guide

69 Installing the Database Step 3 Use the following table to identify the entries that must be modified with the appropriate value. Notes: These values are a recommendation and are based on a system with 16GB RAM and 1 CPU running 8 Cores. These values might not meet your specific environmental requirements. Adjust the values accordingly to meet your environmental requirements. The max online engines value specifies the number of engines that can be used by Sybase, including any that are designated for special purposes for a limited amount of time. The number of engines at startup is the number of engines that are dedicated to Sybase always. Parameter Recommended value [Named Cache:default data cache] cache size = 1024M [Physical Memory] max memory = [Processors] max online engines = 6 number of engines at startup = 4 Step 4 Step 5 Save the file and close the text editor. Recyle Sybase ASE by stopping and starting the database to apply the changes. For instructions on starting and stopping Sybase, refer to the appropriate Sybase ASE guide. Adjusting Shared Memory in Solaris If during startup of the Sybase Data Server you encounter the following messages in the Sybase errorlog, you must adjust shared in memory in the Solaris operating environment. 00:00000:00000:2009/11/25 17:17:49.82 kernel os_create_region: can't allocate number bytes 00:00000:00000:2009/11/25 17:17:49.82 kernel kbcreate: couldn't create kernel region. 00:00000:00000:2009/11/25 17:17:49.82 kernel kistartup: could not create shared memory The variable number is the number of bytes that must be allocated to shared memory. Business Enterprise Server Installation Guide 51

70 Installing the Database To Adjust Shared Memory in Solaris Step 1 Depending on your Solaris operation environment version, as user root, back up the appropriate file according to your installation policies. For version Solaris 9 Solaris 10 Back up the following file /etc/system /etc/project Step 2 Using a text editor, open the appropriate file (/etc/system for Solaris 9 or /etc/project file for Solaris 10) and enter the appropriate line: For file /etc/system /etc/project Add the following entry shmsys:shminfo_shmmax = nnn user.sybase:200:for use by Sybase:sybase::project.max shm memory=(privileged, number,deny) Note: If you are copying the entry from this document, ensure that the entry is on a single line within the file. Step 3 Step 4 The variable number or nnn is the number of bytes that were identified in the kernel os_create_region error message. Note: In the Solaris 10 operating environment, any values defined in the /etc/project file override any values defined in the /etc/system file. Save the file. When all the tasks in this chapter are complete, reboot the system as directed in Rebooting to Implement System Changes on page 32. Where to Go from Here For instructions on installing the Business Enterprise Server, go to Chapter 4, Installing the Business Enterprise Server. 52 Business Enterprise Server Installation Guide

71 Installing the Database Installing and Preparing the DB2 UDB for Business Enterprise Server Complete the tasks identified in the following table to install and prepare the DB2 UDB for Business Enterprise Server. Table 14 Tasks to Install and Prepare the DB2 UDB for Business Enterprise Server Task Description Go to 1 Install the DB2 universal database page 53 2 Create a database instance, fenced user, and administration server page 55 3 Create symbolic links to product libraries and include files page 58 4 Configure the database instance owner to run db2cshrc page 58 5 Verify the installation of the DB2 universal database page 59 6 Create the database to be used by Business Enterprise Server page 60 Installing the DB2 Universal Database Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Log on as user root. Insert the DB2 UDB CD in the CD ROM drive. Note: The Solaris operating system automatically mounts the CD. Change to the directory where the CD ROM drive is mounted: cd /cdrom The variable cdrom is the directory you specified when mounting the CD ROM drive. If you are installing in the AIX 5.1+ or Solaris operating environment proceed to Step 4 AIX or HP UX operating environment, proceed to Step 6 Copy the ese.tar.z file to a temporary installation directory. Change to the directory in which the ese.tar.z file is located and enter the following command to start the DB2 Setup Utility: zcat ese.tar.z tar xf ;./ese/db2setup. The Install DB2 window is displayed, proceed to Step 7. Start the DB2 Setup Utility by entering the following command:./db2setup Business Enterprise Server Installation Guide 53

72 Installing the Database Step 7 Step 8 Step 9 The Install DB2 window is displayed. Select the product that you want to install: 7.A Select DB2 Administration Client and DB2 UDB Enterprise Edition and press Enter. 7.B Select Customize adjacent to DB2 Product Library. The DB2 Product Library window is displayed. 7.C Select the appropriate locale (for example, En_US for U.S. English), select OK, and press Enter. The Install DB2 window is displayed. 7.D Select OK and press Enter. The Create DB2 Services window is displayed. Accept the default values (Do not create a DB2 Instance and Do not create the Administration Server), highlight OK and press Enter. A series of windows are displayed, requiring a response. 8.A When you are warned that you are not creating a DB2 instance and an Administration Server, select OK and press Enter. 8.B When the list of the products that you have elected to install are displayed, select Continue and press Enter. 8.C When you are warned that is this the last opportunity to cancel the installation, select OK and press Enter. 8.D When you are informed that the installation is successful, select OK and press Enter. 8.E When you are informed about the components that have been installed, select OK and press Enter. 8.F When you are returned to the Status Report window, select Close and press Enter. 8.G When you are warned that you are not creating a DB2 instance and an Administration Server, select OK and press Enter. When you are prompted to exit the DB2 Setup Utility, select OK and press Enter. 54 Business Enterprise Server Installation Guide

73 Installing the Database Creating a Database Instance, Fenced User, and Administration Server Step 1 As user root, create home directories for the DB2 Instance, DB2 Fenced User, and DB2 Administration Server by entering the following commands: mkdir db2_instance_name mkdir db2_fenced_user_name mkdir db2_administration_name Where db2_instance db2_fenced_user db2_administration_server is the name that you define for your database instance (for example, db2inst1) A database instance is a logical database manager environment where you catalogue databases and set configuration parameters. is the name that you defined for the fenced user (for example, db2fenc1) A fenced user is the system operating ID under which a fenced procedure or function executes. is the name that you defined for the administration server (for example, db2as) The administration server is component of the DB2 server that is used by the DB2 management tools to manage local and remote databases and to manage jobs. Step 2 Step 3 Step 4 Note: Write down the directory names defined for instance, fenced user, and the administration server; you will use these names later when you define the users. Change to the directory in which the DB2 Setup Utility resides by entering the following command: cd /opt/ibmdb2/version/install The variable Version is the version of the DB2 universal database that you installed (for example, V7.1). Start the DB2 Setup Utility by entering the following command:./db2setup The DB2 Setup Utility window is displayed. Select Create adjacent to To Create a DB2 Instance, an Administrator Server, or a Data Links Manager Administrator, select Create and press Enter. The Create DB2 Instance window is displayed. Business Enterprise Server Installation Guide 55

74 Installing the Database Step 5 Create a DB2 Instance: 5.A Select Create a DB2 Instance and press Enter. The DB2 Instance window is displayed. 5.B Perform the following actions: For the User Name Use default UID Group Name Use default GID Home Directory Password and Verify Password Do this action Type a user name or accept the default value. Note: Write down this name, you will use it later on in the configuration process. Type a user ID or accept the default value. Type a group name or accept the default value. Type a group ID or accept the default value. Type the name that you assigned when created the DB2 Instance directory in Step 1 on page 55 (for example, db2inst1). Type a password for the user The password must contain eight or fewer characters. Step 6 5.C Select OK and press Enter. The Fenced User window is displayed. Create a Fenced User: 6.A Perform the following actions: For the User Name Use default UID Group Name Use default GID Home Directory Password and Verify Password Do this action Type a user name or accept the default value. Note: Write down this name, you will use it later on in the configuration process. Type a user ID or accept the default value. Type a group name or accept the default value. Type a group ID or accept the default value. Type the name that you assigned when you created the Fenced User directory in Step 1 on page 55 (for example, db2fenc1). Type a password for the user. The password must contain eight or fewer characters. 56 Business Enterprise Server Installation Guide

75 Installing the Database Step 7 6.B Select OK and press Enter. The Create DB2 Services window is displayed. Create the Administration Server: 7.A Select Create the Administration Server and press Enter. The Administration Server window is displayed. 7.B Perform the following actions: For the User Name Use default UID Group Name Use default GID Home Directory Password and Verify Password Do this action Type a user name or accept the default value. Note: Write down this name, you will use it later on in the configuration process. Type a user ID or accept the default value. Type a group name or accept the default value. Type a group ID or accept the default value. Type the name that you assigned when you created the Administration Server directory in Step 1 on page 55 (for example, db2as). Type a password for the user. The password must contain eight or fewer characters. Step 8 7.C Select OK and press Enter. A notice window appears, informing you that the DB2SYSTEM environment variable is being created. 7.D Select OK and press Enter to close the window and return to the DB2 Create Services window. Select OK and press Enter. A series of windows are displayed, requiring a response. 8.A When the list of choices that you made is displayed, select Continue and press Enter. 8.B When you are warned that this is the last opportunity to cancel the processes, select OK and press Enter. 8.C When you are informed that the processes are completed, select OK and press Enter. Business Enterprise Server Installation Guide 57

76 Installing the Database Step 9 Step 10 8.D When you are informed that the processes completed successfully, select OK and press Enter. Note: If you have a failure, you can view the log file for information on how to correct a particular failure. The DB2 Setup Utility window is displayed. Select Close and press Enter. Make user root a member of the administrative group that you designated for Group Name for the Administration Server. Creating Symbolic Links to the DB2 UDB Product Libraries and Include Files If you are developing or running applications and you want to avoid specifying the full path to the product libraries and the include files, consider creating symbolic links to the /usr/lib directory and the /usr/include directory. To Create Symbolic Links Open a command window and enter the following command: /opt/ibmdb2/version/cfg/db2in The variable Version is the version of the DB2 universal database that you installed (for example, V7.1). Configuring the Instance Owner to Run db2cshrc When an instance owner is configured to run the db2cshrc script, the db2cshrc script is run during login and the environment variables that are required for the database environment are set. To Configure the Instance Owner to Run db2cshrc Step 1 Step 2 Use one of the following to tools to specify that the instance owner uses C shell: SMIT for AIX Admintool for Solaris Change to the home directory of the instance owner, make a file named.cshrc and add the following entry: source /home/db2_instance/sqllib/db2cshrc 58 Business Enterprise Server Installation Guide

77 Installing the Database Step 3 The variable DB2_Instance is the name that you assigned to the DB2 Instance directory that you created in Step 1 on page 55. For example, if you named it db2inst1, you would add the following entry: source /home/db2inst1/sqllib/db2cshrc Change the group ownership of the.cshrc file to the instance owner by entering the following command: chown DB2_Instance_Owner.cshrc chgrp DB2_Administration_Owner.cshrc Where DB2_Instance_Owner DB2_Administration_Owner is the user name that you assigned during the creation of the DB2 Instance (for example, db2inst) Is the user name that you assigned during the creation of the DB2 Administration Server (for example db2ias) Verifying the Installation of DB2 UDB To ensure that the DB2 universal database has been installed correctly, you need to verify that you can create a sample database by executing a sample script. To Verify the Installation of DB2 UDB Step 1 Step 2 Step 3 Step 4 Log in as the DB2 instance owner. The DB2 Instance owner was defined when you created the DB2 instance in Step 5 on page 56. You should be placed automatically in the home directory for the instance user and the c shell prompt, $, should be displayed. Set your DISPLAY and TERM environment variables. Ensure that the DB2 environment variable has been set up correctly by entering the following command: env grep DB2INSTANCE The value returned must be the name of the DB2 instance owner. Create a sample database by executing the db2sampl script by entering the following command: db2sampl The process can take a few minutes. If the sample database is created, you are ready to create the database that is to be used by Business Enterprise Server. Business Enterprise Server Installation Guide 59

78 Installing the Database Creating a DB2 Database for Business Enterprise Server You must perform the following tasks before proceeding with Installing the Business Enterprise Server on page 61. Task Description 1 Enable remote connections to a user defined port For example, you can use the following sql commands to enable remote connections: update dbm cfg using svcename set DB2COMM=tcpip 2 Create a bufferpool with a PAGESIZE of at least 16K to support the Business Enterprise Server infrastructure and data. Interlink Software recommends 4GB of space for a 10 day Business Enterprise Server retention period. For example, you can use the following sql command to create the bufferpool: create bufferpool sixteen size 8912 PAGESIZE 16K 3 Create a TABLESPACE that uses a PAGESIZE of 16K and the bufferpool that you just created For example, you can use the following sql command to create the tablespace that uses the bufferpool that you just created: CREATE TABLESPACE BESTBSPC1 PAGESIZE 16K MANAGED BY SYSTEM USING ( $DBHOME/$DBNAME ) BUFFERPOOL sixteen EXTENTSIZE 64 PREFETCHSIZE 32 4 Create a temporary tablespace with a PAGESIZE of at least 4K For example, you can use the following sql command to create the tablespace: CREATE USER TEMPORARY TABLESPACE PPDBSPACE2 pagesize 4096 MANAGED BY DATABASE USING (FILE /tmp/ppdbspc 50000) extentsize Set the DB2 application heap size to 2048: For example, you can use the following sql command to set the heap size: db2 update db cfg for $DBNAME using APPLHEAPSZ 2048 immediate Where to Go from Here For instructions on installing the Business Enterprise Server, go to Chapter 4, Installing the Business Enterprise Server. 60 Business Enterprise Server Installation Guide

79 4 1 Installing the Business Enterprise Server 4 This chapter provides step by step instructions for installing the Business Enterprise Server on a Unix host. Note: [SYBASEDIR] refers to the users chosen installation directory for Sybase. Topics included are as follows: Establishing a Link between the /usr Directory and Java Starting the Business Enterprise Server Installation Configuring the Supporting Database for the Business Enterprise Server Installing the Business Enterprise Server Where to Go from Here Business Enterprise Server Installation Guide 61

80 Installing the Business Enterprise Server Establishing a Link between the /usr Directory and Java A link must be established between the /usr directory and the java version that is installed on the Business Enterprise Server host system. The following is an example of a link between the /usr directory and Java 1.5, which is a prerequisite for installing the Business Enterprise Server. lrwxrwxrwx 1 root system 10 Dec /usr/java -> /usr/java5 lrwxrwxrwx 1 root other 11 Feb /usr/java -> jdk1.5.0_11/ Note: Java 1.5 is also referred to as Java 5.0. To Create a Link Step 1 Step 2 Step 3 As user root, open a command window on the Business Enterprise Server host system and type the following command to change to the /usr directory. cd /usr If there is an existing java link, type the following command to remove the link. rm java Type the following command to establish the java link. ln s java_directory java The variable java_directory is the name of the directory for the installed java version. Starting the Business Enterprise Server Installation In this section you will start the Business Enterprise Server installation and specify that you want to configure Sybase for Business Enterprise Server. If you are upgrading from version 3.4 with an underlying DB2 database, Business Enterprise Server must be running during upgrade. To Start the Business Enterprise Server Installation Step 1 Change to the directory in which the Business Enterprise Server installation script is located by entering the following command: cd BESversion_number The variable version_number is the number you wrote down during the untarring process. 62 Business Enterprise Server Installation Guide

81 Installing the Business Enterprise Server Step 2 Start the Business Enterprise Server installation by entering the following command:./setup Note: On execution, the setup script modifies the LANG variable to C for installation and configuration purposes. When the script completes the installation and configuration of the Business Enterprise Server, the LANG variable is returned to its previous value. Step 3 Step 4 When prompted to specify an alternate host name for a clustered environment, perform one of the following actions: To specify the local host name where you have started the installation, press Enter. To specify an alternate host name, type the host name and press Enter. Note: The value that you specify is defined as DBHOST and ALERTSERVERHOST_NET in the ppserver.cfg file and HOSTNAME in the httpd.conf file. When prompted to specify the Supporting Database Type, type DB2 or SYBASE and press Enter. If this is an initial installation using Sybase initial installation using DB2 upgrade to 3.5 from 3.4 using DB2 The following occurs If you a specifying a Veritas raw disk, proceed to Step 5; otherwise, go to Step 6 on 64. Proceed to Configuring the Supporting Database for the Business Enterprise Server on page 65 If you have a soft link to the installation directory, you are prompted to confirm the installation directory or specify a new installation directory. Your environment is backed up, your installation is upgraded, and your Business Enterprise Server environment is restored. Go to Testing the Business Enterprise Server on page 83. Business Enterprise Server Installation Guide 63

82 Installing the Business Enterprise Server Step 5 Step 6 Perform the following actions to specify a Veritas raw disk as the Sybase device. 5.A Open a new command window and change to the work subdirectory within the directory where you are installing Business Enterprise Server by entering the following command: cd install_directory/work The variable install_directory is the directory in which you placed the installation script. 5.B Using a text editor, create a file named DevoInfo and place the following entries within: powerpack filesystem space powerpack_log filesystem space ppdb space ppdbtransactionlog space Where filesystem is the path name of the file system (for example, /dev/vx/rdsk/1159dg00/rawppdb) space is the space requirement for the database (for example, 1.00G) The first two lines identify the devices to be allocated to the databases; the last two lines identify the space requirements for the databases. The space allocated for the databases must be less than the device size. The following is an example of the DevoInfo file: powerpack /dev/vx/rdsk/1159dg00/rawppdb 1.00G powerpack_log /dev/vx/rdsk/1159dg00/rawpptrx 240M ppdb 1024M ppdbtransactionlog 240M 5.C Change back to the installation directory by entering the following command: cd.. 5.D As user root, execute the SybaseScript defining the DevoInfo file as its parameter by entering the following command:./sybasescript 'cat./work/devinfo' 5.E After the execution of the script, reply N to the prompt. 5.F Close the command window, return to the command window in which you executed the installation script, and proceed to Step 6. Type Y to proceed with the Sybase configuration; and go to Configuring the Supporting Database for the Business Enterprise Server on page Business Enterprise Server Installation Guide

83 Installing the Business Enterprise Server Configuring the Supporting Database for the Business Enterprise Server When you configure the supporting database, you are prompted to specify specific information. When configuring for Sybase DB2 Information requested Device or file system where the Business Enterprise Server database and the Business Enterprise Server log are to be installed and the amount of space to be allocated Note: Interlink Software recommends that you use another device than the one where the master database resides. Connection port Database user ID and password Name of database, schema, instance and tablespace Location of the Home directory Note: The port number for the underlying Sybase ASE database is automatically retrieved during the configuration process, eliminating the prompt for the connection port. The connection port number for the DB2 and Sybase is stored in the ppserver.cfg file. For information on the port numbers that are used by the Business Enterprise Server, refer to Appendix B, Business Enterprise Server Communication Ports. Configuring Sybase for the Business Enterprise Server Step 1 For the Business Enterprise Server database: 1.A Perform the appropriate action: If RAW devices are Do these actions discovered 1 When prompted to define a prefix for the RAW devices, type the prefix (which must be a valid directory name) and press Enter. 2 When prompted to select a RAW device or file system, type the number that represents your selection. not discovered When prompted to specify a file system, type the number that represents the Specify File System. Business Enterprise Server Installation Guide 65

84 Installing the Business Enterprise Server Step 2 Step 3 Step 4 Step 5 1.B When prompted to enter the directory name, type the full directory pathname (for example, [SYBASEDIR]/data) and press Enter. 1.C When prompted to specify the allocation of space, type the number of MBs and press Enter. For the Business Enterprise Server log: 2.A Perform one of the following actions: To specify a RAW device, type the number that represents one of the slices from the list. To specify a file system, type the number representing the Specify File System option. 2.B When prompted to enter the directory name, type [SYBASEDIR]/data and press Enter. 2.C When prompted to specify the allocation of space, type the number of MBs and press Enter. After the devices (or files systems) are set up and space is allocated based on your input, you are prompted to allocate the space for the ppdb and the ppdbtransactionlog. When prompted to specify the allocation of space for ppdb, type the number of MBs and press Enter. When prompted to specify the allocation of space for the ppdbtransactionlog, type the number of MBs and press Enter. After specifying the space for the ppdbtransactionlog, you are prompted to proceed with the configuration of the Business Enterprise Server databases, to change definitions, or to exit the installation program. Tip: If you want to change the definitions that you just defined, type N to return to the previous prompts. At the prompt, type Y to proceed with the configuration. The configuration begins and output messages appear in the shell window. Step 6 Proceed to Installing the Business Enterprise Server on page 68 Configuring DB2 for the Business Enterprise Server Step 1 When prompted to specify the Database Remote Connection Port, perform one of the following actions: Type a connection port and press Enter. Press Enter to accept the default value enclosed in parenthesis. 66 Business Enterprise Server Installation Guide

85 Installing the Business Enterprise Server Step 2 Step 3 Step 4 Step 5 Define the Database User ID and password: 2.A When prompted to specify the Database User ID, perform one of the following actions: Type a user ID and press Enter. Press Enter to accept the default values. Note: If you specify an alternate Database User ID, the install program automatically modifies the default values for Database Home and Database Instance. 2.B When prompted to specify the Database Password, type the password and press Enter. Note: The password is stored as an encrypted string in the $PPHOME/cfg/ppserver.cfg file. Define the database name and schema: 3.A When prompted to specify the Database Name, perform one of the following actions: Type a name and press Enter. Press Enter to accept the default value. 3.B When prompted to specify the Database Schema, perform one of the following actions: Type a schema name and press Enter. Press Enter to accept the default value. Note: If a default value is not specified for the database schema, you must specify an invalid database schema name. When prompted to specify the Database Home, press Enter to accept the default value. Define the Database Instance and Tablespace: 5.A When prompted to specify the Database Instance, press Enter to accept the default value. 5.B When prompted to specify the Database Tablespace, type a tablespace name and press Enter. A summary of your selections is displayed and you are prompted to make another selection for installation. Business Enterprise Server Installation Guide 67

86 Installing the Business Enterprise Server Step 6 Step 7 Type Y to proceed with the installation of the Business Enterprise Server. Note: If you type a character other than Y, you are returned to the Database Remote Connection Port prompt. The default values shown for the installation prompts are the values you previously entered. The installation tests the connection to the database. If the connection test fails, you are returned to the Database Remote Connection Port prompt and you must specify the database details again. If the connection test is successful, the installation continues. Proceed to Installing the Business Enterprise Server. Installing the Business Enterprise Server After the Business Enterprise Server database configuration is complete, the Business Enterprise Server installation begins. The Business Enterprise Server installation prompts you to specify the locations of the Install, Log, and Work directories. To Install the Business Enterprise Server Step 1 Define the Install, Log, and Work directories: 1.A At the Install directory prompt, perform one of the following actions: Press Enter to accept the default, /opt. Type a directory name and press Enter. If you specify an invalid response, you are notified that the response is invalid and you are prompted to specify the directory again a directory that does not exist, you are prompted to create the directory or specify the directory again; respond accordingly 1.B At the Log directory prompt, perform one of the following actions: Press Enter to accept the default, /var/log. Type a directory name and press Enter. If you specify an invalid response, you are notified that the response is invalid and you are prompted to specify the directory a directory that does not exist, you are prompted to create the directory or specify the directory again; respond accordingly 68 Business Enterprise Server Installation Guide

87 Installing the Business Enterprise Server 1.C At the Work directory prompt, perform one of the following actions: Press Enter to accept the default, /var/spool. Type a directory name and press Enter. If you specify an invalid response, you are notified that the response is invalid and you are prompted to specify the directory again a directory that does not exist, you are prompted to create the directory or specify the directory again; respond accordingly A summary of your selections is displayed and you are prompted to make another selection for installation: Option Summary Install Directory : /opt Log Directory : /var/log Work Directory : /var/spool Step 2 Step 3 Enter Y to proceed with installation, or N to change definitions, or R to change from original definitions, or X to exit : Type Y to proceed with the installation of the Business Enterprise Server. The installation program lays down the appropriate files and starts the configuration of the Business Service Dashboard. If you are installing Business Enterprise Server for the first time, you are prompted to enter the Business Service Dashboard Administrators e mail address; proceed to Step 3 upgrading from a previous version, the installation program completes the configuration of the Business Service Dashboard, loads and populates the Business Enterprise Server database, installs the QuickStart program that you will use to test the Business Enterprise Server, and prompts you to reboot; proceed to Step 4 on 70 Note: Prior to the reboot prompt, the installation checks to see if the DB2 database name is ppdb, if the database name is ppdb it is automatically changed to besdb. Type the appropriate e mail address and press Enter. The installation program completes the configuration of the Business Service Dashboard loads and populates the Business Enterprise Server database, installs the QuickStart program that you will use to test the Business Enterprise Server, and prompts you to reboot. Business Enterprise Server Installation Guide 69

88 Installing the Business Enterprise Server Step 4 Type Y to proceed with reboot; otherwise, type N. If you type Y, the server reboots and the Business Enterprise Server processes are started as a result of the modifications to the /etc startup sequence. If you type N, the installation completes and you are returned to the Unix prompt. You must start the Business Enterprise Server processes using the ppserver program; see Starting the Business Enterprise Server on page 84. Note: If you have problems during an installation and you want to view the details of the installation, all tasks accomplished during install are logged in the /log subdirectory from where the Setup script was executed. Where to Go from Here For instructions on completing post installation tasks and starting the Business Enterprise Server, go to Chapter 5, Finalising Installation and Starting the Business Enterprise Server. 70 Business Enterprise Server Installation Guide

89 5 1 Finalising Installation and Starting the Business Enterprise Server 5 This chapter provides step by step instructions for completing post installation tasks and starting the Business Enterprise Server. Note: [SYBASEDIR] refers to the users chosen installation directory for Sybase. Topics included are as follows: Changing Ownership and Group Permission on Sybase Obtaining and Installing Your License Key Modifying the Number of User Connections Adjusting AlertServer Memory Allocation Defining Authentication for the Business Service Dashboard Admin Console Modifying the Apache/Tomcat Communication Port Creating a Microsoft.NET Security Policy Defining the Business Enterprise Server on the Business Service Dashboard Host Systems Testing the Business Enterprise Server Ensuring All Processes Are Running Changing the Default System Administrator Password Setting Up User Environments for the Business Enterprise Server Configuring Business Enterprise Server to Use https Installing and Configuring User Defined Servlets Installing and Configuring a Standalone Apache Server Applying Patches to the Business Enterprise Server Where to Go from Here Business Enterprise Server Installation Guide 71

90 Finalising Installation and Starting the Business Enterprise Server Changing Ownership and Group Permission on Sybase After you installed Business Enterprise Server with the supporting database as Sybase, you must reset the ownership and group permission for [SYBASEDIR]. To Change Ownership and Group Permission on Sybase As user root, enter the following command: chown R sybase:ppusers [SYBASEDIR] Obtaining and Installing Your License Key Before you can run the Business Enterprise Server, you must obtain a license key file for the Business Enterprise Server and its associated components. The associated components that rely on the license key file are as follows: Business Enterprise Server Console Business Service Dashboard Enterprise Dashboard Studio The license key file enables you to start the Business Enterprise Server and to connect to the server through the Business Enterprise Server associated components and the API (application programming language). Furthermore, the license key defines the number of message channels and managed services that can be defined in the Business Enterprise Server environment. Obtaining the License Key Step 1 Step 2 On the Business Enterprise Server, open a command window and enter the following command: hostid A number is displayed that identifies the host ID for the Business Enterprise Server; this number is used to obtain your license key. E mail the host ID to support@int link.com to obtain your license key. Interlink Software will send your license key by return e mail. 72 Business Enterprise Server Installation Guide

91 Finalising Installation and Starting the Business Enterprise Server Installing the License Key On the Business Enterprise Server, open a command window and copy the following license file into the $PPHOME directory. Modifying the Number of User Connections If your Business Enterprise Server environment will be receiving a large number of messages, it is possible you might receive the following error message from the server: There are not enough 'user connections' available to start a new process. To circumvent this possible problem, you can increase the number of user connections to a large number such as Before you increase the number of users, you must also increase the amount of memory to ensure that the number is accepted such as To Modify the Number of User Connections Step 1 Step 2 Step 3 Step 4 Open a command window on the Business Enterprise Server and enter the following command: isql Usa Ppassword Sserver_name Where: password is the sa password server_name is the Adaptive Server name The 1> command prompt is displayed if the login is successful. Change the maximum memory allocation: 2.A At the 1> prompt, enter the following command: sp_configure 'max memory', B At the 2> prompt, enter the following command: go Change the number of user connections: 3.A At the 1> prompt, enter the following command: sp_configure 'number of user connections', B At the 2> prompt, enter the following command: go Exit Sybase by entering the following command: quit Business Enterprise Server Installation Guide 73

92 Finalising Installation and Starting the Business Enterprise Server Adjusting AlertServer Memory Allocation By default, memory allocation for the AlertServer is 1024MB (or 1GB) for a large system. Characteristics of a large system are 3,000 or more alerts generated in a day 4,000 or more messages processed by message channels in a day 50 or more users logged into a Business Service Dashboard in a day You might need to adjust the amount of memory allocation for the AlertServer if you will be using a smaller system. To Adjust AlertServer Memory Allocation Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 On the Business Enterprise Server, open a command window and enter the following command to change to the directory in which the AlertServer startup script resides. cd $PPHOME/cfg Using a text editor, open the variables.cfg file. Move down to the bottom of the file until you reach the following line: setenv MEMALLOC 1024 Change the 1024 value to the appropriate value. Save the file and close the editor. If your Business Enterprise Server is already started, you must stop and start the AlertServer to apply the memory allocation adjustment by entering the following commands: ppstop n AlertServer ppstart n AlertServer Defining Authentication for the Business Service Dashboard Admin Console When you connect to the Business Enterprise Server by way of the Business Service Dashboard Admin Console, user access to the information stored in the Business Enterprise Server database can be authenticated by an LDAP server or by the Business Enterprise Server database. You define how authentication occurs by modifying the ppuserauth.cfg file. Figure 1 on page 75 illustrates an example of the ppuserauth.cfg file. 74 Business Enterprise Server Installation Guide

93 Finalising Installation and Starting the Business Enterprise Server Figure 1 Example ppuserauth.cfg File ###################################################################### # Description: Used to determine the method to be used to authenticate users within BES # Options are BES or LDAP/Active Directory. # Last Modified: 22/09/2008 ####################################################################### ##################################################### # VerificationType # Determine if internal BES or external LDAP should be used to authenticate users # Options are: LDAP BES # e.g., VerificationType=LDAP VerificationType=LDAP ###################################################### # LDAP Host # URL of the server running DLAP e.g., ldap://aserver LdapHost=ldap://wsdevtest ###################################################### # PortNum # Port number to be used (default 389 non-secure, 636 secure) PortNum=389 ###################################################### # UseSSL # Use SSL encryption # Boolean variable UseSSL=false ####################################################### # BindDN # If you need to authenticate to search for users, log in as this user # e.g., BindDN=uid=besadmin,ou=staff,ou=ICS,o=Interlink,dc=interlinksoftware,dc=com BindDN= ####################################################### #BindPwd # Password to use to make the Bind to LDAP BindPwd= ####################################################### # TheSearchAttribute # The value in LDAP holding the users login name # e.g., uid or samaccountname (used in ActiveDirectory) TheSearchAttribute=uid ####################################################### # BaseDN # Name of the root node in LDAP from which to search for users # e.g., cn=users,dc=example,dc=com BaseDN= ####################################################### # TheBESGroupAttribute # The value in LDAP holding the user s BES Group information e.g., BESGroup # Concatenated with SearchAttribute # Comment out this entry if LDAP is not used to administer group information TheBESGroupAttribute= Business Enterprise Server Installation Guide 75

94 Finalising Installation and Starting the Business Enterprise Server Figure 1 Example ppuserauth.cfg File (Continued) ####################################################### # BESGroupSearchType # The method by which group information is searched in LDAP e.g., GENERIC or USER # If USER, the user s context will be searched for the group attributes # If GENERIC, a search will be performed starting at TheBESGroupBaseDN (see below) # Comment out this entry if LDAP is not used to administer group information BESGroupSearchType=GENERIC ####################################################### # UseBESIfLDAPGroupMissing # The action to take to determine group authority if LDAP user has no group fields # TRUE or FALSE # If TRUE, the user s group information will be fetched from within BES s configuration # If FALSE, the user will not be authorised to access any groups # Comment out this entry if LDAP is not used to administer group information UseBESIfLDAPGroupMissing=FALSE ####################################################### # UseBESIfLDAPGroupEmpty # The action to take to determine group authority if LDAP user has only empty group field(s) # TRUE or FALSE # If TRUE, the user s group information will be fetched from within BES s configuration # If FALSE, the user will not be authorised to access any groups # Comment out this entry if LDAP is not used to administer group information UseBESIfLDAPGroupEmpty=FALSE ####################################################### # TheBESGroupBaseDN # Name of the root node in LDAP from which to search for users when fetching # group information, e.g., cn=users,dc=example,dc=com # Comment out this entry if LDAP is not used to administer group information TheBESGroupBaseDN= ####################################################### # UserAlterEgo # The value in LDAP holding the user s alternative name in case it is missing # from any tables in BES, e.g., ldapuser # Comment out this entry if LDAP is not used to administer group information UserAlterEgo= ####################################################### # AuthenticateViaBes # List of users that you want to allow authentication locally on the BES system. # User ppadmin is included by default. List is a comma-separated list e.g., # user1,user2,user3,user4 AuthenticateViaBes= ###################################################### # Debug # Turns on the debugging # Boolean variable Debug=false # Debug=true 76 Business Enterprise Server Installation Guide

95 Finalising Installation and Starting the Business Enterprise Server To Modify the ppuserauth.cfg File Step 1 Step 2 Open a command window on the Business Enterprise Server and enter the following command to move to the directory in which the ppuserauth.cfg file resides. cd /opt/iss/powerpack/cfg Using a text editor, open the ppuserauth.cfg file and make the appropriate changes: Parameter VerificationType LdapHost PortNum UseSSL BindDN Description Defines how verification is determined: BES, verification is determined by the internal Business Enterprise Server database LDAP, verification is determined by an external LDAP server that is maintained by way of an LDAP administrator Note: If you select BES, the remaining parameters can be ignored. URL of the LDAP server (e.g., ldap://wsdevtest) Port on the LDAP server to connect to for verification Whether secure socket layer is enabled for communication between the Business Service Dashboard and the LDAP server: True, enabled False, disabled Defines the distinguished name (string of attribute=value pairs that are separated by commas) on which to authenticate a user In the example file, the following attribute=value pairs are defined for the distinguished name. uid=besadmin is the name assigned to the user ou=staff is the group to which the user is assigned ou=ics is the department within the company to which the user is assigned o=interlink is the name of the company dc=interlinksoftware is the name of the company domain dc=com is the type of domain Business Enterprise Server Installation Guide 77

96 Finalising Installation and Starting the Business Enterprise Server Parameter BindPwd TheSearchAttribute BaseDN TheBESGroupAttribute BESGroupSearchType UseBESIfLDAPGroupMissing UseBESIfLDAPGroupEmpty Description Password to use to bind to the LDAP server Attribute in the distinguished name that contains the login name for a user (e.g., uid) Attribute=value pairs that define the root node in LDAP on which to search for users (e.g., cn=users,dc=interlink,dc=com) Attribute that is concatenated with the search attribute that defines the criteria to use for searching for a user (e.g., cn=besgroup) Method by which to search for user group information: GENERIC or USER If USER is defined, the search is performed by user context. If GENERIC is defined, the search is performed starting from TheBESGroupBaseDN value. Action to take when determining group authority if LDAP user does not have any defined group fields: TRUE, the user s group information is retrieved from the Business Enterprise Server group configuration FALSE, the user is not authorised to access any Business Enterprise Server user groups Action to take when determining group authority if LDAP user has empty group fields: TRUE, the user s group information is retrieved from the Business Enterprise Server group information FALSE, the user is not authorised to access any Business Enterprise Server user groups 78 Business Enterprise Server Installation Guide

97 Finalising Installation and Starting the Business Enterprise Server Parameter Description Step 3 TheBESGroupBaseDN UserAlterEgo AuthenticateViaBes Debug Defines the distinguished name (string of attribute=value pairs that are separated by commas) on which to search for users when retrieving group information (e.g., cn=users,dc=interlink,dc=com) In the example file, the following attributes=value pairs are defined for the distinguished name for Business Enterprise Server user groups. cn=user is the name assigned to the common name dc=example is the name of the company domain dc=com is the type of domain Value in an LDAP holding containing an alternate name for a user if the user s main name is missing from any table within the Business Enterprise Server Comma separated list of users to be authenticated locally on the Business Enterprise Server (user1,user2,user3) By default, user ppadmin is automatically defined. Whether debug messages are written to the $PPHOME/escape/tomcat/logs/catalina_out log file: True, enabled False, disabled Save the ppuserauth.cfg file and close the text editor. Modifying the Apache/Tomcat Communication Port If you do not want to use the default Apache/Tomcat port that is automatically defined when you installed the Business Enterprise Server, you are required to modify two files: $PPHOME/eScape/apache/conf/httpd.conf $PPHOME/cfg/ppserver.cfg For information on the communication ports that are used by the Business Enterprise Server and its components, refer to Appendix B, Business Enterprise Server Communication Ports. Business Enterprise Server Installation Guide 79

98 Finalising Installation and Starting the Business Enterprise Server To Modify the Apache/Tomcat Communication Ports Step 1 Step 2 Step 3 Open a command window on the Business Enterprise Server and log in as user ppadmin. Modify the httpd.conf file: 2.A Enter the following command to move the directory in which the httpd.conf file resides. cd $PPHOME/eScape/apache/conf 2.B Using a text editor open the httpd.conf file and locate the following entry: ServerName host:port Where host is the name of the server (for example, wsdevtest) port is the port used by the server (for example, 80 or 443 for SSL) 2.C Change the port value to represent the port that you want defined. 2.D Save the file and close the text editor. Modify the ppserver.cfg file to include the Apache port number: 3.A Enter the following command to move the directory in which the ppserver.cfg file resides. cd $PPHOME/cfg 3.B Using a text editor, open the ppserver.cfg file and add the following text line to the end: APACHEADDRESS=host APACHESOCKET=port APACHEHTTPS=value Where host is the name of the server (for example, wsdevtest) port is the port number that you defined in the httpd.conf file value is a boolean value that specifies whether secure socket layer is enabled (1 for enabled or 0 for disabled) 3.C Save the file and close the text editor. 80 Business Enterprise Server Installation Guide

99 Finalising Installation and Starting the Business Enterprise Server Creating a Microsoft.NET Security Policy For the Interlink Trust Certificate to work correctly on all systems where you will be accessing the Business Service Dashboard, you must have a policy added to the Microsoft.NET policies on each system. A policy can be added manually or through the policy distribution package. When you add a policy manually, you down load a copy of a.dll file (a.net binary) from the $PPHOME/eScape/htodcs/bin directory on the Business Enterprise Server to a location from which you can retrieve the file from a Microsoft system using the distribution package, you copy the Interlink Trust Certificate.msi file on to the Microsoft system; the certificate is available on the Interlink Software website Adding a Policy Manually Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Log on to the system with administrative privileges. From the desktop, choose Start = All Programs => Control Panel => Administrative Tools=>Microsoft.NET Framework 2.0 Configuration. Navigate to Runtime Security Policy\Machine\Code Groups\All Code\LocalIntranet_Zone. From the menu bar, choose Action => New to open the Create Code Group wizard. In the Name box, type Interlink Certificate. Click Next to move to the next page. From the Choose the condition type for this code group drop down list, select Publisher. Click Import from Signed File to open the Import Publisher Certificate from Signed File dialog box. Navigate to the directory in which a copy of the.dll file that you copied from the Business Enterprise Server is located and select it so that it is displayed in the File name box and click Open. Click Next to move to the next page. Select Full Trust and click Finish. Adding a Policy Using the Distribution Package Navigate to the location where you placed the Trust Interlink Certificate.msi file and double click it. Business Enterprise Server Installation Guide 81

100 Finalising Installation and Starting the Business Enterprise Server Defining the Business Enterprise Server on the Business Service Dashboard Host Systems On each of the PCs (or Microsoft Windows hosts) on which you plan on logging on to the Business Enterprise Server by way of the Business Service Dashboard, you must define the address of the server on which the Business Enterprise Server database resides in the Hosts file and in the Intranet Zone in Internet Explorer. If the Business Enterprise Server is not defined in the Hosts file, a connection cannot be made between the Business Service Dashboard and the Business Enterprise Server Intranet zone, you might experience display issues within the Business Service Dashboard such as misalignment of dialog boxes in which you enter data and missing controls (such as an OK button) Defining a Business Enterprise Server in the Hosts File Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Navigate to the directory in which the Hosts file is located (C:\Windows\System32\Drivers\Etc ). Using a text editor, such as Notepad open the Hosts file. Go to the end of the last entry in the file and press Enter to create a new line. Type the following information to define a host name: IP Address Host name #description of the server An example entry is as follows: serverabc #production server From the menu bar, choose File => Save to save the modified Hosts file. From the menu bar, choose File => Exit to close Notepad. Defining the Business Enterprise Server in the Intranet Zone for Internet Explorer Step 1 Step 2 Step 3 Step 4 On a Microsoft Windows host, open an Internet Explorer. From the menu bar, choose Tools=>Internet Options to open the Options dialog box. Click the Security tab to bring it to the forefront. In the zone box, select Local Intranet and click Sites to open the Local Intranet dialog box. 82 Business Enterprise Server Installation Guide

101 Finalising Installation and Starting the Business Enterprise Server Step 5 Step 6 Step 7 Step 8 Click Advanced to open the site dialog box. Add the Business Enterprise Server: 6.A In the Add this website to the zone box, the URL address for the Business Enterprise Server (for example, 6.B Click Add to display the server address in the Websites box. 6.C Click Close to close the site dialog box. 6.D Click OK to close the Local Intranet dialog box. Click OK to close the Options dialog box. Close the Internet Explorer to ensure that the option changes are retrieved the next time Internet Explorer is opened. Security Settings in the Intranet Zone in Internet Explorer Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 On a Microsoft Windows host, open an Internet Explorer. From the menu bar, choose Tools=>Internet Options to open the Options dialog box. Click the Security tab to bring it to the forefront. In the zone box, select Local Intranet and click Custom Level to open the Security Settings dialog box. Select Enable for everything under.net Framework reliant components Select Enable for everything under ActiveX controls and plug ins Click OK to close the Options dialog box. Close the Internet Explorer to ensure that the option changes are retrieved the next time Internet Explorer is opened. Testing the Business Enterprise Server To ensure that the Business Enterprise Server has been installed correctly, you need to test it to see if messages are being received and alerts are being created. To test the Business Enterprise Server, you will Start the Business Enterprise Server Start the Business Service Dashboard and display the Alert View Send sample messages to the Business Enterprise Server Verify the sample messages are displaying in Alert View Business Enterprise Server Installation Guide 83

102 Finalising Installation and Starting the Business Enterprise Server Starting the Business Enterprise Server Step 1 Step 2 Step 3 Log in as user root. On the Business Enterprise Server, open a command window and enter the following command to change to the Business Enterprise Server home directory. cd $PPHOME Start the Business Enterprise Server by entering the following command:./ppserver start All daemon processes are started including the demo message channels. Starting the Business Service Dashboard and Displaying the Alert View Step 1 Step 2 Step 3 Step 4 On a PC, open an Internet Explorer session. In the Address box, type in the IP address of the Business Enterprise Server. The Business Service Dashboard is displayed. Log on to the Business Service Dashboard: 3.A In the User Name box, type ppadmin. ppadmin was defined prior to installing the Business Enterprise Server. 3.B In the Password box, type the password for ppadmin. The password for ppadmin was defined prior to installing the Business Enterprise Server. 3.C Click Login. You are prompted to specify the type of session you are opening. 3.D From the drop down list, select Business Service Dashboard and click Select. 3.E When prompted to grant a session, click Grant this session. Alert View is automatically displayed. Create a selector expression for the ISS message channel alerts: 4.A From the menu bar, choose File => Edit => Selector to open the Selector window. 4.B Create a Selection Expression Group for the ISS alerts: Click New to open the New Selector Group dialog box. 84 Business Enterprise Server Installation Guide

103 Finalising Installation and Starting the Business Enterprise Server Step 5 In the box, type ISSAlerts and click Save. ISSAlerts is displayed in the Selector Expression Group pane. 4.C Create a default selection expression using the message channel name: In the Selector Expression Group pane, select ISSAlerts. In the Fields pane, select mcname and click Add. mcname is placed in the Selection Expression pane at the bottom of the window. By default, mcname has a comparison operator of eq and a percentage sign for value (percentage sign indicates a wildcard). 4.D Edit the mcname selection expression: In the Selection Expression pane, select mcname and click Edit. The mcname comparison operator and value are displayed in the Selection Expression Edit pane. In the Value box, highlight the percentage sign and type ISS. Click Insert to replace the mcname selection expression in the Selection Criteria pane. Click Set to save the mcname selection expression. 4.E Save the ISSAlerts Selector: From the menu bar, choose File => Save As to open the Save As dialog box. In the box, type ISSAlerts and click Save. 4.F From the menu bar, choose File => Exit to close the Selector window. From the menu bar, choose File => Open Config => ISSAlerts to set the display to show the ISS alerts. Sending a Sample Message to the Business Enterprise Server Step 1 Step 2 On the Business Enterprise Server, open a command window and enter the following command to change to the demo directory. cd $PPHOME/demo Enter one of the following commands to send a sample message to the ISS log. Command./QSDown./QSUp To send QuickDown messages QuickUp messages Business Enterprise Server Installation Guide 85

104 Finalising Installation and Starting the Business Enterprise Server Verifying the Sample Messages are Displaying in the Alert View Step 1 Step 2 Return to Internet Explorer on the PC. Check to see if any alerts appear with the QuickDown or QuickUp message text. If the alerts appear, Business Enterprise Server is operating correctly and your installation is a success do not appear, perform the following tasks: 2.A Check to see if all processes are running on the Business Enterprise Server by using the instructions in Ensuring All Processes Are Running on page 86. If all processes are running and the alerts do not appear, proceed to Step 2.B. 2.B Check to see if Waiting for SharedMessageQueue to become ready is continuously displayed in the java console. If the message is continuously displayed, you might have a network issue causing the AlertServer to disconnect from the Business Service Dashboard. Check to see if there are any communication problems between the Business Enterprise Server and the Business Service Dashboard and correct as appropriate. If the alerts do not appear within 2 minutes after re establishing a connection between the Business Enterprise Server and the Business Service Dashboard, proceed to Step 2.C. 2.C Perform the following tasks: Close the Internet Browser. Log in to the Business Service Dashboard using the instructions in Step 1 through Step 3 on page 84. Select the ISS alerts for display using the instructions in Step 5 on page 85. Ensuring All Processes Are Running When the Business Enterprise Server is installed properly and is running, the following processes are visible by way of the ppstate command. ppmd (Business Enterprise Server resource management daemon) BESApi (Business Enterprise Server API daemon) AlertServer (Business Enterprise Server alert server daemon) 86 Business Enterprise Server Installation Guide

105 Finalising Installation and Starting the Business Enterprise Server EventDaemon (Business Enterprise Server event manager daemon) dbi (Business Enterprise Server database interface daemon) AMON (agentless monitoring message channel) pippi (Business Enterprise Server interface message channel) System (System message channel) ISS (ISS message channel) Verifying All Processes Are Running Step 1 On the Business Enterprise Server in a command window, enter the following command: ppstate A list of daemons and message channels is displayed Figure 2 Example of Business Enterprise Server State Table Business Enterprise Server State Table Monitor Name Type Processes EventDaemon Daemon AMON Channel AlertServer Daemon ISS Channel pippi Channel BESApi Daemon System Channel ppmd Daemon dbi Daemon Step 2 Step 3 Verify that the listed processes are displayed. If a process is not listed, enter the following command to start it. ppstart n process_name The variable process_name is any of the following options: ppmd BESApi AlertServer EventDaemon dbi System ISS Business Enterprise Server Installation Guide 87

106 Finalising Installation and Starting the Business Enterprise Server Changing the Default System Administrator Password A user account named sa is created for the Sybase system administrator when you install the Sybase software. A user logged in as sa can use any database on Adaptive Server, including master with full privileges. After you configured the Sybase Adaptive Server for Business Enterprise Server, the default sa password is set to blank (that is, null value). In a production environment, the Sybase system administrator should always use a non blank password. After all tasks have been completed for installation, the Sybase system administrator can log in to the new Adaptive Server as sa and set a password using the sp_password command. To Change the SA Password Step 1 Step 2 Step 3 Step 4 Step 5 On the Business Enterprise Server, open a command window and enter the following command: $SYBASE/$SYBASE_OCS/bin/isql Usa Sserver_name At the password prompt, press Enter. At the 1> prompt, enter the following command to change the password. sp_password null, new_password The variable new_password is the new password that you assign to the sa account; the password must be a minimum of six characters in length and contain both alpha and numeric characters (for example, pass58wd) At the 2> prompt, enter the following command to complete the password change. go If the password change was successful, the system reports back that the command was successful and the 1> prompt is displayed. Exit Sybase by entering the following command: quit Setting Up User Environments for the Business Enterprise Server During the installation of the Business Enterprise Server, the environment for user ppadmin was set up so that user ppadmin can interact with the Business Enterprise Server and the underlying database. If you plan on having additional users that will interact with the Business Enterprise Server and the underlying database, you will need to set up the environment for the user. 88 Business Enterprise Server Installation Guide

107 Finalising Installation and Starting the Business Enterprise Server To Set Up an Environment for a Business Enterprise Server User Step 1 Step 2 Step 3 Ensure that the user is defined in the Unix environment, see Creating the Business Enterprise Server Administration User Accounts and Group on page 25. Ensure that the shell for the user is set correctly in the /etc/password file. If you create the user s Unix account as a csh shell, copy the.usercshrc file from the ppadmin home directory (/home/ppadmin) to the.cshrc file in the user s home directory ksh or sh shell, copy the.userprofile file from the ppadmin home directory (/home/ppadmin) to the.profile file in the user s home directory Notes: A user can modify their own environment scripts to suit their requirements without impacting the ppadmin environment. Because the user script calls the ppadmin scripts to establish the environment, any changes made to the ppadmin scripts as part of an upgrade to the Business Enterprise Server are automatically propagated to the user s environment. If a user wants to move from one shell environment to another, ensure that the.cshrc or.profile files are defined in the user s home directory. Configuring Business Enterprise Server to Use https Communication between the Business Enterprise Server and the Business Service Dashboard is accomplished using the http protocol which enables the viewing of enterprise and service information using views such as AlertView and Service Lens. The http protocol communicates, by default, using port 80 and all data is unencrypted. If your company policy does not allow the http protocol to be used for viewing enterprise and service information relevant to your company, you must configure Business Enterprise Server and Apache to communicate using the secure https protocol. Business Enterprise Server can be configured to use port 443 and the https protocol for communicating with the Business Service Dashboard. Perform the following tasks to configure Business Enterprise Server to use the http protocol: Task Description Go to page 1 Generate an SSL certificate for the Business Enterprise Server environment 90 2 Configure the Business Enterprise Server to use port Configure Apache to use secure communication 92 4 Test the https Protocol Configuration 94 Business Enterprise Server Installation Guide 89

108 Finalising Installation and Starting the Business Enterprise Server Generating the SSL Certificate You will perform the following tasks to generate SSL certificates that the Business Enterprise Server Apache server uses to serve pages over https. Create the SSL Private Key and Certificate Files Step 1 Step 2 Step 3 Ensure openssl is installed on the Business Enterprise Server. Create a private key file: 2.A In a command window on the Business Enterprise Server, enter the following command to move the directory in which the certficate program resides. cd install_directory The variable install_directory is the directory in which you installed (for example, /usr/sfw/bin). 2.B Enter the following command to execute the certificate program../openssl genrsa out host_name.key 1024 The variable host_name is the fully qualified name of the Business Enterprise Server (for example, BESprod.abc.com). 2.C When prompted, enter the appropriate information. After completing the prompts, the following private key file is created host_name.key The variable host_name is the fully qualified name of the Business Enterprise Server. Create the certificate request file: 3.A In a command window on the Business Enterprise Server, enter the following command: openssl req new key host_name.key out host_name.csr The variable host_name is the fully qualified name of the Business Enterprise Server. 3.B When prompted, enter the appropriate information. After completing the prompts, the following certificate request file is created: host_name.csr The variable host_name is the fully qualified name of the Business Enterprise Server. 90 Business Enterprise Server Installation Guide

109 Finalising Installation and Starting the Business Enterprise Server Submitting the Certificate Request File to a Signing Authority Go the appropriate authority web site such as Thawte and follow instructions on the signing authority web site to create an authorised certificate and key file. Note: If you request a trial test certificate from the signing authority, you must download Test CA from the signing authority into your client browser to ensure that the test certificate is trusted. Configure Business Enterprise Server to Use Port 443 Step 1 Step 2 Step 3 Step 4 Step 5 In a command window on the Business Enterprise Server, enter the following command to move to the cfg directory: cd $PPHOME/cfg Using a text editor, open the ppserver.cfg file and add the following lines: APACHEADDRESS=host APACHESOCKET=port APACHEHTTPS=value Where host is the fully qualified name of the server (for example, BESprod.abc.com) port is port number 80 (unencrypted) or 443 (encrypted); use port number 443 Note: You will also you define port number 443 in the httpd.conf file; see Configuring Apache to Use Secure Communication on page 92. value is a boolean value (1 for enable and 0 for disable) that specifies whether secure socket layer is enabled; use value 1 Save the ppserver.cfg file and close the text editor. Enter the following command to move to the escapex directory. cd $PPHOME/eScape/webapps/escapex View the jsp pages to verify that there are not any references to http. An example of an http reference is as follows: Dashboard.HubClient.Client" Note: Currently, the ppwctopframe.jsp file is the only known jsp page that contains references to http. Business Enterprise Server Installation Guide 91

110 Finalising Installation and Starting the Business Enterprise Server Step 6 If you find a reference to http in a jsp page: 6.A Using a text editor open the jsp page and remove the reference. An example of a reference with http removed is as follows: /bin/iss.bes.dashboard.hubclient.dll#iss.bes. Dashboard.HubClient.Client" 6.B Save the jsp page and close the text editor. Configuring Apache to Use Secure Communication Step 1 Step 2 Step 3 Place the certificate file (.crt) and key file (.key) that you received from the assigning authority into $PPHOME/eScape/apache/conf directory. Change permissions on the certificate and key files: 2.A In a command window, enter the following command to move to the conf directory in which you placed the certificate and key files. cd $PPHOME/eScape/apache/conf 2.B Change the read/write permissions to apply to the owner of the file by entering the following commands: chmod 600 name.crt chmod 600 name.key The variable name is the name assigned to certificate and key files. 2.C Change the ownership permission to apply to root only by entering the following commands: chown root:root name.crt chown root:root name.key Modify the httpd.conf file to use secure communication only: 3.A Using a text editor, open the httpd.conf file. 3.B Find the # Secure (SSL/TLS connections line and uncomment the following line by removing preceding hash character as follows: Include conf/extra/httpd-ssl.conf 3.C Find the Listen 80 line and comment it out by adding a preceding hash character as follows: #Listen 80 3.D Save the httpd.conf file and close the text editor. After these changes have been made, the web server will no longer accept http (or unencrypted) requests. 92 Business Enterprise Server Installation Guide

111 Finalising Installation and Starting the Business Enterprise Server Step 4 Modify the httpd ssl.conf file: 4.A Enter the following command to move to the extra directory in which the httpd ssl.conf file resides. cd extra 4.B Using a text editor, open the httpd ssl.conf file. 4.C Find the #SSLRandomSeed lines and uncomment by removing the preceding hash character as follows: SSLRandomSeed startup file:/dev/urandom 512 SSLRandomSeed connect file:/dev/urandom D Find the <VirtualHost _default_:443> line and replace _default_ with the fully qualified host name of the Business Enterprise Server (see example below) <VirtualHost BESprod.abc.com:443> 4.E Find the DocumentRoot line and change the path to /opt/iss/powerpack/escape/htdocs. 4.F Find the ServerName line and change it to contain the fully qualified host name of the Business Enterprise Server (for example, BESprod.abc.com:443). 4.G Find the ServerAdmin line and update it accordingly with a relevant address. 4.H Find the SSLCertificateFile line and modify it to reference the full path of the certificate file (for example, /opt/iss/powerpack/ escape/apache/conf/name.crt). The variable name is the name of the.crt file. 4.I Find the SSLCertificateKeyFile line and modify it to reference the full path of the key file (for example, /opt/iss/powerpack/ escape/apache/conf/name.key). The variable name is the name of the.key file. 4.J Save the httpd ssl.conf file and close the text editor. Business Enterprise Server Installation Guide 93

112 Finalising Installation and Starting the Business Enterprise Server Testing the https Protocol Configuration Step 1 Step 2 Step 3 Step 4 In a command window on the Business Enterprise Server, login as user root. Stop and restart the Business Enterprise Server: 2.A Enter the following command to move to the bin directory. cd $PPHOME/bin 2.B Enter the following command to stop the Business Enterprise Server../ppServer stop 2.C Enter the following command to start the Business Enterprise Server../ppServer start When prompted for the SSL certificate passkey, enter the passkey. After startup is complete, open Microsoft Explorer and enter the following command: The variable server_name is the fully qualified name (for example, BESprod.abc.com). The BES Dashboard logon page should display without any security warnings. Installing and Configuring User Defined Servlets If you create and install servlets under the control of the Business Enterprise Server, you must specify the servlet to the Business Enterprise Server by way of the $PPHOME/eScape/webapps/escapex/ WEB INF/web.xml file. The web.xml file authorises valid servlets to Apache and Tomcat: the web server for supporting the Business Service Dashboard and the application server for supporting the Business Service Dashboard. The servlet, itself, must be placed under the $PPHOME/eScape/webapps/escapex/WEB INF/classes directory. Note: If you perform an upgrade, the servlet definitions and any user defined servlets can be overwritten, requiring you to redefine the servlets to Apache and Tomcat and replace the servlets in the classes directory. Be sure to make a copy of the web.xml file and retain a copy of the servlet sources in an unsupported directory so that you can copy the servlet definitions from the backed up copy of the web.xml file to the updated web.xml file servlets sources into the updated classes directory 94 Business Enterprise Server Installation Guide

113 Finalising Installation and Starting the Business Enterprise Server The following figure depicts an example of defining a servlet in the web.xml file. <servlet> <servlet-name>reportselectionalertdetails</servlet-name> <servlet-class>reportselection.alertdetails</servlet-class > </servlet> To Define a User Defined Servlet Step 1 Step 2 Step 3 Step 4 <servlet-mapping> <servlet-name>reportselectionalertdetails</servlet-name> <url-pattern>/servlet/reportselection.alertdetails</url-pa ttern> </servlet-mapping> Open a command window on the Business Enterprise Server and navigate to the directory in which the web.xml file resides by entering the following command: cd $PPHOME/eScape/webapps/escapex/WEB INF Using a text editor, open the web.xml file. All entries in the web.xml file are encapsulated in opening and closing tags (for example, <tag_name></tag_name>). Move to the location in the file where the <! Define servlets that are included in the application > line is located. Servlets authorisations are defined first followed by servlet locations. In the appropriate location, identify the servlet authorisation and its location by creating the following the tags (listed below) to the web.xml file. XML tag <servlet> </servlet> <servlet name> </servlet name> <servlet class> </servlet class> Description Specifies the servlet to be authorised by Apache and Tomcat Tags that are placed within the servlet tag are as follows: servlet name servlet class Specifies the name of the servlet (for example, ReportSelectionAlertDetails) Specifies the class of the servlet (for example, reportselection.alertdetails) Business Enterprise Server Installation Guide 95

114 Finalising Installation and Starting the Business Enterprise Server XML tag Description Step 5 <servlet mapping> </servlet mapping> <url pattern> </url pattern> Save the file and close the text editor. Specifies the location of the servlet to be authorised by Apache and Tomcat Tags that are placed within the servlet mapping tag are as follows: servlet name url pattern Specifies the location of the servlet that is to be executed (for example,/servlet/ reportselection.alertdetails). Installing and Configuring a Standalone Apache Server If you want to route all Business Service Dashboard connections to the Business Enterprise Server through a proxy server, you can install and configure a standalone Apache server as your proxy server. Perform the following tasks to install and configure a standalone Apache server. Task Description Go to page 1 Add entries to the hosts files on the Business Enterprise Server and the proxy server so that each server can connect to the other 2 Update the backend Apache server on the Business Enterprise Server to recognise a connection from the proxy server 3 Install the standalone Apache server on the proxy server 4 Restart the backend Apache server on the Business Enterprise Server so that the connection from the standalone Apache server is recognised Start the Apache server on the proxy server 99 6 Test URL connections to the Business Enterprise Server and the proxy server Business Enterprise Server Installation Guide

115 Finalising Installation and Starting the Business Enterprise Server Adding Entries to the hosts Files on Each Server Step 1 Step 2 Identify the each server to its counterpart: 1.A Open a command window on each server and move to the etc directory in which the hosts file is located. 1.B Using a text editor, open the hosts file and add the IP address of opposing server (that is, add the proxy server IP address to the Business Enterprise Server hosts file and the Business Enterprise Server IP address to the proxy server hosts file). 1.C Save the file and close text editor. Confirm that the servers can communicate by entering the following command on each server. ping IP_address The variable IP_address is the Business Enterprise Server IP address issued from the proxy server and the proxy server IP address issued from the Business Enterprise Server. Updating the Backend Apache Server on the Business Enterprise Server Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 In the Business Enterprise Server command window, enter the following command to move to the directory in which the httpd.conf file is located. cd $PPHOME/eScape/apache/conf Using a text editor, open the httpd.conf file and locate the line that contains the opening <Directory /opt/iss/powerpack/escape/htdocs > XML tag. Move through each line until you locate its closing </Directory> XML tag. Directly above the closing XML tag is the Allow from all line. Replace all with the host name of the proxy server. The following is an example of how the line can appear. Modify from abcserver. Save the file and close the text editor. Business Enterprise Server Installation Guide 97

116 Finalising Installation and Starting the Business Enterprise Server Installing the Apache Server Software on the Proxy Server Step 1 Step 2 Install the Apache software on the proxy server: 1.A Retrieve the apache2.tar.z file from the Interlink Software web site and place it in a temporary directory on the proxy server. 1.B Change to the directory in which you placed the apache2.tar.z file and enter the following command to uncompress the apache2.tar file. gzip d apache2.tar.z 1.C Enter the following command to untar the Apache software. tar xvpf apache2.tar The Apache server software is placed in the /opt/iss/apache2 directory on the proxy server. Update the httpd.conf file: 2.A Enter the following command to move to the directory in which the httpd.conf file resides. cd /opt/iss/apache2/conf 2.B Using a text editor, open the httpd.conf file and add the following text to the end. ProxyPass / ProxyPassReverse / Add: ProxyPreserverHost ON The variable BES_host is the host name of the Business Enterprise Server. 2.C Save the file and close the text editor. Restarting the Backend Apache Server on the Business Enterprise Server Step 1 Step 2 Step 3 Open a command window on the Business Enterprise Server, log on as user root and enter the following command to stop all Apache processes. $PPHOME/rc.ppwc stop Enter the following command to verify that all Apache processes have been terminated. ps ef grep httpd Enter the following command to restart the Apache processes. $PPHOME/rc.ppwc start 98 Business Enterprise Server Installation Guide

117 Finalising Installation and Starting the Business Enterprise Server Starting the Apache Server on the Proxy Server Step 1 Step 2 Step 3 In a command window on the proxy server, enter the following command to check to see if there are any existing apache processes executing. ps ef grep httpd If there are any existing processes executing, terminate the processes. Start the Apache server: 3.A Enter the following command to change to the directory in which the Apache executable resides. cd /opt/iss/apache2/bin 3.B Enter the following command to start the Apache server../apachectl start & Testing the URL Connections to the Business Enterprise Server and Proxy Server Step 1 Step 2 On a Business Enterprise Server client, open Internet Explorer and enter the following URL which points to the Business Enterprise Server. The variable BES_host is the host name or IP address of the Business Enterprise Server. You should receive a You are not authorised to view this page error message. If you do not receive this message and you are still able to connect to the Business Enterprise Server, review the procedures that were performed on the Business Enterprise Server to see if you made an error. In Internet Explorer, enter the following URL which points to the proxy server. The variable proxy_host is the host name or IP address of the proxy server. The Business Service Dashboard should be displayed and you are prompted to begin the login process. If the Business Service Dashboard does not display, review the procedures that you performed on both servers to see if you made an error. Business Enterprise Server Installation Guide 99

118 Finalising Installation and Starting the Business Enterprise Server Applying Patches to the Business Enterprise Server If you have installed Business Enterprise Server 3.5 after its initial release, all patches that have been released since the initial version are applied after the initial installation process. To determine your build version, go to Viewing Your Build Version.. If your build version is Your patch level is xx None xx xx xx xx xx xx Viewing Your Build Version As user ppadmin, enter the following command to view the build level currently installed: cat $PPHOME/Version Applying Patches to the Business Enterprise Server Go to the Interlink Software web site and retrieve any patches that are available above the patch level currently installed and apply as appropriate. When patches are applied to the Business Enterprise Server, the version level on some of the components will change. After applying the patch, check your component versions to ensure that you are at the same level as defined for the patch. Version component levels are detailed in Business Enterprise Server Release Notes and the Business Enterprise Server Technical Bulletin that accompany the product and patch. Verifying Business Enterprise Server Component Versions After installing the Business Enterprise Server and any of its associated patches, retrieve the component versions to ensure that you are at the same level as defined for the original or patch version. Version components are detailed in the Business Enterprise Server Release Notes and the Business Enterprise Server Technical Bulletin that accompany the product and patch. 100 Business Enterprise Server Installation Guide

119 Finalising Installation and Starting the Business Enterprise Server Retrieving Component Versions from the Business Enterprise Server When you installed the Business Enterprise Server, a versions.out and a versions.non file are placed in the $PPHOME directory. The versions.out file lists all files that have valid version information and the versions.non file lists all files that have invalid or missing information. If you have incorporated updates to the Business Enterprise Server, you will need to execute the getbuildfileversions script to retrieve the latest component version numbers. The syntax is as follows: versions -o directory [- i directory] [-h] [-v] Where Parameter Description o directory Specifies the directory in which to place the versions.out and versions.non files If you do not specify a directory, the current working directory is used. i directory (Optional) specifies the directory in which to retrieve version information You can specify more than one directory, by using this parameter multiple times ( i directory i directory... i directory). If you do not specify a directory, the $PPHOME directory is used. h (Optional) displays usage information for the getbuildfileversions script v (Optional) displays the version information for the getbuildfileversions script If you would like to retrieve a version number for a single component, you can enter the name of the component followed with a v parameter in a command window. The version number and the date of the build are printed out to the screen. For example, if you wanted to retrieve the version number and build for the AlertServer, you enter AlertServer v and the results are displayed similar to the following Name:AlertServer Version: Date:03 Sep :20:00 Where to Go from Here For instructions on installing the Business Enterprise Server Console, go to Chapter 6, Installing the Business Enterprise Server Console. Business Enterprise Server Installation Guide 101

120 Finalising Installation and Starting the Business Enterprise Server 102 Business Enterprise Server Installation Guide

121 6 1 Installing the Business Enterprise Server Console 6 This chapter provides step by step instructions for installing the Business Enterprise Server Console in the Microsoft Windows environment. Topics included are as follows: Installing the Database Client Starting the Business Enterprise Server Console Installation Changing the Default Sybase Driver DLL Setting for International Characters Launching the Business Enterprise Server Console Launching SMART Modules from the Business Enterprise Server Console Managing Business Enterprise Server Connections Verifying Business Enterprise Server Console Component Versions Uninstalling the Business Enterprise Server Console Where to Go from Here Business Enterprise Server Installation Guide 103

122 Installing the Business Enterprise Server Console Installing the Database Client The Business Enterprise Server Console utilises a database client to communicate with the Business Enterprise Server. When you install the Business Enterprise Server Console, the Sybase client is automatically installed. If you are using DB2 as your underlying database, you must install the DB2 client in your Windows environment and modify the settings for the client to enable communication between the Business Enterprise Server Console and the Business Enterprise Server. DB2 Client Settings for the Business Enterprise Server The settings that you define for the Business Enterprise Server in the DB2 client are based on the information that you defined when installing the Business Enterprise Server: IP address of the server on which the database resides UDB client catalogued DBName identifier Database schema These same values will be used when you define your server connections after the installation of the Business Enterprise Server Console; see Managing Business Enterprise Server Connections on page 112. Multiple DB2 Client Business Enterprise Server Definitions If you will be connecting to more than one Business Enterprise Server on separate hosts and the general definitions defined for the Business Enterprise Servers are the same (for example, port number, DBName identifier, and schema), you will need to create catalog entries in the DB2 client that define a node name and an alias for the Business Enterprise Servers. The node defines the connection information to the host on which the Business Enterprise Server resides, and the alias defines an alternative name to be used when connecting to the Business Enterprise Server database. 104 Business Enterprise Server Installation Guide

123 Installing the Business Enterprise Server Console To Create DB2 Client Alias Definitions Step 1 Open an SQL session in the DB2 client. Step 2 Create a catalog entry for a Business Enterprise Server node definition: 2.A Enter the following command to create a node: catalog tcpip node host_name remote IP_address server port_number Define host_name IP_address port_number Name of the host on which the Business Enterprise Server resides IP address of the system on which the Business Enterprise Server resides Port number on the Business Enterprise Server to which the Business Enterprise Server Console connects Step 3 2.B Repeat this step for each Business Enterprise Server definition. Create a catalog entry for the Business Enterprise Server alias definition: 3.A Enter the following command to create an alias: catalog db besdb as alias_name at node host_name authentication server Define alias_name host_name Unique name assigned to a Business Enterprise Server database to be used as a connection definition in the Business Enterprise Server Console Note: The alias_name is identified as the DBName when defining a Business Enterprise Server connection definition in the Business Enterprise Server Console Host name of the system on which the Business Enterprise Server database resides Step 4 3.B Repeat this step for each Business Enterprise Server definition. Confirm the catalog entries that you created by entering the following command to display the entries defined in the db directory: list db directory The output displays the number of entries in the db directory and the catalog information that you defined for each entry. Business Enterprise Server Installation Guide 105

124 Installing the Business Enterprise Server Console Step 5 Close your SQL session and go to Starting the Business Enterprise Server Console Installation. Starting the Business Enterprise Server Console Installation Step 1 Step 2 Step 3 Step 4 Step 5 On the host PC where you want to install Business Enterprise Server Console, place the Business Enterprise Server CD into your CD ROM drive. If the installation does not start automatically, navigate to the Windows subdirectory, and double click the setup.exe file. If you want to install from a CD ROM drive or file system on your network, perform the following actions: Navigate to the CD ROM or file system that contains the Business Enterprise Server Console installation files. Navigate to the Windows subdirectory and double click the setup.exe file. Close all the Windows programs and click Next. The Welcome page is displayed. Click Next to proceed with the installation. The License Agreement page is displayed, prompting you to accept the license. Read the license agreement and perform one of the following actions: Select I accept the terms in the license agreement and click Next. Select I do not accept the terms in the license agreement and click Next. If you accept the license agreement, the Destination Folder page is displayed do not accept the license agreement, you are returned to the Setup window; select Exit Setup Perform one of the following actions: To accept the default destination directory, click Next. To change the default destination directory, click Change and navigate to the directory where you want Business Enterprise Server Console installed, and click Next. The Setup Type page is displayed, prompting you to specify the type of installation you want. 106 Business Enterprise Server Installation Guide

125 Installing the Business Enterprise Server Console Step 6 Select one of the following options and click Next. Option BES Console Client BES Console Admin Description Sets up host as a Business Enterprise Server client, the following functions are accessible to a user: Product Connections Data Manager Free Connection Buffer Application Stay on Top Sets up the host as a Business Enterprise Server administration client, the following functions are accessible to the user: License Manager Product Connections Data Manager Alert Server GUI Event Daemon GUI Repository Image Manager User Management Server Auto Enrichment Generation Free Connection Buffer Application Stay on Top To take full advantage of Business Enterprise Server, Interlink Software recommends that one server per environment be installed. Step 7 Step 8 Step 9 The Ready to Install the Program page is displayed, prompting you to continue the installation. Click Install. After the Business Enterprise Server installation has finished, you are prompted to complete the installation and launch the Business Enterprise Server Console. Select or clear Launch BES Console to specify whether you want to automatically launch the Business Enterprise Server Console after the installation. Click Finish to close the installation wizard. Note: Once the BES console has been installed it must be closed down and restarted to allow users to login. Business Enterprise Server Installation Guide 107

126 Installing the Business Enterprise Server Console Changing Database Client Driver DLL Settings If your Windows environment uses international characters, you must change the default Sybase driver DLL setting so that the international characters are interpreted correctly by Sybase when accessing and storing information in the Business Enterprise Server database. If you will be using the Data Manager in the Business Enterprise Server Console to connect to an Oracle database, you must have installed on the PC where the Business Enterprise Server Console is installed and Oracle client. After installing the Oracle client, you must change the DLL settings. Changing the Default Sybase Driver DLL Setting for International Characters Step 1 Step 2 Step 3 Step 4 Step 5 From you desktop, choose Start => All Programs => Interlink Software => Utilities => BDEadmin to open the BDE Administrator window. Display the Sybase driver DLL settings: 2.A In the left pane, click the Configuration tab to bring it to the forefront. 2.B Using the tree, navigate to Drivers=>Native => SYBASE. Change the Sybase driver DLL settings: 3.A In the Definition tab, select DLL32 to activate the drop down list in the value field. 3.B From the drop down list, select SQLSSC32DLL. 3.C From the menu bar, choose Object => Apply to save the new Sybase Driver DLL setting. 3.D When prompted to save all edits to Sybase, click OK. 3.E When prompted to acknowledge that all BDE applications must be restarted, click OK. From the menu bar, choose Object => Exit to close the BDE Administrator window. Restart the PC to ensure that the BDE applications are restarted with the modified driver settings applied. 108 Business Enterprise Server Installation Guide

127 Installing the Business Enterprise Server Console Changing the Oracle Driver DLL Settings Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 From you desktop, choose Start => All Programs => Interlink Software => Utilities => BDEadmin to open the BDE Administrator window. Display the Oracle driver DLL settings: 2.A In the left pane, click the Configuration tab to bring it to the forefront. 2.B Using the tree, navigate to Drivers=>Native => ORACLE. Change the Oracle driver DLL settings: 3.A In the Definition tab, select DLL32 to activate the drop down list in the value field. 3.B From the drop down list, select the appropriate DLL (for example, SQLORA8DLL). 3.C Select VENDOR INIT to activate the drop down list in the value field. 3.D From the drop down list, select the appropriate DLL (for example, OCI.DLL). From the menu bar, choose Object => Apply to save the new Oracle Driver DLL settings. When prompted to save all edits to Oracle, click OK. When prompted to acknowledge that all BDE applications must be restarted, click OK. From the menu bar, choose Object => Exit to close the BDE Administrator window. Restart the PC to ensure that the BDE applications are restarted with the modified driver settings applied. Launching the Business Enterprise Server Console After the Business Enterprise Server Console is installed, it launches automatically each time the user starts Microsoft Windows. When the Business Enterprise Server application launches, it displays a splash screen, then automatically minimizes itself in the Windows system tray. Figure 3 Windows System Tray Business Enterprise Server Installation Guide 109

128 Installing the Business Enterprise Server Console Showing the Business Enterprise Server Console Perform one of the following actions: In the system tray, click the Business Enterprise Server icon. In the system tray, right click the Business Enterprise Server icon and choose Restore. Hiding the Business Enterprise Server Console Perform one of the following actions: In the Business Enterprise Server Console window, click the minimize button. In the system tray, right click on the Business Enterprise Server icon and choose Minimize. Launching the Business Enterprise Server Console Manually From the system task bar, choose Start =>All Programs => Interlink Software => BES Console => BES Console. Note: You may only have one copy of the Business Enterprise Server Console running on a machine at any one time. Setting the Application to Stay on Top From the Business Enterprise Server Console drop down menu, choose Config => Application Stay on Top. Figure 4 Business Enterprise Server Console Drop Down Menu 110 Business Enterprise Server Installation Guide

129 Installing the Business Enterprise Server Console Launching SMART Modules from the Business Enterprise Server Console The Business Enterprise Server Console contains SMART modules that perform specific functions that enable you to build rules to process collected messages for display as alerts (SMARTView); for instructions on building rules, see the Business Enterprise Server User Guide enrichment policies that add meaningful information to an alert created from a processed message (Enrichment), for instructions on building enrichment policies, see the Business Enterprise Server User Guide correlation pathways that suppress sympathetic alerts that are a result of a condition that is already documented in another alert (SMARTEvc); for instructions on building correlation pathways, see the Business Enterprise Server User Guide service level agreements that identify the underlying technology of which a service is composed; for instructions on building service level agreements, see the Business Enterprise Server SMARTSlaGetting Started Guide automation policies that automate tasks in the Business Enterprise Server environment; for instructions on building automation policies, see the Business Enterprise Server Automation Guide Each SMART module has a quick launch icon on the console toolbar. Figure 5 Business Enterprise Server Console Toolbar To Launch a SMART Module Click the icon that represents the product on the Business Enterprise Server Console toolbar. Tip: If you are not sure which icon to click, move the mouse over a button and a hint pops up indicating the product to which it refers. Business Enterprise Server Installation Guide 111

130 Installing the Business Enterprise Server Console Managing Business Enterprise Server Connections Before you can connect to a Business Enterprise Server, you must add a connection definition. You use the DB Connection Configuration dialog box to create and delete connection definitions. A connection definition is composed of the following information: Underlying database type that the Business Enterprise Server database uses (Sybase or UDB) Operating environment on which the Business Enterprise Server is installed when the underlying database is Sybase IP address or host name of the system on which the Business Enterprise Server database is installed Note: If you will use a host name instead of an IP address, the host name must be defined in the C:\Windows\System32\Drivers\Etc\Hosts file. Database name and database schema defined for the Business Enterprise Server database when the underlying database is UDB Whether the Business Enterprise Server displays in the top most position in the Connection drop down list in a SMART Module Login dialog box If you are defining a connection definition for DB2, you will be identifying your database type as UDB. The values that you define for the connection must map to the values that you defined for the DB2 client you installed for communication between the Business Enterprise Server Console and the Business Enterprise Server. Defining a Host Name to the Business Enterprise Server Console Step 1 Step 2 Step 3 Step 4 Perform one of the following actions to display the DB Connection Configuration dialog box: From the Business Enterprise Server Console drop down menu, choose Product Connections. In the Login window, click Configure. Click Edit Hosts to open the Hosts file in Notepad. Go to the end of the last entry in the file and press Enter to create a new line. Type the following information to define a host name: IP Address Host name #description of the server An example entry is as follows: serverabc #production server 112 Business Enterprise Server Installation Guide

131 Installing the Business Enterprise Server Console Step 5 Step 6 From the menu bar, choose File => Save to save the modified Hosts file. The file is saved in the C:\Windows\System32\Drivers\Etc directory. From the menu bar, choose File => Exit to close Notepad. Adding a Business Enterprise Server Connection Definition Step 1 Step 2 Step 3 Perform one of the following actions to display the DB Connection Configuration dialog box: From the Business Enterprise Server Console drop down menu, choose Product Connections. In the Login window, click Configure. Select the appropriate tab that identifies the underlying database of the Business Enterprise Server to bring it to the forefront: Sybase UDB Perform the following actions: If you are in the Do these actions Sybase tab 1 In the Name box, type the host name or IP address of the server where the underlying database resides for the Business Enterprise Server. The host name or IP address that you entered is automatically placed in the Host/IP box and is the name defined for the connection definition. 2 From the OS drop down list, select the operating environment in which the Business Enterprise Server runs: SunOS AIX 3 In the Port box, type the port number that the Business Enterprise Server Console will use to connect to the Business Enterprise Server. Note: The port value must be the same as defined for the DBPORT parameter in the ppserver.cfg file. 4 In the User box, type the name of the default user that is automatically displayed when selecting this connection definition. Business Enterprise Server Installation Guide 113

132 Installing the Business Enterprise Server Console If you are in the Do these actions Step 4 Step 5 Step 6 Step 7 UDB tab 1 In the Name text box, type a user defined reference name that is to be used for the connection definition. 2 In the Host/IP box, type the host name or IP address of the server where the underlying database resides for the Business Enterprise Server. 3 In the DB Name box, type the UDB client catalogued DBName Identifier defined for the Business Enterprise Server database (for example, besdb). Note: If you have more than one Business Enterprise Server, type the alias name that you defined in To Create DB2 Client Alias Definitions on page In the Schema box, type the database schema for the Business Enterprise Server database (for example, BES). 5 In the User box, type the name of the default user that is automatically displayed when selecting this connection definition. Click Add. If you want to set a Business Enterprise Server as the default so that it is always selected when the user launches any application: 5.A In the Business Enterprise Server Connections list, select the server. 5.B Click Set as Default. If you want to change the order in which the servers are displayed in the Connection drop down list when the user launches any application: 6.A In the Business Enterprise Server Connections list, select a server. 6.B Use the up or down arrow to move the entry to the appropriate location within the list of servers. Click OK to close the DB Connection Configuration dialog box; otherwise, click Cancel. 114 Business Enterprise Server Installation Guide

133 Installing the Business Enterprise Server Console Deleting a Business Enterprise Server Connection Definition Step 1 Step 2 Step 3 Perform one of the following actions to display the DB Connection Configuration dialog box: From the Business Enterprise Server Console drop down menu, choose Product Connections. In the Login window, click Configure. In the Business Enterprise Server Connections list, select the server you want to delete and click Delete. Click OK to close the DB Connection Configuration dialog box; otherwise, click Cancel. Note: If the connection definition that you deleted is for a DB2 underlying database, you must delete the connection information defined for the DB2 client to completely remove the connection definition. Verifying Business Enterprise Server Console Component Versions After installing the Business Enterprise Server Console, retrieve the component versions to ensure that you are at the same level as defined for the original or patch version. Version component levels are detailed in Business Enterprise Server Release Notes and the Business Enterprise Server Technical Bulletin that accompany the product and patch. Retrieving Component Versions from the Business Enterprise Server Console From the Business Enterprise Server Console drop down menu, choose Help => Versions to open the Versions window. Uninstalling the Business Enterprise Server Console You can remove the Business Enterprise Server Console from the Microsoft Windows environment by using the Uninstall application provided by Interlink Software or by using the Microsoft Windows Add/Remove Programs window. The product when listed in the Microsoft Windows Add/Remove Programs window is prefixed with Interlink Software and suffixed with a version number (for example, Interlink Software BES Console 3.5). Business Enterprise Server Installation Guide 115

134 Installing the Business Enterprise Server Console To Remove the Business Enterprise Server Console Using the Uninstall Application Step 1 Step 2 From the desktop, choose Start => Interlink Software => BES Console => Uninstall. When prompted to confirm uninstallation, click Yes; otherwise, click No. Where to Go from Here If you want to integrate with third party products that provide event management, refer to the Business Enterprise Server Integration Guide configure Business Enterprise Server to create alerts from messages retrieved from a source in your enterprise network, refer to the Business Enterprise Server User Guide 116 Business Enterprise Server Installation Guide

135 A 1 Changing the Business Enterprise Server Database Administrator Password A You must perform the following tasks to change the password for the main Business Enterprise Server database administrator account. The main Business Enterprise Server database account is defined in the underlying database (Sybase ASE or DB2). Task Description Go to page 1 Ascertain the name of the Business Enterprise Server database administrator account 2 Change the Business Enterprise Server database password within the Business Service Dashboard 3 Stop all Business Enterprise Server processes except for the underlying database 4 Change the Business Enterprise Server database administrator password 5 Encrypt and store the new password in the BES password file Note: When you change the Business Enterprise Server database account for the underlying database, the corresponding account password in the Business Service Dashboard is not changed. If you want to keep the two account passwords synchronised, you must log in to the Business Service Dashboard Admin Console to change the account password to map to the account password defined for the underlying database. Business Enterprise Server Installation Guide 117

136 Ascertaining the Main Business Enterprise Server Database Administrator Account As user ppadmin, open a command window on the Business Enterprise Server and enter the following command to display the name of the main Business Enterprise Server administrator account. echo $DBUSER Note: When installing the Business Enterprise Server using Sybase as the underlying database, user ppadmin is the main Business Enterprise Server administrator account. Changing the Business Enterprise Server Database Password within the Business Service Dashboard Step 1 Step 2 Step 3 Step 4 Step 5 Log on to the Business Service Dashboard using the database administrator user (for example, ppadmin). In the upper right corner, click Profile to open the User Profile window. In the User Security information, adjacent to Change Password, click Click here to move to the Change Password page, and perform the following actions: In the Old Password box, type your current password. In the New Password and Confirm Password boxes, type your new password. Click Change Password to apply the modification and return to the previous page. Click Close to close the User Profile window. Log off the Business Service Dashboard. Stopping All Business Enterprise Server Processes Stop all Business Enterprise Server processes except for the underlying database by entering the following command: ppstop n shutdown 118 Business Enterprise Server Installation Guide

137 Changing the Database Administrator Password Perform the appropriate action: If the underlying database is Do these actions Sybase ASE 1 On the Business Enterprise Server, open a command window and enter the following command to open an isql session in Sybase. isql Umain_BES_user The variable main_bes_user is the name of the main Business Enterprise Server database administrator account. 2 At the 1> prompt, enter the following command to change the password. sp_password password, new_password Where: password is the current password new_password is the new password that you assign to the administrator account; the password must be a minimum of six characters in length and contain both alpha and numeric characters (for example, pass58wd) 3 At the 2> prompt, enter the following command to complete the password change. go If the password change was successful, the system reports back that the command was successful and the 1> prompt is displayed. 4 Exit Sybase by entering the following command: quit DB2 Change the password for the main Business Enterprise Server database administrator account using the appropriate interface to the database. Business Enterprise Server Installation Guide 119

138 Encrypting and Storing the New Database Password Step 1 Step 2 Step 3 Step 4 Step 5 In a command window on the Business Enterprise Server, enter the following command to move to the home directory of user ppadmin. cd ~ppadmin Enter the following command to encrypt the new password. pwencrypt p new_password The new password is returned as encrypted characters. Using a text editor such as vi, open the.main_bes_user file and replace the current content with the encrypted characters that were returned in the previous step; the variable main_bes_user is the name of the main Business Enterprise Server database administrator account. Save the file and exit the editor. Shutdown the Business Enterprise Server and restart to ensure that the changes are applied. 120 Business Enterprise Server Installation Guide

139 B 1 Business Enterprise Server Communication Ports B The following table identifies the port numbers that are used on the Business Enterprise Server. Some of the port values can be reassigned using the identified configuration file on the Business Enterprise Server. Component Port number Configuration file Business Enterprise Server Application Interface (BESApi) Communicates with Business Enterprise Server clients and the Business Enterprise Server Console, port needs to be opened on any firewalls between the server and its clients and the Business Enterprise Server Console Business Enterprise Server Hub Client (Java) (.NET) /etc/services (alertserver java, alertserver dotnet) ppserver.cfg (ALERTSERVERHOST_JAVA, ALERTSERVERPORT_JAVA, ALERTSERVERHOST_DOTNET, ALERTSERVERPORT_DOTNET Note: When host and port is set for the Hub Client in the ppserver.cfg file, entries defined for the AlertServer in the /etc/services file are overridden. Business Enterprise Server Installation Guide 121

140 Component Port number Configuration file Business Enterprise Server Console AlertServer GUI Business Enterprise Server Console EventDaemon GUI Business Enterprise Server database Business Enterprise Server database interface (Dbi) Business Enterprise Server EventDaemon Business Enterprise Server Interface (PPI/PPIe) Business Enterprise Server AlertServer (message channel connections) Business Enterprise Server Management Daemon (ppmd) Business Enterprise Server message channels (Ports used within the message channels to communicate between different parts of the message channel, such as the connection program that collects event messages) Business Enterprise Server Reporting $PPHOME/bin/AlertServer (DQPORT); see Modifying the AlertServer Port Connection in the Business Enterprise Server User Guide $PPHOME/bin/EventDaemon (DQPORT); see see Modifying the EventDaemon Port Connection in the Business Enterprise Server User Guide 5000 (Sybase) (DB2 on AIX) ppserver.cfg (DBPORT) Note: The default port values for Sybase and DB2 can be changed /etc/services (dbi) /etc/services (PP2KEvent) /etc/services (pippi, pippie) ppi.conf /etc/services (PP2KWeb) /etc/services (ppmd) Starting at and increments of 20 ppmd assigns ports numbers to message channels by increments of 20 starting from the port number that ppmd is assigned For example, if you have three message channels, ports numbers used are 45020, 45040, and /etc/services entry for ppmd (see above) defines the starting point at which an increment of 20 is to be used for the message channels /etc/services (PP2KReport) 122 Business Enterprise Server Installation Guide

141 Component Port number Configuration file Resilient Server for Business Enterprise Server Business Service Dashboard (Apache) 443 (ApacheSSL) $PPHOME/eScape/apache/conf/httpd. conf $PPHOME/cfg/ppserver.cfg Note: For information on changing the port numbers, refer to Modifying the Apache/Tomcat Communication Port on page 79. Note: Port 5001 which is used by the SOAP monitor in the apache application server is disabled. If you want to enable the SOAP monitor, refer to Business Enterprise Server Installation Guide 123

142 124 Business Enterprise Server Installation Guide

143 C 1 Modifying a Non Clustered Installation of Business Enterprise Server for a Clustered Environment C If you installed Business Enterprise Server into a non clustered environment and you want to move to a clustered environment, you must modify one or more parameters in the ppserver.cfg, httpd.conf, and interfaces files. Note: [SYBASEDIR] refers to the users chosen installation directory for Sybase. The following table identifies the files that are modified to point to the service clusters. File ppserver.cfg httpd.conf interfaces Description Lists the hosts and ports needed to provide communication between the Business Enterprise Server database and its clients Lists the connection parameters used by the Apache web server that supports the Business Service Dashboard Lists the connection parameters for the underlying database used for the Business Enterprise Server To Configure Business Enterprise Server for a Clustered Environment Step 1 Modify the ppserver.cfg file: 1.A Open a command window on the Business Enterprise Server and enter the following command to move the directory in which the ppserver.cfg file resides: cd $PPHOME/cfg 1.B Using a text editor, open the ppserver.cfg file. Business Enterprise Server Installation Guide 125

144 1.C Locate the DBHOST parameter and modify values to reflect the cluster service as shown below. Step 2 Step 3 DBHOST = host The variable host is the name of the cluster service where the database resides. 1.D Locate the ALERTSERVERHOST_NET parameter and modify the values to reflect the cluster service as shown below. ALERTSERVERHOST_NET = host The variable host is the name of the service to which the Business Enterprise Server Hub Client connects. 1.E Save the file and close the text editor. Modify the httpd.conf file: 2.A Move to the directory in which the httpd.conf file resides: cd $PPHOME/eScape/apache/conf 2.B Using a text editor open the httpd.conf file and locate the ServerName parameter. following entry: ServerName host The variable host the host name or IP address of the server 2.C Change the host value to represent the IP address of the cluster service. 2.D Save the file and close the text editor. Modify the interfaces file for the database: 3.A Enter the following command to move to the directory in which the interfaces file resides. cd [SYBASEDIR] 3.B Using a text editor, open the interfaces file and locate the following entries: SYBASE master tcp ether host port querytcp ether host port SYBASE_BACK master tcp either host port querytcp ether host port Where host is the name of the server port is the port number used by the server 126 Business Enterprise Server Installation Guide

145 Step 4 3.C Change the host value to the cluster service name (for example, service01). 3.D Save the file and close the text editor. Stop and restart the Business Enterprise Server to apply the modifications: 4.A Change to user root. 4.A Enter the following command to move to the bin directory. cd $PPHOME/bin 4.B Enter the following command to stop the Business Enterprise Server../ppServer stop 4.C Enter the following command to start the Business Enterprise Server../ppServer start Business Enterprise Server Installation Guide 127

146 128 Business Enterprise Server Installation Guide

147 Index Symbols /etc/services file parameter alertserver dotnet 121 alertserver java 121 dbi 122 pippi 122 pippie 122 PP2KEvent 122 PP2KReport 122 PP2KWeb 122 ppmd 122 A AIX clustered environment 44, 125 enabling large file support 24 setting file size security limit 28 SMIT tool 27 version 17 AlarmPoint 5 AlertServer adjusting memory allocation 74 connection port 122 description 3 starting/stopping 74 startup script 74 AlertServer file parameter, DQPORT 122 Apache server 10 Apache/Tomcat communication port, modifying 79 asynchronous I/O, setting 31 B BESApi communication port 121 description 3 Business Enterprise Server adding to Intranet Zone for Internet Explorer 82 adding to the Business Service Dashboard system Hosts file 82 applying patches 100 communication ports 121 component versions 100 components 3 configuring the supporting database 65 defining connections from the Business Enterprise Server Console 112 file systems and directories 14 installing 68 migrating to version 3.5 from optional products 4 retrieving component versions 100 retrieving distribution software 35 starting 84 system requirements 17 testing 83 third party software 10 upgrading 34 what is 2 Business Enterprise Server AlertServer adjusting memory allocation 74 connection port 122 description 3 starting/stopping 74 startup script 74 Business Enterprise Server Application Interface (BESApi) Business Enterprise Server Installation Guide 129

148 Index connection port 121 description 3 Business Enterprise Server Console AlertServer GUI connection port 122 component versions 115 defining a connection definition 113 defining a host name 112 deleting a connection definition 115 description 4 EventDaemon GUI connection port 122 hiding 110 launching 109 license key 72 managing connection definitions 112 retrieving component versions 115 setting to stay on top 110 showing 110 starting installation 106 system requirements 21 Business Enterprise Server Console SMART module, description 111 Business Enterprise Server database Business Service Dashboard user authentication 74 changing the administrator password 117 connection port 122 Business Enterprise Server database interface (Dbi) connection port 122 description 3 Business Enterprise Server EventDaemon connection port 122 description 3 Business Enterprise Server Hub Client, connection port 121 Business Enterprise Server Interface (PPI/PPIe), connection ports 122 Business Enterprise Server Management Daemon (ppmd) connection port 122 description 3 Business Enterprise Server Reporting, connection port 122 Business Service Dashboard connection ports 123 defining the Business Enterprise Server in the Hosts file 82 defining the Business Enterprise Server in the Intranet Zone 82 description 4 C license key 72 starting 84 system requirements 20 third party software required 10 CD ROM mounting local 33 mounting remote 33 changing ownership and group permission 28 write permission 28 changing, ownership and group permission 49, 72 command ppserver 84 ppstart 74, 87 ppstate 87 ppstop 74 component version retrieving from Business Enterprise Server 100 retrieving from Business Enterprise Server Console 115 configuring DB2 65 DB2 for Business Enterprise Server installation 66 supporting database for Business Enterprise Server 65 Sybase Adaptive Server 65 Sybase ASE for Business Enterprise Server installation 65 connection port 65 creating /usr/sybase directory 25 db2 administration server 55 db2 database for Business Enterprise Server 60 db2 fenced user 55 db2 instance 55 ISS alerts selector expression 84 symbolic links to DB2 UDB libraries and include file 58 user accounts and groups Business Enterprise Server Installation Guide

149 Index D daemon, list 86 database distributing in SAN environment 24 size 21 DB2 Enterprise Server Edition 11, 18 DB2 universal database administration server 55 database instance 55 fenced user 55 installation verification 59 installing 53 instance owner 58 kernel parameters 30 symbolic links 58 DB2, configuring 65 Dbi connection port 122 description 3 device, allocating 21 directory /bin/csh 27 /home 14 /home/ppadmin 26 /opt 37 /opt/iss 14 /opt/iss/apache2/bin 99 /opt/iss/apache2/conf 98 /opt/sybase 49, 72 /tmp 37 /usr/sybase 14, 24, 25, 27, 126 /usr/sybase/data 14 /var/log/iss 14 /var/spool/iss 14 /var/tmp 28 $PPHOME 73, 101 $PPHOME/cfg 74 $PPHOME/eScape/apache/conf 34, 97 $PPHOME/escape/tomcat/logs 79 $PPHOME/eScape/webapps/escapex/WEB I NF 94 $PPHOME/eScape_AIX/apache/conf 126 $PPHOME/POWERpack/eScape/webapps/es capex/web INF/ classes 94 $SYBASE/$SYBASE_ASE/bin 44 apache/conf_x.x 34 disk space, allocating 21 distributing files and databases 24 distribution software retrieving 35 uncompressing 36 driver Oracle DLL setting 108 Sybase DLL setting 108 E Enterprise Dashboard Studio, license key 72 environment variable PATH 47 setting for Sybase 47 SYBASE 47 SYBASE_ASE 47 SYBASE_OCS 47 event management 2 EventDaemon connection port 122 description 3 EventDaemon file parameter, DQPORT 122 F file /etc/services 121 AlertServer 122 apache2.tar 98 apache2.tar.z 98 BES.tar 35, 37 catalina_out 79 EventDaemon 122 hosts 97 http.conf 34 httpd.conf 63, 79, 97, 98, 123, 126 interfaces 126 license_key 73 POWERpack_Log 28 ppi.conf 122 ppserver.cfg 65, 79, 113, 121, 123 ppuserauth.cfg 74 setting size security limit 28 SYBASE.cfg 49 SYBASE.csh 48 SYBASE.sh 47, 48 Sybase/OS/ase1503_OS_2.tgz 35 Sybase/OS/number.lic 35 variables.cfg 74 Business Enterprise Server Installation Guide 131

150 Index G versions.non 101 versions.out 101 web.xml 94 group permission, changing 28, 49, 72 H httpd.conf file parameter HOSTNAME 63 ServerName 80, 126 I increasing, number of processes 30 installing DB2 universal database 53 installing, Business Enterprise Server 68 Interlink Software Services Integration for Agentless Monitoring, introduction 4 Interlink Software Services Integration for AlarmPoint, introduction 5 Interlink Software Services Integration for AutoOPERATOR, introduction 5 Interlink Software Services Integration for BMC Event Manager, introduction 5 Interlink Software Services Integration for Business Enterprise Server Interface, introduction 6 Interlink Software Services Integration for Business Enterprise Server, introduction 6 Interlink Software Services Integration for HP Network Node Manager, introduction 6 Interlink Software Services Integration for HP OpenView IT/Operations, introduction 6 Interlink Software Services Integration for HP OpenView Operations for Windows, description 7 Interlink Software Services Integration for HP Service Manager, introduction 7 Interlink Software Services Integration for IBM Tivoli Enterprise Console, introduction 7 Interlink Software Services Integration for IBM Tivoli Monitoring, introduction 7 Interlink Software Services Integration for IBM Tivoli Netcool/OMNIbus, introduction 7 Interlink Software Services Integration for IBM Websphere MQ, introduction 8 Interlink Software Services Integration for Microsoft Operations Manager, introduction 8 Interlink Software Services Integration for Microsoft System Center Operations Manager 2007, introduction 8 Interlink Software Services Integration for NetIQ AppManager, introduction 8 Interlink Software Services Integration for Oracle Database, introduction 8 Interlink Software Services Integration for Oracle Enterprise Manager, introduction 9 Interlink Software Services Integration for PATROL Enterprise Manager, introduction 5 Interlink Software Services Integration for Performance Manager, introduction 6 Interlink Software Services Integration for Quest Foglight, introduction 9 Interlink Software Services Integration for Remedy AR System, introduction 9 Interlink Software Services Integration for SNMP, introduction 9 Interlink Software Services Integration for Sun Management Center, introduction 9 Interlink Software Services Integration for Web Services, introduction 10 Interlink Software Services Intergration for mailx, introduction 8 international character 108 J Java, version 18 K kernel configuration changing parameters 29 maxuproc parameter 30 kernel parameters DB2 universal database 30 Sybase Adaptive Server Enterprise 31 L LDAP authentication Business Service Dashboard Business Enterprise Server Installation Guide

151 Index system requirements 21 license key installing on the Business Enterprise Server 73 obtaining and installing 72 limiting, number of threads per process 32 listing, message channels 86 M message channel connection ports 122 description 3 list 86 message queue parameters, setting 51 Microsoft Windows, version 21 migration to version 3.5 backing out 41 tasks performed 37 modifying, ppuserauth.cfg file 77 O Orace driver DLL setting 108 ownership permission, changing 28, 49, 72 P password changing 88 locking 27 setting 27 PATROL Agent 6 perl 11 port, used by Business Enterprise Server components 121 ppadmin user property default shell 26 group ID 26 group name 26 home directory 26 setting 26 user ID 26 user name 26 ppmd connection port 122 description 3 ppserver.cfg file parameter ALERTSERVERHOST_DOTNET 121 ALERTSERVERHOST_JAVA 121 ALERTSERVERHOST_NET 63, 126 ALERTSERVERPORT_DOTNET 121 ALERTSERVERPORT_JAVA 121 APACHEADDRESS 80, 91 APACHEHTTPS 80, 91 APACHESOCKET 80, 91 DBHOST 63, 126 DBPORT 113, 122 ppuserauth.cfg file parameter Authenticate 79 BaseDN 78 BindDN 77 BindPwd 78 Debug 79 LdapHost 77 PortNum 77 TheBESGroupAttribute 78 TheBESGroupBaseDN 79 TheBESGroupSearchType 78 TheSearchAttribute 78 UseBESIfLDAP 78 UseBESIfLDAPGroupMissing 78 UserAlterEgo 79 UseSSL 77 VerificationType 77 ppusers group property group ID 26 group name 26 setting 26 pre installation checklist 15 process increasing number 30 running 86 R raw devices, allocating 23 rebooting 32 Resilient Server for Business Enterprise Server, connection ports 123 S sample messages, sending 85 SAN (Storage Area Network) environment 24 script Business Enterprise Server Installation Guide 133

152 Index db2cshrc 58 service level agreement (SLA) 2 service level management 2 setting asynchronous I/O 31 message queue parameters 51 ppadmin user properties 26 ppusers group properties 26 Sybase user properties 27 TCP Node Layer Acknowledgement 32 SNMP managers 2 SNMP traps 9 Solaris installation 18 version 17 Solaris kernel configuration parameter msgsys:msginfo_msgmax 30, 31 msgsys:msginfo_msgmnb 30, 31 msgsys:msginfo_msgmni 30, 31 msgsys:msginfo_msgseg 30 msgsys:msginfo_msgssz 30 msgsys:msginfo_msgtql 30, 31 msgsys:sginfo_msgmap 30 semsys:seminfo_semmap 30 semsys:seminfo_semmns 31 semsys:seminfo_semmnu 31 semsys:seminfo_semume 31 semsys:semnifo_semmni 30 shmsys:shminfo_shmmax 30 shmsys:shminfo_shmmni 30 shmsys:shminfo_shmseg 30 shmsys:shmino_shmmax 31 Solaris kernel parameters DB2 universal database 30 Sybase Adaptive Server Enterprise 31 standalone Apache server adding hosts file entries 97 installation/configuration task list 96 installing Apache server software on proxy server 98 restarting backend Apache server on Business Enterprise Server 98 starting the Apache server on the proxy server 99 testing URL connections 99 updating backend Apache server on the Business Enterprise Server 97 starting Business Enterprise Server 84 Business Enterprise Server installation 62 Business Service Dashboard 84 Sybase Adaptive Server changing ownership and group permission 49 configuring 65 installation methods 44 setting environment variables 47 using cache to improve enrichment performance 49 using engines to improve event processing 49 verifying execution and connection 48 Sybase Adaptive Server Enterprise 10 kernel parameters 31 Solaris kernel parameters 31 starting installation 53 Sybase ASE retrieving distribution software 35 Sybase driver DLL setting 108 Sybase environment number of user connections 73 variable 47 Sybase user property default shell 27 group ID 27 group name 27 home directory 27 setting 27 user ID 27 user name 27 SYBASE.cfg, modifying 49 Sybperl 11 system requirement Business Enterprise Server 17 Business Enterprise Server Console 21 Business Service Dashboard 20 devices 21 disk space 21 LDAP authentication 21 T TCP Node Layer Acknowledgement, setting 32 threads, limiting per process 32 Tivoli Enterprise Console 7 Tivoli Enterprise Portal 7 Tomcat Business Enterprise Server Installation Guide

153 Index U Uni REXX 10 upgrading from Business Enterprise Server 3.2 or Business Enterprise Server POWERpack 3.0 or user ppadmin 25, 28 root 25, 28 sybase 25, 28 user account and group, creating 25 user installed servlets, defining to Apache and Tomcat 94 utility asecfg 44 srvbuildres 44 V variables.cfg file parameter, MEMALLOC 74 verifying DB2 universal database installation 59 W write permission, changing 28 Business Enterprise Server Installation Guide 135

154 Index 136 Business Enterprise Server Installation Guide