Java Web Start Installation Guide - help.sap.com

CUSTOMER

SAP BusinessObjects Predictive Analytics 3.12017-10-26

Java Web Start Installation GuideSetting-up Multiple Instances

Content

1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.1 General Multiple Installation Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Installing SAP BusinessObjects Predictive Analytics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.1 Server Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.2 Client Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 Configuring the Application Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.1 Managing Your Software License(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3.2 Log Files Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Configuring the Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

4 Microsoft Windows Application Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84.1 Configuring the Service Ports and Starting the Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

To Configure the CORBA Name Service Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

To Configure the Authenticated Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Starting the Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

5 Microsoft Windows Service Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105.1 Configuring the Service Ports and Registering the Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

To Configure the CORBA Name Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

To Configure the Authenticated Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

To Register the Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

6 UNIX Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126.1 To Configure the Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

7 Connecting to the Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137.1 On MS-Windows Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

To Configure the Remote Assistant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

To Configure the Control Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

7.2 On UNIX Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

To Configure the Remote Assistant and the Control Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

8 Setting Multiple Java Web Start Launchers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168.1 JNLP Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Configuring the SAP Java Web Start Launchers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

8.2 Web Server Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2 C U S T O M E RJava Web Start Installation Guide

Content

1 Overview

A standard SAP BusinessObjects Predictive Analytics installation contains the following components:

● The client application● The server application itself composed of:

○ The CORBA Name service (the default port is 12345)○ The application authenticated server (the default port is 12347)

● The Java Web Start launcher, that requires a Web server to be operational (the default port is 80).

You can have several versions of the application server running simultaneously, for example:

● To test the latest version of the application without impacting the current production environment.● To use a feature of version Y when it is not possible to change the current version X (thus to have both X

and Y running at the same time).

This guide provides the steps to configure the system in order to run several SAP BusinessObjects Predictive Analytics servers simultaneously.

For simplicity reasons, this documentation is based on a clear-cut example to clarify the different concepts and steps.

It is, however, relatively simple to use as a basis for installing more than two versions of the application server.

1.1 General Multiple Installation Architecture

This demonstration scenario shows SAP BusinessObjects Predictive Analytics version 2.0 and SAP InfiniteInsight version 6.1.0 running at the same time on a UNIX server.

The UNIX Server is running Apache HTTP Server.

The application Authenticated servers will be accessed through the application Java Web Start launcher.

Java Web Start Installation GuideOverview C U S T O M E R 3

The server architecture is the following:

NotePlease ensure the different services receive connections on different port numbers, in order to avoid dysfunctions.

It is also necessary to have two web URLs setup for the application Web Start launchers, one for each application version.


Overview

2 Installing SAP BusinessObjects Predictive Analytics

This section provides guidance for the specific case of installing and configuring multiple versions of the application.

For further details on how to install the application server, please refer to the SAP BusinessObjects Predictive Analytics Java Web Start Installation Guide. It provides information on further aspects of the installation process that will not be repeated in this document.

2.1 Server Side

The installation process does not differ from a normal installation. Please check the SAP BusinessObjects Predictive Analytics Java Web Start Installation Guide to guide you through the different steps.

On Microsoft Windows, you must choose between installing the application as a Windows service or as a standard application:

● On a test environment, the software may be installed as a standard application.● It is recommended to install the application as a Windows service on a production environment.

2.2 Client Side

There are two possibilities for the client machines:

● Install the client application in order to connect to the server. If you choose to install the client application, please refer to the Client Installation Guide.

● Use a Web browser to connect to the Java Web Start launcher deployed on the server.

NoteUsing a web browser is the recommended mode if several users need to connect to the application server. It allows simplifying the configuration and update processes (only the server needs to be configured).

Java Web Start Installation GuideInstalling SAP BusinessObjects Predictive Analytics C U S T O M E R 5

3 Configuring the Application Server

This section describes the configuration steps to have two versions of the application server running simultaneously. For each server, the configuration will cover the following elements:

● License files● Connection ports● Log files● Java Web Start files

3.1 Managing Your Software License(s)

Ensure that the configuration files point to the right licenses. In case of problems using one of the servers, check if the license configuration is correct.

3.2 Log Files Configuration

After configuring the Windows services and the application server port numbers, it is necessary to make sure the different application servers will not write their outputs in the same log files. This would make them particularly difficult to read.

The default file describing the log policy of the application servers is named logconf.txt.

3.2.1 Configuring the Log Files

The file logconf.txt is located in AuthServer. This file has the two following log file names declared.

Root.Directory $KXTEMPDIR Root.Filename kxen_auth_log.txt...Usage.Directory $KXTEMPDIR Usage.Filename kxenusagelog.txt

Authenticated servers use two different log entries:

● The Root entries are used for tracing the activity of the server which can later be used for debugging purposes.

● The Usage entries are sparser and report a more global view of the activity on the server. They consist of one line per event on the following events: user connection, user disconnection, training a model, applying a model, saving a model.


Configuring the Application Server

For the demonstration scenario used in this documentation we chose to change the name of the files so that the log files remain located in the same folder under different names.

So we get two logconfig.txt files, one for each software version/install, in the following directories:

● C:\Program Files\SAP InfiniteInsight\InfiniteInsightV <version>\EXE\Servers\AuthServer

● C:\Program Files\SAP BusinessObjects Predictive Analytics\Server <version>\EXE\Servers\AuthServer

For clarity, rename the log files in the respective logconfig.txt files. In this example, the logconfig.txt file for SAP InfiniteInsight v6.1.0 was edited to reflect the following changes:

Root.Filename kxen_610_auth_log.txt ...Usage.Filename kxen_610_usagelog.txt

The logconfig.txt file for SAP BusinessObjects Predictive Analytics was edited to reflect the following changes:

Root.Filename pa_20_auth_log.txt ... Usage.Filename pa_20_usagelog.txt

Java Web Start Installation GuideConfiguring the Application Server C U S T O M E R 7

4 Microsoft Windows Application Mode

The schema below provides a partial view of the installation folders on a Microsoft Windows platform. It shows the files that need to be configured in order to run multiple application versions simultaneously.

Please use it as a reference to retrieve the files mentioned in the procedure steps below

NoteEach server must run on a different port number. If necessary, edit the configuration in order to allocate the right port numbers to the different services before launching the applications.

4.1 Configuring the Service Ports and Starting the Server

Do the following:

● Configure the CORBA Named Service Port● Configure the Authenticated Server Port● Start the server


Microsoft Windows Application Mode

4.1.1 To Configure the CORBA Name Service Port

When you run more than one installation, you must make sure that each installation uses a unique CORBA Name Service port.

1. For each installation, open the file nameserv.bat (in the <application_server_folder>\EXE\Namesrv folder).

2. For each installation, edit the line set NS_PORT=12345 to set a different (unique) number. For example: set NS_PORT=12445. Note that it is possible to enter any free port number here.

Your different applications should use different CORBA Named Service port numbers. Our example uses the following:

Installation CORBA Name Service Port

SAP BusinessObjects Predictive Analytics 2.0 set NS_PORT=12345

InfiniteInsight v6.1.0 set NS_PORT=12445

4.1.2 To Configure the Authenticated Server

When you run more than one version of the application, you must make sure that each installation uses a unique authenticated server port.

1. For each installation, open the runserver.bat file (in the <application_server_folder>\Servers\AuthServer folder).

2. For each installation, edit the line set KXEN_PORT=12347 to set a different (unique) number. For example: set KXEN_PORT=12447. Note that it is possible to enter any free port number here.

3. Edit the line set NS_PORT=12345 so that it matches the line in the nameserv.bat file described in step 2 of the procedure To Configure the CORBA Name Service Port.

4.1.3 Starting the Servers

For each version of the software you are running, do the following:

1. Double-click the file namesrv.bat to start the CORBA name server.

2. Run the script corresponding to your configuration: double-click the file runserver.bat to start the authenticated server.

Java Web Start Installation GuideMicrosoft Windows Application Mode C U S T O M E R 9

5 Microsoft Windows Service Mode

The SAP BusinessObjects Predictive Analytics Windows Services are registered under the following names:

SAP BusinessObjects Predictive Analytics Directory (v<version number>) for the CORBA Name Service.

SAP BusinessObjects Predictive Analytics - Automated Analytics Server (v<version number>) for the Server.

5.1 Configuring the Service Ports and Registering the Services

For each version of the application you are running, do the following:

● Configure the CORBA Named Service Port● Configure the Authenticated Server Port● Register the Services

5.1.1 To Configure the CORBA Name Service


1. Open the file KxRegisterNameService.bat.

2. Edit the line set NS_PORT=12345 so that the port number used is unique in your installation. For example, set NS_PORT=12445 (you may enter any free port number here).

5.1.2 To Configure the Authenticated Server


1. Open the file KxRegisterAuthService.bat.

2. Edit the line set KXEN_PORT=12347 so that the port number used is unique in your installation. For example, set KXEN_PORT=12447(you may enter any free port number here).

3. For each application, edit the line set NS_PORT=12345 so that it matches the value used in the corresponding KxRegisterNameService.bat file (use the port number of step 2 of the procedure To Configure the CORBA Name Service).


Microsoft Windows Service Mode

5.1.3 To Register the Services


1. In the NameSrv folder, double-click the file KxRegisterNameService.bat to run it.

2. In the AuthServer folder, double-click the file KxRegisterAuthService.bat to run it.

Java Web Start Installation GuideMicrosoft Windows Service Mode C U S T O M E R 11

6 UNIX Services

This document is aimed at system administrators, therefore it does not provide detailed information on how to install daemons on the system. It will focus on the configuration of the port numbers used by SAP BusinessObjects Predictive Analytics services.

The required files are located at the root of the application installation folder:

● KxenCorbaConfig.sh: that controls the port numbers used by SAP InfiniteInsight ® .● KxenServer_initd: that may be helpful to install a daemon. The script is commented and only requires

setting the KXEN_INSTALLATION_PATH variable, do not hesitate to refer to it.

The schema below provides a partial view of the installation folder of the application on a UNIX platform. It shows the files that need to be configured in order to run multiple application versions simultaneously.

Please use it as a reference to retrieve the files mentioned in the procedure steps below:

6.1 To Configure the Services


1. Open the file KxenCorbaConfig.sh.

2. Replace the line NS_PORT=12345 by NS_PORT=12445(It is possible to enter any free port number here).

3. To configure Authenticated Server, replace the line KXEN_AUTH_PORT=12347 by KXEN_AUTH_PORT=12447 (It is possible to enter any free port number here).


UNIX Services

7 Connecting to the Server

If you have installed the SAP BusinessObjects Predictive Analytics Remote Assistant on a computer, to connect to the server you need to edit its configuration so it can connect to the server. These changes must be done on all the computers on which the remote assistant is installed

NoteWe recommend you to connect to the SAP BusinessObjects Predictive Analytics Server via the SAP BusinessObjects Predictive Analytics Java Web Start launcher. With this option, only the host server needs to be configured. All the client machines retrieve the right configuration thanks to the Java Web Start launcher.

7.1 On MS-Windows Platforms

The diagram below provides a partial view of the installation folder of the application on a Microsoft Windows client-machine. It shows the files that need to be configured so the Remote Assistant can connect to a custom server.

Please use it as a reference to retrieve the files mentioned in the procedure steps.

Java Web Start Installation GuideConnecting to the Server C U S T O M E R 13

7.1.1 To Configure the Remote Assistant

1. Open the file KJWizardCorba.ini.2. Edit the line arg.x=12345 to match the port number of step 2 of the procedure To Configure the CORBA

Name Service described in section Ms-Windows Services.3. Click Programs > SAP Business Intelligence > SAP Predictive Analytics

Server>Remote Assistant 2.0 to connect to the application server.

7.1.2 To Configure the Control Panel

1. Open the file KxControlPanel.ini.

2. Edit the line arg.x=12345 to match the port number of step 2 of the procedure To Configure the CORBA Name Service described in section Ms-Windows Services).

3. Click Programs > SAP Business Intelligence > SAP Predictive Analytics Server>Control Pane 2.0 to connect to the server.

7.2 On UNIX Platforms

The diagram below provides a partial view of the installation folder of the application on a UNIX client-machine. It shows the files that need to be configured so the Remote Assistant can connect to a custom server.

By default the file KxenCorbaConfig.sh contains the configuration for the port numbers. If you have already configured this file, the Remote Assistant should access the server correctly.


Connecting to the Server

If you have not configured it yet, please follow the procedure.

7.2.1 To Configure the Remote Assistant and the Control Panel

1. Edit the file KxenCorbaConfig.sh.

2. Edit the line NS_PORT=12345 so that it matches the port number of step 2 of the procedure To Configure the KXEN Services described in section UNIX Services. We recommend making a copy of the file before editing it.

3. To start the Remote Assistant and connect to the server, run the following command: $ KJWizardCORBA/KJWizardCORBA.sh

4. To start the Control Panel and connect to the server, run the following command:$ KJWizardCORBA/KxControlPanel.sh

Java Web Start Installation GuideConnecting to the Server C U S T O M E R 15

8 Setting Multiple Java Web Start Launchers

Once have successfully configured and started the services, you need to configure the Java Web Start launcher so that the remote computers can access the servers by simply connecting to a given URL and clicking the Start SAP Predictive Analytics button.

The easiest way to achieve this is by deploying each Java Web Start launcher on a different web context, for instance: make SAP Predictive Analytics 2.0 accessible from http://host/PA_20/ and SAP InfiniteInsight ® version 6.1.0 from http://host/KXEN_610/.

8.1 JNLP Files

For each SAP BusinessObjects Predictive Analytics version you need to deploy, you must configure the Java Web Start launcher related to it. Depending on whether you are running an authenticated server or not, you will have to edit respectively two files or one file.

This chapter only details the settings needed to run multiple SAP BusinessObjects Predictive Analytics versions. For information on the installation of the Web Start launcher and on the configuration of the Web server refer to the Java Web Start Installation Guide for Windows or UNIX.

The following JNLP files need to be edited:

● KJWizard_auth.jnlp: used to connect to an SAP Predictive Analytics Server.● KxAdminConsole.jnlp: used to control the connections to the server.


Setting Multiple Java Web Start Launchers

For Windows platforms, they are located in the following directory:

For UNIX platforms, they are located in the following directory:

There are three parameters of the JNLP files that need to be edited to correspond to the settings of your server:

● The codebase: indicates where the Java Web Start Launcher is deployed.● The ORBInitialPort: indicates which port the server is listening to.● The ORBInitialHost: indicates the host on which the server is deployed.

Java Web Start Installation GuideSetting Multiple Java Web Start Launchers C U S T O M E R 17

Typical JNLP file structure:

<?xml version="1.0" encoding="UTF-8"?><jnlp spec="1.0+" codebase="http://localhost/KXEN/" href="xxx.jnlp"> … <argument>-ORBInitialPort</argument> <argument>12345</argument> <argument>-ORBInitialHost</argument> <argument>localhost</argument> …

For the demonstration scenario used in this documentation, we need two Java Web Start Launchers, one for each software version.

8.1.1 Configuring the SAP Java Web Start Launchers

The example below shows the changes made on the files KJWizard_auth.jnlp and KxAdminConsole.jnlp for SAP BusinessObjects Predictive Analytics:

<?xml version="1.0" encoding="UTF-8"?><jnlp spec="1.0+" codebase="http://host/PA_20/" href="xxx.jnlp"> … <argument>-ORBInitialPort</argument> <argument>12345</argument> <argument>-ORBInitialHost</argument> <argument>host</argument> …

NotePlease ensure to make these changes on both files.

The example below shows the changes made on the files KJWizard_auth.jnlp and KxAdminConsole.jnlp for SAP InfiniteInsight ® version 6.1.0:

<?xml version="1.0" encoding="UTF-8"?><jnlp spec="1.0+" codebase="http://host/KXEN_610/" href="xxx.jnlp"> … <argument>-ORBInitialPort</argument> <argument>12445</argument> <argument>-ORBInitialHost</argument> <argument>host</argument> …

NotePlease ensure to make these changes on both files.


Setting Multiple Java Web Start Launchers

8.2 Web Server Mapping

The last step is to ensure that the web server has been set to reflect the right mapping between the SAP BusinessObjects Predictive Analytics installation folders and the web URLs.

For Apache HTTP, the configuration used for this demonstration scenario is the following:

# # THIS SECTION DEFINES THE HTTP CONFIGURATION TO PUBLISH KXEN VIA WEBSTART#ALIAS /PA_20/KJWIZARD/ "/SOFTS/PA_V20/KJWIZARDCORBA/"ALIAS /PA_20/DOCUMENTATION/ "/SOFTS/PA_V20/DOC/"ALIAS /PA_20/ "/SOFTS/PA_20/WEBSTART/"<DIRECTORY "/SOFTS/PA_V20/">ORDER ALLOW,DENYALLOW FROM ALL</DIRECTORY>ALIAS /KXEN_610/KJWIZARD/ "/SOFTS/KXEN_V6_1_0/KJWIZARDCORBA/"ALIAS /KXEN_610/DOCUMENTATION/ "/SOFTS/KXEN_V6_1_0/DOC/"ALIAS /KXEN_610/ "/SOFTS/KXEN_V6_1_0/WEBSTART/"<DIRECTORY "/SOFTS/KXEN_V6_1_0/">ORDER ALLOW,DENYALLOW FROM ALL </DIRECTORY>

Once these steps are correctly followed, you can send an e-mail to the users providing them the URLs from which they can run the software.

NoteMake sure to specify which URL matches which software version.

Java Web Start Installation GuideSetting Multiple Java Web Start Launchers C U S T O M E R 19

Important Disclaimers and Legal Information

Coding SamplesAny software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.

AccessibilityThe information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral LanguageAs far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet HyperlinksThe SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: http://help.sap.com/disclaimer).


Important Disclaimers and Legal Information

http://help.sap.com/disclaimer/

Java Web Start Installation GuideImportant Disclaimers and Legal Information C U S T O M E R 21

go.sap.com/registration/contact.html

© 2017 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

https://go.sap.com/registration/contact.html

https://go.sap.com/registration/contact.html

http://www.sap.com/corporate-en/legal/copyright/index.epx

http://www.sap.com/corporate-en/legal/copyright/index.epx

Java Web Start Installation Guide - help.sap.com

Documents

Transcript of Java Web Start Installation Guide - help.sap.com