installation planning guide - tibco software...page 4 target audience the intended audience for this...

Installation Planning Guide

™

Software Release 10.2.0November 2017

TIBCO Nimbus

Important Information

TIBCO Nimbus™ Installation Planning Guide

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDEDOR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITEDADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLEDSOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FORANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF ALICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT,OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENTWHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH ISDUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT ORCLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE LICENSE FILE(S) OF THESOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USEHEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.

This document contains confidential information that is subject to U.S. and international copyright lawsand treaties. No part of this document may be reproduced in any form without the written authorizationof TIBCO Software Inc.

TIBCO, Two-Second Advantage and TIBCO Nimbus are either registered trademarks or trademarks ofTIBCO Software Inc. in the United States and/or other countries.

All other product and company names and marks mentioned in this document are the property of theirrespective owners and are mentioned for identification purposes only.

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALLOPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAMETIME. SEE THE RELEASE NOTE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFICOPERATING SYSTEM PLATFORM. THIS DOCUMENT IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGESARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATEDIN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/ORCHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANYTIME. THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY ORINDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUTNOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

Copyright © 1997-2017 TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information


Table of Contents

......................................................................................................................... 4Introduction

....................................................................................................... 4Target Audience

....................................................................................................... 4About the Installation Planning Guide

....................................................................................................... 4About TIBCO Nimbus

......................................................................................................................... 5General Recommendations

....................................................................................................... 5Installation Components

....................................................................................................... 5Operating Platforms

....................................................................................................... 5Author Client

....................................................................................................... 5Windows Server 2008/R2 and 2012/R2

....................................................................................................... 6Data Storage

......................................................................................................................... 7Installation Scenarios

....................................................................................................... 7Scenarios

....................................................................................................... 7Small Deployment on a Single Application Server Host

....................................................................................................... 10Medium Sized 'Split' Installation

....................................................................................................... 13Large Complex Installation

......................................................................................................................... 16TIBCO Nimbus Support

....................................................................................................... 16Contact Details

......................................................................................................................... 17Appendix

....................................................................................................... 17Windows Server 2008/R2 and 2012/R2 Considerations

....................................................................................................... 17Performance Implications

....................................................................................................... 17SMB2/SMB3 and Opportunistic Locking (OpLocks)


Introduction

Target Audience

The intended audience for this Installation Planning Guide includes:

· The Technical Architect responsible for the overall technical solution

· The Technical Architect responsible for planning and managing the TIBCO Nimbusinstallation

About the Installation Planning Guide

The purpose of this guide is to provide the Technical Architect an overview of TIBCO Nimbus, and howthe architecture can be scaled to support multi-national corporations. It also describes the hardwarerequirements for deploying and hosting TIBCO Nimbus. The figures given are purely indicative andeach organization will have their own characteristics that determine their requirements. In addition,the requirements for a particular organization will change over time, driven by a changing usageprofile. This means that there will be an ongoing capacity planning activity required to ensure thatTIBCO Nimbus performs to the requirements of an organization.

About TIBCO Nimbus

TIBCO Nimbus is a process management mapping application that allows corporate information to bepresented graphically and hierarchically in the form of maps and diagrams. It provides a simple user-interface that enables any employee within an organization to access information that is relevant andessential to fulfil their role.

Maps are a collection of diagrams created by process authors. A map is initially created as a draftversion until it is promoted to a master. Maps may also comprise a number of scenarios. Accessrights can be assigned to individual users and groups, allowing or preventing access to an entire mapor parts of a map. Continuous improvement to processes is achieved through a number ofcollaboration features. Acknowledgement requests ensure users are aware of process content thataffects their roles. Reviews ensure that content is kept up-to-date. Feedback and change requestsallow users to suggest improvements. Users can also be notified when content changes through theuse of subscriptions.

Statement sets are a hierarchical set of regulatory and auditable statements that ensure complianceto specific business and legal requirements, such as ISO 9000/12001/17799, CMMi, internalcompany policies, etc. Statements can be linked to activities that are related to compliance andgovernance.

General Recommendations


Installation Components

The basic deployment is made up of the following components:

· Author Client

· Web Server

· Action Server

· LDAP

· Office Integration

· Email

· Locking Service

· Batch Server

· BI server

It is possible to deploy these components on a single server for a simple low volume installation, or toseparate them to facilitate higher loadings and user throughputs. This will be shown in the samplescenarios.

Operating Platforms

Operating platform choice will be site specific. The release notes detail specific operating systemsand browser support for the version of choice, and can be found on the TIBCO documentation website docs.tibco.com.

Author Client

Author access through the Author Client should be deployed on an appropriate terminal services (TS)platform. Microsoft RDS or Citrix Xenapp are examples of supported platforms. The TS platformshould be placed on the same physical network as the application host server to minimise networkdelays between components. The TIBCO Nimbus Author Client is classed as a “High volume” terminalservices application and the host platform and any load balancing will need to be sized toaccommodate this.

Windows Server 2008/R2 and 2012/R2

Opportunistic locking should be disabled.

SMB2 should be disabled.

Further details on this can be found in the appendix.


General Recommendations

These can be disabled by the addition/import of two registry keys to the server. Included in theinstallation media are the “reg” files that detail these steps.

To prepare a server for use with TIBCO Nimbus, an administrator should import“DisableFileServerOplocks.reg” and “ForceSMB1.reg”. These can be backed out using thecorresponding reg files as shown above.

Data Storage

It is highly recommended when installing the product that the data is placed on a drive that's separatefrom the system volume, both physically and virtually as far as is practicable. I/O competition will beexacerbated by sharing the same data space.

Installation Scenarios


Scenarios

There are three basic scenarios demonstrated that can be extended to fit specific requirements:

1. Small deployment on a single server host

2. Medium sized “split” installation

3. Large sized complex installation

Note: It is recommended that you review the entire scenario before attempting installation.

Small Deployment on a Single Application Server Host

The following example provides a reference deployment to support 10 to 1000 users.

The diagram shows the component layouts.



The component blocks above should be installed in two different locations on the server. Placement ofthe data store is critical. This should be installed on a data drive that is physically separated from thesystem drive. In a physical system this means it should not share physical space with the systemdrive. In a virtual system this should operate on its own Virtual Hard Drive. Normal operations factorswill apply.

Recommended performance:

· CPU Minimum 1 Ghz performance

· Memory 4GB allocated to installation minimum

· Disk Space and Type required will depend upon usage profiles and documentation storage.As an absolute minimum the drive should have 40GB of uncontested disk space. It is yourresponsibility to carry out Capacity Management and to ensure that there is enough diskspace for the Nimbus Data at all times. You should also ensure that when using theNimbus Backup Utility, the target location of the backup is on a separate drive to theNimbus Data. Failure to observe either of these recommendations could result inirrecoverable data or capacity management issues.

ProcedureThe steps for installation are documented in the TIBCO Nimbus Administration Guide but theprocedure is as follows:

1. Deploy pre-requisites

· IIS

· Excel (optional if using Office integration)

· Recommended Anti-Virus exclusions

· Domain service account

2. Install the Author Client software

3. Install the Web Server software

4. Install the Action Server services

5. Install the Batch Server

6. Install the BI server (optional)

7. Launch the Author Client and create initial user

8. Configure shares and permissions

9. Configure the Web Server and DCOM permissions

10. Deploy the Author Client on terminal services platform

11. Configure LDAP (optional)



When installing the Client software in step 2, it is recommended that the installation folder and datafolders are created separately before commencing. In the figure below you will see that separatefolders have been created.

Also, the installation has been placed away from the system drive.

Further to this, a Process Repository was created with a shortened path – “PR”.

The folder can have any name, however it should be noted that several folders will be created in thislocation following the first launch of the Author Client and subsequent advanced configurationactions:

· Document storage

· Scorecard repository storage

· Secure credentials

Each of these will need to be accessible to some degree by the Author Client. Separation into aseparate data folder minimizes the changes required for security and reduces complexity. TheTIBCONimbusData folder will need to be shared to allow remote access. Change permissions on theshare should be set for all Administrators and Authors, along with any required domain serviceaccounts. The File system folders will need to be set with “modify” permissions for these accounts.



Medium Sized 'Split' Installation

The following example provides a reference deployment to support 1000 to 5000 users.

The diagram shows the component layouts. In this scenario the application components are separatedto allow greater performance levels from the Web Server platform. LDAP is highly recommended tosupport the number of users in this scenario.

Recommended Performance:

· CPU Minimum dual 2.5 GHz performance


· Disk Space and Type required will depend upon usage profiles and documentation storage.As an absolute minimum the drive should have 40GB of uncontested disk space. It is yourresponsibility to carry out Capacity Management and to ensure that there is enough diskspace for the Nimbus Data at all times. You should also ensure that when using the



Nimbus Backup Utility, the target location of the backup is on a separate drive to theNimbus Data. Failure to observe either of these recommendations could result inirrecoverable data or capacity management issues.

Note: The disk space requirements can grow over time. The figure quoted is not an absolute value.

ProcedureThe steps for installation are documented in the TIBCO Nimbus administration Guide but theprocedure is as follows. As this is split across two servers the steps are graded as S1 and S2 todenote the relevant hosts:

1. Deploy pre-requisites Server 1 (S1)

· IIS




· Excel (optional if using Office integration)

3. Install the Author Client software (S1)

4. Install the Web Server software (S1)

5. Install the Action Server services (S2)

6. Install the Batch Server (S2)

7. Install the BI server (optional) (S2)

8. Launch the Author Client and create initial user (S1)

9. Configure shares and permissions (S1)

10. Configure the Web Server and DCOM permissions (S1)

11. Deploy Author Client on terminal services platform

12. Configure LDAP (optional) (S1/S2)

13. Configure Windows Integrated Authentication (S1)

When installing the Author Client software in step 3, it is recommended that the Installation folderand data folders are created separately before commencing. In the figure below you will see thatseparate folders have been created.





The folder can have any name, however it should be noted that several folders will be created in thislocation following the first launch of the Author Client and subsequent advanced configurationactions:

· Document storage



Each of these will need to be accessible to some degree by the Author Client users. Separation into aseparate data folder minimizes the changes required for security and reduces complexity. TheTIBCONimbusData folder will need to be shared to allow remote access. Change permissions on theshare should be set for all Administrators and Authors along with any required domain serviceaccounts.



Large Complex Installation

The following example provides a reference deployment to support 5000+ users in varying increments.

The diagram shows the component layouts. In this scenario the application components are separatedto allow greater performance levels from the Web Server platform. LDAP is highly recommended tosupport the number of users in this scenario.

Recommended Performance:

· CPU Minimum dual 2.5 GHz performance


· Disk Space and Type required will depend upon usage profiles and documentation storage.As an absolute minimum the drive should have 40GB of uncontested disk space. It is yourresponsibility to carry out Capacity Management and to ensure that there is enough diskspace for the Nimbus Data at all times. You should also ensure that when using theNimbus Backup Utility, the target location of the backup is on a separate drive to theNimbus Data. Failure to observe either of these recommendations could result inirrecoverable data or capacity management issues.

These requirement numbers are provided “per host server”.



ProcedureThe steps for installation are documented in the TIBCO Nimbus administration guide but theprocedure is as follows. As this is split across a potential of 5 servers plus a load balancer andterminal services stack, the steps are graded as S1 to S5 to denote the relevant hosts. S1 to S3 areWeb Servers, S4 is the Action Server Host and S5 is the data store.

1. Deploy pre-requisites Server 1 (S1-S3)

· IIS




· Excel (optional if using Office integration

3. Install the Author Client software (S5)

4. Configure shares and permissions (S5)

5. Install the Web Server software (S1-S3)

6. Install the Action Server services (S4)

7. Install the Batch Server (S4)

8. Install the BI server (optional) (S4)

9. Launch the Author Client and create initial user (S5)

10. Configure the Web Server and DCOM permissions (S1-S3)

11. Deploy Author Client on terminal services platform stack

12. Configure LDAP (optional) (S5)

13. Configure Windows Integrated Authentication (S1-S3)

When installing the Author Client software in step 3 it is recommended that the installation folder anddata folders are created separately before commencing. In the figure below you will see that separatefolders have been created.





The folder can have any name, however it should be noted that several folders will be created in thislocation following the first launch of the Author Client and subsequent advanced configurationactions.

· Document storage



Each of these will need to be accessible to some degree by the Author Client users. Separation into aseparate data folder minimizes the changes required for security and reduces complexity. TheTIBCONimbusData folder will need to be shared to allow remote access. Change permissions on theshare should be set for all Administrators and Authors along with any required domain serviceaccounts

Load balancers will need to be set with session affinity to ensure that a user session remains with itsoriginal server during that connection session. An appropriate sticky bit must be set at the Loadbalancer with reference to the internal network architecture.

It is possible to use SSL offloading at the load balancer, however it is still recommended that back endWeb Servers are supported at least by self-signed certificates, in this case with appropriate validationoptions set at the load balancer. Refer to your LB documentation for relevant configurationguidelines.

Advanced FeaturesAdvanced product features include the secure process repository, the VSSBackup utility and the abilityto extract the application data to a SQL database for data mining. Descriptions of these features canbe found in the TIBCO Nimbus Administration Guide, downloadable from the TIBCO Documentationsite at docs.tibco.com.

http://docs.tibco.com


TIBCO Nimbus Support

Contact Details

Our specialized team are on hand to provide assistance with the TIBCO Nimbus product. TIBCOSupport is an online resource where you can log cases directly, 24 hours a day, 7 days a week. Youcan also view updates on current cases and search the TIBCO Nimbus Knowledge Base.

Use the links below to access the relevant service.

Requirement Contact Details

To register for a TIBCO Support account. Request an account for TIBCO Support

To log in to TIBCO Support. support.tibco.com

If your support issue is urgent and you havenot yet registered for an account please email.

[email protected]

For phone numbers and further information onservice level agreements.

TIBCO Support Services

Access the TIBCO Community site. TIBCO Community

https://support.tibco.com/s/contact-support-agent

https://support.tibco.com

mailto:[email protected]

http://www.tibco.co.uk/services/support

https://community.tibco.com/products/tibco-nimbus

Appendix


Windows Server 2008/R2 and 2012/R2 Considerations

Performance Implications

Disabling SMB2/3 will only have a very minor impact on performance and hence this will not usuallybe noticeable. Opportunistic locking can provide significant performance improvements but only whena single PC or server accesses remote files. However, once a process on the file server or on anotherPC/server starts accessing the same file, this gain is lost. As the Process Repository will either beaccessed either entirely from the local server or more usually several servers, opportunistic locking isnot in use and therefore disabling it should not have any significant impact on performance.

SMB2/SMB3 and Opportunistic Locking (OpLocks)

A potential data corruption issue has been identified when the Process Repository is placed on a;Microsoft Windows Server 2008/R2, Windows Server 2012/R2, or on a Microsoft Windows Vista/Windows 7 workstation and then accessed by another Windows Server 2008/R2, 2012/R2 or a Vista/Windows 7 workstation that is SMB2 enabled. To avoid any possible corruption to the data in thisdeployment set-up, Nimbus highly recommends disabling both the Server Message Block (SMB2/3) filesharing protocol and Opportunistic Locking on the file server.

Note: Opportunistic locking can only be disabled when SMB2/3 has been disabled. After disablingSMB2/3, SMB1 will be used, even when clients that are SMB2/3 capable open files on the file server.

To disable SMB2/3 and Opportunistic Locking:The CD image contains registry import files that will disable SMB2/3 and Opportunistic Locking on aserver (found in System Updates and Utils/Oplocks and SMB2).

Force SMB1.reg will disable SMB2/3 and use SMB1.

DisableFileServerOplocks.reg will disable opportunistic locking.

Alternatively, the Windows Server System Registry can be manually edited:

To disable SMB2/3, change or add the following REG_DWORD value:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\SMB2

Set the value to 0.

To disable Opportunistic Locking, change or add the following REG_DWORD value:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

\EnableOplocks

Set the value to 0.

Note: You must restart the computer for the above registry changes to take effect.


Appendix

To enable SMB2/3 and Opportunistic Locking:AllowSMB2.reg will enable SMB2/3.EnableFileServerOplocks.reg will enable opportunistic locking.Alternatively, you can manually set the registry values above to 1.

installation planning guide - tibco software...page 4 target audience the intended audience for this...

Documents