MSC SimManager Enterprise Edition R3.1. Installation and Administration Guide

Transcription

1 MSC SimManager Enterprise Edition R3.1 Installation and Administration Guide

2 Corporate MSC.Software Corporation 2 MacArthur Place Santa Ana, CA Telephone: (800) FAX: (714) Europe MSC.Software GmbH Am Moosfeld Munich GERMANY Telephone: (49) (89) Fax: (49) (89) Asia Pacific MSC.Software Japan Ltd. Shinjuku First West 8F 23-7 Nishi Shinjuku 1-Chome, Shinjuku-Ku Tokyo , JAPAN Telephone: (81) (3) Fax: (81) (3) Worldwide Web This documentation, as well as the software described in it, is furnished under license and may be used only in accordance with the terms of such license. MSC.Software Corporation reserves the right to make changes in specifications and other information contained in this document without prior notice. The concepts, methods, and examples presented in this text are for illustrative and educational purposes only, and are not intended to be exhaustive or to apply to any particular engineering problem or design. MSC.Software Corporation assumes no liability or responsibility to any person or company for direct or indirect damages resulting from the use of any information contained herein. The software described herein may contain certain third-party software that is protected by copyright and licensed from MSC.Software suppliers. To the extent that SimManager Enterprise includes IBM components, such components may only be used as part of SimManager Enterprise. Additional information regarding third party software is available at MSC and SimManager are trademarks or registered trademarks of MSC.Software Corporation or its subsidiaries in the United States and/or other countries. FLEXlm is a registered trademark of Macrovision Corporation. All other brand names, product names or trademarks belong to their respective owners. Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR (Commercial Computer Software) and DFARS (Commercial Computer Software and Commercial Computer Software Documentation), as applicable. Copyright 2008 MSC.Software Corporation. All Rights Reserved. Printed in the U.S.A. Any reproduction or distribution of this document, in whole or in part, without the prior written consent of MSC.Software Corporation is strictly prohibited. Date: 9/24/08 SMEN:R3.1:Z:Z:Z:DC-OPS

3 Contents MSC SimManager Enterprise Edition R3.1 Installation and Administration Guide 1 About this Guide Introduction 2 Organization of this Guide 3 Related Documentation 4 Technical Support 5 2 SimManager Topology and Overview Introduction to SimManager Enterprise Edition 8 SimManager Topology 9 Overview of System Components 11 Creating a Development and Production Environment 13 Production System 13 Configuration and Test Environment 13 Defining Roles and Responsibilities 14 3 Hardware and Software Requirements Overview 16 Supported Hardware Platforms 16 Prerequisite Software Requirements 17 Server-side Software Requirements 18 License Server (1 Required) 18 Web Application Server (1 required) 19 Relational Database Server (1 required) 20 Optional Server-Side Components 21 Client-side Software Requirements 23

4 iv 4 Preparing for SimManager Installation Overview 28 Installing Prerequisite Software 28 Steps for installing MSC.Software Solutions Download Center files 30 SimManager Enterprise 30 IBM WebSphere Application Server 31 IBM DB2 Universal Database: 32 IBM DB2 Universal Database Setup Utility: 32 Analysis Manager 33 Installing a Web Application Server 34 Installing the WebSphere Application Server 34 Installing the Tomcat Web Application Server 46 Installing the JBoss Web Server 46 Installing a Database Server 49 Installing IBM DB2 Database Server 49 Installing Oracle Database Server 79 Installing Microsoft SQL Server 81 Utilities 83 Security and User Authentication Software 85 Job Scheduling/Queuing Software 85 Installing X Virtual Frame Buffer 99 Installing Xvfb on AIX 99 Installing Xvfb on Linux and Solaris 99 5 Installing and Deploying SimManager Overview 106 Product Licensing with FLEXlm 107 Product Licensing 107 Obtain Licenses 107 Windows 107 Unix 109 Client Access/User licensing 111 Network User licensing 111 Named User licensing 111 Installing and Deploying SimManager 112 Installing SimManager 114 Performing a Full/Typical Installation 114

5 CONTENTS v Activating Portal 126 Setting up the Workspace Launcher 126 Starting the Portal Activation Process 127 Specifying the Directories 128 Logging In 130 Selecting a Portal 130 Specifying the Portal Instance Name 131 Specifying the Database Configuration Information 132 File Vault Configuration Dialog Box 136 Initializing the Knowledge Base 139 Specifying the Load Data File 141 Setting Properties 142 Installed SimManager Enterprise Directory Structure 144 Confirming the Installation 146 Performing a Custom Installation 148 Testing the Installation 150 Setting up SimManager in a clustered WebSphere environment System Administration Overview 156 Administrative Tools 157 SimManager Classic Studio 157 SimManager Eclipse-based Studio 158 Running the Activate Command 158 SimManager Batch Admin Tool 158 Administrative Functions 160 Creating and Deleting SimManager Databases 160 Matching a SimManager Database to the RDBMS 160 Vault Management 170 Vault Administration 172 Revision Change Notification 178 Authorization and Authentication 180 Authorization Rules and Concepts 180 Authentication 192 Authorization 207 Users 208 Organizing Your Work with Hierarchical Projects 236 Projects and Domains Providing Context for Your Data 236 Hierarchical Context Structures 237

6 vi Refined Context Data Model and Migration 239 User and Profile Roles for Hierarchical Projects 240 Action Selection Rules, Action Classification 241 Web Server Administration 243 Support for Load Balancing and Failover 243 Load Balancing setup on Apache/mod_jk/Tomcat 244 Application Connection pooling 248 Portal Configuration 269 Global properties and preferences 269 Database Manager Settings 270 SimManager.properties File 275 Portal.properties and PortalDefinition.properties 276 Defining Units 281 Logging 284 Specifying Mime-type Mapping 285 Lifecycle Management and System Actions 287 Security Labels and Attributes 287 Object Life-cycle Management 293 Life-cycle Process 294 Configuring Life Cycle Behavior 296 Clearing References on Delete 306 Action Permission Checking 306 Execution Privilege 307 Action Permission Checking 311 A Troubleshooting and FAQ Overview 314 Error Messages 315 Tomcat Temp Folder 318 IBM DB2 319 WebSphere Admin Console 321 Mimetype Mapping Problems 322 Web Browser Problems 323 SimManager Startup Error on Tomcat Web Server 324 System Administration 326

7 CONTENTS vii WebStart FAQ 328 B Backup and Recovery Guide Backup and Recovery 332 Introduction 332 SimManager Database/Vault Architecture 332 General Backup and Recovery Considerations in SimManager 334 Offline Backup 335 Online Backup Methods with Tivoli Storage Manager 335 Alternate Online Backup Methods 340 C Tivoli Directory Server Installation for Windows Introduction 342 Installation Process 343 DB2 and IBM Directory Server 343 IBM Tivoli Directory Server Instance 347 IDS Web Administration Tool 354 Starting WAS express version 354 Adding Directory Server Instance to IDS Web Administration Tool 355 Verifying the Installation of IDS 357 D Enterprise Connect Deployment and Usage Guide Deployment of Enterprise Connect Module 360 Deployment of OpenPDM Server 360 PasswordManager 360 Batch Applications set up 360 Interactive client set up 361 Usage of Enterprise Connect Module 362 Batch PDM Import(CSAE) 362 Batch PDM Export (CSAE) 362 Interactive PDM Import 364

8 viii

9 Chapter 1: About this Guide 1 About this Guide Introduction 2 Organization of this Guide 3 Related Documentation 4 Technical Support 5

10 2 Introduction Introduction This guide describes how to install the MSC SimManager Enterprise Edition R3.1 suite of software and to activate a portal. A portal makes it possible to efficiently perform the basic patterns of operations that occur in the simulation process. It makes the virtual product development (VPD) process effective by enabling organizations to perform more simulations earlier in the development cycle. This enables companies to make intelligent decisions earlier and with more confidence, which ultimately leads to better products, improved quality and lower cost of operation for the consumer.

11 Chapter 1: About this Guide Organization of this Guide 3 Organization of this Guide This guide consists of the following chapters and appendices: SimManager Topology and Overview, 7 Hardware and Software Requirements, 15 Preparing for SimManager Installation, 27 Installing and Deploying SimManager, 105 System Administration, 155 Troubleshooting and FAQ, 313 Migration Guide, 331 Backup and Recovery Guide, 331 Tivoli Directory Server Installation for Windows, 341 Enterprise Connect Deployment and Usage Guide, 359

12 4 Related Documentation Related Documentation Additional SimManager documentation includes the following PDF files and an online user guide in HTML: MSC SimManager Enterprise Edition R3.1 Release Guide MSC SimManager Enterprise Edition R3.1 Configuration and Deployment Guide MSC SimManager R3.1 User's Guide MSC SimManager Enterprise Edition R3.1 Process Builder User's Guide Online help for MSC SimManager Enterprise Edition R3.1 Classic Studio MSC SimManager Enterprise Edition R3.1 Programmer's Guide

13 Chapter 1: About this Guide Technical Support 5 Technical Support For help with installing or using an MSC.Software product, contact your local technical support. Our technical support services include: Resolution of installation problems Verification of code error For support information, go to the MSC.Software Web site: Here, you can find a wide variety of support resources, including application examples, technical application notes, and available training courses.

14 6 Technical Support

15 Chapter 2: SimManager Topology and Overview 2 SimManager Topology and Overview Introduction to SimManager Enterprise Edition 8 SimManager Topology 9 Overview of System Components 11 Creating a Development and Production Environment 13 Defining Roles and Responsibilities 14

16 8 Introduction to SimManager Enterprise Edition Introduction to SimManager Enterprise Edition SimManager facilitates simulation processes by integrating external batch-based server applications, enterprise databases, enterprise services and client applications. For optimal operation, it requires specific hardware, storage, and networking infrastructures. For successful SimManager deployment, an appropriate level of planning, design, and implementation (installation, configuration, and optional customization) is required. This chapter includes a system-wide overview for the systems administrator responsible for SimManager installation. Sections discuss the general requirements of the basic SimManager system including system components, SimManager topology, and roles and responsibilities of those involved in the project. Specific capabilities for a particular implementation are achieved by configuring and customizing the system. This process is described in detail in the MSC SimManager Enterprise Edition R3.1 Configuration and Deployment Guide. Note: You will also find installation instructions for basic deployment of the EnterpriseEdition Portal. This portal is intended to work in conjunction with other MSC.Software products such as SimXpert and SimDesigner. The sophistication of the SimManager environment can vary considerably, which may result in the need for additional hardware and software components.

17 Chapter 2: SimManager Topology and Overview SimManager Topology 9 SimManager Topology This section provides an overview of the SimManager topology and layout. While the scope of this can vary considerably, a simple, single system providing all the essential services is shown in the following diagram: Figure 2-1 Single System

18 10 SimManager Topology To achieve a scalable (high-availability) enterprise solution, a cluster setup is suggested in which the different services run on different systems or clusters of systems. Figure 2-2 Cluster setup

19 Chapter 2: SimManager Topology and Overview Overview of System Components 11 Overview of System Components The installation process assumes the performance of a Requirement and/or System Definition Assessment (RDA/SDA) in order to scope the infrastructure required for the intended usage. For this requirement to be met, it is assumed that the customer and the system solution architect have identified the software applications, their setup and configuration. The minimum set of operational software is: Server Relational database system Web application server File Vault Client Web browser As the installation grows and a scalable high-performance environment needs to be established, the individual components/services can be moved to different systems. Considerations for individual components include: Database - The database server (DB) of SimManager can be easily moved to a separate DB server. This can be a company's central database instance or a dedicated DB server just for SimManager. Since every transaction in SimManager includes DB transactions, the DB server needs to be readily available. To ensure the responsiveness of SimManager, make sure that the connection between the DB server and SimManager has very low latency. Compute server - As the execution of the procedures in SimManager can have demanding compute requirements in terms of CPU, memory, and I/O, we recommend that a compute cluster be established. To efficiently use the resources in the cluster, SimManager relies on a job-submission environment to schedule the individual compute tasks. High availability needs to be ensured for the submission host. Content Vault / Storage(file server) - In many instances of SimManager, a large number of data files need to be managed and stored. This requires the setup of a dedicated file server in the SimManager environment that considers near-term sizing requirements as well as future scalability. The file server needs to have high availability, because almost every transaction with SimManager involves file movements between the web server (or compute systems) and the file server. As the storage requirements grow with increasing maturity and use of the Portal, a hierarchical storage management system should be considered, which automatically migrates the less frequently used data files to a back-end tape archive.

20 12 Overview of System Components Web application server - As the number of users of SimManager grows, a cluster of web application servers should be considered with the appropriate load-balancing solution. LDAP server - For authorization, integration with an LDAP server is suggested, which manages user passwords in a central location. Typically, in an organization, there will already be a central LDAP server with which SimManager will interact as users log into the system.

21 Chapter 2: SimManager Topology and Overview Creating a Development and Production Environment 13 Creating a Development and Production Environment While planning a deployment, consider establishing a primary and secondary environment to ensure the highest reliability of the deployed system. The two environments are: Production system Configuration and test environment Establishing these two environments requires additional hardware, software, and personnel. You should factor in these requirements while planning for deployment. The approach has considerable value, however, as explained in the next sections. Production System When the completely configured system is ready for use by end users and system administrators, it can be deployed to the production environment. Do not configure or test on this system. We recommend that you create a test environment for this purpose. Configuration and Test Environment The configuration of the test system should be representative of the deployed SimManager environment. It is used to: Test patches and new software versions Experiment with configurations and processes Configure new processes Introduce a new simulation discipline Determine sizing requirements The configuration and test environment is the staging area for deployed configurations. This test environment does not require the disk space required for a deployed system. If handling sensitive data, however, it should remain on site for security and confidentiality reasons.

22 14 Defining Roles and Responsibilities Defining Roles and Responsibilities The following section defines the responsibilities and required capabilities of SimManager users and administrators. The process of installation will be primarily in the domain of the system administrator. Position End user Webmaster Configuration and deployment specialist Database administrator System administrator Database system integrator External process integrator Responsibilities The end user accesses the system through a web browser. The end user has no responsibilities for the configuration or installation of the system. The webmaster is responsible for initiating and maintaining an operational website. The webmaster should be familiar with the web server application and the site internet configuration. The configuration and deployment specialist modifies the configuration files and web pages to reflect the requirements of the customer s user population. The database administrator: Installs the target database and/or configures the database with the schema definition files Builds the database tables using SimManager administrative tools Monitors and tunes the performance The system administrator provides support for connecting the SimManager system to the site s infrastructure, which includes providing the configuration information for release procedures, the LDAP configuration and connection information, installation access, network support, and so on. The system administrator is responsible for monitoring and supporting the system for end users. The database system integrator designs the site s database schema and implements the schema using XML configuration files. The external process integrator implements the Action Encapsulation (AE) scripts for the SimManager system. These AE scripts are used to configure the information for an external process to run properly, execute the process, then capture the results and put them back into the database.

23 Chapter 3: Hardware and Software Requirements 3 Hardware and Software Requirements Overview 16 Supported Hardware Platforms 16 Prerequisite Software Requirements 17 Server-side Software Requirements 18 Client-side Software Requirements 23

24 16 Overview Overview The hardware and software requirements for a SimManager installation are derived from industrystandard technologies and widely available commercial products. Based on specific configuration, there may be other optional components. Some of these components are briefly mentioned in this chapter. The minimum requirements are described in the sections which follow. Supported Hardware Platforms For an initial deployment of SimManager, only a single machine is required. The recommended minimum system should have 3GHz processor, 4GB RAM, and disk space as required. For a typical, full deployment of SimManager, the minimum hardware environment should have: Web application server - 3 GHz processor, 4GB RAM, 30GB disk Database server - 3 GHz processor, 4GB RAM, 100 GB RAID 4 + disk File-server - 2 GHz processor, 512 MB RAM, RAID 5 storage with appropriate disk space Application cluster - Application-dependent sizing

25 Chapter 3: Hardware and Software Requirements Prerequisite Software Requirements 17 Prerequisite Software Requirements The following software applications must be available on the planned hardware environment before installing the SimManager system. See Overview of System Components, 11, for a brief description of high-level software requirements and configuration. The applications are: Browser (one required, client-side) Java Runtime Environment (JRE) Note: Java plug-ins may be required to perform client-side actions. Web application server (one required, server-side) Relational Database (one required, server-side) File vault server (one required, server-side) FLEXlm license server (required, server-side) The following optional software application may also be required before the installation and deployment of SimManager: Lightweight Directory Access Protocol (LDAP) compatible directory service The following additional software applications may be added during or after the installation and deployment of SimManager to enhance performance or extend capabilities: MSC SimXpert for advanced simulation functionality including template building/running that is seemlessly integrated with SimManager MSC SimDesigner for designer-level analysis that provides easy data publishing and template execution using SimManager. Patran for pre/post processing with advanced finite element modeling tools to import native CAD geometry, build geometry from scratch, create quality meshes, define loads and boundary conditions, and apply material properties. MD Adams for simulating the full-motion behavior of complex mechanical systems. Easy5 for schematic-based modeling and simulation of dynamic systems containing hydraulic, pneumatic, mechanical, thermal, electrical, and digital subsystems. MSC Process Builder for authoring advanced best practice processes within SimManager MSC SimXpert for batch execution of templates managed by SimManager MSC Analysis Manager for job submission and queue management of batch processes Load balancing system for scalability and redundancy of the web application servers PDM integration (generally a custom activity) Required applications running on the server and/or client computers. For example, batch versions of MSC Patran or MSC Nastran.

26 18 Server-side Software Requirements Server-side Software Requirements The following tables describe the server-side system components, versions, operating system/platform information, and locations of software. The links and locations listed were valid at the time of publication. MSC Software recommends that a fully functional, licensed version of the required software be purchased for use in a production environment and that individual license agreements be reviewed prior to usage. License Server (1 Required) Table 3-1 Licensing Software Software Version Supported Operating Systems Source FLEXlm 10.8 Windows, Linux, Unix Included with SimManager Workgroup CD set or Download from MSC.Software Solution Download Center:

27 Chapter 3: Hardware and Software Requirements Server-side Software Requirements 19 Web Application Server (1 required) Table 3-2 Software IBM WebSphere Application Server Network Deployment Web application servers Version Supported Operating Systems Microsoft Windows 2003 Server Red Hat Enterprise 4.3 (2.6 Kernel) IBM AIX 5.3 TL 0 Apache Tomcat Microsoft Windows 2003 Server Red Hat Enterprise 4.3 (2.6 Kernel) Red Hat JBoss Microsoft Windows 2003 Server Source Included with SimManager Enterprise CD set or Download from MSC.Software Solution Download Center: Download from Apache project: Download from: Sun Solaris 9 (Sparc)

28 20 Server-side Software Requirements Relational Database Server (1 required) Table 3-3 Software IBM DB2 Enterprise Relational database server Version Fixpack 3 (Equivalent to Fixpack 10) Supported Operating systems IBM AIX 5.3 TL 0 Source Contact your MSC Software Sale Representative Fixpack 2 Microsoft Windows 2003 Server Red Hat Enterprise 4.3 (2.6 Kernel) Included with SimManager Enterprise CD set or Download from MSC.Software Solution Download Center: IBM AIX 5.3 TL IBM AIX 5.3 TL 7 Contact your MSC Software Sale Representative Microsoft SQL Server Version 2005 Microsoft Windows 2003 Server Refer to Microsoft Corp: Oracle Enterprise Edition 10g Release 2 Microsoft Windows 2003 Server Red Hat Enterprise 4.3 (2.6 Kernel) Refer to Oracle Corp: roducts/database/index.html Sun Solaris 9 (Sparc)

29 Chapter 3: Hardware and Software Requirements Server-side Software Requirements 21 Optional Server-Side Components The following table lists optional, server-side system components and the download source: Job Submission System Table 3-4 Software MSC Analysis Manager Platform LSF Sun Grid Engine Optional server-side components Version Supported Operating Systems Source Included with SimManager Enterprise CD set Download from: Download from: Directory Server Table 3-5 Software IBM Tivoli Directory Server Optional server-side components Version Supported Operating Systems Source Download from: ibm.com/software/tivoli/products/di rectory-server/ Storage Manager Table 3-6 Software IBM Tivoli Storage Manager Optional server-side components Version Supported Operating Systems Source Contact your MSC Account Manager

30 22 Server-side Software Requirements System Automation Table 3-7 Software IBM Tivoli System Automation Optional server-side components Version Supported Operating Systems Source Contact your MSC Account Manager Other MSC Server Applications Table 3-8 Software MSC SimXpert (optional) Other MSC Server Applications R3 Version Supported Operating Systems Source Download from MSC.Software Solution Download Center:

31 Chapter 3: Hardware and Software Requirements Client-side Software Requirements 23 Client-side Software Requirements The following tables describe the client-side system components, versions, operating system/platform information, and locations of software. The links and locations listed were valid at the time of publication. MSC.Software recommends that a fully functional, licensed version of the required software be purchased for use in a production environment and that individual license agreements be reviewed prior to usage.

32 24 Client-side Software Requirements Table 3-9 Software Microsoft Internet Explorer Client-side Requirements Version Supported Operating Systems 6.x Download from: Source 6/downloads/default.mspx Mozilla Firefox 2 Download from: MSC Process Builder (optional) R3 Microsoft Windows XP (32-bit and 64 bit) Included on SimManager Enterprise CD set Red Hat Enterprise 4.3 (32-bit and 64-bit) or Download from MSC.Software Solution Download Center: MSC SimXpert (optional) R3 Microsoft Windows XP (32-bit and 64 bit) Download from MSC.Software Solution Download Center: MSC SimDesigner Template Client Edition (optional) R3 Red Hat Enterprise 4.3 (32-bit and 64-bit) Microsoft Windows XP (32-bit and 64 bit) Red Hat Enterprise 4.3 (32-bit and 64-bit) Patran (optional) 2008 Microsoft Windows XP (32-bit and 64 bit) Download from MSC.Software Solution Download Center: Download from MSC.Software Solution Download Center: MD Adams (optional) R3 Microsoft Windows XP (32-bit and 64 bit) Download from MSC.Software Solution Download Center:

33 Chapter 3: Hardware and Software Requirements Client-side Software Requirements 25 Table 3-9 Software Client-side Requirements Version Supported Operating Systems Easy5 (optional) 2008 Microsoft Windows XP (32-bit and 64 bit) Source Download from MSC.Software Solution Download Center: Java Web Start (Standard Edition) version R3 Microsoft Windows XP (32-bit and 64 bit) Red Hat Enterprise 4.3 (32-bit and 64-bit) Download from MSC.Software Solution Download Center:

34 26 Client-side Software Requirements

35 Chapter 4: Preparing for SimManager Installation 4 Preparing for SimManager Installation Overview 28 Steps for installing MSC.Software Solutions Download Center files 30 Installing a Web Application Server 34 Installing a Database Server 49 Utilities 83

36 28 Overview Overview When preparing to install SimManager, we recommend the following: 1. Read this document completely to plan your environment. 2. Define and document the details of the processes that the system must support. 3. Ensure that you have the required environment as specified in Prerequisite Software Requirements, 17 and install the various components as required. 4. Design the physical architecture. Plan the configuration with consideration for items such as load balancing, vault management, database management, and server combinations for these services. For more information, see the SimManager Logical Topology section in the MSC SimManager Enterprise Configuration and Deployment Guide. This chapter describes all the tasks required to prepare the environment for the installation, configuration, and deployment of the SimManager system. The installation, configuration, deployment, and testing of the SimManager Portal are described in Installing and Deploying SimManager, 105. Installing Prerequisite Software The specific prerequisite software required for your system is dependent on the supported hardware platforms (see Prerequisite Software Requirements, 17) and the overall requirements of your specific simulation solution. Therefore, not all of the software components and applications described in this section may be required for your installation. To install and deploy a basic (demonstration) version of the SimManager Portal, you must install (or have available on your system) and configure the following prerequisite components: Web application server Database server FLEXlm license server or MSC license file The instructions for the installation and configuration of the prerequisite software components are described in the following sections. Required platform-specific differences or instructions are noted in the descriptions. In general, a download location or source for third-party software and auxiliary components are listed in Server-side Software Requirements, 18. We recommend, but do not require, that the software components be installed in the order presented in this section. Note: To configure the required prerequisite software and the SimManager system, several system environment variables are required. We recommend that you limit the scope of these environment variables to avoid conflicts with existing settings and applications.

37 Chapter 4: Preparing for SimManager Installation Overview 29 In the instructions that follow, symbols (for example: <*.dir>) are used in place of directory locations that are specified during the installation process. Table 4-1 Symbol <SM_INSTALL_DIR> Symbols used for directory locations Directory This is the directory under which SimManager is installed. For example, <drive>/msc.software/simmanager/<version> where: <version> is the current version of SimManager, such as R3 <drive> is: <SMAPP_ROOT> Linux/UNIX - /var or /opt or /usr Windows - C:, D:, and so on This is a Web application directory. For example: <WEBSPHERE_HOME>/profiles/<server_name>/InstalledApp s/<node_name> or <WEBSPHERE_HOME> <TOMCAT_INSTALL_DIR> <TOMCAT_INSTALL_DIR>/webapps The installation directory for the IBM WebSphere application server. For example, D:\WebSphere\AppServer For example, the installation directory for Jakarta Tomcat, <CATALINA_HOME> is: D:\jakarta-tomcat-5.5

38 30 Steps for installing MSC.Software Solutions Download Center files Steps for installing MSC.Software Solutions Download Center files If you are an authorized customer with a valid login ID and password, SimManager Enterprise and other software such as IBM DB2 and WebSphere may be downloaded from the MSC.Software Solutions Download Center at: For more information on accessing the Solutions Download Center, please contact your local MSC Sales Office. SimManager Enterprise UNIX / Linux Systems 1. Login as root 2. "cd" to a temporary directory with sufficient disk space. Create a subdirectory and "cd" to the subdirectory. 3. Download the appropriate delivery file from Solution Download Center: AIX: simmanager_r3.1_aix5l.tar Linux: simmanager_r3.1_redhat.tar If you have already downloaded the files, you may proceed to the next step. 4. Execute the delivery file (.bin) which is a Universal Install Script. Executing the delivery file may require adding execution privilege: chmod +x Delivery_File 5. For the remainder of the installation process follow instructions in Installing SimManager. 6. Cleanup: After installation is complete, you may remove the subdirectory created in Step 2. Windows Systems 1. Download delivery file (simmanager_r3.1_windows.exe) from Solution Download Center to a temporary folder. 2. Execute the delivery file (.exe) which is a Universal Install Script. 3. For the remainder of the installation process follow instructions in Installing SimManager. 4. Cleanup: After installation is complete, you may remove temporary files from the download location used in Step 1 above.

39 Chapter 4: Preparing for SimManager Installation Steps for installing MSC.Software Solutions Download Center files 31 IBM WebSphere Application Server UNIX / Linux Systems 1. Login as root 2. "cd" to a temporary directory with sufficient disk space. Create a subdirectory and "cd" to the subdirectory. 3. Download the appropriate WebSphere Application Server Network Deployment (ND) delivery file from the Solution Download Center: AIX: simmanager_ws_ _aix5l.tar.gz Linux: simmanager_ws_ _redhat.tar.gz If you have already downloaded the files, you may proceed to the next step. 4. GUnzip and Untar the delivery file into the current subdirectory: gunzip Delivery_File tar -xf tar_file 5. Execute the launchpad.sh and follow the instructions in the Installing the WebSphere Application Server for the remainder of the installation process. Executing the installation script may require adding execution privilege: chmod +x launchpad.sh 6. Cleanup: After installation is complete, you may remove the subdirectory. Windows Systems 1. Download the WebSphere Application Server Network Deployment (ND) delivery file simmanager_ws_ _windows.zip from the Solution Download Center to a temporary folder. 2. Unzip the delivery file: unzip Delivery_File 3. Execute launchpad.bat and follow the instructions in the Installing the WebSphere Application Server for the remainder of the installation process. 4. Cleanup: After installation is complete, you may remove temporary files from the download location in Steps 1 and 4.

40 32 Steps for installing MSC.Software Solutions Download Center files IBM DB2 Universal Database: UNIX/LINUX Systems 1. Login as root 2. "cd" to a temporary directory with sufficient disk space. Create a subdirectory and "cd" to the subdirectory. 3. Download the appropriate DB2 Universal Database delivery file from Solution Download Center DB2 v9 on AIX: simmanager_db2_9.1_fix_pack_2_aix5l.tar.gz DB2 v9 on Linux: simmanager_db2_9.1_fix_pack_2_redhat.tar.gz If you previously downloaded the file, please proceed to the next step. 4. "Unzip" the delivery file into current subdirectory: unzip Delivery_File 5. The product installer will start automatically. For the remainder of the installation process follow instructions in Installing IBM DB2 Database Server. Executing the installation script may require adding execution privilege: chmod +x install.script IBM DB2 Universal Database Setup Utility: All Systems 1. Download the delivery file from Solution Download Center simmanager_r3_db2_setup.zip to a temporary folder. 2. Unzip the delivery file into current subdirectory: unzip Delivery File 3. The product installer will start automatically. For the remainder of the installation process follow instructions in Run DB2 Setup Utility:. 4. Cleanup: After installation is complete, you may remove temporary files from the download location in Step 1 above.

41 Chapter 4: Preparing for SimManager Installation Steps for installing MSC.Software Solutions Download Center files 33 Analysis Manager UNIX/LINUX Systems 1. Download the delivery file from Solution Download Center to a temporary folder simmanager_anmgr_ _linux-unix.sh. 2. Execute the Install Script (.sh) 3. The product installer will start automatically. For the remainder of the installation process follow instructions in Job Scheduling/Queuing Software. 4. Cleanup: After installation is complete, you may remove temporary files from the download location in Step 1 above. Windows Systems 1. Download the delivery file from Solution Download Center to a temporary folder simmanager_anmgr_ _windows.exe. 2. Execute the Install Script (.exe) 3. The product installer will start automatically. For the remainder of the installation process follow instructions in Job Scheduling/Queuing Software. 4. Cleanup: After installation is complete, you may remove temporary files from the download location in Step 1 above.

42 34 Installing a Web Application Server Installing a Web Application Server SimManager requires one web application server to be installed on the host platform on which SimManager is installed. SimManager has been certified with the IBM WebSphere, Apache Tomcat, and Red Hat JBoss web application server software. If you currently have a SimManager-supported web application server installed and operational, verify the setup and configuration settings described below, and then proceed with the SimManager installation and deployment. Installing the WebSphere Application Server SimManager requires an IBM WebSphere Application Server version 6.1 for proper operation. The IBM WebSphere Application Server is a Java-based application server, integrating enterprise data and transaction for the dynamic e-business world. IBM WebSphere Application Server can be installed on different operating systems. The supported version for WebSphere Application Server is included with SimManager Enterprise. There is a WebSphere Application Server ND CD packaged with SimManager Enterprise for each supported operating system. IBM WebSphere Application Server Network Deployment (1 each for 32-bit AIX, Linux, Windows) During the installation, follow the instructions for the software installation from CD. Installing WebSphere Application Server Network Deployment 6.1 Obtain the correct IBM WebSphere Application Server CD for your platform from the SimManager Enterprise package and initiate the installation process from the IBM WebSphere Application Server v6.1 CD. Execute Launchpad and follow the default installation as per the following instructions: Note: The procedure and dialogs for installing WebSphere Application Server Network Deployment are similar for Windows, Linux and AIX platforms. One difference is the file path syntax and the executable program extension. Windows uses.exe or.bat and Linux and AIX use.sh or no extension.

43 Chapter 4: Preparing for SimManager Installation Installing a Web Application Server Click on Websphere Application Server Network Deployment Installation. 2. Click on Launch the installation wizard for the WebSphere Application Server Network Deployment.

44 36 Installing a Web Application Server 3. Click Next.

45 Chapter 4: Preparing for SimManager Installation Installing a Web Application Server Click Next to continue.

46 38 Installing a Web Application Server 5. Click Next to continue.

47 Chapter 4: Preparing for SimManager Installation Installing a Web Application Server Enter an installation directory (i.e. C:\IBM\Websphere\AppServer). Note: Make sure there are no spaces in the path.

48 40 Installing a Web Application Server 7. Click on Application Server and click Next. 8. Uncheck Enable administrative security and click Next.

49 Chapter 4: Preparing for SimManager Installation Installing a Web Application Server Review the installation information and click Next. 10. Review the progress and click Next.

50 42 Installing a Web Application Server 11. After successful installation, check the Launch the First steps console box and click Finish. You have now installed WebSphere Application Server 6.1.

51 Chapter 4: Preparing for SimManager Installation Installing a Web Application Server 43 To verify the installation, from the First Steps console, select Installation verification.

52 44 Installing a Web Application Server

53 Chapter 4: Preparing for SimManager Installation Installing a Web Application Server 45 Optionally, to verify the installation, run the versioninfo.bat file from the bin directory. For example: C:\IBM\WebSphere\AppServer\bin>versioninfo.bat This completes Installation of WebSphere Application Server 6.1.

54 46 Installing a Web Application Server Installing the Tomcat Web Application Server Apache Tomcat is a supported web application server for the SimManager system. Tomcat is a purely Java-based software, created and supported by the Apache Jakarta Project development organization. The Tomcat web application software is a stand-alone TCP/IP server that communicates with Apache. It can also act as an HTTP server or run within the Apache process. See Web Application Server (1 required), 19, for the download location. Note: When installing Tomcat 5.x for use with SimManager you should download and install the.zip version. Some command-line scripts are NOT included in the.exe download version. To install the Tomcat web application server: 1. Download the binary distribution which is applicable to your platform. 2. Unzip (extract) and untar the downloaded file as required. Ensure that there are no spaces in the directory name. 3. Follow the installation instructions, Tomcat Setup, available at Web Application Server (1 required), 19 In this guide, the installation directory that is created will be referred to as <TOMCAT_INSTALL_DIR>. 4. Set the environment variable CATALINA_HOME to < TOMCAT_INSTALL_DIR>. Installing the JBoss Web Server JBoss is a supported Web Server for the SimManager system. JBoss Web Server is an enterprise ready web server designed for medium and large applications, based on Tomcat < JBoss Web Server provides organizations with a single deployment platform for Java Server Pages (JSP) and Java Servlet technologies, PHP, and CGI. It uses a genuine high performance hybrid technology that incorporates the best of the most recent OS technologies for processing high volume data, while keeping all the reference Java specifications. See Web application server (One required), 19, for the download location. To install the JBoss Web server: Installation on Linux and Unix based systems 1. Downloading JBoss Web JBoss Web is distributed as a standalone web server. The distribution can be downloaded directly from the JBossWeb downloads page < JBoss Web is not pure Java. It contains native code, compiled and optimized for each operating system. Download the package appropriate for your platform, paying particular attention to whether or not you are running on the 64-bit system. 2. Uncompress the distribution wherever you would like JBoss Web installed.

55 Chapter 4: Preparing for SimManager Installation Installing a Web Application Server 47 The resulting directory (jbossweb-4.0.4beta-linux-i686, for example) contains the JBoss Web instance. 3. Adjusting setenv.sh On some system you may have to do an extra step. 4. Edit the $CATALINA_HOME/bin/setenv.sh (CATALINA_HOME should be something like jbossweb ga) add the LD_LIBRARY_PATH variable and modify/add: * LD_LIBRARY_PATH=LD_LIBRARY_PATH:$CATALINA_HOME/bin/native export LD_LIBRARY_PATH * Running JBoss Web Before starting, make sure that your JAVA_HOME environment variable is set to your Java install directory. From the bin directory, run the startup.bat or startup.sh script, as is appropriate for your platform. If you run this from a shell, you will see the JBoss Web console log scroll by. If JBoss Web started correctly, the last few lines of output should contain something like the following: *Feb 15, :45:10 AM org.apache.coyote.http11.http11aprprotocol start INFO: Starting Coyote HTTP/1.1 on http-8080 Feb 15, :45:10 AM org.apache.coyote.ajp.ajpaprprotocol start INFO: Starting Coyote AJP/1.3 on ajp-8009 Feb 15, :45:10 AM org.apache.catalina.startup.catalina start INFO: Server startup in 888 ms * The last line is the message JBoss Web sends when all services are up and running, letting you know that everything is good. However, the two lines before it are important for JBoss Web. They tell you that JBoss Web is listening on two ports, 8080 and More importantly, you can see from the output that JBoss Web is using the APR(Apache portable runtime) libraries. This means that you are using the optimized native libraries. Without the APR libraries, you would see output more like the following, with no reference to the APR code. *INFO: Starting Servlet Engine: JBoss Web/ Feb 15, :31:10 AM org.apache.coyote.http11.http11protocol start INFO: Starting Coyote HTTP/1.1 on http-8080 Feb 15, :31:10 AM org.apache.coyote.ajp.ajpprotocol start INFO: Starting Coyote AJP/1.3 on ajp-8009 Feb 15, :31:10 AM org.apache.catalina.startup.catalina start INFO: Server startup in 1192 ms * In worse cases, like using the wrong version of the libraries for your platform, JBoss Web may completely fail to start. If there is an error, check the console log (the output in your terminal window) or the server log in logs/catalina.out for more information about the problem. To access your JBoss Web instance, go to in your web browser. If everything went well, you will see the JBoss Web start welcome screen. Congratulations, your JBoss Web instance is ready to go.

56 48 Installing a Web Application Server Windows Overview JBoss Web comes with Windows service executable that can run JBoss WebServer as service. The service executable jbosssvc.exe transforms the run.bat and shutdown.bat batch scripts to services. This means that any change made to those scripts will be used both in service and command line mode. 1. Installing the service To install the JBoss Web server as Windows service use the provided service.bat batch file. *Change directory to the JBossWeb bin directory* /C:\> /*cd c:\jbossweb-4.0.4rc1-windows-i586\bin*. *Install the service* /C:\> /*service.bat install* 2. Starting the service To start the JBoss Web server as Windows service use Control panel or *net start* command.. *Start the service* /C:\> /*net start JBossWebServer*. *The JBoss Web Server 4 service is starting.*. *The JBoss Web Server 4 service was started successfully.* When running in service mode the console output is redirected to the file *run.log*. You can inspect the file for any errors during service startup. 3. Stopping the service To stop the JBoss Web server as Windows service use Control panel or *net stop* command.. *Stop the service* /C:\> /*net stop JBossWebServer*. *The JBoss Web Server 4 service was stopped successfully.* When running in service mode the console output is redirected to the file *shutdown.log*. You can inspect the file for any errors during service shutdown. 4. Stopping the service To restart the JBoss Web server as Windows service use Control panel. 5. Removing the service To remove the JBoss Web server as Windows service use the provided *service.bat* batch file.. *Change directory to the JBossWeb bin directory* /C:\> /*cd c:\jbossweb-4.0.4rc1-windows-i586\bin*. *Remove the service* /C:\> /*service.bat uninstall* 6. Customization of the service Service customization is done by editing the service.bat script. Each command has a separate section that you can customize. The most common customization task would be changing service names if more than one service instances per box are required.

57 Chapter 4: Preparing for SimManager Installation Installing a Database Server 49 Installing a Database Server SimManager requires one database server. The database server does not have to be installed on the host platform on which SimManager is installed. The SimManager host platform, however, must have access to the database server host platform. SimManager has been certified with the IBM DB2 database and Oracle server software. If you currently have a SimManager-supported database server installed and operational, verify the setup and configuration settings described below for your database server application, and then proceed with the SimManager installation and deployment. Installing IBM DB2 Database Server The DB2 Universal Database Server software is IBM's database management system for the Windows, Linux, and UNIX platforms. DB2 ESE Installation for Windows 1. Create the users of the system username: schemauser, Password: SimManager00 username: appuser, Password: SimManager00 If the DB2 instance owner (administrator) does not exist create the username db2admin, Password: SimManager00

58 50 Installing a Database Server For creating a user, follow the dialogs displayed below: 2. Install DB2. Follow the instructions, as shown in the following sections to create a typical, single-partition DB2 Enterprise Server Edition Installation.

59 Chapter 4: Preparing for SimManager Installation Installing a Database Server 51 a. Click Install a Product on DB2 Setup Launchpad. Click Install New under DB2 EnterpriseServer Edition to start installation.

60 52 Installing a Database Server b. Click Next