Installation Guide

Rev. (Y-M-D): 2019-01-17

360suite.io
 360Suite Installation Guide

Table of Contents
Chapter 1. Prerequisites .................................................................................................................................................. 1
Chapter 2. Installation ...................................................................................................................................................... 2
Chapter 3. Application configuration ............................................................................................................................. 5
1. General base configuration ..................................................................................................................................... 5
1.1. Initial configuration ........................................................................................................................................ 5
1.2. License Key Registration .............................................................................................................................. 6
1.3. Administration console .................................................................................................................................. 7
1.3.1. Database configuration, license management and specific preferences ............................................ 7
1.3.2. Cluster preferences ........................................................................................................................... 10
2. Specific per-module base configurations .............................................................................................................. 11
2.1. 360Live configuration .................................................................................................................................. 11
2.1.1. 360Probe Setup ................................................................................................................................ 11
2.1.1.1. 360Probe Agent command-line parameter reference ............................................................. 12
2.2. 360Plus / 360Vers configuration ................................................................................................................. 12
2.2.1. Backup/Versioning configuration ....................................................................................................... 13
2.2.2. 360Vers - Webi extension ................................................................................................................ 14
2.2.2.1. Webi extension deployment ................................................................................................... 15
2.2.2.2. Configuration ........................................................................................................................... 15
Chapter 4. Accessing 360Suite ..................................................................................................................................... 18
Chapter 5. 360Suite update ........................................................................................................................................... 19
1. Application update ................................................................................................................................................. 19
2. 360Live: 360Probe agent update .......................................................................................................................... 19
2.1. 360Probe agent update .............................................................................................................................. 20

Appendix A. Special case: Basic installation .............................................................................................................. 21

Appendix B. JDBC URL reference ................................................................................................................................ 22
1. SQL Server - Integrated Windows authentication configuration ........................................................................... 22
2. SQL Server - Windows authentication configuration using jTDS .......................................................................... 23
Appendix C. Single Sign-on setup and configuration ................................................................................................ 24
1. Trusted SSO Authentication configuration ............................................................................................................ 24
2. Active Directory SSO authentication configuration ............................................................................................... 24
Appendix D. Installer options ....................................................................................................................................... 26

i
 360Suite Installation Guide

Chapter 1. 360Suite: Installation prerequisites

This quick installation sheet will guide you through the standard 360Suite installation process.
The installation package includes the application as well as its technical dependencies (standard runtime environment
composed of Apache Tomcat, Java JRE and PostgreSQL).
Before proceeding, please make sure the target system complies with the following technical requirements:
• 64-bit Operating System: Microsoft Windows Server 2008 (or higher).
• At least 2 GB of RAM and at least 60 MB of disk space for the 360 application, plus 300 to 500 MB if installing the
standalone setup (Apache Tomcat, Java JRE and PostgreSQL).
• SAP BO SDK Libraries (<BOBJ installation>\SAP BusinessObjects Enterprise XI 4.0\java\lib).

WARNING
360Suite requires all the BOBJ SDK Java libraries provided with the standard SAP BusinessObjects
CMS setup. Those libraries are NOT included in BOBJ Webtier setups. Make sure to copy the libraries
from a full standard version (e.g.: to a temporary location to select at installation time) BEFORE installing
360Suite, then use the previously copied libraries during the setup procedure.

• If not installing the provided environment packages, please make sure that the following are already installed on
the target system:
– Java JRE 8.
– Apache Tomcat 8.
– A dedicated database schema (using a supported local or remote database server).

DANGER
Always use a separate empty database schema for each GB&SMITH software tool. Severe
database corruption and data loss will occur if sharing a same schema between products (e.g.: if
using 360Suite and 360Eyes concurrently).

Perform a full backup of existing databases BEFORE INSTALLING AND RUNNING the application.

Chapter 1. Prerequisites 1
 360Suite Installation Guide

Chapter 2. Installation
Procedure
If installing 360Suite along with the provided Tomcat and/or database servers, follow the instructions below (otherwise,
follow the Basic installation procedure in order to deploy the web application without installing the pre-configured
dependencies):

1. Download the installation archive from GB&SMITH's support site

2. Extract the downloaded ZIP file to a local folder (e.g.: on the Windows desktop).

3. Run (as administrator) 360Suite-bi<BO_version>-v<version>.exe

4. The installation wizard opens. Select "Full" (installs the dependencies and environment. The "Basic Install / Update"
option copies BO libraries and the application .war file only), then click on "Next" to continue.

5. Check the "Install Tomcat" option (default) to install the provided Apache Tomcat server (recommended. If using a
third-party Tomcat, make sure it is stopped prior to installing), then, if applicable edit the service name (technical
registration name), display name and description (as will be displayed on the Windows Services panel accessible by
running services.msc). Using the default settings is highly recommended. Click on "Next" to continue:

6. Check the "Install Postgre SQL" option (default) to install the provided database server (recommended). If applicable,
specify a different super account name (the user must have DB schema administrator rights). In any case, specify
the user's password. These account, password and port number will then be used by 360Suite when connecting to
the default three60suite database. Click on "Next" to continue:

WARNING
Before installing PostgreSQL from the 360Suite package, please make sure to delete any files and registry
keys left by previous Postgre setups (e.g.: following uninstallation).

Chapter 2. Installation 2
 360Suite Installation Guide

7. Specify the path to the locations that contain the following dependencies:

• SAP BusinessObjects (standard CMS setup, not BOBJ web-tier) libraries location (files stored in
%programfiles[(x86)]%\SAP Business Objects\SAP BusinessObjects Enterprise XI 4.0\java\lib).

• WebiAdmin tool libraries (usually stored in %programfiles[(x86)]%\SAP Business Objects\SAP

BusinessObjects Enterprise XI 4.0\java\apps\WebiAdminTool).

• Optional (if installing 360Univ): Select the "Import SL SDK" option and specify the appropriate location (usually
%programfiles[(x86)]%\SAP Business Objects\SAP BusinessObjects Enterprise XI 4.0\SL SDK).

8. If using an alternate database (other than the provided PostgreSQL setup), specify the path to the corresponding
JDBC driver for Java 8 (.jar file). If using the provided database, this field can be ignored. Click on "Next" to continue.

9. Accept the license agreement and click on "Next".

10. Use the default installation folder if installing the provided Tomcat server. If deploying the application on an existing third-
party Tomcat server (e.g.: if not using the application server bundled in the 360Suite installer), you MUST specify to the
appropriate <Tomcat>\webapps deployment directory otherwise the application will not be installed (empty installation
folder). Click on "Next".

Chapter 2. Installation 3
 360Suite Installation Guide

11. The installer displays the pre-installation summary. Click on "Install" to proceed.
12. During installation, and if installing the provided PostgreSQL database, a console window opens and prompts for
the database Super Account password. Specify the password and confirm it (hit the Enter key to validate).

Note
As a security measure, the prompt in the console window DOES NOT display any output when specifying
the password and its confirmation. This behavior is normal.

Following this, the installation process will go on and may open other console windows. Press any key when indicated.
13. Optional (service restart): If deploying the application on a server other than the provided Tomcat, run services.msc
(or Control Panel - Administrative tools - Windows Services panel), then start (if not already running) or restart the
corresponding Apache Tomcat service.

Chapter 2. Installation 4
 360Suite Installation Guide

Chapter 3. Application configuration

This chapter details general and per-module base configuration procedures.

1. General base configuration

1.1. Initial configuration

Procedure
Once the application installed, basic settings must be set. Open a compatible web browser (e.g.: Google Chrome, Mozilla
Firefox, IE 11 or later, etc.) and open the 360Suite administration console as follows:

Tip
Port 5920 if using the standalone setup, or custom port if using another application server

• From the server the application is running on:

http://localhost:<port>/360.suite/admin

• From another machine on the network:

http://<server_name/IP>:<port>/360.suite/admin

The administration console login prompt is displayed:

Enter the default administration credentials and clink on "Log on":

• User: 360

• Password: 360

You are then prompted to change the Administration Console password. Specify the new password and validate.

Follow the instructions hereafter to initialize 360Suite.

1. If using a custom database setup, configure the database path accordingly (please refer to the vendor-provided
documentation for specific URI details. See JDBC URL reference). Sample syntax for the default PostgreSQL database:

jdbc:postgresql://<server>:5432/three60suite

Chapter 3. Application configuration 5

 360Suite Installation Guide

2. If using the provided PostgreSQL database, specify the Super Account name (as specified at installation time) and
check the "Change Password" option to enter the Super Account password. If not using the provided PostgreSQL
database, specify the user name and password of the user having access to the previously created schema.

Important
In any case, the database user account password MUST be specified at first-time configuration.

3. Click on the "Save" button.

1.2. License Key Registration

Procedure
Valid license keys are required for logging in to 360Suite.

Follow the instructions below to register license keys:

1. Make sure you have received a license key via E-mail or via GB&SMITH's Support Site

2. From a web browser, open the 360Suite Administration Console:

Tip
Port 5920 if using the standalone setup, or custom port if using another application server

• From the server the application is running on:

http://localhost:<port>/360.suite/admin

• From another machine on the network:

http://<server_name/IP>:<port>/360.suite/admin

3. Open the "License" tab.

4. Paste the license key code into the "License Key" field (1) and click on the "Add" button (2).

5. Optional (Administrator Licenses only): In the "Administrators" block, enter a valid SAP BusinessObjects user
name (3) to map as a 360Suite administrator (within the limits allowed by Administrator License keys), then select
the product the mapping applies to (4) and click on the "Add" button (5) to save the changes.

Troubleshooting
Should you have any issues or questions about license keys, please get in touch with your commercial
contact or submit a trouble ticket on GB&SMITH's Support Site

Chapter 3. Application configuration 6

 360Suite Installation Guide

1.3. Administration console

WARNING
The database settings console should only be used by system administrators when performing scheduled
platform maintenance. Please make sure to back-up the current database and related SQL configurations
before proceeding. GB&SMITH shall NOT be held liable for any damage resulting from any misconfiguration.

To access the administration console, open a compatible web browser and enter the following URL (or click on in the
top banner > Administration Console):

http://<server>[:<port>]/360.suite/admin

Log in using the following credentials:

• Username: 360 (dedicated root 360 administrator account).

• Password: 360 (default password for initialization only). If logging in using the default password, the application
automatically requires it to be changed. Once done, log in again using the new password.

The console allows managing the settings of the database used by the application for storing settings, scheduled tasks,
job information, etc.

1.3.1. Database configuration, license management and specific preferences

Database configuration and license management options are available from the administration console.

• Database configuration tab:

– Database configuration:

• Database: Select the database type and its version. If the exact version is not listed, use the next higher one.

• URL: Specify the URI scheme depending on the database used by 360Suite (e.g.: three60suite as database
name):

MySQL jdbc:mysql://<server>:<port>/<database_name>

Oracle jdbc:oracle:thin:@<server>:<port>:<database_name> or
jdbc:oracle:thin:@<server>:<port>/<service_name>

PostgreSQL jdbc:postgresql://<server>:<port>/<database_name>

SQL Server jdbc:sqlserver://

<server>:<port>;databaseName=<database_name>[;integratedSecurity=true]

SQL Server with jdbc:jtds:sqlserver://<server>:<port>/

jTDS <database_name>[;useNTLMv2=true][;domain=<domain_name>]

Note
If using another database type, please refer to the corresponding vendor-provided
documentation.

• Windows Authentication: Select this option if using Windows Integrated Security or NTLMv2.

• User: Specify the user name for connecting to the application database.

• Change Password: Check this option to specify the database user's password.

• Advanced configuration: Adjust the settings to fine-tune database performances.

DANGER
Edit the following settings very carefully. Any misconfiguration may lead to application or
database crashes and may result in corrupted data or loss of information.

Chapter 3. Application configuration 7

 360Suite Installation Guide

– Minimum connection pool size: Minimum amount of concurrent connections between the application and
the database server.

– Maximum connection pool size: Maximum amount of concurrent connections between the application
and the database server.

– Maximum number of statements: Maximum number of SQL instructions (statements) passed to the
database for a single connection.

– Number of cached statement closing threads: Number of threads dedicated to closing active connections
and terminating cached SQL statements.

Click on Save to apply the settings.

• License tab:

– Keys block: Paste the license key code provided by GB&SMITH's support into the License Keys field and click
on Add to save it.

Existing keys are displayed in the list below the text field, indicating which product the license applies to, the
maximum number of users, the licence type (Administrator or User/Standard license), validity dates.

Expired or invalid licenses can be removed from the list by clicking on the corresponding button(s).

Tip
Expired keys are highlighted in orange. Please contact a GB&SMITH representative for licence key
renewal.

Figure 3-1. Expired key

– Administrators block: Existing SAP BusinessObjects user accounts can be mapped as 360Suite administrators up
to the limit(s) allowed by valid Administrator Licenses for each given product.

To map a specific BO user name, follow the instructions below:

Figure 3-2. Administrator mapping

1. Specify a valid user name in the Name field.

2. According to available license keys, select the product(s) the user will administer (click on toggle buttons
to highlight them).

3. Click on Add to save the entry.

Note
Existing 360 administrators can be removed from the list by clicking on the corresponding
button(s).

Depending on available and installed licenses, mapped users can be promoted to 360 administrator role or
demoted: Select or de-select the corresponding checkboxes next to each product listed beside mapped user
names, then click on Update to save the changes.

Chapter 3. Application configuration 8

 360Suite Installation Guide

Figure 3-3. Updating mapped administrators

• Technical settings tab:

– RMI port: Specify the port to use for connections between 360Suite and the 360Probe Agent (default: 1337).

– Query Batch Size: Specify the maximum number of BO objects to fetch per request.

– Allowed IP addresses for external tasks: Specify a list of IPv4 and/or IPv6 addresses allowed to launch external
tasks. Each IP address must be separated by a semicolon (;). If this field is empty, external tasks can be launched
from any machine on the network.

Attention
If IP restrictions are enforced (IP listed in the field) and that 360Suite is running in cluster mode, add
the IP address of each cluster node to the white list.

– Cluster Preferences: See details in the dedicated cluster configuration section.

– CMS Preferences: Specify the default CMS and authentication kind to display on the main 360Suite log-in screen.
Select the "Hide CMS" option to disable and hide the CMS field on the main login screen.

Restriction
If the "Hide CMS" option is selected, only the specified default CMS is accessible. Users are
therefore not allowed to specify and to log in to other environments.

– SSL Properties:

• Enable SSL: Check this option if using secure connections to fetch watcher metrics (please contact your
system administrator for secure configuration settings).

• Keystore path: Specify the path to the keystore file containing public and private client keys and certificates.
e.g.: /path/to/keystore/file.name

• SSL Keystore password: If the keystore file is encrypted, check this option and enter the password.

• Truststore path: Specify the path to the truststore file containing the public keys and certificates of trusted
locations (system probes, CMS, etc.). e.g.: /path/to/truststore/file.name

• SSL truststore password: If the truststore file is encrypted, check this option and enter the password.

Note
In cluster mode, make sure that all nodes belonging to the same cluster trust the client (360
certificate). Also ensure that all nodes in the cluster are trusted by the client.

• Keystore and Truststore type: Select the keystore and truststore type matching the format of the specified
files (please refer to the Oracle documentation for details).

– and Webi comparison properties: Adjust the similitude rate from which 360Suite considers that two
compared items match (Webi report/document version and backup comparison).

– SSO preferences:

• Enable SSO : Check this option to enable the Single Sign-On feature.

• CMS : Environment to connect to when using SSO. Specify the CMS hostname or IP address (e.g.:
sapbi42w12.bo.corp.net).

Chapter 3. Application configuration 9

 360Suite Installation Guide

Restriction
Each 360Suite setup can connect to only ONE CMS when using single sign-on.

• Type :

– AD : Active Directory single sign-on (requires a specific configuration. Please refer to the 360Suite
installation and SSO configuration procedures).

– Trusted : Uses a trusted authentication provider to centralize login tokens. The following settings must
be specified to use trusted authentication (requires a specific configuration. Please refer to the 360Suite
installation and SSO configuration procedures):

1. Retrieval method: Select the authentication token retrieval method in the drop-down list.

2. Retrieval user parameter: Specify the parameter used by the retrieval method (e.g.: header name
if using the Http Header method, etc.).

• Administration tab:

– Change password: Update the administration console access password.

1.3.2. Cluster preferences

360Suite supports cluster mode. The following instructions detail how to configure the application for operating in this mode.

WARNING
Cluster mode configuration is usually set at installation time and should not be modified. Any change
should be made by system administrators when performing scheduled maintenance. Misconfiguration
may result in unreachable nodes or application malfunction. GB&SMITH shall NOT be held liable for
any damage resulting from any misconfiguration.

Cluster mode requirements are:

• 1 virtual machine or physical server per node.

• The 360 application deployed on each node.

• Each 360 application configured for operating in cluster mode.

• A single common database for the cluster.

To enable cluster mode from the administration console, follow the instructions below:

1. Access the "Technical settings" tab and scroll down to the Cluster Preferences block.

2. Check the Cluster Enabled option (the application checks if previously defined cluster nodes are available.
Unreachable nodes are indicated with in the list).

3. Specify the location of each existing node (except the current one). The application name (appName) refers to the
name of (or path to) the deployed war file in the <Tomcat>/webapps directory on each node.

The syntax used in the list is: <protocol>://<server>:<port>/<appName>

4. Click on "Add" to append each node to the list.

To remove a node from the list click on the corresponding button.

Example: Configuring a 3-node cluster.

• The first node is hosted on 360cluster0.lan and is listening on port 8081.

• The second node is on 360cluster1.lan (port 8082).

• The third node is on 360cluster2.lan (port 8082).

Node list, as displayed by 360cluster0.lan:

Chapter 3. Application configuration 10

 360Suite Installation Guide

Figure 3-4. Node list

Note
If using secure connections (SSL/TLS), populate truststore and keystore files (please refer to the
documentation of your key generation tool such as OpenSSL, Java KeyTool, etc.) on each cluster node and
configure the corresponding settings accordingly in the general settings.

2. Specific per-module base configurations

The following sections provide extra per-module configuration instruction when applicable.

2.1. configuration

2.1.1. 360Probe Setup

Procedure
The 360Probe Agent is required for monitoring of system metrics (e.g.: used by 360Live metric Monitors and Watchers).
The agent requires Java JRE 8 to run and should be deployed and launched on each system running the BO services to
monitor from the 360 application (corresponding metrics are detailed in the User Guide).
Follow the instructions below to deploy the Probe Agent:
1. On the machine to monitor, create a dedicated folder (e.g.: C:\360ProbeAgent).
2. Copy 360.suite.probe-<version>.jar and other files (archive probe folder) to the previously created directory.
3. If using SSL/TLS connections, edit the ssl_configurations.properties file and set the following parameters:
• hostname: IP or hostname of the server running the Probe Agent.
• keystore: absolute path to the keystore file.
• truststore: absolute path to the truststore file.
• filetype: type of the truststore and keystore files. Expects: jks or pkcs12 or jceks (See the Oracle documentation
for keystore and truststore file type details).
4. Open a command line and run the probe agent from its deployment location:

Tip
360Probe can be run using the provided standalone JRE installed in %windir%\360Suite

java -jar -Xmx128m [-Dhttps.protocols=TLSv1.1,TLSv1.2] 360.suite.probe-<version>.jar [params]

• [params]: Optional parameters. See command line parameter reference.

• -Dhttps.protocols=TLSv1.1,TLSv1.2: Optional. Recommended if using SSL/TLS connections between
360Suite and the Probe Agent. Forces the use of TLS 1.1 and 1.2 ciphersuites.
5. The Probe Agent starts. If using SSL (-s parameter), specify the password of the truststore and keystore files (first
execution only).

C:\360ProbeAgent\>java -jar -Xmx128m -Dhttps.protocols=TLSv1.1,TLSv1.2 360.suite.probe.jar -s

Chapter 3. Application configuration 11

 360Suite Installation Guide

360Probe vx.x.x
Starting Probe using SSL
Default port is 1337
[...]
Enter keystore password:
[...]
-- 27 processes under probing --

2.1.1.1. 360Probe Agent command-line parameter reference

360.suite.probe.jar [-d] [--debug] [-f <sec>] [--frequency <sec>] [-h] [--help] [-p <port>] [--port
<port>] [-pass <password>] [--sslpassword <password>] [-s] [--ssl] [-v] [--version]

Parameters
-d, --debug
Verbose mode. Logs display more detailed information (useful for troubleshooting).

-f, --frequency
Overrides de default data retrieval frequency value in seconds (defaults to 1 second). Low values will cause higher
CPU usage due to more frequent probing.

-h, --help
Displays help information then exits.

-p, --port
Overrides the default port (defaults to 1337).

-pass, --sslpassword
Updates the keystore password in the configuration file then exits.

Attention
This option is not recommended: passwords in command lines may be saved as plain text in the
command history. Using the -s parameter in interactive mode is recommended for first-time password
configuration.

-s, --ssl
Starts the Probe agent with secure connection support (SSL/TLS). The Probe agent prompts for the keystore
password at first execution.

-tpass, --ssltspassword
Updates the truststore password in the configuration file then exits.

Attention
This option is not recommended: passwords in command lines may be saved as plain text in the
command history. Using the -s parameter in interactive mode is recommended for first-time password
configuration.

-v, --version
Displays version information then exits.

2.2. and configuration

This section details the available configuration options for 360Plus and 360Vers.

Please note that both products are dealt with together in this section as, depending on your configuration, each module
may complement the other.

Each module requires a separate license key. Please get in touch with your commercial support in order to obtain product
keys.

Chapter 3. Application configuration 12

 360Suite Installation Guide

2.2.1. and - Backup/Versioning Configuration

The following options are available if a 360Plus and/or a 360Vers product key has been entered in the Licence section.

Use the "Activate 360Plus/360Vers" toggle buttons to enable the backup (360Plus) and/or versioning (360Vers) modules
and unlock the corresponding configuration options.

• Internal Tasks configuration: Internal tasks scan SAP BO repositories on a regular basis in order to keep
track of deleted objects. Configuring deletion tracking for each CMS to monitor is required for the recycle bin to work.
The currently active CMS are listed in the table. Click on the "Configure backup indexing" button to open the wizard and
configure the task for the corresponding CMS. Specify the appropriate credentials (login and password), then select
the task frequency (object monitoring interval) and confirm the settings.

• directory: Specify the full path to the backup storage directory (e.g.: C:\360Suite\backup or /360Suite/
backup). If required for creating/accessing the specified directory, check the System Credentials option and enter
valid user account information (e.g.: Windows or Linux user name and password).

Troubleshooting
If the versioning/backup directory is invalid or not specified, 360Suite may return an error message or may
disable access to backup and versioning functionalities.

• Open the Vers Configuration Wizard: If a 360Vers key has been entered, the wizard allows enabling and
configuring versioning service.

1. 360Vers directory tab:

– 360Vers directory: Specify the full path to the versioning work directory (e.g.: C:\360Suite\vers or
/360Suite/vers).

– System Credentials: If required for creating/accessing the specified directory, check this option and enter
valid user account information (e.g.: Windows or Linux user name and password). If necessary, check the
Change Password option to enable the field, then specify the account password.

2. Version tab:

– Set versioning number format: Select between the Fixed and Free format. The initial version of a given
object is then created when adding it to a package.

Important
Switching from Fixed to Free numbering is possible, however the opposite is not accepted. In
fixed format, the numbering scheme is irrevocable and cannot be altered later on.

Figure 3-5. Fixed version numbering options

– Fixed: Defines a standardized fixed version numbering scheme by incrementing the current number.

• Add new part to the Version Number Format: Select a numbering format element (Numbers: Number1:
counting from 1 or Number0: counting from 0. Alphabetic characters: alpha: lowercase and ALPHA:
uppercase. Please note that version numbering is case-sensitive), then click on "Add", and select a
separator (second drop-down list), click on "Add" again to append the separator and select a new part.

– Free: If using free numbering, the number must be specified when creating a new version of a given object.
Any version number is possible provided that it was not previously attributed to the same object. Following
numbering order is not mandatory.

– Version number format: In Fixed mode, the numbering scheme is defined by the selected version number
format parts/elements. In Free mode, enter a base/initial version number for later use.

Chapter 3. Application configuration 13

 360Suite Installation Guide

3. Release tab:

– Set release number format: Select between the fixed and free format (similarly to version number format).

– Enable versioning workflow: Select this option to allow sending the administrators an E-mail notification when
creating versions (the notification content can be set in the general settings in the "Workflow Properties - E-
mail Template" section). When enabled, temporary releases are also created by the application.

• Workflow Properties - E-Mail Template: Specify the texts used by 360Vers when sending object
versioning workflow E-mail notifications (general subject, requests in temporary releases, accepted/
rejected versions, finalised or rejected temporary releases). Dynamic values can be added to fields.
Available per-field values are displayed in pop-ups when the corresponding field is active.

4. CMS configuration tab: This tab allows sorting environments by type (development, qualification, test, integration
and production) for easier versioning workflow management. At least one CMS must be set as Development
Environment. Packages and releases can only be created and updated under a development environment. All
the other types allow displaying versioned content only.

Remember
Content management systems that are not attributed any environment type (namely, not added to
the list) will have no access to packages and releases (view, create, update, etc.).

– If no CMS is listed in the environment types list, toggle the "Add a new CMS" option on, then specify the
appropriate login details and click on the "Add CMS" button. Alternatively, if entries are available in the
"CMS" drop-down list, select the desired environment. Define the desired Environment Type in the drop-
down list.

– If the CMS list is already populated, select the desired Environment Type in the drop-down list.

5. Security lock tab:

– Security lock: Select to enable the versioning security lock (sets checked-out objects to read-only mode for
all users, except the one having locked the objects).

The security lock feature requires specifying at least one BusinessObjects user having sufficient rights
over content (e.g.: an administrator or specifically configured account) in order to set the appropriate read-
only rights on locked objects not belonging to the current user. Fine security can also be used to limit locking to
objects matching a specific custom access level. The following options are available when locking is enabled:

Figure 3-6. Versioning security lock settings

To add a security lock, expand the "Security Lock Parameters" block, select a CMS, then specify the
appropriate user credentials. If applicable, check the Use Fine Security option and specify the Custom
Access Level to use for limiting locking rights. Click on "Add Security Lock" to save the new entry.

– Click on the "Save Configuration" button to save the changes.

2.2.2. - Webi extension

Chapter 3. Application configuration 14

 360Suite Installation Guide

2.2.2.1. Webi extension deployment

Procedure
The 360Vers Webi Extension is an optional bundle for SAP BusinessObjects providing direct access to object locking and
versioning functionalities directly from the Central Management Console or BI LaunchPad.

Note
A valid 360Vers license is required to run the extension. Please get in touch with your GB&SMITH commercial
contact for information and pricing.

Follow the instructions below to deploy the extension bundle:

1. Stop the SAP BusinessObjects application server.

2. Extract the content of the \extension\360VersWebiExtension folder from the 360Suite installation archive (if
necessary download the package again from the 360Suite support site) and copy the following file (where vers_nb
is the extension version number):

com.businessobjects.webpath.AnalyticalReporting_GBS_360VersUserExtension_<vers_nb>.jar

To the following locations on the SAP BusinessObjects server:

• <tomcat>\webapps\BOE\WEB-INF\eclipse\plugins

• <tomcat>\work\Catalina\localhost\BOE\eclipse\plugins

• <BO_INSTALL_DIR>\SAP BusinessObjects Enterprise XI 4.x\warfiles\webapps\BOE\WEB-INF\eclipse

\plugins

3. Copy 360VersExtension.property to the following location on the SAP BusinessObjects server:

• <tomcat>\webapps\BOE\WEB-INF\eclipse\plugins

4. Edit 360VersExtension.property and specify the URL to the 360Suite deployment:

360_APPLICATION_URL = <protocol>://<hostname/IP>[:<port>]/<deployment_location>/

Important
The specified URL must end with a forward slash (/).

Example:

360_APPLICATION_URL = http://360.bo-internal.lan:8080/360.suite/

5. Restart the SAP BusinessObjects application server.

Important
Always clear your browser cache after EACH deployment or update of the 360Vers Webi extension and
BEFORE configuring it or accessing the CMC.

The extension is deployed and can be configured.

2.2.2.2. Configuration

Procedure

Remember
Before using the extension, make sure that the following requirements are met:

• Versioning is enabled and configured (360Suite Administration Console).

• At least one development environment has been configured (Vers configuration wizard).

Chapter 3. Application configuration 15

 360Suite Installation Guide

• The security lock feature is enabled and configured (the extension will return errors if locking is not
configured).

Optionally, if using the versioning workflow functionalities, enable the corresponding option and configure E-
mail templates (Workflow properties) in the general 360Suite preferences (please refer to the user guide).

The configuration of the Webi extension is stored in 360VersExtension.property located in <tomcat>\webapps\BOE

\WEB-INF\eclipse\plugins and includes the following parameters:

• 360Suite deployment URL (required):

360_APPLICATION_URL = <protocol>://<hostname/IP>[:<port>]/<deployment_location>/

Important
The protocol can be http or https. If using https (secure SSL/TLS connections), the
360_HTTPS_PROTOCOL parameter must be set. The specified URL must end with a forward slash (/).

• Secure connection protocol:

360_HTTPS_PROTOCOL = <protocol_name>

Where protocol_name should match the SSL/TLS protocol used by the SAP BusinessObjects Apache Tomcat server
configuration.

Tip
Please refer to the corresponding Apache Tomcat documentation for detailed instructions:

– Tomcat 7.0: https://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html#Configuration

– Tomcat 8.0: https://tomcat.apache.org/tomcat-8.0-doc/ssl-howto.html#Configuration

– Tomcat 8.5: https://tomcat.apache.org/tomcat-8.5-doc/ssl-howto.html#Configuration

Follow these instructions to enable secure connections:

1. If not already enabled in the Apache Tomcat configuration, specify the following property to select the desired
HTTPS protocol:

-Dhttps.protocols=<protocol_name>

Example:

-Dhttps.protocols=TLSv1.2

2. Edit 360VersExtension.property and set the 360_HTTPS_PROTOCOL value accordingly:

– If running Java 7:

• If the selected protocol is TLSv1, TLSv1.1 or TLSv1.2, then 360_HTTPS_PROTOCOL = TLSv1

• If using any other protocol, then 360_HTTPS_PROTOCOL = <protocol_name>

– If running Java 8: In any case, 360_HTTPS_PROTOCOL = <protocol_name>

3. Restart the application server.

The Webi extension must then be enabled in the SAP BusinessObjects Central Management Console and groups must be
given the appropriate permissions in order to use it:

1. In the Central Management Console, select Users and Groups.

2. Right-click on the desired group and select Customization in the context menu.

Chapter 3. Application configuration 16

 360Suite Installation Guide

3. Open the Extensions tab and select the GB&SMITH 360Vers extension in the list (checkbox).

4. Click on Save or Save & Close.

The Webi extension is configured and ready for use.

Chapter 3. Application configuration 17

 360Suite Installation Guide

Chapter 4. Accessing 360Suite

Following installation, product initialization and license key registration:
Open a compatible web browser (e.g.: Google Chrome, Mozilla Firefox, IE 11, etc.) and enter the URL to your 360Suite
deployment and log in to 360Suite using valid SAP BusinessObjects CMS information and user credentials:

http://<server>:<port>/360.suite/

Chapter 4. Accessing 360Suite 18

 360Suite Installation Guide

Chapter 5. 360Suite update

1. Application update
Procedure
Follow the instructions below to update an existing 360Suite installation:

WARNING
The Apache Tomcat server running the 360Suite application (or the 360Suite service) MUST be stopped
BEFORE proceeding to the update.

Tip
If a previous 360Suite installation is detected, "Basic Install / Update" is the only available option. The full
installation option is therefore greyed out. If you wish to perform a full setup again, uninstall the application
and run the installer again, then select "Full installation" mode.

1. Download the installation archive from GB&SMITH's support site

2. Extract the downloaded ZIP file to a local folder (e.g.: on the Windows desktop).

3. Run (as administrator) 360Suite-bi<BO_version>-v<version>.exe

4. The installation wizard opens. Select "Basic Install / Update", then click on "Next" to continue.

5. Specify the path to the locations that contain the following dependencies:

• SAP BusinessObjects (standard CMS setup, not BOBJ web-tier) libraries location (files stored in
%programfiles[(x86)]%\SAP Business Objects\SAP BusinessObjects Enterprise XI 4.0\java\lib).

• WebiAdmin tool libraries (usually stored in %programfiles[(x86)]%\SAP Business Objects\SAP

BusinessObjects Enterprise XI 4.0\java\apps\WebiAdminTool).

• Optional (if installing 360Univ): Select the "Import SL SDK" option and specify the appropriate location (usually
%programfiles[(x86)]%\SAP Business Objects\SAP BusinessObjects Enterprise XI 4.0\SL SDK).

6. Specify the path to the JDBC driver and select the 360Suite installation location and click on "Next".

7. The installer displays the pre-installation summary. Click on "Install" to proceed.

Once done, the Apache Tomcat or the Tomcat 360Suite service can be restarted.

2. 360Probe agent update

Chapter 5. 360Suite update 19

 360Suite Installation Guide

2.1. 360Probe agent update

Procedure
The 360Probe agent should be updated manually when deploying a new 360Suite version. This procedure ensures proper
compatibility between the main application and the Probe agent. If updating the Probe agent may not be required when
installing minor versions or fixes, this operation is still recommended for stability and communication reliability (360Suite
and 360Probe agent versions should match).
1. Terminate any running 360Probe agent to update.
2. Delete the existing 360.suite.probe-<version>.jar, 360probe.bat and 360probe_debug.bat files in the 360Probe
agent deployment location.

CAUTION
Make sure NOT TO DELETE the ssl_configurations.properties file nor any keystore and/or
truststore file that may be stored in the 360Probe agent directory.

3. Copy the 360.suite.probe-<version>.jar, 360probe.bat and 360probe_debug.bat files (available in the archive
probe directory) to the existing 360Probe agent deployment location.

4. Restart the 360Probe agent by running 360probe.bat (on Microsoft Windows) or the following command (see
command line parameters reference for details):

java -jar -Xmx128m [-Dhttps.protocols=TLSv1.1,TLSv1.2] 360.suite.probe-<version>.jar [params]

Chapter 5. 360Suite update 20

 360Suite Installation Guide

Appendix A. Special case: Basic installation

The installer provides a Basic Install / Update option. If using this mode at first installation time, only the web application
and BO libraries are copied to the user-specified location.

WARNING
The Apache Tomcat server running the 360Suite application (or the 360Suite service) MUST be stopped
BEFORE proceeding to the update.

This option allows deploying 360Suite on an already existing (custom) Apache Tomcat server without installing the server
and database engine provided by GB&SMITH:
1. Specify the path to the locations that contain the following dependencies:
• SAP BusinessObjects (standard CMS setup, not BOBJ web-tier) libraries location (files stored in
%programfiles[(x86)]%\SAP Business Objects\SAP BusinessObjects Enterprise XI 4.0\java\lib).

• WebiAdmin tool libraries (usually stored in %programfiles[(x86)]%\SAP Business Objects\SAP

BusinessObjects Enterprise XI 4.0\java\apps\WebiAdminTool).

• Optional (if installing 360Univ): Select the "Import SL SDK" option and specify the appropriate location (usually
%programfiles[(x86)]%\SAP Business Objects\SAP BusinessObjects Enterprise XI 4.0\SL SDK).

2. Specify the path to the JDBC driver (.jar file) 360Suite will be using.
3. Specify the path to the appropriate <Tomcat>\webapps location corresponding to the already existing Apache
Tomcat server (or <Tomcat>\<path_to_360Suite>).

Important
The same path must be specified again when later updating the application. If not, the installer will perform
a fresh installation and may not update the existing one. Therefore, make sure to specify the custom path
used at initial installation time before proceeding to updates.

4. The installer displays the pre-installation summary. Click on "Install" to proceed.

Once the installation complete, the application can be configured.

Appendix A. Special case: Basic installation 21

 360Suite Installation Guide

Appendix B. JDBC URL reference

The table below lists per-database JDBC URI schemes as required for accessing each database from 360Suite:

MySQL jdbc:mysql://<server>:<port>/<database_name>

Oracle jdbc:oracle:thin:@<server>:<port>:<database_name> or
jdbc:oracle:thin:@<server>:<port>/<service_name>

PostgreSQL jdbc:postgresql://<server>:<port>/<database_name>

SQL Server jdbc:sqlserver://

<server>:<port>;databaseName=<database_name>[;integratedSecurity=true]

SQL Server with jTDS jdbc:jtds:sqlserver://<server>:<port>/<database_name>[;useNTLMv2=true]

[;domain=<domain_name>]

1. SQL Server - Integrated Windows authentication configuration

Procedure
A specific configuration is required in order to connect 360Suite to a SQL Server database using Integrated Windows
Authentication (Single Sign-On).

Follow the instructions below to configure the 360Suite Apache Tomcat server and the application:

1. Stop the Apache Tomcat server (or 360Suite service).

2. Create a setenv.bat file (if it does not already exist) in the <Tomcat>\bin folder, then add the following line:

set CATALINA_OPTS=%CATALINA_OPTS% -Djava.library.path=<path_to_DLL_file>

Important
The DLL file (sqljdbc_auth.dll) is provided as part of the SQL Server JDBC driver version 6.2
package. Make sure that the -Djava.library.path parameter points to the appropriate driver for the
deployment and JVM architecture. Depending on the case, specify one of the following locations:

• 32-bit (x86): <Microsoft JDBC Driver>\sqljdbc\enu\auth\x86

• 64-bit (x64): <Microsoft JDBC Driver>\sqljdbc\enu\auth\x64

3. Save the previously created and edited file.

4. Restart the Apache Tomcat server (or 360Suite service).

5. Access the 360Suite Administration Console:

http://<server>[:<port>]/360.suite/admin

6. In the "Database configuration" block, configure as follows:

• Database: SQL Server (then, select the appropriate version).

• URL:

jdbc:sqlserver://<server>:<port>;databaseName=<database_name>;integratedSecurity=true

• Windows Authentication: Selected.

• Advanced configuration: Not selected.

7. Click on "Save".

The new configuration is immediately applied. If the application does not return any error, click on the "Close" button to
exit the Administration Console.

Appendix B. JDBC URL reference 22

 360Suite Installation Guide

2. SQL Server - Windows authentication configuration using jTDS

Procedure
A specific configuration is required in order to connect 360Suite to a SQL Server database using Windows Authentication
via jTDS.
Follow the instructions below to configure the 360Suite Apache Tomcat server and the application:
1. Stop the Apache Tomcat server (or 360Suite service).
2. Add the following line to the Apache Tomcat Java options:

-Djava.library.path=<path_to_DLL_file>

Important
The DLL file (ntlmauth.dll) is provided as part of the jTDS driver version 1.3.1 package. Make sure that
the -Djava.library.path parameter points to the appropriate driver for the deployment and JVM
architecture. Depending on the case, specify one of the following locations:

• 32-bit (x86): <jTDS>\x86\SSO

• 64-bit (x64): <jTDS>\x64\SSO

3. Restart the Apache Tomcat server (or 360Suite service).

4. Access the 360Suite Administration Console:

http://<server>[:<port>]/360.suite/admin

5. In the "Database configuration" block, configure as follows:

• Database: SQL Server (then, select the appropriate version).
• URL:

jdbc:jtds:sqlserver://<server>:<port>/<database_name>;useNTLMv2=true;domain=<domain_name>

• Windows Authentication: Selected.

• Advanced configuration: Not selected.
6. Click on "Save".
The new configuration is immediately applied. If the application does not return any error, click on the "Close" button to
exit the Administration Console.

Appendix B. JDBC URL reference 23

 360Suite Installation Guide

Appendix C. Single Sign-on setup and configuration

1. Trusted SSO Authentication configuration

Procedure
To use Single Sign-on Trusted Authentication with 360Suite, follow the instructions below.

1. Deploy the 360Suite application following the procedures described in the installation section.

2. On the CMC Home page, click on "Authentication" ("Manage" section), then, double-click on "Enterprise" to open
the authentication mode properties.

3. Select the "Trusted Authentication is enabled" option.

Figure C-1. Enterprise authentication properties

4. Click on the "New Shared Secret" button to generate the secret.

WARNING
This operation destroys the existing secret. Click on this button ONLY IF the shared secret should be
created OR updated/renewed.

5. Click on the "Download Shared Secret" button and save the file as TrustedPrincipal.conf (this name is
mandatory).

6. Click on "Update" to save the configuration changes.

7. Copy TrustedPrincipal.conf to <360Suite_install_dir>\WEB-INF\conf

8. Access the 360Suite Administration Console, then "Technical settings" tab > "SSO preferences" and configure
the application:

a. Select the "Enable SSO" option.

b. Specify the CMS environment.

c. Select the "Trusted" mode.

d. Select the appropriate retrieval method, then, specify the shared secret as exported in
TrustedPrincipal.conf.

e. Click on "Save".

2. Active Directory SSO authentication configuration

Procedure
To use Active Directory Single Sign-on Authentication with 360Suite, follow the instructions below.

1. Deploy the 360Suite application following the procedures described in the installation section.

2. Edit the appropriate file according to your configuration (AD SSO Keytab or AD SSO Password):

• SSO Keytab:

a. Open the <Tomcat>\webapps\360.suite\WEB-INF\ad_sso_keytab\web.xml file in an editor (e.g.: vim,

NotePad++, etc.).

Appendix C. Single Sign-on setup and configuration 24

 360Suite Installation Guide

b. Edit line number 132 and add the principal name between the <param-value> tags (idm.princ parameter
in the BOE application SSO configuration).
c. Edit line number 144 and add the path to the keytab file between the <param-value> tags (idm.keytab
parameter in the BOE application SSO configuration).
d. Save the changes and exit the editor.
e. Copy the edited web.xml file to <Tomcat>\webapps\360.suite\WEB-INF (overwrite the existing file).
f. Configure Admin Tool and restart the Apache Tomcat server.
• SSO Password:
a. Open the <Tomcat>\webapps\360.suite\WEB-INF\ad_sso_password\web.xml file in an editor (e.g.: vim,
NotePad++, etc.).
b. Edit line number 128 and add the Active Directory domain name between the <param-value> tags
(idm.realm parameter in the BOE application SSO configuration).
c. Edit line number 132 and add the principal name between the <param-value> tags (idm.princ parameter
in the BOE application SSO configuration).
d. Edit line number 144 and add the principal password between the <param-value> tags.
e. Save the changes and exit the editor.
f. Copy the edited web.xml file to <Tomcat>\webapps\360.suite\WEB-INF (overwrite the existing file).
g. Configure Admin Tool and restart the Apache Tomcat server.
3. Access the 360Suite Administration Console, then "Technical settings" tab > "SSO preferences" and configure
the application:
a. Select the "Enable SSO" option.
b. Specify the CMS environment.
c. Select the "AD" mode.
d. Click on "Save".

Appendix C. Single Sign-on setup and configuration 25

 360Suite Installation Guide

Appendix D. Installer options

The table below lists all the options available in the installer.
Table D-1. Options and available installation-time settings

Option Description Related / Dependent options

Full installation Installs the web application and its • Install Tomcat: Enabled by default. Installs the
dependencies (Apache Tomcat, provided Apache Tomcat server as a system service
PostgreSQL, platform-dependent (can be customized by editing the Service/Display
libraries), copies the SAP BO name and description fields).
SDK libraries and, if applicable, a
• Specify Tomcat User: Disabled by default. Allows
third-party JDBC driver.
specifying the user the Tomcat server will be run as
(by default: Local System). Specify a valid user name
and password (existing user account).
• Install PostgreSQL: Enabled by default. Installs the
provided SQL server and database engine. Specify
the installation folder (default: <drive>\PostgreSQL),
the server port (default: 5432), Super account name
(default: postgre) and password.
• Location of the BO libraries folder: MANDATORY.
Specify the path to the SAP BO SDK libraries (please
refer to installation procedure).
• Location of JDBC Driver: optional. If using a database
engine other than the provided PostgreSQL, specify
the path to the corresponding driver file (.jar).
• Destination location: Use the default installation folder
if installing the provided Tomcat server (or specify
to the appropriate <Tomcat>\webapps deployment
directory if using an existing Tomcat server).

Basic Installation / Installs or update the web • Location of the BO libraries folder: MANDATORY.
Update application only and copies, Specify the path to the SAP BO SDK libraries (please
when required, the SAP BO SDK refer to installation procedure).
libraries and, if applicable, a third-
• Location of JDBC Driver: optional. If using a database
party JDBC driver.
engine other than the provided PostgreSQL, specify
the path to the corresponding driver file (.jar).
• Destination location: Use the default installation folder
if installing the provided Tomcat server (or specify
to the appropriate <Tomcat>\webapps deployment
directory if using an existing Tomcat server).

Appendix D. Installer options 26