Also Available As

Installation Guide | PUBLIC Document Version: 1.0 – 2021-05-06

THE BEST RUN 2021 SAP SE or an SAP © Content

1 Introduction...... 7 1.1 About This Document...... 7 1.2 Audience...... 7 1.3 Product Name Abbreviations...... 7 1.4 References to Third-Party Software...... 8 1.5 SAP NetWeaver Administrator...... 8

2 Preparing to Install...... 9 2.1 Understanding the FS-PRO Modules...... 9 2.2 Understanding the FS-PRO Deployment Options...... 10 2.3 Required FS-IPW Version ...... 13 2.4 System Requirements for FS-QUO...... 13 Integrating with FS-PM...... 13 Removal of IBM WebSphere Application Server Support...... 13 Supported FS-PRO Version ...... 13 Supported Shell Software for FS-QUO...... 14 Server Requirements...... 14 Client Requirements for FS-QUO...... 18 Substitution Variable Placeholders...... 19

3 Installing and Configuring the Designer/Runtime Application...... 21 3.1 Downloading the Installation Files...... 21 3.2 Installing FS-QUO...... 22 Installing FS-QUO Using the Installation Wizard in GUI Mode...... 22 Installing FS-QUO Using the Installation Wizard in Console Mode...... 23 3.3 Configuring the Encryption Key...... 24 3.4 Creating the FS-QUO Database...... 25 Creating the FS-QUO Oracle Database Using the Database Creation Wizard in GUI Mode...... 25 Creating the FS-QUO Oracle Database Using the Database Creation Wizard in Console Mode ...... 27 Creating the FS-QUO Microsoft SQL Server database using the Database Creation Wizard in GUI Mode...... 28 Creating the FS-QUO Microsoft SQL Server database using the Database Creation Wizard in Console Mode...... 29 Creating the FS-QUO SAP HANA Database Using the Database Creation Wizard in GUI Mode ...... 31 Creating the FS-QUO SAP HANA Database Using the Database Creation Wizard in Console Mode...... 32

Installation Guide 2 PUBLIC Content Creating the FS-QUO IBM DB2 database using the Database Creation Wizard in GUI Mode...... 33 Creating the FS-QUO IBM DB2 database using the Database Creation Wizard in Console Mode ...... 34 3.5 Configuring the NetWeaver Instance...... 35 Configuring the Java Settings...... 35 Configuring SSL and Enabling HTTPS on NetWeaver...... 36 Increasing the P4 Request Size Limit...... 37 Increasing the HTTP Service Process Timeout...... 37 Adjusting the Content Filter of the HTTP Access Handler...... 38 Increasing the Severity Level of the System.out and System.err Tracing Locations...... 39 Configuring the HttpOnly Flag...... 40 3.6 Configuring Database Settings in NetWeaver...... 41 Configuring Oracle Settings in NetWeaver...... 41 Configuring Microsoft SQL Server Settings in NetWeaver...... 43 Configuring SAP HANA Settings in NetWeaver...... 44 Configuring IBM DB2 Settings in NetWeaver...... 46 3.7 Disabling Heavy Resource Loading...... 48 3.8 Deploying the FS-QUO SCA...... 48 Deploying the SCA Using Telnet...... 49 Deploying the SCA Using SUM...... 50 3.9 Customizing the FS-QUO Installation...... 51 Logging In to the Administrative Console...... 51 Configuring the System Environment...... 52 3.10 Verifying the FS-QUO Installation...... 55 3.11 Locking Down a Production Environment...... 55

4 Loading FS-QUO Contents into Product Configurator...... 57 4.1 Uploading the Custom Stem Classes...... 57 4.2 Updating Objects and Loading Data for Underwriting in the Product Configurator Database...... 58 Updating the Oracle Database for the Product Configurator Using the Database Update Wizard in GUI Mode...... 58 Updating the Oracle Database for the Product Configurator Using the Database Update Wizard in Console Mode...... 60 Updating the Microsoft SQL Server Database for the Product Configurator Using the Database Update Wizard in GUI Mode...... 61 Updating the Microsoft SQL Server Database for the Product Configurator Using the Database Update Wizard in Console Mode...... 62 Updating the SAP HANA Database for the Product Configurator Using the Database Update Wizard in GUI Mode...... 64 Updating the SAP HANA Database for the Product Configurator Using the Database Update Wizard in Console Mode...... 65 Updating the IBM DB2 Database for the Product Configurator Using the Database Update Wizard in GUI Mode...... 66

Installation Guide Content PUBLIC 3 Updating the IBM DB2 Database for the Product Configurator Using the Database Update Wizard in Console Mode...... 68

5 Setting Up the Line of Business Bootstrap Products...... 70 5.1 Configuring the Commercial PnC Bootstrap...... 70 Importing the Commercial PnC Bootstrap Products...... 70 Setting Up Publish Manager in the Product Configurator Administrative Console for the Commercial PnC Bootstrap...... 72 Building the Imported Commercial PnC Bootstrap Products...... 74 Updating the Commercial PnC Bootstrap Product Selection...... 75 Publishing and Deploying Imported Commercial PnC Bootstrap Products Into the Designer/ Runtime Instance...... 76 5.2 Configuring the Personal Lines of Business (LoBs) Bootstrap...... 76 Importing the Personal LoB Bootstrap Products in a Production Environment...... 77 Importing Sample LoB Products in a Sandbox Environment...... 79 Setting Up Publish Manager in Product Configurator Administrative Console for the Personal LoB Bootstrap...... 81 Building and Publishing the Data Models for the Personal LoB Bootstrap...... 83 Building the Imported Personal LoB Bootstrap Products...... 84 Updating the Personal LoB Bootstrap Product Selection (Sandbox Environment Only)...... 86 Publishing the Imported Personal LoB Bootstrap Products...... 87

6 Configuring the Designer and Runtime Environments for Underwriting...... 89 6.1 Creating JMS Resources for the Integration Framework (IFW)...... 89 6.2 Installing the FS-QUO Application...... 90 6.3 Updating Configuration Settings...... 92 6.4 Importing Flowlet Groups in Designer...... 93 6.5 Importing and Deploying the Scheme...... 95 6.6 Building Imported Flowlets with the BatchFlowBuildServlet Tool...... 96 6.7 Synchronizing Product Flowstores...... 97 6.8 Updating Objects and Loading Data for Underwriting in the Designer Runtime Environment...... 98 Updating the Oracle Database Using the Database Update Wizard in GUI Mode...... 98 Updating the Oracle Database Using the Database Update Wizard in Console Mode...... 99 Updating the SAP HANA Database Using the Database Update Wizard in GUI Mode...... 100 Updating the SAP HANA Database Using the Database Update Wizard in Console Mode...... 102 Updating the Microsoft SQL Server Database Using the Database Update Wizard in GUI Mode ...... 103 Updating the Microsoft SQL Server Database Using the Database Update Wizard in Console Mode...... 104 Updating the IBM DB2 Database Using the Database Update Wizard in GUI Mode...... 105 Updating the IBM DB2 Database Using the Database Update Wizard in Console Mode...... 106 6.9 Pre-Loading Products Into Memory...... 107 6.10 Validating the Installation...... 109

Installation Guide 4 PUBLIC Content 7 Integrating with FS-IPW...... 110 7.1 Configuring the Virus Scan Interface (VSI)...... 110 7.2 Configuring SAP Mobile Documents as a CMS service...... 111 7.3 Configuring CMS settings for SAP Mobile Documents...... 111

8 Setting Up the Scheduler...... 113 8.1 Installing the Scheduler...... 113 8.2 Configuring the Scheduler...... 114 Encoding Security-Sensitive Information...... 114 Configuring the Scheduler Settings...... 115 8.3 Running the Scheduler...... 115 8.4 Shutting Down the Scheduler...... 116 8.5 Troubleshooting the Scheduler...... 116

9 Clustering...... 118 9.1 Prerequisites for Clustering...... 119 9.2 Checklist for Setting Up Clustering...... 119 Enabling a Shared CSI Home Directory...... 120 Configuring NetWeaver for FS-PRO or FS-QUO Clustering...... 120 Configuring the SAP Web Dispatcher...... 121 Configuring an Application Server for Clustering...... 122

10 Uninstalling FS-QUO...... 124 10.1 Undeploying the SCA...... 124 Undeploying the SCA Using Telnet...... 124 Undeploying the SCA Using SUM...... 125 10.2 Removing Related Configurations from NetWeaver...... 125 10.3 Deleting the FS-QUO Database...... 126 Deleting the FS-QUO Oracle Database in GUI Mode...... 126 Deleting the FS-QUO Oracle Database in Console Mode...... 127 Deleting the FS-QUO Microsoft SQL Server Database in GUI Mode...... 128 Deleting the FS-QUO Microsoft SQL Server Database in Console Mode...... 129 Deleting the FS-QUO SAP HANA Database in GUI Mode...... 130 Deleting the FS-QUO SAP HANA Database in Console Mode...... 131 Deleting the FS-QUO IBM DB2 Database in GUI Mode...... 132 Deleting the FS-QUO IBM DB2 Database in Console Mode...... 133 10.4 Uninstalling FS-QUO...... 135 Uninstalling FS-QUO Using the Wizard in GUI Mode...... 135 Uninstalling FS-QUO Using the Wizard in Console Mode...... 135

11 Installing ActiveMQ...... 137 11.1 Installing ActiveMQ on Windows...... 137 11.2 Installing ActiveMQ on UNIX...... 138

Installation Guide Content PUBLIC 5 12 Next Steps...... 140

Installation Guide 6 PUBLIC Content 1 Introduction

1.1 About This Document

This document contains instructions and guidance on how to install SAP Underwriting for Insurance (FS-QUO) on a server running Microsoft Windows-based or UNIX-based operating systems.

1.2 Audience

This guide is intended for application server administrators, database administrators (DBAs), and SAP Underwriting for Insurance developers.

1.3 Product Name Abbreviations

In the documentation, the products are also referred to by their abbreviations, as listed in the following table:

Product Name Abbreviations

Full Product Name Abbreviation Alias

SAP Product and Quotation FS-PQM n/a Management for Insurance

SAP Product Lifecycle Management for FS-PRO Product Configurator Insurance

SAP Underwriting for Insurance FS-QUO Designer

SAP Workplaces for Insurance FS-IPW n/a

SAP Policy Management FS-PM n/a

Installation Guide Introduction PUBLIC 7 1.4 References to Third-Party Software

To help you complete the installation procedures, this documentation describes the third-party software settings.

For up-to-date information, see the relevant SAP, IBM, Oracle and Microsoft documentation.

1.5 SAP NetWeaver Administrator

Use

SAP NetWeaver Administrator (NWA) is a Web-based framework tool for administration, configuration, and monitoring. It consists of respective integrated tools that help you to configure, administer, and monitor your SAP NetWeaver system, its components, and the applications running on top of it. You will be using the NWA throughout this guide for various configurations.

Prerequisites

1. To start NWA, go to the following URL: http://:/nwa , where: host Specifies the host where AS Java is installed. port Specifies the HTTP port of the Internet Communication Manager (ICM). It consists of 500 .

For example, if the Java instance number is 60 , the HTTP port is 56000.

Installation Guide 8 PUBLIC Introduction 2 Preparing to Install

2.1 Understanding the FS-PRO Modules

Before installing FS-PRO, you need to understand the different modules available and the main implementation scenarios available.

FS-PRO is composed of three different modules:

Insurance Allows insurance product managers, actuaries, and other related functions to design, Product configure and manage their insurance products, within a central, shared repository. Product Configurator Configurator lets the product manager do the following:

● Create customized products for specific markets ● Specify state, industry, and channel variations. ● Test product rules.

Product definitions are stored for reuse and reconfiguration in a product repository within Product Configurator. When Product Configurator is installed in NetWeaver, the following modules are automatically installed:

Administrative An administrative application that is used to configure and Console manage the system, application, and user profiles.

Product Configurator An application that is used to create and manage a catalog of insurance products.

Product Configurator also has a database module that requires database tables and objects to be installed.

Product Web Makes available the insurance product content to other insurance functions such as policy Services administration, claims management, agent portals, and other systems that make use of insurance product content. The Product Web Services deploys and manages insurance product interfaces. If this installation is intended to support third party systems, other than FS-QUO, to access product information, then you should also configure the optional Product Web Services module. This module allows the product information to be made available to consuming systems using standard SOAP-based web services. This module is optional. For a complete discussion of web services, see the SAP Underwriting for Insurance Integration Framework and Web Services Guide.

SAP Provides quotation, underwriting and policy administration functions to end users such as Underwriting insurance sales staff, underwriting and customer service representatives. This module is for Insurance optional.

Installation Guide Preparing to Install PUBLIC 9 There are three main implementation scenarios supported:

Standalone Product By implementing only the Insurance Product Configurator Module, an insurance Configurator carrier can manage their insurance products, generate specifications, or integrate the Product Configurator into their existing insurance systems.

Product Configurator By implementing the Insurance Product Configurator Module module and the and Product Web Product Web Services Module, an insurance carrier can manage products as in the Services scenario above, and can also manage the product services (for example, SOA Web Services) to integrate using modern XML-based approaches.

Product Configurator The typical scenario would be to implement the Insurance Product Configurator and SAP Underwriting Module and SAP Underwriting for Insurance Module, which would allow an for Insurance insurance carrier to configure their insurance product, and use those products to quote and write business.

2.2 Understanding the FS-PRO Deployment Options

The following diagrams illustrate a minimum and recommended deployment of the solution.

For a complete list of supported OS platforms and databases, refer to the Netweaver Product Availability Matrix. FS-PQM is supported on the same operating system platforms as NetWeaver. However, the FS-PQM database is only supported on IBM DB2, SAP HANA, Microsoft SQL Server, and Oracle.

Overview of a Minimal System Landscape Deployment for FS-PRO

The diagram below depicts the minimal system landscape for deployment. This approach is recommended for a prototype or early development environment.

Installation Guide 10 PUBLIC Preparing to Install In a minimal system landscape, one server hosts all application servers and databases. This includes the following items:

● One NetWeaver AS Java system (SID) where the FS-PRO component is deployed ● One NetWeaver AS Java system (SID) where the FS-QUO component is deployed ● One database that is shared by the NetWeaver AS Java systems and the FS-PRO and FS-QUO application databases, each of which is a separate schema or user ● For Oracle and SAP HANA, one database for the NetWeaver AS Java systems and the FS-PRO and FS-QUO schemas ● For Microsoft SQL Server and IBM DB2, one database for the NetWeaver AS Java systems and a separate database for the FS-PRO and FS-QUO schemas.

 Note

During NetWeaver AS Java installation users should select the Multiple Components, One Database (MCOD) option in this setup

Installation Guide Preparing to Install PUBLIC 11 For productive use, refer to the Recommended Deployment solution below, and ensure that sufficient database instances are installed to support each application server.

Overview of the Recommended System Landscape for FS-PRO

The diagram below depicts a recommended system landscape. This approach provides optimal performance and redundancy.

In a recommended system landscape, numerous servers are utilized for performance and redundancy. Typically it includes the following items, each hosted on a separate server:

● One NetWeaver AS Java system where the FS-PRO component is deployed ● One NetWeaver AS Java system where the FS-QUO component is deployed ● One database hosting the FS-PRO NetWeaver AS Java system schemas ● One database hosting the FS-QUO NetWeaver AS Java system schemas ● One database hosting the FS-PRO application database schemas ● One database hosting the FS-QUO application database schemas

Installation Guide 12 PUBLIC Preparing to Install For a productive environment, systems may also be clustered to support a higher workload.

2.3 Required FS-IPW Version

As part of your FS-QUO 4.0 SP06 installation process, you will need to install FS-IPW 2.0 SP05.

For more information, see the SAP Workplaces for Insurance Installation Guide

2.4 System Requirements for FS-QUO

Before you begin installing FS-QUO, you must ensure that all of the system requirements are satisfied.

2.4.1 Integrating with FS-PM

When integrating FS-QUO with FS-PM, Unicode must be enabled on FS-PM for successful integration.

For details on enabling Unicode refer to the FS-PM documentation.

2.4.2 Removal of IBM WebSphere Application Server Support

Beginning with FS-PQM 3.0, FS-PRO and FS-QUO now run only on SAP NetWeaver. IBM WebSphere Application Server is no longer supported.

2.4.3 Supported FS-PRO Version

You must install FS-PRO before installing FS-QUO.

There are some differences between the system requirements for FS-PRO and FS-QUO. Verify that your FS- PRO server meets the system requirements for FS-QUO.

Installation Guide Preparing to Install PUBLIC 13 2.4.4 Supported Shell Software for FS-QUO

The FS-QUO database installation and update wizards require that a POSIX-compliant shell be installed when run on a UNIX family.

The wizards have been tested on KornShell (ksh) and Bash shells.

2.4.5 Server Requirements

2.4.5.1 Operating System Requirements for FS-QUO

Ensure that the operating system requirements for FS-QUO are satisfied before beginning the installation process.

The system will support all current in-maintenance versions of the Windows operating systems, Linux (Red Hat and SUSE), Solaris and AIX provided that they are supported by the underlying NetWeaver platform with the latest updates installed.

 Note

Refer to the NetWeaver 7.5 SPS19 documentation for specific versions and service packs.

2.4.5.2 Java Runtime Environment (JRE) Requirements for FS-QUO

The FS-QUO installer requires a 64-bit Java Runtime Environment (JRE) 8.0.

The JAVA_HOME environment variable must be set to this JRE for the operating system user that the installer runs under. The JRE that comes with the SAP JVM 8 can be used, or the JRE can be downloaded from the Oracle website.

2.4.5.3 Database Requirements for FS-QUO

Ensure that you satisfy the database requirements before beginning.

The following database versions are certified and supported:

 Note

A certified version means that the database has been tested and verified. A supported version means any bugs identified are addressed but the database has not been tested and verified. The certified version is the recommended version.

Installation Guide 14 PUBLIC Preparing to Install SAP HANA

Certified Version: 2.0 SPS04

Notes: ● Increase the plan_cache_size config parameter from 2GB (default) to 8GB. If using the SAP HANA Studio, this can be found under the Configuration tab within indexserver.ini ● Disable Transparent Huge pages in the OS (Ref: SAP Note 2131662 ) ● For multitenant architecture, use a tenant container. Do not use the SYSTEMDB container to install the database. ● The Database Creation Wizard loads data into the database using TXT files. Disable the import path filter for the duration of the database creation by changing the config parameter enable_csv_import_path_filter value to false. If using the SAP HANA Studio, this can be found under the Configuration tab within indexserver.ini import_export

Oracle

Certified Version: 19c

Notes: Database parameters:

● Processes set to a minimum value of 300 ● Open Cursor = 1000 ● Cursor Sharing = Force ● Session Cached Cursors = 500 ● SGA set to a minimum of 500 MB ● PGA set to a minimum of 100 MB ● Database character set = AL32UTF8 ● National character set = AL16UTF16

If your Oracle 19c database is configured with multitenant database architecture, use a pluggable database for the FS-PRO database setup.

When Oracle is initially installed as part of the NetWeaver installation, the database and national character sets are set to UTF8. In a minimal landscape where FS-PRO and FS-QUO shares the same database with NetWeaver, UTF8 is supported with the caveat that Unicode characters of higher range consume considerably more storage compared to the AL32UTF8/AL16UTF16 character sets. This may lead to data exceeding column lengths defined in FS-PRO and FS-QUO. As such, this setup is only suitable for evaluation purposes with mainly single-byte language data and less data. For productive setup, allocate a separate database where the character sets as set as recommended.

Depending on the number of FS-PRO databases deployed to the instance, you might need to set SGA and PGA to a larger size. However, we strongly recommend that you use Automatic Memory Management (AMM) for the database.

Tablespace requirements:

Installation Guide Preparing to Install PUBLIC 15 ● A tablespace named CAMILION_DATA (at least 10 GB) ● A tablespace named INDX (at least 10 GB) ● Temporary tablespace named TEMP

Microsoft SQL Server

Certified Version: Standard or Enterprise Edition 2019

Notes:

● Requires at least 6 GB of memory ● Enable Lock pages in Memory in a production environment.

IBM DB2

Certified Version 11.5

Notes:

● Use the shell software to run initial database setup wizard. ● Create the following operating sytem groups: db2users db2iadm1

 Remember

Group and user names on UNIX systems must be lower case

● Create the following operating system user: _sys (with default user group db2users) ● Add the _sys user to the db2iadm1 group ● Set the following environment variables: db2set db2_compatibility_vector=ora db2set db2_deferred_prepare_semantics=yes ● After creating groups and users and setting variables, restart the IBM DB2 service.

Installation Guide 16 PUBLIC Preparing to Install 2.4.5.4 Application Server Requirements for FS-QUO

The following table lists the application server software supported by FS-QUO:

Application Server Requirements

Application Server Version Notes

SAP NetWeaver 7.5 SPS19 Install the following usage types:

● Application Server Java - Basic ● NW Product - NW-Model

Consult SAP Support Portal for information about specific fix packs.

2.4.5.5 Java Message Service (JMS) Requirements for FS- QUO

The following Java Message Service (JMS) providers are supported:

JMS Provider Details

JMS Provider Version Notes

NetWeaver AS Java built-in JMS Pro Relevant to the Integration Framework vider (IFW) and Web Services features.

Apache ActiveMQ 5.14.5 Relevant to distributed caching in a clustered environment.

2.4.5.6 X-Windows Virtual Frame Buffer Requirements

FS-QUO requires Xvfb (X-Windows Virtual Frame Buffer) for Solaris, Linux, and AIX implementations.

Set the display environment variable for the user account that NetWeaver is running under to the display that Xvfb is configured for.

2.4.5.7 Hardware Requirements for FS-QUO

For a typical 20-user development environment, we recommend the following hardware:

● Dual SPARC 1.2 GHz or better processors or dual Intel Xeon 2.8 GHz or better processors ● Dual core processor with 2GB RAM per processor (4GB total) (required) ● Quad core processor with 2GB RAM per processor (8GB total) or better (recommended)

Installation Guide Preparing to Install PUBLIC 17 ● Minimum of two physical drives for the database ● Minimum of two physical drives for NetWeaver and FS-PRO ● Operating system and swap located on their own physical drives

The actual hardware requirement depends on the number of products, product sizes and number of concurrent users.

The database can be installed on the same physical server as the application server, or on a separate dedicated database platform. For high volume, productive use, it's recommended that the database be installed on a dedicated server.

For information about the hardware required for production environments, consult the SAP Support Portal . The requirements depend on the number of products, the size of the products, and the number of concurrent users.

2.4.6 Client Requirements for FS-QUO

The FS-QUO client is browser-based. Ensure that you are using a supported browser for the applicable UI.

Browser support for Fiori-based applications (FS-IPW)

The browsers supported for FS-IPW applications are determined by the SAP UI5 product. For more information, see 1935915

Browser support for Sencha-based UI

The following browsers are recommended for use with the Sencha-based UI of FS-QUO:

● Microsoft Internet Explorer 9, 10 and 11 (native mode)

The following browsers are supported for use with the Sencha-based UI of FS-QUO:

● Google Chrome 56 ● Firefox 51 ● Safari 9

Minimum screen resolution

The recommended minimum screen resolution for FS-QUO is 1024 by 768 pixels. However, this value could be impacted by customization to the interface.

For FS-IPW Fiori applications, there is no minimum screen resolution.

Installation Guide 18 PUBLIC Preparing to Install 2.4.7 Substitution Variable Placeholders

The following table defines the substitution variables used in this guide. Gather the information listed prior to beginning.

Substitution Variable Description

The support package version you are installing or upgrading.

The patch level of you are installing or upgrading.

The FS-PQM release version you are installing or upgrading.

The installation directory of the file system portion of an FS- PRO or FS-QUO installation.

The database user name prefix.

The uppercase database user name prefix, followed by _SYS.

 Note

For IBM DB2, use the OS user which must contain a _SYS suffix.

This user also has access to objects from all other schemas (_PC, _PPMC, _PPMS, _PS, _SEQ, _UDIR, and _USR) that are created when the FS-QUO database is created.

Database server name.

Port number.

(Applicable to SAP HANA only)

For Single Tenant:

Port = 3<>15

For Multi Tenant:

The port can be obtained by running the following query as the system user:

SELECT SQL_PORT FROM M_SERVICES WHERE SERVICE_NAME='indexserver'

The password of the database user .

Installation Guide Preparing to Install PUBLIC 19 Substitution Variable Description

Specifies the JDBC URL of the FS-QUO database once it has been created. The JDBC URL format is specific to the data base vendor. For more information refer to the DBMS docu mentation.

The following are the typical JDBC URL formats:

● Oracle: jdbc:oracle:thin:@:: or jdbc:oracle:thin:@:/

 Note

For Oracle 12c Pluggable Databases, it is recom mended to connect through

● Microsoft SQL Server: jdbc:sqlserver:// :;datab aseName= ● SAP HANA: jdbc:sap:// : ● IBM DB2: jdbc:db2:// :/

The host name of the NetWeaver instance on which FS-QUO is deployed.

The HTTP port of the NetWeaver instance on which FS-QUO is deployed.

The secured HTTPS port of the NetWeaver instance on which FS-QUO is deployed.

The P4 port of the NetWeaver instance on which FS-QUO is deployed.

The host name of the NetWeaver instance on which FS-PRO is deployed.

The HTTP port of the NetWeaver instance on which FS-PRO is deployed.

The secured HTTPS port of the NetWeaver instance on which FS-PRO is deployed.

Installation Guide 20 PUBLIC Preparing to Install 3 Installing and Configuring the Designer/ Runtime Application

Designer/Runtime is the module of FS-QUO that provides the core execution platform allowing you to configure business processes. It isn't available as a stand-alone module.

You need to install and configure the Designer/Runtime database on servers running Microsoft Windows-based or on UNIX-based servers and how to install and configure the Designer/Runtime application.

You will need to perform the following tasks:

1. Set up a Designer/Runtime environment, which serves as the underlying platform for FS-QUO. 2. Load the insurance product content into the Product Configurator environment. 3. Configure and deploy required products. 4. Configure your Designer/Runtime environment with the insurance underwriting workflow. 5. (Optional) If your organization is using the scheduler feature from FS-QUO for batch insurance policy renewal, set up the scheduler.

Notes:

● The information about installing and configuring the Designer/Runtime application is intended for information technology personnel. ● This guide assumes that FS-QUO software is installed in the directory and is accessible (both read and write) to the NetWeaver admin user (adm) from the instance deploying FS-PRO. ● This guide follows the UNIX convention of using the forward slash (/) for describing file paths. In a Windows environment, use the backslash (\) instead.

3.1 Downloading the Installation Files

To get the installer, log in to Installations and Upgrades on the SAP Support Portal . Choose Access Downloads and search for FS-QUO and download the correct ZIP file. Search for FS-PRO also and download the correct ZIP file. Extract the FS-PRO and FS-QUO artifacts from the downloaded zip file.

FS-PRO and FS-QUO are tightly integrated and share a common code base. Hence certain parts of FS-QUO will be installed from FS-PRO artifacts.

To obtain credentials for the Support Portal, contact your administrator.

Installation Guide Installing and Configuring the Designer/Runtime Application PUBLIC 21 3.2 Installing FS-QUO

In addition to being an insurance product configurator, FS-PRO also serves as the underlying application platform for FS-QUO. An installation of FS-QUO begins with an installation of FS-PRO before it's configured for underwriting use.

You can run the FS-PRO installation wizard in any of the following modes:

GUI mode Provides an interactive, graphical interface to easily install FS-PRO. The is the most typically used mode of installation for Windows-based systems.

Console Useful on UNIX-based systems with limited GUI access. The flow in console mode is mode essentially the same as that of GUI mode, except that messages are displayed in plain text within a command prompt, and the user uses the keyboard to make choices and provide field values.

To run the FS-PRO installer, the following prerequisites must be met:

● You can install multiple FS-PRO modules in a single environment (for example, Product Configurator and Designer Runtime). When you run the installer to upgrade these environments, the installer only detects the last installed module. The installer prompts you to overwrite the detected installation path or to specify another path. For example, you might have installed Product Configurator first and Designer Runtime second in your existing environment. When you run the installer to upgrade that environment, the installer detects the Designer installation path. To upgrade the Product Configurator instance, select No, install into a different directory in the Destination Directory field of the installer, and provide the Product Configurator installation path. ● When using a wizard to install or uninstall you can't exit or cancel. If you want to abort, you must manually kill the installation or uninstallation process through the operating system.

3.2.1 Installing FS-QUO Using the Installation Wizard in GUI Mode

The Installation Wizard is typically run in GUI mode, which provides an interactive, graphical interface to easily install FS-QUO.

Prerequisites

● Java Runtime Environment (JRE) 8.0 (64-bit) must be installed, and the JAVA_HOME environment variable for this JRE must be set for the operating system user that the installer runs under. ● For database creation, the database management system (DBMS) client software must be installed. ● If you are a Solaris user and you want to install the FS-QUO database using the installer or the Database Creation Wizard, you must set the language on your Solaris computer to C/POSIX before running the installer or wizard. Otherwise, the database creation process fails.

Installation Guide 22 PUBLIC Installing and Configuring the Designer/Runtime Application Context

To install FS-QUO using the installer in GUI mode, perform the following steps:

Procedure

1. Launch the Installation Wizard executable file appropriate to your operating system: ○ Windows 64-bit: FS-PRO-install-..-windows-x64.exe ○ UNIX: FS-PRO-install-..-unix.bin 2. On the Welcome screen, choose Next. 3. On the Destination Directory screen, provide the installation directory and choose Next.

 Note

The installation directory is also referred to as in this guide.

4. On the Select Components screen, select the appropriate components. Choose Next to continue. For details on the components, refer to the context help on the screen. 5. Review the information on the Installation Summary screen, and choose Next to continue.

The Progress screen displays. 6. Wait until the installation of files completes. If you are prompted to overwrite a previous installation, choose Yes. 7. On the Finish screen, review the results and choose Finish to exit.

3.2.2 Installing FS-QUO Using the Installation Wizard in Console Mode

The FS-QUO Installation Wizard can be run in console mode, which is useful on UNIX-based systems with limited GUI access. The flow in console mode is essentially the same as that of GUI mode, except that messages are displayed in plain text within a command prompt, and the user uses the keyboard to make choices and provide field values.

Prerequisites

Installation Guide Installing and Configuring the Designer/Runtime Application PUBLIC 23 Context

To install FS-QUO using the installer in console mode, perform the following steps:

Procedure

1. Launch the Installation Wizard executable file appropriate to your operating system, with the -c option:

○ Windows 64-bit: FS-PRO-install-..-windows-x64.exe -c ○ UNIX: FS-PRO-install-..-unix.bin -c 2. On the Destination Directory prompt, provide the installation directory and choose Next.

 Note

The installation directory is also referred to as in this guide.

3. On the Select Components prompt, select the appropriate components. Choose Next to continue. 4. On the Select Additional Tasks prompt, choose Next. 5. Review the information on the Installation Summary and choose Next to continue. 6. Wait until the installation of files completes. If you are prompted to overwrite a previous installation, choose Yes. 7. On the Finish screen, review the results and choose Finish to exit.

3.3 Configuring the Encryption Key

An encryption key needs to be generated. This requires running a KeyGenerator utility. Entering a unique passphrase in the utility's input parameters generates a new key.config file.

Context

To configure the Encryption Key, perform the following steps:

Procedure

1. Set the system variable JAVA_HOME to point to a directory where your Java Runtime Environment (JRE) is located. Set the JAVA_HOME system variable as follows:

Installation Guide 24 PUBLIC Installing and Configuring the Designer/Runtime Application a. Open a command prompt in Windows or UNIX b. Run the following command: ○ Windows: SET JAVA_HOME="" ○ UNIX: setenv JAVA_HOME

where is the location of your JRE. For example SET JAVA_HOME="D:\Java\jre" (Windows) or setenv JAVA_HOME /usr/bin/java/jre (UNIX). c. Check that the system variable has been set correctly by running the following command: ECHO %JAVA_HOME% (Windows) or echo $JAVA_HOME (UNIX) which should display the location you set in the previous step 2. Go to the /bin directory and modify the genkey.properties file to set a passphrase. The key will be generated by converting characters to a series of numbers in 0-255 range. The passphrase can be of any length and contain any characters (including Unicode). The recommended size is at least 16 characters for a 128-bit key. 3. From the /bin directory, run the key generator utility as follows: ○ Windows: genkey.bat ○ UNIX: genkey.sh The key.config file is generated in /system/config.

3.4 Creating the FS-QUO Database

Use the Database Creation Wizard to create the FS-QUO database on either Oracle, IBM DB2, SAP HANA or Microsoft SQL Server.

Ensure that the prerequisites for your database type are satisfied before attempting to create the FS-QUO database.

3.4.1 Creating the FS-QUO Oracle Database Using the Database Creation Wizard in GUI Mode

Use the Database Creation Wizard to create a new FS-QUO Oracle database for the Designer Runtime environment. You can run the Database Creation Wizard in GUI mode, which provides an interactive, graphical interface to easily create the database.

Prerequisites

Before you create the database, verify the following requirements are met:

● The Oracle database software is installed. ● An Oracle database and its listener are created and running.

Installation Guide Installing and Configuring the Designer/Runtime Application PUBLIC 25 ● The operating system user that you will use to run the Database Creation Wizard must have read/write access to the sqlplus command. You can either use the operating system user which you used to install the Oracle database software, or create a separate operating system user specifically for SAP insurance applications with the necessary access. ● The database creation wizard uses the sqlplus and sqlldr (SQL Loader) commands. Confirm that these commands are functioning properly to ensure that the table content gets populated in the database.

For information on installing and configuring Oracle, see the Oracle documentation.

Context

To create the database in GUI mode, perform the following steps:

Procedure

1. On the machine with the database client installed, extract the executable files from the ZIP file appropriate for your operating system: ○ Windows 64-bit: FS-PRO-db-..-windows-x64.zip (using a Windows unzip utility) ○ UNIX: FS-PRO-db-..-unix.tar.gz (using the tar -xvzf command) 2. Launch the Database Creation Wizard executable file: ○ Windows 64-bit: FS-PRO-db\bin\createDB.exe ○ UNIX: FS-PRO-db/bin/createDB 3. On the Welcome screen, choose Next. 4. On the Select Additional Tasks screen, ensure that nothing is selected, and choose Next. 5. On the Database Information form screen, provide all required information. In particular, set the Application type to Designer Runtime and the Database type to Oracle. Choose Next when all information is provided. For details on the other fields, refer to the context help on the screen. 6. On the Summary screen, review the summary and choose Next. 7. On the Progress screen, wait until the database creation is completed. 8. On the Finish screen, review the results and choose Finish to exit.

Results

If the database creation fails, note the failure messages.

● Check the database creation logs and correct the problem. ● If data has already been partially populated, drop the related database user with content. ● Then restart the database creation process.

Installation Guide 26 PUBLIC Installing and Configuring the Designer/Runtime Application 3.4.2 Creating the FS-QUO Oracle Database Using the Database Creation Wizard in Console Mode

Use the Database Creation Wizard to create a new FS-QUO Oracle database for either the Designer Runtime environment You can run the Database Creation Wizard in console mode. The flow in console mode is essentially the same as that of GUI mode, except that messages are displayed in plain text within a command prompt, and the user uses the keyboard to make choices and provide field values. This mode is useful on UNIX- based systems with limited GUI access.

Prerequisites

Before you create the database, verify the following requirements are met:

● The Oracle database software is installed. ● An Oracle database and its listener are created and running. ● The operating system user that you will use to run the Database Creation Wizard must have read/write access to the sqlplus command. You can either use the operating system user which you used to install the Oracle database software, or create a separate operating system user specifically for SAP insurance applications with the necessary access. ● The database creation wizard uses the sqlplus and sqlldr (SQL Loader) commands. Confirm that these commands are functioning properly to ensure that the table content gets populated in the database.

For information on installing and configuring Oracle, see the Oracle documentation.

Context

To create the database in GUI mode, perform the following steps:

Procedure

Installation Guide Installing and Configuring the Designer/Runtime Application PUBLIC 27 4. When prompted for database information, provide all required information. In particular, set the Application type to Designer Runtime and the Database type to Oracle.

5. Review the summary and press Enter . 6. Wait until the database creation is completed.

Results

If the database creation fails, note the failure messages.

3.4.3 Creating the FS-QUO Microsoft SQL Server database using the Database Creation Wizard in GUI Mode

Use the Database Creation Wizard to create a new FS-QUO Microsoft SQL Server database for either the Designer Runtime environment. You can run the Database Creation Wizard in GUI mode, which provides an interactive, graphical interface to easily create the database.

Prerequisites

Before you install the database, verify the following requirements are met:

● The Microsoft SQL Server software is installed, and a Microsoft SQL Server instance is created and its associated services are properly configured and running. ● The operating system user that you will use to run the Database Creation Wizard must have read/write access to the sqlcmd command. You can either use the operating system user which you used to install the Microsoft SQL Server software, or create a separate operating system user specifically for SAP insurance applications with the necessary access.

For more information about installing and configuring Microsoft SQL Server, see the Microsoft SQL Server documentation.

Installation Guide 28 PUBLIC Installing and Configuring the Designer/Runtime Application Context

To create the database in GUI mode, perform the following steps:

Procedure

1. On the machine with the database client installed, extract the executable files from the ZIP file appropriate for your operating system: FS-PRO-db-..-windows-x64.zip 2. Launch the Database Creation Wizard executable file: FS-PRO-db\bin\createDB.exe 3. On the Welcome screen, choose Next. 4. On the Select Additional Tasks screen, ensure that nothing is selected, and choose Next. 5. On the Database Information form screen, provide all required information. In particular, set the Application type to Designer Runtime and the Database type to Microsoft SQL Server. Choose Next when all information is provided. For details on the other fields, refer to the context help on the screen. 6. On the Summary screen, review the summary and choose Next. 7. On the Progress screen, wait until the database creation is completed. 8. On the Finish screen, review the results and choose Finish to exit.

Results

If the database creation fails, note the failure messages.

3.4.4 Creating the FS-QUO Microsoft SQL Server database using the Database Creation Wizard in Console Mode

Use the Database Creation Wizard to create a new FS-QUO Microsoft SQL Server database for either the Designer Runtime environment. You can run the Database Creation Wizard in console mode. The flow in console mode is essentially the same as that of GUI mode, except that messages are displayed in plain text within a command prompt, and the user uses the keyboard to make choices and provide field values. This mode is useful on UNIX-based systems with limited GUI access.

Installation Guide Installing and Configuring the Designer/Runtime Application PUBLIC 29 Prerequisites

Before you install the database, verify the following requirements are met:

For more information about installing and configuring Microsoft SQL Server, see the Microsoft SQL Server documentation.

Context

To create the database in console mode, perform the following steps:

Procedure

1. On the machine with database client installed, extract the Database Creation Wizard executable file from the ZIP file: FS-PRO-db-..-windows-x64.zip 2. Launch the Database Creation Wizard executable file with the -c option: FS-PRO-db\bin\createDB.exe -c

3. When prompted to Create a response file only, choose the default (n) by pressing Enter . 4. When prompted for database information, provide all required information. In particular, set the Application type to Designer Runtime and the Database type to Microsoft SQL Server.

5. Review the summary and press Enter . 6. Wait until the database creation is completed.

Results

If the database creation fails, note the failure messages.

Installation Guide 30 PUBLIC Installing and Configuring the Designer/Runtime Application 3.4.5 Creating the FS-QUO SAP HANA Database Using the Database Creation Wizard in GUI Mode

Use the Database Creation Wizard to create a new FS-QUO SAP HANA database for either the Designer Runtime environment. You can run the Database Creation Wizard in GUI mode, which provides an interactive, graphical interface to easily create the database.

Prerequisites

Before you create the database, verify the following requirements are met:

● The SAP HANA database software is installed. ● The operating system user of the SAP HANA database server machine that you will use to run the Database Creation Wizard must have read/write access to the hdbsql command. You can either use the operating system user which you used to install the SAP HANA database software, or create a separate operating system user specifically for SAP insurance applications with the necessary access. ● For a SAP HANA database server configured in Multiple Container mode, the Tenant container database must be already created. It's always recommended to have a separate Tenant database container. ● The Database Creation Wizard is supported to run only from the SAP HANA database server host.

For additional information on installing and configuring SAP HANA, see the SAP HANA documentation.

Context

To create the database in GUI mode, perform the following steps:

Procedure

1. On the machine with the database client installed, extract the executable files from the ZIP file appropriate for your operating system: FS-PRO-db-..-unix.tar.gz using the tar -xvzf command. 2. Launch the Database Creation Wizard executable file: FS-PRO-db/bin/createDB 3. On the Select Additional Tasks screen, ensure that nothing is selected, and choose Next. 4. On the Database Information form screen, provide all required information. In particular, set the Application type to Designer Runtime and the Database type to SAP HANA. Also ensure the Container Mode is set to Multiple. Press Enter when all information is provided.

5. Review the summary and press Enter . 6. Wait until the database creation is completed.

Installation Guide Installing and Configuring the Designer/Runtime Application PUBLIC 31 Results

If the database creation fails, note the failure messages.

3.4.6 Creating the FS-QUO SAP HANA Database Using the Database Creation Wizard in Console Mode

Use the Database Creation Wizard to create a new FS-QUO SAP HANA database for either the Designer Runtime environment. You can run the Database Creation Wizard in console mode. The flow in console mode is essentially the same as that of GUI mode, except that messages are displayed in plain text within a command prompt, and the user uses the keyboard to make choices and provide field values. This mode is useful on UNIX- based systems with limited GUI access.

Prerequisites

Before you create the database, verify the following requirements are met:

For additional information on installing and configuring SAP HANA, see the SAP HANA documentation.

Context

To create the database in console mode, perform the following steps:

Procedure

1. On the machine with the database client installed, extract the executable files from the ZIP file appropriate for your operating system:

Installation Guide 32 PUBLIC Installing and Configuring the Designer/Runtime Application FS-PRO-db-..-unix.tar.gz using the tar -xvzf command. 2. Launch the Database Creation Wizard executable file with the -c option: FS-PRO-db/bin/createDB -c

5. Review the summary and press Enter . 6. Wait until the database creation is completed.

Results

If the database creation fails, note the failure messages.

3.4.7 Creating the FS-QUO IBM DB2 database using the Database Creation Wizard in GUI Mode

Use the Database Creation Wizard to create a new FS-QUO IBM DB2 database for either the Designer Runtime environment. You can run the Database Creation Wizard in GUI mode, which provides an interactive, graphical interface to easily create the database.

Context

To create the database in GUI mode, perform the following steps:

Procedure

Installation Guide Installing and Configuring the Designer/Runtime Application PUBLIC 33 4. On the Select Additional Tasks screen, ensure that nothing is selected, and choose Next. 5. On the Database Information form screen, provide all required information. In particular, set the Application type to Designer Runtime and the Database type to DB2. Choose Next when all information is provided. For details on the other fields, refer to the context help on the screen. 6. On the Summary screen, review the summary and choose Next. 7. On the Progress screen, wait until the database creation is completed. 8. On the Finish screen, review the results and choose Finish to exit.

Results

If the database creation fails, note the failure messages.

3.4.8 Creating the FS-QUO IBM DB2 database using the Database Creation Wizard in Console Mode

Use the Database Creation Wizard to create a new FS-QUO IBM DB2 database for either the Designer Runtime environment. You can run the Database Creation Wizard in console mode. The flow in console mode is essentially the same as that of GUI mode, except that messages are displayed in plain text within a command prompt, and the user uses the keyboard to make choices and provide field values. This mode is useful on UNIX- base systems with limited GUI access.

Context

To create the database in console mode, perform the following steps:

Procedure

3. When prompted to Create a response file only, choose the default (n) by pressing Enter .

Installation Guide 34 PUBLIC Installing and Configuring the Designer/Runtime Application 4. When prompted for database information, provide all required information. In particular, set the Application type to Designer Runtime and the Database type to DB2.

5. Review the summary and press Enter . 6. Wait until the database creation is completed.

Results

If the database creation fails, note the failure messages.

3.5 Configuring the NetWeaver Instance

You need to configure settings on the NetWeaver instance to which the FS-QUO application is deployed.

The instructions assumes that you already have a database created for your instance and already installed on the NetWeaver server.

Related Information

SAP NetWeaver Administrator [page 8]

3.5.1 Configuring the Java Settings

Configure additional VM parameters through the AS Java Config Tool.

Context

When using the AS Java Config Tool (configtool) for offline configuration, additional JVM parameters must be added at the instance level.

Installation Guide Installing and Configuring the Designer/Runtime Application PUBLIC 35 Procedure

1. Run the configtool, which can be found at the following location: \usr\sap\\\j2ee\configtool\.

2. Within the left panel navigate to cluster-data template - Usage_Type_All_in_One instance . 3. Open the VM Parameters tab on the right panel. 4. Select the Memory tab. a. Change the value of maxHeapSize parameter to be at least 4096 MB. b. Configure the JVM memory sizes at the instance level as appropriate. 5. Select the System tab and edit the following parameters:

CSI.home=

file.encoding=UTF-8

 Caution

In , use forward slashes (/) only

6. After all the settings are made, restart the instance using the SAP MMC.

Related Information

SAP NetWeaver Administrator [page 8]

3.5.2 Configuring SSL and Enabling HTTPS on NetWeaver

You must configure SSL and enable an HTTPS access point on your NetWeaver instance.

Related Information

SAP NetWeaver Administrator [page 8]

Installation Guide 36 PUBLIC Installing and Configuring the Designer/Runtime Application 3.5.3 Increasing the P4 Request Size Limit

The default maximum value in NetWeaver for the P4 request size of 12288 kb might not be sufficient for remotely deploying larger insurance products from a Product Configurator instance to a Designer Runtime instance. It should be increased on both the Product Configurator instance and the Designer Runtime instance

Context

To increase the P4 request size limit, perform the following steps:

Procedure

1. Open the SAP Web Dispatcher profile file of the NetWeaver instance with a text editor. The file is typically located at: /usr/sap//SYS/profile/__ 2. Add the following parameters to the profile file, where is the new maximum size based on the insurance product size. It's recommended that you set the to 49152, which is four times the default size and is generally sufficient for most large-scale insurance products. icm/P4/max_request_size_KB = 3. Save the profile file. 4. Restart the NetWeaver instance for the changes to take effect.

Related Information

SAP NetWeaver Administrator [page 8]

3.5.4 Increasing the HTTP Service Process Timeout

NetWeaver has a default timeout of 600 seconds for communication of the HTTP service with the AS Java back-end. For larger insurance products, certain tasks such as building insurance product rules might take longer than the default timeout. When the timeout is reached, NetWeaver will prematurely disconnect the HTTP connection for reporting progress of such task in the front-end.

Installation Guide Installing and Configuring the Designer/Runtime Application PUBLIC 37 Context

To increase the timeout value on the Designer Runtime instance, perform the following steps:

Procedure

1. Open the SAP Web Dispatcher profile file of the NetWeaver instance with a text editor. The file is typically located at /usr/sap/SID/SYS/profile/__ 2. Locate the line that specifies the HTTP port definition. For example: icm/server_port_0 = PROT=HTTP,PORT=50000,TIMEOUT=60,PROCTIMEOUT=600 3. Change the PROCTIMEOUT parameter to the new timeout value. It's recommended that you set the new timeout value to 10800, which is sufficient for most large-scale insurance products. For example: icm/server_port_0 = PROT=HTTP,PORT=50000,TIMEOUT=60,PROCTIMEOUT=10800 4. Repeat step 2 and step 3 to also add the PROCTIMEOUT setting for the HTTPS port definition. 5. Save the profile file. 6. Restart the NetWeaver instance for the changes to take effect.

Related Information

SAP NetWeaver Administrator [page 8]

3.5.5 Adjusting the Content Filter of the HTTP Access Handler

Some features in Product Configurator require that the content filter of the HTTP access handler be adjusted in the SAP Web Dispatcher Web Administration Interface.

Context

To adjust the content filter of the HTTP access handler, perform the following steps:

Procedure

1. Log in to the SAP Web Dispatcher Web Administration Interface.

Installation Guide 38 PUBLIC Installing and Configuring the Designer/Runtime Application 2. From the left menu, expand HTTP Handler and choose Access Handler. 3. Under the Content Filter section, choose SAP and choose Change Content Filter. 4. Select the following rule and choose Edit Rule: <\s*(script|object|iframe|embed|img)[^>]*>(.*)<\s*/(script|object|iframe|embed| img)\s*> 5. Remove the object keywords and adjacent separators from the rule and choose Save: The rule should appear as follows: <\s*(script|iframe|embed|img)[^>]*>(.*)<\s*/(script| iframe|embed|img)\s*> 6. Restart the NetWeaver instance for the changes to take effect.

Related Information

SAP NetWeaver Administrator [page 8]

3.5.6 Increasing the Severity Level of the System.out and System.err Tracing Locations

To maintain compatibility with the SAP NetWeaver application server, the FS-QUO application writes formatted log information to the system out and system error streams.

By default, SAP NetWeaver AS Java doesn't have the required severity level enabled, so it must be done in SAP NetWeaver Administrator (NWA).

To access the tool, open NWA and then choose Troubleshooting Logs and Traces Log Configuration . You can alternatively use the quick link: http://:/nwa/log-config. Under the Show: dropdown, select Tracing Locations. Set the severity level in the following tracing locations to All:

● ROOT LOCATION System ● ROOT LOCATION System err ● ROOT LOCATION System out

Related Information

SAP NetWeaver Administrator [page 8]

Installation Guide Installing and Configuring the Designer/Runtime Application PUBLIC 39 3.5.7 Configuring the HttpOnly Flag

Configuring the HttpOnly flag in SAP NetWeaver Administrator (NWA) can help to minimize the possibility of session hijacking.

Context

To configure the HttpOnly flag, perform the following steps:

Procedure

1. In NWA, go to NWA Configuration Infrastructure Java System Properties Services HTTP Provider . 2. Update the following settings in the Extended Details section:

SystemCookiesDataProtection set to true. This enables the HttpOnly cookie attribute for the JSESSIONID to mitigate the risk of session hijacking over XSS.

SystemCookiesHTTPSProtection set to true. This enables the Secure cookie attribute for the JSESSIONID to minimize the risks of session hijacking over network sniffing – the JSESSIONID cookie would be sent only over SSL encrypted HTTPS connections.

 Caution

Don't set the SystemCookiesHTTPSProtection to true if SSL encrypted HTTPS isn't configured on the server. Otherwise, all applications that rely on sessions (which includes NWA itself) won't work. This setting causes cookies to only work if using an SSL encrypted HTTPS connection. For example, NWA pages will only be accessible via an HTTPS URL.

3. Save your changes.

Results

Refer to the SAP Product and Quotation Management Security Guide for additional security-related information.

Related Information

SAP NetWeaver Administrator [page 8]

Installation Guide 40 PUBLIC Installing and Configuring the Designer/Runtime Application 3.6 Configuring Database Settings in NetWeaver

You need to configure the database connection settings in NetWeaver.

Only one of the databases needs to be configured in NetWeaver; either SAP HANA, Oracle, IBM DB2, or Microsoft SQL Server.

 Remember

Database User name, as mentioned in Substitution Variable Placeholders topic, needs to be configured in uppercase

3.6.1 Configuring Oracle Settings in NetWeaver

You need to configure database connection settings in NetWeaver for your Oracle database.

Deploying the Oracle JDBC Driver

Oracle JDBC Drivers

Database Version Driver

Oracle 19c Using the SAP NetWeaver Administrator web console (NWA), deploy a new JDBC driver with the Oracle JDBC driver JAR file, ojdbc8.jar, which can be obtained from the Oracle Technology Network Software Downloads page.

Configuring the Oracle DataSource

Configure the Oracle JDBC custom DataSource using the following settings.

Property Name Value

Settings Application Name Use the recommended name, CamilionDs, or a name of your choice.

Settings DataSource Name Use the recommended name CamilionDs, or a name of your choice. If you choose a different name, you must add CamilionDs as an alias (see below).

Settings Driver Name The name of the Oracle JDBC driver created earlier.

Installation Guide Installing and Configuring the Designer/Runtime Application PUBLIC 41 Property Name Value

Settings SQL Engine Vendor SQL

Settings Isolation Level Default

Settings JDBC Version 2.0 (with XA support)

Settings DataSource Type ConnectionPool DataSource

Settings CPDS Class Name oracle.jdbc.pool.OracleConnectionPoolDat aSource

Connection Pooling Maximum connections 100

Adjust this value as required.

Connection Pooling Maximum Time to Wait for 180 Connection Adjust this value as required.

Connection Pooling Expiration Enable this option.

Connection Pooling Connection Lifetime (Sec.) 1800

Adjust this value as required.

Connection Pooling Cleanup Interval (Sec.) 180

Adjust this value as required.

Additional Properties user , as defined in the Substitution Variable Placeholders topics  Note

The additional property names are case-sensitive

Additional Properties password , as defined in the Substitution Varia ble Placeholders topic

, as defined in the Substitution Variable Place Additional Properties URL holders topic

JDBC DataSource Aliases 1. CamilionDs, if you use a data source name other than CamilionDs 2. psrepositoryDs 3. psruntimeDs

Installation Guide 42 PUBLIC Installing and Configuring the Designer/Runtime Application 3.6.2 Configuring Microsoft SQL Server Settings in NetWeaver

You need to configure database connection settings in NetWeaver for your Microsoft SQL Server database.

Deploying the Microsoft SQL Server JDBC Driver

Using the SAP NetWeaver Administrator web console (NWA), deploy a new JDBC driver with the Microsoft SQL Server JDBC driver 4.0 JAR file, mssql-jdbc-8.2.2.jre8.jar, which can be obtained from the Microsoft Download Center.

Configuring the Microsoft SQL Server DataSource

Configure Microsoft SQL Server JDBC custom DataSource using the following settings.

Property Name Value

Settings Application Name Use the recommended name, CamilionDs, or a name of your choice.

Settings DataSource Name Use the recommended name CamilionDs, or a name of your choice. If you choose a different name, you must add CamilionDs as an alias (see below).

Settings Driver Name The name of the Microsoft SQL Server JDBC driver created earlier.

Settings SQL Engine Vendor SQL

Settings Isolation Level Default

Settings JDBC Version 2.0 (with XA support)

Settings DataSource Type ConnectionPool DataSource

Settings CPDS Class Name com.microsoft.sqlserver.jdbc.SQLServerCo nnectionPoolDataSource

Connection Pooling Maximum connections 100

Adjust this value as required.

Installation Guide Installing and Configuring the Designer/Runtime Application PUBLIC 43 Property Name Value

Connection Pooling Maximum Time to Wait for 180

Connection Adjust this value as required.

Connection Pooling Expiration Enable this option.

Connection Pooling Connection Lifetime (Sec.) 1800

Adjust this value as required.

Connection Pooling Cleanup Interval (Sec.) 180

Adjust this value as required.

Additional Properties user , as defined in the Substitution Variable Placeholders topic  Note

The additional property names are case-sensitive

Additional Properties password , as defined in the Substitution Varia ble Placeholders topic

Additional Properties URL , as defined in the Substitution Variable Place holders topic

JDBC DataSource Aliases 1. CamilionDs, if you use a data source name other than CamilionDs 2. psrepositoryDs 3. psruntimeDs

3.6.3 Configuring SAP HANA Settings in NetWeaver

You need to configure database connection settings in NetWeaver for your SAP HANA database.

Deploying the SAP HANA JDBC Driver

Deploy the ngdbc.jar JDBC driver JAR file using the SAP NetWeaver Administrator (NWA) web console. Typically, this file is bundled with the SAP HANA client libraries of the same version as HANA Database Server. See the SAP HANA documentation for further details.

Installation Guide 44 PUBLIC Installing and Configuring the Designer/Runtime Application Configuring the SAP HANA Data Source

Configure the SAP HANA JDBC Custom DataSource using the following settings.

Property Name Value

Settings Application Name Use the recommended name, CamilionDs, or a name of your choice.

Settings DataSource Name Use the recommended name CamilionDs, or a name of your choice. If you choose a different name, you must add CamilionDs as an alias (see below).

Settings Driver Name The name of the SAP HANA JDBC driver created earlier.

Settings SQL Engine Vendor SQL

Settings Isolation Level Default

Settings JDBC Version 2.0 (with XA support)

Settings CPDS ClassName com.sap.db.jdbcext.ConnectionPoolDataSourceSA P

Settings Database URL , as defined in the Substitution Variable Placeholders topic

, in uppercase only, as defined in the Substitu Settings User Name tion Variable Placeholders topic

, as defined in the Substitution Variable Pla Settings Password ceholders topic

Connection Pooling Maximum connections 100

Adjust this value as required.

Connection Pooling Maximum Time to Wait for 180 Connection Adjust this value as required.

Connection Pooling Expiration Enable this option.

Connection Pooling Connection Lifetime (Sec.) 1800

Adjust this value as required.

Connection Pooling Cleanup Interval (Sec.) 180

Adjust this value as required.

Installation Guide Installing and Configuring the Designer/Runtime Application PUBLIC 45 Property Name Value

JDBC DataSource Aliases 1. CamilionDs, if you use a data source name other than Ca milionDs 2. psrepositoryDs 3. psruntimeDs

3.6.4 Configuring IBM DB2 Settings in NetWeaver

You need to configure database connection settings in NetWeaver for your IBM DB2 database.

Deploying the IBM DB2 JDBC Driver

Using the SAP NetWeaver Administrator web console (NWA), deploy a new JDBC driver with the IBM DB2 JDBC driver JAR file, db2jcc4.jar, which can be obtained from the IBM support site.

Select the file that matches the database and JDBC version.

Configuring the IBM DB2 DataSource

Create the IBM DB2 JDBC custom DataSource using the following settings:

Property Name Value

Settings Application Name Use the recommended name, CamilionDs, or a name of your choice.

Settings DataSource Name Use the recommended name CamilionDs, or a name of your choice. If you choose a different name, you must add CamilionDs as an alias (see below).

Settings Driver Name The name of the IBM DB2 JDBC driver created earlier.

Settings SQL Engine Vendor SQL

Settings Isolation Level Default

Settings JDBC Version 2.0 (with XA support)

Settings CPDS Class Name com.ibm.db2.jcc.DB2ConnectionPoolDataS ource

Installation Guide 46 PUBLIC Installing and Configuring the Designer/Runtime Application Property Name Value

Additional Properties user , in uppercase, as defined in the Sub stitution Variable Placeholders topic.

Additional Properties password , as defined in the Substitution Variable Placeholders topic.

Additional Properties portNumber Port number of the instance where the server is listening for requests.

Additional Properties databaseName Specifies the name for the data source. This name is used as the database portion of the connection URL.

Additional Properties serverName The host name or the TCP/IP address of the data source.

Additional Properties driverType 4

Additional Properties statementConcentrator 2

Connection Pooling Maximum connections 100

Adjust this value as required.

Connection Pooling Maximum Time to Wait for 180 Connection Adjust this value as required.

Connection Pooling Expiration Enable this option.

Connection Pooling Connection Lifetime (Sec.) 1800

Adjust this value as required.

Connection Pooling Cleanup Interval (Sec.) 180

Adjust this value as required.

JDBC DataSource Aliases 1. CamilionDs, if you use a data source name other than CamilionDs 2. psrepositoryDs 3. psruntimeDs

Installation Guide Installing and Configuring the Designer/Runtime Application PUBLIC 47 3.7 Disabling Heavy Resource Loading

Heavy resource loading must be disabled for the instance to which FS-QUO is deployed.

Context

Disable heavy resource loading using the AS Java Config Tool for offline configuration (configtool) using the following steps:

 Tip

The configtool can be found in the following location: \usr\sap\\J\j2ee\configtool\.

Procedure

1. Using the configtool for the instance to which the SAP software is deployed, navigate to Template - Usage_Type_All_in_One Services Library_container 2. Override the value of the property Define_Heavy_Resources from true to false. 3. Save your changes. 4. Close the configtool. 5. Restart the instance using the SAP MMC.

Related Information

SAP NetWeaver Administrator [page 8]

3.8 Deploying the FS-QUO SCA

The Java EE application is packaged as a Software Component Archive (SCA) file and is deployed to the server.

The SCA file can be deployed using the Software Update Manager (SUM) tool or using the Telnet administration interface.

 Note

If you have a custom SCA file that has already been merged with the changes from the release then use that. Otherwise, use the downloaded file.

Installation Guide 48 PUBLIC Installing and Configuring the Designer/Runtime Application 3.8.1 Deploying the SCA Using Telnet

By using a Telnet client through the Telnet protocol, you can connect to the SAP NetWeaver Application Server and deploy your SCA file.

Prerequisites

● A connection can be established if the AS Java system is installed and running, and the machine has a Telnet client through which a connection to the server can be established. ● The appropriate SCA file has been downloaded.

Procedure

1. Copy the SCA file to a local directory. 2. Open a command prompt and run the following command:

telnet localhost 508

where is the system number of the AS Java instance (next to the thin server icon in SAP MMC). The telnet port is the HTTP port for your instance + 8. 3. Log in with NetWeaver Administrator credentials. 4. Once logged in, execute the following commands:

add deploy deploy version_rule=all

5. Ensure the output messages display a successful deployment.

For further details on using telnet, refer to the following article in the SAP Library: Administration Using Telnet. 6. After deploying the SCA file, restart the instance using the SAP MMC.

Installation Guide Installing and Configuring the Designer/Runtime Application PUBLIC 49 3.8.2 Deploying the SCA Using SUM

The Software Update Manager (SUM) is a multipurpose tool that supports various processes, such as performing a release upgrade and installing enhancement packages among other things. As such, SUM can be used to deploy your SCA file.

Prerequisites

● Make sure that SUM is downloaded and available on your SAP NetWeaver AS Java. SUM is part of the Software Logistics Toolset delivery and available for download from the Software Logistics Toolset page on the Support Portal

 Note

When running SUM, the logged in user must be the owner of the installed application server. For example, b01adm must be signed into Windows to run SUM for B01, and b02adm must be signed into Windows to run SUM for B02. Also, the application server must be started by the owner before running SUM.

● Before running and using the SUM, you have to complete all required preparation and planning actions in the SUM user guide. ● Make sure that the SAP system and its database are started. ● The appropriate SCA file has been downloaded.

Procedure

1. Copy your SCA file to an empty directory. 2. In SUM, select Manually prepared directory as the target version definition and browse to the directory where you placed your SCA file. 3. Continue with the update process.

For details, refer to the Update of SAP systems using Software Update Manager guide in the Installation and Upgrade section of the SAP NetWeaver 7.5 product page.

 Note

When the application is started, NetWeaver might report a java.io.FileNotFoundException on j2ee/ cluster/apps/sap.com/FS-.ear/orpersistence/jars/lib/camilionlib.jar in the SAP system logs and traces, even though the start up is reported as successful. The error doesn't cause any harm and can be safely ignored.

4. After deploying the SCA file, restart the instance using the SAP MMC.

Installation Guide 50 PUBLIC Installing and Configuring the Designer/Runtime Application  Note

In a clean install scenario, SCA deployment could issue a warning related to Extended Underwriting Application Configuration, which can be safely ignored as the product will be published and deployed later subsequently.

5. Log into http://:/csiroot/admin and navigate to the Help About page to confirm that the SCA version got updated.

This serves as a test that the application is accessible for the next step of importing the bootstraps.

3.9 Customizing the FS-QUO Installation

You need to apply the final settings that customize a Designer/Runtime server for your site.

Perform these procedures in this section after deploying Designer/Runtime to your application server. To configure Designer/Runtime, you use the Designer Administrative Console.

 Restriction

Your application server must be running.

3.9.1 Logging In to the Administrative Console

The following procedure describes how to log in to the Administrative Console.

Context

To log in to the Administrative Console, perform the following steps:

Procedure

1. Open a web browser and enter the following address: https://:/csiroot/admin

The Administrative Console login screen appears. 2. Enter admin in the User Name field 3. Enter the password for the admin account in the Password field. The default password is password.

Installation Guide Installing and Configuring the Designer/Runtime Application PUBLIC 51 4. Choose Enter.

Results

The Designer/Runtime Administrative Console screen appears.

Next Steps

Change the default password to a secure one as soon as possible. To change the password, choose Change password in the Administrative Console login screen, and follow the prompts

3.9.1.1 Warning Symbols in the Configuration Manager

Warning symbols may be displayed in the Configuration Manager tree in the FS-QUO Administrative Console.

The following warning symbols appear in the tree:

● —Indicates that a variable that has no value assigned exists, but value assignment isn't mandatory. In this situation, you can ignore the warning and the system still functions properly.

● —Indicates that variable exists without a default value or an override value, but a value must be assigned. For the setting to function properly, you must assign a value.

3.9.2 Configuring the System Environment

There are some default system settings that you must override as part of a successful installation.

Context

 Caution

You can perform the following procedure only once. After you save the changes, you can't undo them. For help with this procedure, consult the SAP Product Support if you are implementing clusters or highly available solutions.

Installation Guide 52 PUBLIC Installing and Configuring the Designer/Runtime Application To set the server type and configure the system environment, perform the following steps:

Procedure

1. Log in to the Designer Administrative Console.

2. Choose System Edit Configuration Settings from the menu bar.

The Configuration tree displays.

3. Choose Configuration System Env System Manager . The System Manager settings display. 4. Complete the following fields, and save your changes: ○ In the PPMCEnabled row, in the Override field, select Yes. ○ In the PPMSEnabled row, in the Override field, select Yes.

The settings to enable Designer are saved.

 Note

This setting can only be changed once, immediately after the installation.

5. Choose System Reload Configuration Settings from the menu bar. The reload options display. 6. Choose Reload System Config. The system environment is configured. Additional configuration options display.

 Note

You may see some warnings associated with these additional configuration options, which you will resolve in later sections.

7. Perform the following steps if you are installing FS-QUO in a Windows environment:

a. Choose System Edit Configuration Settings from the menu bar.

The Configuration tree displays. b. Go to Configuration System Env System Environment .

The System Environment settings display. c. Copy the value from the Default field and paste it into the Override field for the JavaCompilerOptions row. Change the colon (:) delimiters for UNIX to semi-colons (;) for Windows. d. Save your changes. 8. Optionally, set the values for the following parameters:

a. Choose System Edit Configuration Settings from the menu bar.

The Configuration tree displays. b. Go to Configuration System Env System Environment .

The System Environment settings display.

Installation Guide Installing and Configuring the Designer/Runtime Application PUBLIC 53 c. Enter the name of the appropriate email server to enable the system to send emails in the Override field for the EmailServerName row.

Alternately, you can select the Empty Value checkbox d. Enter a value in the Override field for the DefaultPassword row. This value is used when a user requests an automatic password reset. e. Save your changes. The email and default password settings are saved.

9. Go to Configuration PPMC Env PPMC Environment . In the Override field for the EnableWorkspace row, select No and save your changes.

10. Optionally, go to Configuration PPMS Env Async Scheduler Setting in the configuration tree and complete the following fields: ○ AsyncTask.ScheduledDate—Select the Empty Value checkbox. ○ AsyncFailureEmailTo—Select the Empty Value checkbox. ○ AsyncFailureEmailFrom—Select the Empty Value checkbox. ○ AsyncFailureSubjectPrefix—Select the Empty Value checkbox. 11. Optionally, you can disable rule tracing in production environments to increase performance:

a. Go to Configuration System Env Debugging Setting in the configuration tree. b. In the Override field of the EnableRuleTrace row, select No.

 Note

Don't disable this setting in development environments. Otherwise, you can't trace rules during testing and debugging. For more information about the EnableRuleTrace setting, see the SAP Product Lifecycle Management for Insurance Administration Guide. For more information about rule tracing, see the Product Configurator User Guide.

12. Choose System Reload Configuration Settings from the menu bar.

The reload options display. 13. Choose Reload All Config.

Installation Guide 54 PUBLIC Installing and Configuring the Designer/Runtime Application 3.10 Verifying the FS-QUO Installation

Use the following procedure to verify that the installation completed successfully.

Context

To verify the installation, perform the following steps:

Procedure

1. Log in to the Designer at the following location: https://:/csiroot/author If the login screen displays, the application set up properly. 2. Enter system as the user name and the correct password, then choose Log In.

If you haven't changed the password, enter password

3. Choose Help About . The About dialog displays. 4. Verify the following information displays: Version ..

3.11 Locking Down a Production Environment

Typically, an application under development and testing doesn't use full security so that the content can be developed and tested. When you move the application into production, you must apply all the required security settings and ensure only secure IDs and passwords are active. This set of procedures is known as locking down the application environment.

Context

 Remember

Immediately after an installation, it's imperative that the Administrative Console password and the system password be changed to ensure security integrity..

Installation Guide Installing and Configuring the Designer/Runtime Application PUBLIC 55 Procedure

1. Lock down the database, by performing the following steps: a. Access the database and change all user passwords in the schemas. b. Change the user password entry for the datasource.

 Note

This entry is the login ID that NetWeaver uses to connect to the database.

2. Change the password for the Designer Administrative Console admin account, by performing the following steps: a. Open a web browser and enter the following address: https://:/csiroot/admin The Designer Administrative Console login screen appears. b. Choose Change password. The Change Password dialog opens. c. Enter admin in the User name field d. Enter password in the Password field The Change your password dialog displays. e. Choose Next. f. Enter a new password, confirm the value, enter a hint, and choose Change. The password for the admin account is changed. 3. Change the default password for automatic password resets, by performing the following steps: a. Log in to the Designer Administrative Console. b. Choose System Edit Configuration Settings from the menu bar.

The Configuration tree displays. c. Go to Configuration System Env System Environment .

The System Environment settings display. d. Enter a value in the Override field for the DefaultPassword row. e. Save your changes. The default password is changed. This value is used when a user requests an automatic password reset.

4. Choose System Reload Configuration Settings from the menu bar.

The reload options display. 5. Choose Reload System Config.

Results

The system environment is configured. The production environment is locked down.

Installation Guide 56 PUBLIC Installing and Configuring the Designer/Runtime Application 4 Loading FS-QUO Contents into Product Configurator

4.1 Uploading the Custom Stem Classes

Prerequisites

You should already have set up a FS-PRO Product Configurator instance by following the steps outlined in the SAP Product Lifecycle Management for Insurance Installation Guide for SAP NetWeaver.

Context

To upload the custom classes, perform the following steps:

Procedure

1. Extract the contents of the FS-QUO-pc-custom-stems.zip file found in the custom_stems directory of the FS-QUO-exports-...zip file into the /ps/custom/class directory for the FS-PRO Product Configurator instance. Since these are binary files, don't use the -a or the -aa option with the unzip command to extract these files on UNIX and Linux. 2. Log into the Product Configurator Administrative Console at the following address: https://:/csiroot/admin

3. Clear the function cache by selecting System Register Function Library and choosing the Clear Function Cache icon next to the Library Manager title.

4. Reset the class loader by selecting System Reset ClassLoader .

Installation Guide Loading FS-QUO Contents into Product Configurator PUBLIC 57 4.2 Updating Objects and Loading Data for Underwriting in the Product Configurator Database

Some database updates need to be applied to the Product Configurator database using a database update utility to prepare the environment for the insurance underwriting workflow. You can choose to run the Database Update Wizard in GUI mode (typical), console mode or unattended mode.

You will need to download the database update utility file from sap.com prior to attempting to update the database objects.

It's assumed that the database requirements are already met.

 Note

Ensure that you have the correct UNIX shell software installed before attempting to update database objects.

It's only necessary to perform the update task that applies to your database type, using your preferred run mode.

Related Information

Supported Shell Software for FS-QUO [page 14]

4.2.1 Updating the Oracle Database for the Product Configurator Using the Database Update Wizard in GUI Mode

You can use the Database Update Wizard in GUI mode to update the FS-QUO Oracle database for the Product Configurator. GUI mode provides an interactive, graphical interface to easily update the database.

Prerequisites

You should have already set up a FS-PRO Product Configurator instance by following the steps outlined in the SAP Product Lifecycle Management for Insurance Installation Guide for SAP NetWeaver.

Installation Guide 58 PUBLIC Loading FS-QUO Contents into Product Configurator Context

To update the database in GUI mode, perform the following steps:

Procedure

1. Download the database update utility file: a. Go to Installations and Upgrades on the SAP Support Portal. b. Choose Search for Software. c. Search for FS-QUO. d. Download the following ZIP file: FS-QUO-db-..-unix.tar.gz via the command tar -xvzf. 2. Stop the Product Configurator instance using the SAP MMC. 3. From the ZIP file, extract the Database Update Wizard executable file: FS-QUO-db/bin/updateDB. 4. Launch the Database Update Wizard executable file: FS-QUO-db/bin/updateDB 5. On the Welcome screen, choose Next. 6. On the Select Additional Tasks screen, choose Next. 7. On the Database Information form screen, provide all required information. In particular, set the Application type to Product Configurator and the Database type to Oracle.

 Caution

Ensure that the Create Test Users checkbox isn't enabled.

For details on the FS-PRO database user name prefix field, refer to the description of the substitution variable in the Substitution Variable Placeholders topic. For details on the other fields, refer to the context help on the screen. Choose Next when all information is provided. 8. On the Summary screen, review the summary and choose Next. 9. On the Progress screen, wait until the database update is completed. 10. On the Finish screen, review the results and choose Finish to exit.

If the database update fails, note the failure messages. ○ Check the database update logs and correct the problem. ○ Then restart the database update process. 11. Start the Product Configurator instance using the SAP MMC.

Installation Guide Loading FS-QUO Contents into Product Configurator PUBLIC 59 4.2.2 Updating the Oracle Database for the Product Configurator Using the Database Update Wizard in Console Mode

You can use the Database Update Wizard in console mode to update the FS-QUO Oracle database for the Product Configurator environment.

Prerequisites

You should have already set up a FS-PRO Product Configurator instance by following the steps outlined in the SAP Product Lifecycle Management for Insurance Installation Guide for SAP NetWeaver.

Context

The flow in console mode is essentially the same as that of GUI mode, except that messages are displayed in plain text within a command prompt, and the user uses the keyboard to make choices and provide field values. This mode is useful on UNIX-based systems with limited GUI access.

To update the database in console mode, perform the following steps:

Procedure

5. When prompted to Create a response file only, choose the default (n) by pressing Enter . 6. On the Database Information form, provide all required information. In particular, set the Application type to Product Configurator and the Database type to Oracle.

 Caution

Ensure that the Create Test Users isn't enabled.

Installation Guide 60 PUBLIC Loading FS-QUO Contents into Product Configurator For details on the FS-PRO database user name prefix field, refer to the description of the substitution variable in the Substitution Variable Placeholders topic. Hit Enter when all information is provided.

7. Review the summary and press Enter . 8. Wait until the database update is completed.

9. Review the results and press Enter to exit.

If the database update fails, note the failure messages. ○ Check the database update logs and correct the problem. ○ Then restart the database update process. 10. Start the Product Configurator instance using the SAP MMC.

4.2.3 Updating the Microsoft SQL Server Database for the Product Configurator Using the Database Update Wizard in GUI Mode

You can use the Database Update Wizard in GUI mode to update the FS-QUO Microsoft SQL Server database for the Product Configurator environment. GUI mode provides an interactive, graphical interface to easily update the database.

Prerequisites

You should have already set up a FS-PRO Product Configurator instance by following the steps outlined in the SAP Product Lifecycle Management for Insurance Installation Guide for SAP NetWeaver.

Context

To update the database in GUI mode, perform the following steps:

Procedure

Installation Guide Loading FS-QUO Contents into Product Configurator PUBLIC 61 3. From the ZIP file, extract the Database Update Wizard executable file: FS-QUO-db\bin\updateDB.exe. 4. Launch the Database Update Wizard executable file: FS-QUO-db\bin\updateDB.exe 5. On the Welcome screen, choose Next. 6. On the Select Additional Tasks screen, choose Next. 7. On the Database Information form screen, provide all required information. In particular, set the Application type to Product Configurator and the Database type to Microsoft SQL Server.

 Caution

Ensure that the Create Test Users checkbox isn't enabled.

4.2.4 Updating the Microsoft SQL Server Database for the Product Configurator Using the Database Update Wizard in Console Mode

You can use the Database Update Wizard in console mode to update the FS-QUO Microsoft SQL Server database for the Product Configurator environment.

Prerequisites

You should have already set up a FS-PRO Product Configurator instance by following the steps outlined in the SAP Product Lifecycle Management for Insurance Installation Guide for SAP NetWeaver.

Context

Installation Guide 62 PUBLIC Loading FS-QUO Contents into Product Configurator To update the database in console mode, perform the following steps:

Procedure

 Caution

Ensure that the Create Test Users isn't enabled.

For details on the FS-PRO database user name prefix field, refer to the description of the substitution variable in the Substitution Variable Placeholders topic. Hit Enter when all information is provided.

7. Review the summary and press Enter . 8. Wait until the database update is completed.

9. Once complete, review the results and press Enter to exit.

Installation Guide Loading FS-QUO Contents into Product Configurator PUBLIC 63 4.2.5 Updating the SAP HANA Database for the Product Configurator Using the Database Update Wizard in GUI Mode

You can use the Database Update Wizard in GUI mode to update the FS-QUO SAP HANA database for the Product Configurator. GUI mode provides an interactive, graphical interface to easily update the database.

Prerequisites

● You should have already set up a FS-PRO Product Configurator instance by following the steps outlined in the SAP Product Lifecycle Management for Insurance Installation Guide for SAP NetWeaver. ● Currently, the SAP HANA Database Update Wizard can only be run from the SAP HANA database server host.

Context

To update the database in GUI mode, perform the following steps:

Procedure

1. Download the database update utility file: a. Go to Installations and Upgrades on the SAP Support Portal. b. Choose Search for Software. c. Search for FS-QUO. d. Download the following ZIP file: FS-QUO-db-..-unix.tar.gz. 2. Stop the Product Configurator instance using the SAP MMC. 3. From the ZIP file, extract the Database Update Wizard executable file: FS-QUO-db/bin/updateDB via the command tar -zxvf. 4. On the UNIX machine where the SAP HANA database server is installed, launch the Database Update Wizard executable file with the -c option: FS-QUO-db/bin/updateDB -c 5. On the Welcome screen, choose Next. 6. On the Select Additional Tasks screen, choose Next. 7. On the Database Information form screen, provide all required information. In particular, set the Application type to Product Configurator and the Database type to SAP HANA. Also ensure the Container Mode is set to Multiple.

 Caution

Ensure that the Create Test Users checkbox isn't enabled.

Installation Guide 64 PUBLIC Loading FS-QUO Contents into Product Configurator For details on the FS-PRO database user name prefix field, refer to the description of the substitution variable in the Substitution Variable Placeholders topic. For details on the other fields, refer to the context help on the screen. Choose Next when all information is provided. 8. On the Summary screen, review the summary and choose Next. 9. On the Progress screen, wait until the database update is completed. 10. On the Finish screen, review the results and choose Finish to exit.

4.2.6 Updating the SAP HANA Database for the Product Configurator Using the Database Update Wizard in Console Mode

You can use the Database Update Wizard in console mode to update the FS-QUO SAP HANA database for the Product Configurator environment.

Prerequisites

Context

To update the database in console mode, perform the following steps:

Procedure

1. Download the database update utility file: a. Go to Installations and Upgrades on the SAP Support Portal.

Installation Guide Loading FS-QUO Contents into Product Configurator PUBLIC 65 b. Choose Search for Software. c. Search for FS-QUO. d. Download and extract the following ZIP file: FS-QUO-db-..- unix.tar.gz using the tar -xvzf command. 2. Stop the Product Configurator instance using the SAP MMC. 3. From the ZIP file, extract the Database Update Wizard executable file: FS-QUO-db/bin/updateDB. 4. On the UNIX machine where the SAP HANA database server is installed, launch the Database Update Wizard executable file with the -c option: FS-QUO-db/bin/updateDB -c

 Caution

Ensure that the Create Test Users isn't enabled.

7. Review the summary information and press Enter . 8. Wait until the database update is completed.

9. Once complete, review the results and press Enter to exit.

If the database update fails, note the failure messages.

○ Check the database update logs and correct the problem. ○ Then restart the database update process. 10. Start the Product Configurator instance using the SAP MMC.

4.2.7 Updating the IBM DB2 Database for the Product Configurator Using the Database Update Wizard in GUI Mode

You can use the Database Update Wizard in GUI mode to update the FS-QUO IBM DB2 database for the Product Configurator. GUI mode provides an interactive, graphical interface to easily update the database.

Prerequisites

● You should have already set up a FS-PRO Product Configurator instance by following the steps outlined in the SAP Product Lifecycle Management for Insurance Installation Guide for SAP NetWeaver. ● Currently, the IBM DB2 Database Update Wizard can only be run from the IBM DB2 database server host.

Installation Guide 66 PUBLIC Loading FS-QUO Contents into Product Configurator Context

To update the database in GUI mode, perform the following steps:

Procedure

1. Download the database update utility file: a. Go to Installations and Upgrades on the SAP Support Portal. b. Choose Search for Software. c. Search for FS-QUO. d. Download the following ZIP file: FS-QUO-db-..-unix.tar.gz using the tar -xvzf command. 2. Stop the Product Configurator instance using the SAP MMC. 3. From the ZIP file, extract the Database Update Wizard executable file: FS-QUO-db/bin/updateDB. 4. Launch the Database Update Wizard executable file: FS-QUO-db/bin/updateDB 5. On the Welcome screen, choose Next. 6. On the Select Additional Tasks screen, choose Next. 7. On the Database Information form screen, provide all required information. In particular, set the Application type to Product Configurator and the Database type to IBM DB2.

 Caution

Ensure that the Create Test Users checkbox isn't enabled.

Installation Guide Loading FS-QUO Contents into Product Configurator PUBLIC 67 4.2.8 Updating the IBM DB2 Database for the Product Configurator Using the Database Update Wizard in Console Mode

You can use the Database Update Wizard in console mode to update the FS-QUO IBM DB2 database for the Product Configurator environment.

Prerequisites

● You should have already set up a FS-PRO Product Configurator instance by following the steps outlined in the SAP Product Lifecycle Management for Insurance Installation Guide for SAP NetWeaver. ● Currently, the IBM DB2 Database Update Wizard can only be run from the IBM DB2 database server host.

Context

To update the database in console mode, perform the following steps:

Procedure

 Caution

Ensure that the Create Test Users isn't enabled.

Installation Guide 68 PUBLIC Loading FS-QUO Contents into Product Configurator For details on the FS-PRO database user name prefix field, refer to the description of the substitution variable in the Substitution Variable Placeholders topic. Hit Enter when all information is provided. 7. On the Summary screen, review the summary and choose Next. 8. On the Progress screen, wait until the database update is completed.

9. Review the summary information and press Enter . 10. Wait until the database update is completed.

11. Once complete, review the results and press Enter to exit.

If the database update fails, note the failure messages. ○ Check the database update logs and correct the problem. ○ Then restart the database update process. 12. Start the Product Configurator instance using the SAP MMC.

Installation Guide Loading FS-QUO Contents into Product Configurator PUBLIC 69 5 Setting Up the Line of Business Bootstrap Products

You import product bootstraps based on your line of business (LoB) needs.

After importing, you build the relevant data models and products. Then, you update the product selection in the application configuration, set up Publish Manager in the Administrative Console, and finally publish and deploy.

Before proceeding, you need to determine which of the bootstraps to use. Select either Commercial PnC or any combination of the following other LoB insurance coverages:

● Personal PnC ● LnA (Life) ● Auto ● Longterm ● Group Insurance Master Policy

You don't need to import both types of bootstraps. Pick either PnC or LoB.

5.1 Configuring the Commercial PnC Bootstrap

5.1.1 Importing the Commercial PnC Bootstrap Products

After FS-PRO is customized, you must load some bootstrap data by importing the product definition JAR files from the FS-QUO artifact package into Product Configurator.

Prerequisites

Before beginning, ensure that you have imported the Product_Management_Bootstrap_1-0D.jar first as outlined in the SAP NetWeaver Installation Guide for SAP Product Lifecycle Management for Insurance.

Context

You need to import the following 3 bootstraps which are located within the bootstraps folder of the extracted archive file mentioned above:

● P_and_C_Insurance_Bootstrap_1-0D.jar

Installation Guide 70 PUBLIC Setting Up the Line of Business Bootstrap Products ● Underwriting_Application_Bootstrap_1-0D.jar ● Mock_GL_Underwriting_Bootstrap_1-0D.jar

To import the bootstrap data, perform the following steps:

Procedure

1. Extract the product JAR and bootstrap files from the FS-QUO-exports- ...zip archive file.

 Note

The bootstrap files within the zip archive are binary. If you are on a UNIX or Linux system, don't use the -a or -aa option with the unzip command when extracting these files.

2. Log in to FS-PRO at the following location: https://:/csiroot/ii/pc 3. Enter system as the user name and the correct password, then choose Log In.

If you haven't changed the password, enter password

4. In the Studio, go to File Import Product Wizard .

The Import Product Wizard dialog opens. 5. Choose Browse and select the P_and_C_Insurance_Bootstrap_1-0D.jar file. 6. Enter appropriate information in the Description and Comments fields, as the import process creates an audit record. 7. Choose Next>>.

The Import Options tab appears and the system begins comparing the JAR file to the target, looking for name conflicts and Final versions. No changes are made to the target. If any problems are found, the specified objects are listed in the Validation Issues panel. 8. The Input Options require you to choose between importing while keeping any changes you have made to the target product, or overwriting them with the product version or revision that you want to import. Because this is an upgrade, be sure to select the overwrite option. 9. The Input Type options allow you to import data alone, objects alone, or both together. For a first-time import you typically choose Both. If you are importing to an existing product, you must decide based on development needs. 10. By default, the key column settings are lost for any components that you are importing and that already exist in the target. Select the Key Column checkbox if you want the imported key column settings to overwrite all those existing in the target.

 Note

During the import process, use the default options and ignore any messages warning of conflicts.

11. Choose Next>>.

The Import tab appears and displays the progress of the import operation.

Installation Guide Setting Up the Line of Business Bootstrap Products PUBLIC 71  Caution

Ensure that the product is imported successfully.

An import operation automatically recreates the necessary paths within the Studio Tree for all the imported products and their objects. 12. To save the log file, choose Download Log. 13. Choose Done. 14. Commit all newly created data rows through the Locked Data Row Manager:

a. In the Studio, go to File Locked Data Row Manager .

The dialog opens and displays the names of objects with locked rows, the number of locked rows in each object, the path within the product or coverage to the rows, and who has locked them. b. Select all rows by enabling the checkbox in the heading row. c. Choose Commit and confirm your decision.

 Note

There may be multiple pages containing data rows to be committed.

15. Repeat steps 4 through 14 for the following bootstraps: ○ Underwriting_Application_Bootstrap_1-0D.jar ○ Mock_GL_Underwriting_Bootstrap_1-0D.jar

Next Steps

Next, you need to set up Publish Manager in the FS-PRO Administrative Console for the Commercial PnC Bootstrap.

Don't build or publish the imported products at this time. This will be done at a later stage of the installation process.

5.1.2 Setting Up Publish Manager in the Product Configurator Administrative Console for the Commercial PnC Bootstrap

Product Configurator provides functionality to publish and deploy insurance products to a Designer Runtime instance for runtime use.

Prerequisites

You must have already imported the Commercial PnC bootstrap products.

Installation Guide 72 PUBLIC Setting Up the Line of Business Bootstrap Products Context

To set up the Publish Manager with information about the Designer/Runtime environment, perform the following steps:

Procedure

1. Log into the Product Configurator Administrative Console at the following address: https://:/csiroot/admin

2. Go to Product Edit Product Deployments . 3. For each of the imported products, add an entry by choosing Add New and then choosing the search icon which will bring up the Object Picker window allowing you to enter the product name. Add the following products: ○ Mock Common UW Data Model ○ Extended Underwriting Application Configuration ○ Mock Reference Config ○ Mock GL Reference Countrywide ○ Mock GL Reference AL ○ Mock GL Reference CA ○ Mock GL Reference NV ○ Mock GL Reference OH V1 ○ Mock GL Reference OH V2 ○ Mock Commercial General Liability Monoline ○ Underwriting Application Data List

For each entry, define the following:

○ Server Name: Any name identifying the Designer Runtime instance to which the product is deployed. For example, you may use the host name and port number of the Designer Runtime instance as the name. ○ Server URL: :. For example: fsquo.mycompany.com:50004 ○ Context Path: com.sap.engine.services.jndi.InitialContextFactoryImpl 4. Save your changes. 5. To verify that the entries are added correctly, choose Test Connection to test the connection to the Designer Runtime instance. If the information was provided incorrectly, correct the information in the text fields of the list and choose Update to save the changes.

 Note

The FS-QUO server must be up in order for the Test Connection to work.

Installation Guide Setting Up the Line of Business Bootstrap Products PUBLIC 73 Next Steps

Next, you need to build the metadata for the data model (UW Application Reference Data Model). Then you need to build the products.

5.1.3 Building the Imported Commercial PnC Bootstrap Products

Context

To build the imported products, perform the following steps:

Procedure

1. Log in to Product Configurator at the following location: https://:/csiroot/ii/pc 2. In the Studio, use the Search view located at the bottom left to search for each product added in the Publish Manager and then double-click on the product in the search result to open it.

 Note

Build the metadata for UW Application Reference Data Model before any of the other products and data models.

3. Select Build Rules from the menu to build the rules. Leave the Include committed changes only option selected and both build options unselected. Review the log when the build process completes.

4. Select Build Metadata from the menu to build the metadata. Review the log when the build process completes.

5. Select Build Questionnaire Views from the menu to build questionnaire views. Review the log when the build process completes.

6. Select Build Screens from the menu to build screens. Leave the Include committed changes only option selected. Review the log when the build process completes.

Next Steps

Next, you need to update the product selection in FS-PRO

Installation Guide 74 PUBLIC Setting Up the Line of Business Bootstrap Products 5.1.4 Updating the Commercial PnC Bootstrap Product Selection

In order for a product to be available in a Designer Runtime instance, it needs to be selected in FS-PRO.

Context

To update the product selection, perform the following steps:

Procedure

1. Log in to Product Configurator at the following location: https://:/csiroot/ii/pc 2. Enter system as the user name and the correct password, then choose Log In.

If you haven't changed the password, enter password 3. Open Extended Underwriting Application Configuration. 4. Expand the Reference folder on the Product Tree. 5. Choose the Available Products component, and go to the Values tab. 6. Select All from the Views dropdown list. 7. Unselect the rows that aren't related to the products. 8. Save your changes on the Values tab.

Next Steps

Next, you need to publish and deploy the products.

Installation Guide Setting Up the Line of Business Bootstrap Products PUBLIC 75 5.1.5 Publishing and Deploying Imported Commercial PnC Bootstrap Products Into the Designer/Runtime Instance

After the Publish Manager settings are configured, you need to perform the actual publish and deployment to the Designer Runtime instance.

Context

To publish and deploy the bootstrap products, perform the following steps:

Procedure

1. Log in to Product Configurator at the following location: https://:/csiroot/ii/pc 2. In the Studio, use the Search view located at the bottom left to search for the product and then double- click on the product in the search result to open it.

3. For each product, go to File Publish Product , accept the default settings, and choose Execute Now. 4. A pop-up message notifies you when the publishing process completes.

 Tip

You can also check the status in the Studio under Tools Scheduled Activity Manager .

Results

The insurance products are now deployed to the Designer Runtime instance, which can then be used for underwriting once the Designer Runtime instance is configured as an underwriting engine.

5.2 Configuring the Personal Lines of Business (LoBs) Bootstrap

The LoB bootstraps have been consolidated into a single bootstrap file named SAP_Templates_Bootstrap_1- 0D.jar. This consolidation allows for the following efficiencies:

● Improve installation performance

Installation Guide 76 PUBLIC Setting Up the Line of Business Bootstrap Products ● Remove redundancies in bootstraps ● Simplify the install and upgrade process

This single bootstrap file contains the following bootstraps pertaining to the various personal LoBs:

● SAP Insurance Base Bootstrap ● SAP Insurance UWA Bootstrap ● SAP LnA Bootstrap ● SAP PnC Bootstrap ● SAP Longterm Bootstrap ● SAP Auto Bootstrap ● SAP Master Policy Bootstrap

This bootstrap is intended for a production environment only.

A second bootstrap file named SAP_Sample_Products_Bootstrap_1-0D.jar is also available. This file contains SAP_Templates_Bootstrap_1-0D.jar, as well as all of the sample product bootstraps:

● SAP Sample Household Bootstrap ● SAP Sample Life Bootstrap ● SAP Sample Master Policy

This bootstrap is intended for a sandbox environment only.

5.2.1 Importing the Personal LoB Bootstrap Products in a Production Environment

After FS-PRO is customized, you must load some bootstrap data by importing the bootstrap JAR files from the FS-QUO exports artifact package into Product Configurator.

Prerequisites

Ensure that you have imported the Product_Management_Bootstrap_1-0D.jar file as part of the your FS- PRO installation. For more information about importing the bootstraps, see the SAP NetWeaver Installation Guide for SAP Product Lifecycle Management for Insurance.

Installation Guide Setting Up the Line of Business Bootstrap Products PUBLIC 77 Context

To import the LoB bootstrap products in a production environment, perform the following steps:

Procedure

1. Extract the product JAR and bootstrap files from the FS-QUO-exports- ...zip archive file.

 Note

The bootstrap files within the zip archive are binary. If you are on a UNIX or Linux system, don't use the -a or -aa option with the unzip command when extracting these files.

2. Log in to FS-PRO at the following location: https://:/csiroot/ii/pc 3. Enter system as the user name and the correct password, then choose Log In.

If you haven't changed the password, enter password

4. In the Studio, go to File Import Product Wizard .

The Import Product Wizard dialog opens. 5. Choose Browse and select the SAP_Templates_Bootstrap_1-0D.jar file. 6. Enter appropriate information in the Description and Comments fields, as the import process creates an audit record. 7. Choose Next>>.

The Import tab appears and displays the progress of the import operation.

 Caution

Ensure that the product is imported successfully.

Installation Guide 78 PUBLIC Setting Up the Line of Business Bootstrap Products  Note

An import operation automatically recreates the necessary paths within the Studio Tree for all the imported products and their objects.

12. To save the log file, choose Download Log. 13. Choose Done. 14. Commit all newly created data rows through the Locked Data Row Manager:

a. In the Studio, go to File Locked Data Row Manager .

 Note

There may be multiple pages containing data rows to be committed.

Next Steps

Next, you need to set up Publish Manager in the FS-PRO Administrative Console for the Personal LoB Bootstrap.

Don't build or publish the imported products at this time. This will be done at a later stage of the installation process.

5.2.2 Importing Sample LoB Products in a Sandbox Environment

Sample products are provided specifically for a sandbox environment.

Prerequisites

Ensure that you have imported the Product_Management_Bootstrap_1-0D.jar. For more information about importing the bootstraps, see the SAP NetWeaver Installation Guide for SAP Product Lifecycle Management for Insurance.

Installation Guide Setting Up the Line of Business Bootstrap Products PUBLIC 79 Context

The sample offerings pertain to all lines of business and include the following products:

● SAP Sample Household Bootstrap ● SAP Sample Life Bootstrap ● SAP Sample Master Policy

 Note

There isn't a migration path for sample products if you have changed its original content. You should use sample products in sandbox environments only for evaluation and reference purposes. The sample products shouldn't be imported into a production Product Configurator environment.

To import the sample bootstrap products, perform the following steps:

Procedure

1. Log in to Product Configurator at the following location: https://:/csiroot/ii/pc 2. Enter system as the user name and the correct password, then choose Log In.

If you haven't changed the password, enter password

3. In the Studio, go to File Import Product Wizard .

The Import Product Wizard dialog opens. 4. Choose Browse and select the SAP_Sample_Products_Bootstrap_1-0D.jar file. 5. Enter appropriate information in the Description and Comments fields, as the import process creates an audit record. 6. Choose Next>>.

The Import Options tab appears and the system begins comparing the JAR file to the target, looking for name conflicts and Final versions. No changes are made to the target. If any problems are found, the specified objects are listed in the Validation Issues panel. 7. The Input Options require you to choose between importing while keeping any changes you have made to the target product, or overwriting them with the product version or revision that you want to import. Because this is an upgrade, be sure to select the overwrite option. 8. The Input Type options allow you to import data alone, objects alone, or both together. For a first-time import you typically choose Both. If you are importing to an existing product, you must decide based on development needs. 9. By default, the key column settings are lost for any components that you are importing and that already exist in the target. Select the Key Column checkbox if you want the imported key column settings to overwrite all those existing in the target. 10. Choose Next>>.

The Import tab appears and displays the progress of the import operation.

Installation Guide 80 PUBLIC Setting Up the Line of Business Bootstrap Products 11. To save the log file, choose Download Log. 12. Choose Done. 13. Commit all newly created data rows through the Locked Data Row Manager:

a. In the Studio, go to File Locked Data Row Manager .

 Note

There may be multiple pages containing data rows to be committed.

Next Steps

Don't build or publish the imported products. This will be done at a later stage of the installation process.

5.2.3 Setting Up Publish Manager in Product Configurator Administrative Console for the Personal LoB Bootstrap

Product Configurator provides functionality to publish and deploy insurance products to a Designer Runtime instance for runtime use.

Prerequisites

You must have already imported the LoB bootstrap products.

Installation Guide Setting Up the Line of Business Bootstrap Products PUBLIC 81 Context

To set up the Publish Manager with information about the Designer/Runtime environment, perform the following steps:

Procedure

1. Log in to the FS-PRO Administrative Console. https://:/csiroot/admin

Optionally, if you are in a sandbox environment, you can also add the following sample products that pertain to your line of business:

Personal PnC

○ Sample Household Product ○ Sample Household Product Traditional Chinese ○ Sample Household Product Korean ○ Sample Household Product Extended

LnA Life

○ Life Capital 2009 92H0000S0002

Master Policy

○ SAP Master Policy 4. Add an entry for each of the following data models pertaining to your line of business by choosing Add New:

Personal PnC

○ SAP Insurance Reference Data Model ○ SAP PnC Data Model ○ SAP PnC Combined Data Model

LnA Life

○ SAP Insurance Reference Data Model ○ SAP LnA Insurance Data Model ○ SAP LnA Combined Data Model

Auto

Installation Guide 82 PUBLIC Setting Up the Line of Business Bootstrap Products ○ SAP Auto Insurance Reference Data Model ○ SAP Auto Data Model ○ SAP Auto Combined Data Model

Longterm ○ SAP Insurance Reference Data Model

Master Policy ○ SAP Insurance Reference Data Model 5. For each entry, define the following: ○ Server Name: Any name identifying the Designer Runtime instance to which the product is deployed. For example, you may use the host name and port number of the Designer Runtime instance as the name. ○ Server URL: :. For example: fsquo.mycompany.com:50004 ○ Context Path: com.sap.engine.services.jndi.InitialContextFactoryImpl 6. Save your changes. 7. To verify that the entries are added correctly, choose Test Connection to test the connection to the Designer Runtime instance. If the information was provided incorrectly, correct the information in the text fields of the list and choose Update to save the changes.

 Note

The FS-QUO server must be up in order for the Test Connection to work.

8. Repeat this procedure for any other desired products.

5.2.4 Building and Publishing the Data Models for the Personal LoB Bootstrap

For each line of business, the corresponding data models need to be built and published.

Context

The following list shows which data models pertain to which line of business. Use this list to determine which data models to build and publish.

Personal PnC

● SAP Insurance Reference Data Model ● SAP PnC Data Model ● SAP PnC Combined Data Model

LnA Life

● SAP Insurance Reference Data Model

Installation Guide Setting Up the Line of Business Bootstrap Products PUBLIC 83 ● SAP LnA Insurance Data Model ● SAP LnA Combined Data Model

Auto

● SAP Auto Insurance Reference Data Model ● SAP Auto Data Model ● SAP Auto Combined Data Model

Longterm

● SAP Insurance Reference Data Model

Master Policy

● SAP Insurance Reference Data Model

To build and publish the data models for the LoB boostraps, perform the following steps:

Procedure

1. Log in to Product Configurator at the following location: https://:/csiroot/ii/pc 2. In the Studio, use the Search view located at the bottom left to search for a data model pertaining to your line of business and then double-click on the data model in the search result to open it.

3. Go to Build Metadata to build the metadata. Review the log when the build process completes.

4. Go to File Publish Product , accepting the default settings, and choose Execute Now. 5. A pop-up message notifies you when the publishing process completes.

You can also check the status in the Studio under Tools Scheduled Activity Manager . 6. Repeat steps 2 through to 5 for all the remaining data models pertaining to your line of business if needed.

5.2.5 Building the Imported Personal LoB Bootstrap Products

After you have built and published the data models, you need to build the products.

Prerequisites

Ensure that the data models have already been built, published, and deployed.

Installation Guide 84 PUBLIC Setting Up the Line of Business Bootstrap Products Context

Follow the steps in this procedure to build the following products:

● Extended Underwriting Application Configuration ● SAP Global Reference Object ● SAP Insurance UWA Data List

Optionally, if you are in a sandbox environment, you can also add the following sample products that pertain to your line of business:

Personal PnC

● Sample Household Product ● Sample Household Product Traditional Chinese ● Sample Household Product Korean ● Sample Household Product Extended

LnA Life

● Life Capital 2009 92H0000S0002

Master Policy

● SAP Master Policy

To build and publish the products for the LoB boostraps, perform the following steps:

Procedure

1. In Studio, use the Search view located at the bottom left to search for the product and then double-click on the product in the search result to open it.

2. Select Build Metadata from the menu to build the metadata. Review the log when the build process completes.

3. Select Build Questionnaire Views from the menu to build questionnaire views. Review the log when the build process completes.

4. Select Build Screens from the menu to build screens. Leave the Include committed changes only option selected. Review the log when the build process completes.

5. Select Build Rules from the menu to build the rules. Leave the Include committed changes only option selected and both build options unselected. Review the log when the build process completes.

 Note

This process may take an hour or more, depending on system performance.

Installation Guide Setting Up the Line of Business Bootstrap Products PUBLIC 85 Next Steps

Next, you need to update the product selection in FS-PRO

5.2.6 Updating the Personal LoB Bootstrap Product Selection (Sandbox Environment Only)

In order for a product to be available in a Designer Runtime instance, it needs to be selected in Product Configurator.

Prerequisites

The LoB data models must already be published and deployed.

Context

In a sandbox environment, you can select the following sample products that pertain to your line of business:

Personal PnC

● Sample Household Product ● Sample Household Product Traditional Chinese ● Sample Household Product Korean ● Sample Household Product Extended

LnA Life

● Life Capital 2009 92H0000S0002

Master Policy

● SAP Master Policy

To update the LoB product selection in your sandbox environment, perform the following steps:

Procedure

1. Log in to Product Configurator at the following location: https://:/csiroot/ii/pc 2. Enter system as the user name and the correct password, then choose Log In.

If you haven't changed the password, enter password

Installation Guide 86 PUBLIC Setting Up the Line of Business Bootstrap Products 3. Open Extended Underwriting Application Configuration. In the Search field, enter either the full or partial name of the Extended Underwriting Application Configuration product and choose Search. All matching objects will be displayed in the Search Results. Double-click on the desired item to open it. 4. Expand the Reference folder on the Product Tree. 5. Choose the Available Products component, and go to the Values tab. 6. Select All from the Views dropdown list. 7. Unselect the rows that aren't related to the products. 8. Save your changes on the Values tab.

Next Steps

Next, you need to publish and deploy the products.

5.2.7 Publishing the Imported Personal LoB Bootstrap Products

After the Publish Manager settings are configured, you need to perform the actual publish and deployment to the Designer Runtime instance.

Prerequisites

Ensure that the Personal LoB product data models have already been published

Context

In a sandbox environment, you can select the following sample products that pertain to your line of business:

Follow the steps in this procedure to publish the following products:

● Extended Underwriting Application Configuration ● SAP Global Reference Object ● SAP Insurance UWA Data List

Optionally, if you are in a sandbox environment, you can also add the following sample products that pertain to your line of business:

Personal PnC

● Sample Household Product

Installation Guide Setting Up the Line of Business Bootstrap Products PUBLIC 87 ● Sample Household Product Traditional Chinese ● Sample Household Product Korean ● Sample Household Product Extended

LnA Life

● Life Capital 2009 92H0000S0002

Master Policy

● SAP Master Policy

Procedure

3. Go to File Publish Product , accepting the default settings, and choose Execute Now. 4. A pop-up message notifies you when the publishing process completes.

You can also check the status in the Studio under Tools Scheduled Activity Manager . 5. Repeat this procedure for all the remaining products pertaining to your line of business if needed.

Results

The products are now built and published.

Installation Guide 88 PUBLIC Setting Up the Line of Business Bootstrap Products 6 Configuring the Designer and Runtime Environments for Underwriting

6.1 Creating JMS Resources for the Integration Framework (IFW)

FS-QUO requires some JMS resources for its Integration Framework (IFW) and Web Services features. Specifically a JMS queue connection factory and a number of JMS queues are required in the application server.

Prerequisites:

● As a prerequisite, a clean FS-PRO Designer/Runtime environment is required. Clean means a simple out- of-the-box installation, without customizations. For details, see the SAP Product Lifecycle Management for Insurance Installation Guide for SAP NetWeaver. ● The instructions assumes that you already have a database created for your instance and already installed on the NetWeaver server. ● An administrator or equivalent user with privileges in the NetWeaver Administrator web console to add a JMS Connection Factory and add JMS queues. If you don't have access to the NetWeaver Administrator web console, contact your IT department to configure the NetWeaver instance. ● The following settings for IFW are required for both Designer/Runtime instances. The Product Configurator instance doesn't require these settings.

Adding a JMS Connection Factory Reference

Create a new JMS Connection Factory Reference for the queue connection factory with the following settings.

Property Name Value

Settings Application Name Use the recommended name FS_QUO_IFW_QCF, or a name of your choice.

Settings Factory Name ifwConnection

Settings JMS Factory Type javax.jms.QueueConnectionFactory

All other fields should be left with the default values.

Installation Guide Configuring the Designer and Runtime Environments for Underwriting PUBLIC 89 Adding JMS Destination References

Create the following JMS Destination References for the three queues with the following settings.

Property Name Value

Settings Application Name 1. Use the recommended name FS_QUO_Queue_A, or a name of your choice. 2. Use the recommended name FS_QUO_Queue_B, or a name of your choice. 3. Use the recommended name FS_QUO_Queue_C, or a name of your choice.

Settings Destination Name 1. queue.A 2. queue.B 3. queue.C

Settings JMS Type javax.jms.Queue

Granting JMS Privileges

JMS permissions were revoked from the Everyone role after Netweaver 7.4 SP11 (see 2311866 for more details). Some permissions need to be granted in order for FS-QUO to be able to use JMS queues. Follow these steps to grant the appropriate permissions:

1. Sign into the SAP NetWeaver Administrator console. 2. Navigate to Configuration Security Identity Management . 3. Change the Search Criteria to Role, enter Everyone, and then select Go. 4. Select the Everyone row. 5. Select the Assigned Actions tab. 6. Select Modify. 7. Search for *jms*. 8. Select all the Service / Application with jms.default and jms_provider. 9. Select Add. 10. Save your changes.

6.2 Installing the FS-QUO Application

FS-QUO is an add-on component for the Designer/Runtime environment. After your product goes into runtime, FS-QUO generates a Policy Model using the information from the product JAR file and the form field data. The Policy Model is an XML representation of the data for a specific Policy transaction. The model is generated by

Installation Guide 90 PUBLIC Configuring the Designer and Runtime Environments for Underwriting FS-QUO and contains information from the FS-QUO Data Model and the Product Data Model assembled in Product Configurator.

Prerequisites

● A clean FS-PRO Designer/Runtime environment is required. "Clean" means a simple out-of-the-box installation, without customizations. For details, see the SAP Product Lifecycle Management for Insurance Installation Guide for SAP NetWeaver. ● The instructions assumes that you already have a database created for your instance and already installed on the NetWeaver server.

Context

To install the FS-QUO application, perform the following steps:

Procedure

1. Stop the instance using the SAP MMC. 2. Extract the FS-QUO-install-...zip into the directory for the FS-QUO Designer/Runtime instance. On UNIX and Linux, use the –a option with the unzip command. 3. Start the instance using the SAP MMC.

Installation Guide Configuring the Designer and Runtime Environments for Underwriting PUBLIC 91 6.3 Updating Configuration Settings

The configuration settings need to be updated as part of the FS-QUO installation process.

Context

To update the configuration settings, perform the following steps:

Procedure

1. Log in to the FS-QUO Administrative Console at the following address: http://<[FS- QUO_server_host]>:<[FS-QUO_server_http_port]>/csiroot/admin Log in with the Admin user account.

2. Choose System Edit Configuration Settings from the menu bar.

3. Go to Configuration Application Authority Suite . 4. Expand Env. 5. Select Application Environment. 6. Override RuntimeApplicationURL with https://:.

7. Go to Configuration Application AuthoritySuite Env Application Environment . The Application Environment settings display. a. In the Override field for the CustomIncludeScript row, enter /classpath/com/camilion/ renderer/multilevelrisk/web/js/CommonInclude.js, unless you received other configuration instructions. b. Save your changes.

8. Go to Configuration Application AuthoritySuite Env Application Environment . The Application Environment settings display. a. In the DefaultClientPage row, enable the Empty Value checkbox, unless you received other configuration instructions. b. Save your changes. 9. Save the settings.

10. Choose System Reload Configuration Settings from the menu bar. 11. Choose Reload All Config.

Installation Guide 92 PUBLIC Configuring the Designer and Runtime Environments for Underwriting 6.4 Importing Flowlet Groups in Designer

A flowlet is a representation and definition of a business process. A flowlet's data is stored in a container called a flowstore when running the process in the runtime client. A flowstore has one master table by default, and can have multiple child tables, each of which can have child tables of its own.

Prerequisites

Before you attempt this procedure, unzip the FS-QUO-exports-...zip to your local machine and not the server. Because these are binary files, don't use the -a or the -aa option with the unzip command to extract these files on UNIX and Linux.

Context

To import the flowlet JAR files to the Designer server, perform the following steps:

Procedure

1. Log in to the Designer at the following location: https://:/csiroot/author 2. Enter system as the user name and the correct password, then choose Log In.

If you haven't changed the password, enter password 3. In the Folders tree panel, select Applications.

4. In the Details panel which is to the right of the Folders tree panel, right-click and choose New Application . 5. Enter SAP Underwriting for Insurance as the application name and choose OK. 6. Import the flowlet groups as follows: a. In the Folders tree, select SAP Underwriting for Insurance. b. In the detail panel, right-click and choose Import Flowlet Group. c. Browse to the directory where you unzipped FS-QUO-exports-...zip, go to the flowlet_groups directory, select the flowlet JAR file to import, and choose Next.

 Restriction

The flowlet groups must be imported in the following order:

Installation Guide Configuring the Designer and Runtime Environments for Underwriting PUBLIC 93 Import Order Name of Flowlet Name of JAR File Version Introduced

1 Address Address-10004(lp- 3.0 SP00 flowlet-group).jar

2 Account Account-10005(lp- 3.0 SP00 flowlet-group).jar

3 PAS Client PAS_Client-10006(l 3.0 SP00 p-flowlet- group).jar

4 Producer Rep Producer_Rep-1000 3.0 SP00 7(lp-flowlet- group).jar

5 Producer Producer-10008(lp- 3.0 SP00 flowlet-group).jar

6 Task Item Task_Item-10009(lp 3.0 SP00 -flowlet- group).jar

7 Policy Policy-10010(lp- 3.0 SP00 flowlet-group).jar

8 Policy Processes Policy_Processes-1 3.0 SP00 0011(lp-flowlet- group).jar

9 Policy Quote Policy_Quote-1001 3.0 SP00 2(lp-flowlet- group).jar

10 Work Desk Work_Desk-10013(lp 3.0 SP00 -flowlet- group).jar

11 Delta Tracker Delta_Tracker-1001 3.0 SP00 4(lp-flowlet- group).jar

12 Display Delta Tracker Display_Delta_Trac 3.0 SP00 ker-10015(lp- flowlet-group).jar

13 UW Case UW_Case-10016(lp- 3.0 SP00 flowlet-group).jar

Installation Guide 94 PUBLIC Configuring the Designer and Runtime Environments for Underwriting Import Order Name of Flowlet Name of JAR File Version Introduced

14 Note Note-11004(lp- 3.0 SP00 flowlet-group).jar

15 Business Partner Business_Partner-1 3.0 SP02 0018(lp-flowlet- group).jar

16 Document Item Document_Item-1001 3.0 SP03 9(lp-flowlet- group).jar

17 Access Control Access_Control-110 3.0 SP03 03(lp-flowlet- group).jar

d. In the Flowlet Group Details screen, choose Next. e. In the Flowlet Group Validation screen, ensure that there aren't any validation errors and choose Next. f. In the details screen specific for the flowlet group being imported, choose Next to begin the import. g. When asked to specify a target name to rename the imported objects, choose Next. h. Wait for the import to complete. Some flowlet groups (like Policy Processes) take longer to finish. When the import completes, a message (in green) appears, indicating the completion at the end of the import log. Ensure that there aren't any errors in the import log, and choose Close.

6.5 Importing and Deploying the Scheme

You need to first import and then deploy the scheme.

Context

To import and deploy the scheme, perform the following steps:

Procedure

1. Log in to the Designer at the following location: https://:/csiroot/author 2. Enter system as the user name and the correct password, then choose Log In.

If you haven't changed the password, enter password

Installation Guide Configuring the Designer and Runtime Environments for Underwriting PUBLIC 95 3. In the Folders tree, select Applications.

4. Go to File Scheme Chooser . The Scheme Chooser opens. 5. Choose Import. 6. Search for the JAR file AS_Scheme-1(csslib).jar in the schemes directory of FS-QUO-exports- ...zip. 7. Accept the default scheme name AS Scheme when prompted by the Designer Import dialog and choose Next. 8. While still in Scheme Chooser after importing the scheme, choose the newly-imported scheme on the left panel and choose Edit on the bottom of the right panel. The Scheme Editor opens.

9. Select File Deploy to deploy the scheme. 10. Once the deployment completion messages are displayed, close the screen.

6.6 Building Imported Flowlets with the BatchFlowBuildServlet Tool

After the flowlets have been imported, they need to be built.

Prerequisites

The flowlets need to be successfully imported before attempting a build.

Context

To build the flowlets, perform the following steps:

Procedure

1. Run the following URL to invoke a process building all imported flowlets: https://:/csiroot/cservlet/ BatchFlowBuildServlet 2. There are some expected error messages in the log regarding child flowstores when the build process completes. These error messages can be safely ignored.

Installation Guide 96 PUBLIC Configuring the Designer and Runtime Environments for Underwriting  Note

The servlet will take some time to execute and will complete once the page stops loading.

6.7 Synchronizing Product Flowstores

A flowstore is a container for a flowlet's data when running the process in the runtime client. Every flowlet has one flowstore. A flowstore has one master table by default, and can have multiple child tables, each of which can have child tables of its own.

Context

This process will confirm the structure of your database tables matches the flowstore definitions defined in the Designer server.

If you have previously published the optional mock products or the Sample Household Product, follow the instructions below to synchronize the applicable product flowstore.

To synchronize a product flowstore, perform the following steps:

Procedure

1. Log in to the FS-QUO Administrative Console at the following address: http://<[FS- QUO_server_host]>:<[FS-QUO_server_http_port]>/csiroot/admin Log in with the Admin user account.

2. Choose Product Synchronize Product Flowstore from the Designer Administrative Console menu bar. 3. In the Product Name field, enter a product name based on the line of business you are configuring: ○ For the Commercial PnC LoB, enter Mock Commercial General Liability Monoline in the Product Name field. ○ For the Personal PnC: Enter Sample Household Product in the Product Name field. ○ For the Life LoB, enter Life Capital 2009 92H0000S0002 in the Product Name field. ○ For the Auto LoB, this field isn't applicable, as there isn't a sample product. ○ For the Longterm LoB, this field isn't applicable, as there isn't a sample product. ○ For the Master Policy LoB, enter SAP Master Policy in the Product Name field. 4. The system will process the flowstores in the product. When it's complete, you will see the process time at the end of the log. 5. Choose Next. 6. In the flowstore tree, select each of the flowstores in red, then choose Apply to sync the flow store.

Installation Guide Configuring the Designer and Runtime Environments for Underwriting PUBLIC 97 6.8 Updating Objects and Loading Data for Underwriting in the Designer Runtime Environment

Some database updates need to be applied to the Designer Runtime database using a database update utility to prepare the environment for the insurance underwriting workflow.

It's assumed that the database requirements for the respective database type, are already met.

Ensure that you have the correct UNIX shell software installed before attempting to update database objects.

 Note

It's only necessary to perform the update task that applies to your database type, using your preferred run mode.

6.8.1 Updating the Oracle Database Using the Database Update Wizard in GUI Mode

You can use the Database Update Wizard in GUI mode to update the FS-QUO Oracle database for the Designer Runtime environment. GUI mode provides an interactive, graphical interface to easily update the database.

Context

To update the database in GUI mode, perform the following steps:

Procedure

1. Download the database update utility file: Go to Installations and Upgrades on the SAP Support Portal. Choose Search for Software, search for FS- QUO and download the following zip file: ○ UNIX: FS-QUO-db-unix-...tar.gz ○ Windows: FS-QUO-db-windows-x64-...zip 2. Stop the Designer Runtime instance using the SAP MMC. 3. Extract the Database Update Wizard executable file from the ZIP file: ○ UNIX: FS-QUO-db/bin/updateDB ○ Windows: FS-QUO-db/bin/updateDB.exe 4. Launch the Database Update Wizard executable file: ○ UNIX: FS-QUO-db/bin/updateDB ○ Windows: FS-QUO-db/bin/updateDB.exe

Installation Guide 98 PUBLIC Configuring the Designer and Runtime Environments for Underwriting 5. On the Welcome screen, choose Next. 6. On the Select Additional Tasks screen, choose Next. 7. On the Database Information form screen, provide all required information. In particular, set the Application type to Designer Runtime and the Database type to Oracle. For details on the FS-QUO database user name prefix field, refer to the description of the substitution variable in the Substitution Variable Placeholders topic. For details on the other fields, refer to the context help on the screen. Choose Next when all information is provided.

 Note

If you wish to create test users for validation purposes, enable the Create Test Users checkbox. These test users can be removed at any time.

8. On the Summary screen, review the summary and choose Next. 9. On the Progress screen, wait until the database update is completed. 10. On the Finish screen, review the results and choose Finish to exit.

If the database update fails, note the failure messages. ○ Check the database update logs and correct the problem. ○ Then restart the database update process. 11. Start the Designer Runtime instance using the SAP MMC.

6.8.2 Updating the Oracle Database Using the Database Update Wizard in Console Mode

You can use the Database Update Wizard in console mode to update the FS-QUO Oracle database for the Designer Runtime environment.

Context

To update the database in console mode, perform the following steps:

Procedure

Installation Guide Configuring the Designer and Runtime Environments for Underwriting PUBLIC 99 ○ Windows: FS-QUO-db-windows-x64-...zip 2. Stop the Designer Runtime instance using the SAP MMC. 3. Extract the Database Update Wizard executable file from the ZIP file: ○ UNIX: FS-QUO-db/bin/updateDB ○ Windows: FS-QUO-db/bin/updateDB.exe 4. Launch the Database Update Wizard executable file with the -c option: ○ UNIX: FS-QUO-db/bin/updateDB -c ○ Windows: FS-QUO-db/bin/updateDB.exe -c 5. On the Create a response file only (no operation will be performed) prompt, choose the default option (n) by pressing Enter . 6. On the Database Information form, provide all required information. In particular, set the Application type to Designer Runtime and the Database type to Oracle. For details on the FS-QUO database user name prefix field, refer to the description of the substitution variable in the Substitution Variable Placeholders topic. Press Enter when all information is provided.

 Note

If you wish to create test users for validation purposes, enable the Create Test Users. These test users can be removed at any time.

the

7. Review the summary information and press Enter . 8. Wait until the database update is completed.

9. Once complete, review the results and press Enter to exit.

If the database update fails, note the failure messages.

○ Check the database update logs and correct the problem. ○ Then restart the database update process. 10. Start the Designer Runtime instance using the SAP MMC.

6.8.3 Updating the SAP HANA Database Using the Database Update Wizard in GUI Mode

You can use the Database Update Wizard in GUI mode to update the FS-QUO SAP HANA database for the Designer Runtime environment. GUI mode provides an interactive, graphical interface to easily update the database.

Prerequisites

Currently, the HANA Database Update Wizard can only be run from the HANA database server host

Installation Guide 100 PUBLIC Configuring the Designer and Runtime Environments for Underwriting Context

To update the database in GUI mode, perform the following steps:

Procedure

1. Download the database update utility file: Go to Installations and Upgrades on the SAP Support Portal. Choose Search for Software, search for FS- QUO and download the following zip file: FS-QUO-db-...tar.gz 2. Stop the Designer Runtime instance using the SAP MMC. 3. Extract the Database Update Wizard executable file from the ZIP file: FS-QUO-db/bin/updateDB 4. On the UNIX machine where the SAP HANA database server is installed, launch the Database Update Wizard executable file with the -c option: FS-QUO-db/bin/updateDB -c 5. On the Welcome screen, choose Next. 6. On the Select Additional Tasks screen, choose Next. 7. On the Database Information form screen, provide all required information. In particular, set the Application type to Designer Runtime and the Database type to SAP HANA. Also ensure the Container Mode is set to Multiple. For details on the FS-QUO database user name prefix field, refer to the description of the substitution variable in the Substitution Variable Placeholders topic. For details on the other fields, refer to the context help on the screen. Choose Next when all information is provided.

 Note

If you wish to create test users for validation purposes, enable the Create Test Users checkbox. These test users can be removed at any time.

Installation Guide Configuring the Designer and Runtime Environments for Underwriting PUBLIC 101 6.8.4 Updating the SAP HANA Database Using the Database Update Wizard in Console Mode

You can use the Database Update Wizard in console mode to update the FS-QUO SAP HANA database for the Designer Runtime environment.

Prerequisites

Currently, the HANA Database Update Wizard can only be run from the HANA database server host

Context

To update the database in GUI mode, perform the following steps:

Procedure

1. Download the database update utility file: Go to Installations and Upgrades on the SAP Support Portal. Choose Search for Software, search for FS- QUO and download the following zip file: FS-QUO-db-...tar.gz 2. Stop the Designer Runtime instance using the SAP MMC. 3. Extract the Database Update Wizard executable file from the ZIP file: FS-QUO-db/bin/updateDB 4. On the UNIX machine where the SAP HANA database server is installed, launch the Database Update Wizard executable file with the -c option: FS-QUO-db/bin/updateDB -c 5. On the Create a response file only (no operation will be performed) prompt, choose the default option (n) by pressing Enter . 6. On the Database Information form, provide all required information. In particular, set the Application type to Designer Runtime and the Database type to SAP HANA. Also ensure the Container Mode is set to Multiple. For details on the FS-QUO database user name prefix field, refer to the description of the substitution variable in the Substitution Variable Placeholders topic. For details on the other fields, refer to the context help on the screen. Choose Next when all information is provided.

 Note

If you wish to create test users for validation purposes, enable the Create Test Users. These test users can be removed at any time.

Installation Guide 102 PUBLIC Configuring the Designer and Runtime Environments for Underwriting 7. Review the summary information and press Enter . 8. Wait until the database update is completed.

9. Once complete, review the results and press Enter to exit.

If the database update fails, note the failure messages. ○ Check the database update logs and correct the problem. ○ Then restart the database update process. 10. Start the Designer Runtime instance using the SAP MMC.

6.8.5 Updating the Microsoft SQL Server Database Using the Database Update Wizard in GUI Mode

You can use the Database Update Wizard in GUI mode to update the FS-QUO Microsoft SQL Server database for the Designer Runtime environment. GUI mode provides an interactive, graphical interface to easily update the database.

Context

To update the database in GUI mode, perform the following steps:

Procedure

1. Download the database update utility file: Go to Installations and Upgrades on the SAP Support Portal. Choose Search for Software, search for FS- QUO and download the following zip file: FS-QUO-db-windows-x64-...zip 2. Stop the Designer Runtime instance using the SAP MMC. 3. Extract the Database Update Wizard executable file from the ZIP file: FS-QUO-db/bin/updateDB.exe 4. Launch the Database Update Wizard executable file with the -c option: FS-QUO-db/bin/updateDB.exe 5. On the Welcome screen, choose Next. 6. On the Select Additional Tasks screen, choose Next. 7. On the Database Information form screen, provide all required information. In particular, set the Application type to Designer Runtime and the Database type to Microsoft SQL Server. For details on the FS- QUO database user name prefix field, refer to the description of the substitution variable in the Substitution Variable Placeholders topic. For details on the other fields, refer to the context help on the screen. Choose Next when all information is provided.

 Note

If you wish to create test users for validation purposes, enable the Create Test Users checkbox. These test users can be removed at any time.

Installation Guide Configuring the Designer and Runtime Environments for Underwriting PUBLIC 103 8. On the Summary screen, review the summary and choose Next. 9. On the Progress screen, wait until the database update is completed. 10. On the Finish screen, review the results and choose Finish to exit.

If the database update fails, note the failure messages.

○ Check the database update logs and correct the problem. ○ Then restart the database update process. 11. Start the Designer Runtime instance using the SAP MMC.

6.8.6 Updating the Microsoft SQL Server Database Using the Database Update Wizard in Console Mode

You can use the Database Update Wizard in console mode to update the FS-QUO Microsoft SQL Server database for the Designer Runtime environment.

Context

To update the database in console mode, perform the following steps:

Procedure

1. Download the database update utility file: Go to Installations and Upgrades on the SAP Support Portal. Choose Search for Software, search for FS- QUO and download the following zip file: FS-QUO-db-windows-x64-...zip 2. Stop the Designer Runtime instance using the SAP MMC. 3. Extract the Database Update Wizard executable file from the ZIP file: FS-QUO-db/bin/updateDB.exe 4. Launch the Database Update Wizard executable file with the -c option: FS-QUO-db/bin/updateDB.exe -c 5. On the Create a response file only (no operation will be performed) prompt, choose the default option (n) by pressing Enter . 6. On the Database Information form screen, provide all required information. In particular, set the Application type to Designer Runtime and the Database type to Microsoft SQL Server. For details on the FS- QUO database user name prefix field, refer to the description of the substitution variable in the Substitution Variable Placeholders topic. Press Enter when all information is provided.

Installation Guide 104 PUBLIC Configuring the Designer and Runtime Environments for Underwriting  Note

If you wish to create test users for validation purposes, enable the Create Test Users. These test users can be removed at any time.

7. Review the summary information and press Enter . 8. Wait until the database update is completed.

9. Once complete, review the results and press Enter to exit.

6.8.7 Updating the IBM DB2 Database Using the Database Update Wizard in GUI Mode

You can use the Database Update Wizard in GUI mode to update the FS-QUO IBM DB2 database for the Designer Runtime environment. GUI mode provides an interactive, graphical interface to easily update the database.

Prerequisites

Currently, the IBM DB2 Database Update Wizard can only be run from the IBM DB2 database server host

Context

To update the database in GUI mode, perform the following steps:

Procedure

Installation Guide Configuring the Designer and Runtime Environments for Underwriting PUBLIC 105 5. On the Welcome screen, choose Next. 6. On the Select Additional Tasks screen, choose Next. 7. On the Database Information form screen, provide all required information. In particular, set the Application type to Designer Runtime and the Database type to IBM DB2. For details on the FS-QUO database user name prefix field, refer to the description of the substitution variable in the Substitution Variable Placeholders topic. For details on the other fields, refer to the context help on the screen. Choose Next when all information is provided.

 Note

If you wish to create test users for validation purposes, enable the Create Test Users checkbox. These test users can be removed at any time.

If the database update fails, note the failure messages.

○ Check the database update logs and correct the problem. ○ Then restart the database update process. 11. Start the Designer Runtime instance using the SAP MMC.

6.8.8 Updating the IBM DB2 Database Using the Database Update Wizard in Console Mode

You can use the Database Update Wizard in console mode to update the FS-QUO IBM DB2 database for the Designer Runtime environment.

Prerequisites

Currently, the IBM DB2 Database Update Wizard can only be run from the IBM DB2 database server host

Context

Installation Guide 106 PUBLIC Configuring the Designer and Runtime Environments for Underwriting To update the database in GUI mode, perform the following steps:

Procedure

1. Download the database update utility file: Go to Installations and Upgrades on the SAP Support Portal. Choose Search for Software, search for FS- QUO and download the following zip file: FS-QUO-db-unix-...tar.gz 2. Stop the Designer Runtime instance using the SAP MMC. 3. Extract the Database Update Wizard executable file from the ZIP file: FS-QUO-db/bin/updateDB 4. Launch the Database Update Wizard executable file with the -c option: FS-QUO-db/bin/updateDB -c 5. On the Create a response file only (no operation will be performed) prompt, choose the default option (n) by pressing Enter . 6. On the Database Information form, provide all required information. In particular, set the Application type to Designer Runtime and the Database type to IBM DB2. For details on the FS-QUO database user name prefix field, refer to the description of the substitution variable in the Substitution Variable Placeholders topic. Press Enter when all information is provided.

 Note

If you wish to create test users for validation purposes, enable the Create Test Users. These test users can be removed at any time.

7. Review the summary information and press Enter . 8. Wait until the database update is completed.

9. Once complete, review the results and press Enter to exit.

6.9 Pre-Loading Products Into Memory

Pre-loading products into memory will decrease response time after the application server has been started.

Context

If you have previously published the optional mock products or the Sample Household Product, follow the instructions below to synchronize the applicable product flowstore.

Installation Guide Configuring the Designer and Runtime Environments for Underwriting PUBLIC 107 To pre-load products into memory, perform the following steps:

Procedure

1. Run the following URL: https://:/ csiroot/cservlet/GenerateProductModelXSD. A screen displays showing a list of products that were imported and built previously during the installation process. 2. Select the checkbox for relevant products displayed in the list, based on line of business: ○ For the Commercial PnC LoB, enable the Mock Commercial General Liability Monoline checkbox. ○ For Personal PnC, enable the Sample Household Product, Sample Household Product Traditional Chinese,Sample Household Product Korean,Sample Household Product Extended, and Sample Household Product Japanese checkboxes. ○ For the Life LoB, enable the Life Capital 2009 92H0000S0002 checkbox. ○ For the Auto LoB, this field isn't applicable, as there isn't a sample product. ○ For the Longterm LoB, this field isn't applicable, as there isn't a sample product. 3. Choose Submit Query.

Results

A confirmation message displays after all products are pre-loaded into memory.

 Note

Repeat this procedure each time the application server is stopped and then re-started.

Installation Guide 108 PUBLIC Configuring the Designer and Runtime Environments for Underwriting 6.10 Validating the Installation

After the installation process is complete, it is best practice to validate that the installation was successful.

Context

To validate the FS-QUO installation, perform the following steps:

Procedure

1. Log into FS-QUO using the following URL:. https://:/csiroot 2. Enter uw2 as the user name and password as the password, then choose Log In. 3. Choose About. The About SAP Underwriting for Insurance dialog displays. 4. Verify the following information displays: Version ..

Results

The installation is verified.

Installation Guide Configuring the Designer and Runtime Environments for Underwriting PUBLIC 109 7 Integrating with FS-IPW

SAP Workplaces for Insurance (FS-IPW) provides many of the same features as FS-QUO using the SAP Fiori interface. SAP Fiori is a collection of apps with a simple and easy-to-use experience for broadly used SAP software functions that work seamlessly across devices – desktop, tablet, and smartphone.

To integrate FS-QUO with FS-IPW, the following features must be configured:

● Virus Scan Interface ● SAP Mobile Documents ● CMS Settings

See the SAP Workplaces for Insurance Installation Guide for further information.

7.1 Configuring the Virus Scan Interface (VSI)

You can use the Virus Scan Interface to include external virus scanners in the SAP system to increase the security of your system.

Context

The interface consists of two parts: an external part for the certified anti-virus products of the various vendors and an internal part, with which you can integrate the virus scan functions into your own applications.

 Note

For more information and a list of the certified products for the interface (VSI), see SAP Note 786179 .

FS-QUO uses Virus Scan Adapter as Virus Scan Provider.

After you have installed an external anti-virus product including a certified adapter, you only need to enter the path to the adapter specified in the documentation for the partner product in the VSA_LIB field.

To configure a Virus Scan Adapter for a Purely-Java Installation, perform the following steps:

Procedure

1. Go to the NetWeaver Visual Administrator page at https://:/nwa and log on as the administrator.

2. Go to the Virus Scan Provider page with the following path: Configuration Security Virus Scan Provider .

Installation Guide 110 PUBLIC Integrating with FS-IPW 3. Choose Edit to enter editing mode. 4. Define a Scanner Group. 5. Define a Virus Scan Provider. 6. Define a Virus Scan Profile.

7.2 Configuring SAP Mobile Documents as a CMS service

In FS-QUO, you can upload files, such as documents or pictures, as evidence or attachment in notes. To manage these files, you can use tools which use industry standard CMIS (Content Management Interoperability Services).

By default, FS-QUO uses SAP Mobile Documents, which is SAP's solution for secure mobile content management.

For more information about setting up and using SAP Mobile Documents, see the SAP Documentation .

7.3 Configuring CMS settings for SAP Mobile Documents

The Content Management Server (CMS) settings must be configured in the Administrative Console.

Context

To configure the CMS settings in the Administrative Console, perform the following steps:

Procedure

1. Log in to the FS-QUO Administrative Console at the following address: http://<[FS- QUO_server_host]>:<[FS-QUO_server_http_port]>/csiroot/admin

2. Choose System Edit Configuration Settings from the menu bar.

3. Go to Configuration System Env Content Management System Setting . 4. Enter the following value in the CMSService field: com.sap.fs.uw.cms.service.smd.SAPMobileDocumentsService. If you aren't using SAP Mobile Documents as the CMS service, modify this value accordingly. 5. Enter the URL of the Content Management Service in the CMSServerURL field. 6. Enter the logon user of the Content Management Service in the CMSServerUser field. 7. Enter the password of the logon user of the Content Management Service in the CMSServerPassword field.

Installation Guide Integrating with FS-IPW PUBLIC 111 8. Choose save and reload.

Installation Guide 112 PUBLIC Integrating with FS-IPW 8 Setting Up the Scheduler

FS-QUO provides an optional feature for scheduling insurance policy renewals using a stand-alone scheduler, which is useful for automated batch processing.

It is a Java-based, command-line application based on the Quartz framework, which makes a policy renewal web service request to an FS-QUO runtime environment on any desired schedule.

The scheduler requires the following on the system running it:

● Java SE Runtime Environment (JRE) 8 or Java SE Development Kit (JDK) 8. (The environment variable must be set.) ● Connection to the FS-QUO server, so that it can make web service requests.

8.1 Installing the Scheduler

The scheduler can be installed on any Windows, UNIX or Linux server that your IT organization deems appropriate. For consolidation purposes, you can run it on the server where FS-QUO is running on NetWeaver.

Procedure

1. Unzip FS-QUO-scheduler-...zip to a local directory. A directory named FS-QUO-scheduler is created. 2. (UNIX and Linux only) In a command prompt, change to the FS-QUO-scheduler directory and run the following command to change the permission of shell script: chmod 750 *.sh

Installation Guide Setting Up the Scheduler PUBLIC 113 8.2 Configuring the Scheduler

8.2.1 Encoding Security-Sensitive Information

The scheduler requires that the password of the user making the web service request to the FS-QUO server be set in the scheduler configuration file.

Context

To avoid putting passwords into the configuration file in plain text, the scheduler provides a tool that you can use to encode such information before saving it in the configuration file. Keep in mind this is only a rudimentary security measure – you should combine it with other operating system and physical security measures to ensure that your information is safe.

Follow the steps below to obtain encoded values that can be put into the scheduler configuration file:

Procedure

1. In a command prompt, change to the FS-QUO-scheduler directory where the scheduler is installed. 2. Depending on your operating system, run one of the following commands: ○ Windows: encode.bat ○ UNIX and Linux: ./encode.sh 3. When prompted to enter a string to encode, type in the web service user password to be encoded and press Enter. The encoded string is displayed. 4. Copy the string and set the request.webServiceUserPassword property in the scheduler settings as per the next section.

Installation Guide 114 PUBLIC Setting Up the Scheduler 8.2.2 Configuring the Scheduler Settings

After you have encoded the security-sensitive information, you need to configure the schedule settings.

Context

Follow the steps below to configure the scheduler settings:

Procedure

1. Make a copy of FS-QUO-scheduler/config/scheduler.properties.template as FS-QUO- scheduler/config/scheduler.properties. 2. Open FS-QUO-scheduler/config/scheduler.properties with a text editor and provide all required settings. For details for each property, refer to the comments in scheduler.properties.

Results

The scheduler settings are now configured.

8.3 Running the Scheduler

After you install and configure the scheduler, it needs to be started.

Procedure

1. In a command prompt window, change to the FS-QUO-scheduler directory where the scheduler is installed. 2. Depending on your operating system, run one of the following commands: ○ Windows: scheduler.bat ○ UNIX and Linux: ./scheduler.sh

Installation Guide Setting Up the Scheduler PUBLIC 115 Results

The scheduler is now started and you will see information message displayed in the console.

8.4 Shutting Down the Scheduler

The scheduler is a long-running Java process, that may have to be stopped occasionally.

Procedure

1. Select the command prompt window in which the scheduler is run. 2. Press Ctrl+C on your keyboard to send a kill signal to the process. Information messages are displayed in the console notifying you that the scheduler is being shut down. 3. In a Windows environment, you are prompted whether to terminate batch process. Enter Y to terminate it.

Results

This scheduler is now shut down.

8.5 Troubleshooting the Scheduler

In addition to the information displayed in the console, the scheduler also provides additional details about the process in the following locations:

FS-QUO- Contains the same informational messages that are displayed in the console. This is scheduler/log/ useful for reviewing historical activities since the console log would eventually be scheduler.log truncated.

FS-QUO-scheduler/ Contains the web service SOAP request XML files that are generated and used when requests the policy renewal web service is invoked by the scheduler. The file name of the XML file corresponds to the date and time when the request was made by the scheduler. Note that security-sensitive information such as user names and passwords are masked in the request XML file.

FS-QUO-scheduler/ Contains the web service SOAP response XML file that the server returned when a response policy renewal web service was made by the scheduler. As with the files in the requests directory, the name of the XML file corresponds to the date and time when

Installation Guide 116 PUBLIC Setting Up the Scheduler the request was made by the scheduler. You can therefore locate the request and response XML files of the same request based on the file name.

Installation Guide Setting Up the Scheduler PUBLIC 117 9 Clustering

Clustering lets you deploy FS-PRO and FS-QUO environments across multiple servers. This configuration helps you better support teams of users concurrently configuring products. Clustering allows for better scaling for a given number of users.

In a clustered environment, changes made by developers on one server are immediately available to developers on other servers in the cluster. Published products are also available to all users in the cluster. Similarly, any configuration changes an administrator makes on one server are immediately applied to the other servers in the cluster.

 Note

FS-PRO and FS-QUO clustering works with SAP NetWeaver clustering. That is, a cluster must be deployed on a NetWeaver distributed system.

SAP NetWeaver clustering provides the ability to scale up and down as needed. If you are unsure about the size of your initial cluster, then start with a SAP NetWeaver cluster that consists of only one instance. To scale up, add more instances to the cluster; to scale down, remove instances from the cluster and bring it back down to a single instance. You don't need to remove the cluster, as a cluster of one runs like a standalone application server.

Clustering works as follows:

Distributed The caches in FS-PRO and FS-QUO are distributed. This configuration removes "stale" Caching copies of objects from memory. Each application server within the cluster notifies its peers of changes and removes objects from the caches. EHCache using JMS is used to transport the invalidate messages to a topic.

Change Event Similar to distributed caching, other changes to system or object states must be Management communicated to an application server's peers to update their changes. This also uses JMS to act as a transport for the messages.

Shared Sharing this directory lets all the generated content to be shared across the cluster. To avoid files (such as log files) clashing, the directory contains files that directory can't be shared for each application server. This directory value targets a different location for each application server of the cluster.

Shared database A shared database helps ensure that all application servers change the same data and all application servers have access to the same data. Database redundancy is achieved by leveraging the high availability features within the Database Management System (DBMS).

With these changes, the following elements are synchronized across the NetWeaver distributed system:

● Caches ● FS-PRO and FS-QUO configuration settings ● Uploaded custom classes and files (also, uploading new files causes the affected classloaders to refresh) ● Generated content (that is, product JAR files, rules, and so on) is common among all the application servers

Installation Guide 118 PUBLIC Clustering The directory can either be placed on the file system of one cluster member and shared among all other cluster members, or in a central file server (for example, a Storage Area Network) that is shared across the cluster. All cluster members must have read/write access to the shared directory.

9.1 Prerequisites for Clustering

Before implementing clustering, a NetWeaver distributed system must be available for deployment.

In addition, a NetWeaver Web Dispatcher instance must be available as the entry point to the NetWeaver distributed system. Apache ActiveMQ must also be available for distributed caching.

To configure ActiveMQ, refer to the Installing ActiveMQ topic for detailed instructions.

Related Information

Supported Shell Software for FS-QUO [page 14]

9.2 Checklist for Setting Up Clustering

FS-PRO and FS-QUO clustering works with NetWeaver clustering. A cluster must be deployed on a NetWeaver distributed system, and you must use Apache ActiveMQ for distributed caching.

 Note

Clustering is optional. If your organization doesn't intend to use this feature at this time, skip this section. Creating a clustered environment in the future is still possible but requires some system down time and reconfiguring.

To set up clustering, perform the following tasks:

1. Install FS-PRO using the installer on the primary host of the NetWeaver distributed system. 2. Enabling a shared directory 3. Configuring NetWeaver for FS-PRO or FS-QUO clustering 4. Configuring the SAP Web Dispatcher 5. Configuring an Application Server for Clustering 6. Restart the NetWeaver distributed system.

Related Information

Supported Shell Software for FS-QUO [page 14]

Installation Guide Clustering PUBLIC 119 9.2.1 Enabling a Shared CSI Home Directory

Each host containing an application server instance in the cluster must access the shared directory on a network share.

The directory must be shared and accessible (with read and write access) to all NetWeaver instances in the distributed system.

Follow the instructions for your system to do the following:

● On Windows, the directory can be shared with mapped network drives. ● On UNIX and Linux, the directory can be shared with NFS mounts.

After you enable the shared directory, note the path to this directory, either as the network share address on Windows or the NFS mount on UNIX/Linux. You need this path to complete the cluster configuration.

9.2.2 Configuring NetWeaver for FS-PRO or FS- QUO Clustering

You will need to set some JVM parameters in NetWeaver to configure FS-PRO and FS-QUO for clustering.

Context

The following table describes the JVM parameters to configure in NetWeaver for FS-PRO and FS-QUO clustering and the differences between the parameters:

Parameter In standard environment In clustered environment

-DCSI.home Contains a pointer to the main direc Contains content that is shared by all tory. members of the cluster.

Points to the shared di rectory.

-DLocal.home Not used. Contains only configuration settings specific to each member of the cluster (for example, logs and other temporary files).

Installation Guide 120 PUBLIC Clustering To configure NetWeaver for FS-PRO or FS-QUO clustering, perform the following steps:

Procedure

1. Launch the NetWeaver AS Java Config Tool for the instance where FS-PRO or FS-QUO is deployed (the primary host). 2. For each application server instance in the cluster, define the following JVM parameters: -DCSI.home Specifies the fully-qualified path and host name of the shared directory of the cluster. All application server instances use the same directory. -DLocal.home Specifies the local path to the individual localhome of the application server instance. Each application server instance requires a unique localhome. ○ Use forward slashes (/) only. For Windows, substitute the backslash character (\) in paths with a forward slash (/). For example, if the network share to the shared directory is \ \\, then enter ///// for -DCSI.home setting. The four forward (/) slashes is the proper notation for specifying an UNC name in a java command. ○ If you use the System tab to set the parameters, you don't need the leading -D. If you use the Additional tab to set the parameters, you need the leading -D. 3. Configure the JVM memory sizes at the instance level as appropriate. At a minimum, set the maximum heap size to 4096 MB. 4. Restart the instance using the SAP MMC.

9.2.3 Configuring the SAP Web Dispatcher

In the SAP Web Dispatcher, you need to define a single entry point to the cluster.

Procedure

1. Open the profile file of the SAP Web Dispatcher instance with a text editor. The file is typically located at: /usr/sap//SYS/profile/ __ 2. Add the following parameters to the profile file:

icm/server_port_ = PROT=HTTP,HOST=,PORT=

wdisp/system_ = SID=,SSL_ENCRYPT=0,MSHOST=,MSPORT=,S RCSRV=*:,SRCURL=/csiroot

Installation Guide Clustering PUBLIC 121 and Specifies a number without a leading 0 that isn't already used within the profile for the specified parameter.

Specifies the host name of the machine where the SAP Web Dispatcher is installed.

Specifies the single entry point to the cluster.

Specifies the SID of the NetWeaver distributed system.

Specifies the fully qualified host name of the machine where the message server of the NetWeaver distributed system is installed.

Specifies the HTTP port of the message server.

3. Save the profile file. 4. Restart the SAP Web Dispatcher instance.

9.2.4 Configuring an Application Server for Clustering

To add clustering to your environment, you only need to configure a single application server instance. These changes automatically apply to all of the application server instances in the NetWeaver distributed system.

Context

To configure an application server for clustering, perform the following steps:

Procedure

1. Log into the Administrative Console.

2. Choose System Edit Configuration Settings from the menu bar.

The Configuration tree displays.

3. Choose Configuration PS Env Cluster Settings . The Cluster settings display. 4. In the ClusterEnabled row, select Yes in the Override field. 5. In the ClusterJMSBrokerURL row, enter the URL to connect your installed ActiveMQ using TCP protocol in the Override field, as shown in the following example: failover:(tcp://:)

Specifies the computer name where ActiveMQ is installed.

Specifies the port that the ActiveMQ server is listening on.

6. In the ClusterJmsUsername row, enter the user name for connecting to ActiveMQ in the Override field. The default user name for ActiveMQ is typically system, but your system administrator might have set up

Installation Guide 122 PUBLIC Clustering other uses for use with Product Configurator. Check with your system administrator for ActiveMQ login details as needed. 7. In the ClusterJmsPassword row, enter the password for connecting to ActiveMQ in the Override field. The default password for the system user for ActiveMQ is typically manager, but your system administrator might have set up other uses for use with Product Configurator. Check with your system administrator for ActiveMQ login details as needed. 8. In the ClusterCacheTopic row, enter any value for the cache topic name. We recommend the following format: __cacheTopic 9. In the ClusterCacheQueue row, enter any value for the cache queue name. We recommend the following format: __cacheQueue 10. In the ClusterEventTopic row, enter any value for the event topic name. We recommend the following format: __eventTopic

 Note

All members of the same cluster must have the same ClusterCacheTopic, clusterCacheQueue, and ClusterEventTopic

11. Save your changes.

12. Choose System Reload Configuration Settings from the menu bar. 13. Choose Reload PS Config.

Results

The application server is configured for clustering.

Installation Guide Clustering PUBLIC 123 10 Uninstalling FS-QUO

10.1 Undeploying the SCA

When you are uninstalling FS-QUO, undeploy the SCA.

The SCA file can be undeployed using the Software Update Manager (SUM) tool or using the Telnet administration interface.

10.1.1 Undeploying the SCA Using Telnet

By using a Telnet client through the Telnet protocol, connect to the SAP NetWeaver Application Server and undeploy your SCA file.

Prerequisites

A connection can be established if the AS Java system is installed and running, and the machine has a Telnet client through which a connection to the server can be established.

Procedure

1. Open a command prompt and run the following command:

telnet localhost 508

where is the system number of the AS Java instance (next to the thin server icon in SAP MMC). The telnet port is the HTTP port for your instance + 8. 2. Log in with NetWeaver Administrator credentials. 3. Once logged in, you will undeploy the component: FS-QUO-ear by executing the following commands:

add deploy undeploy vendor=sap.com name=FS-QUO-ear

4. Ensure the output messages display a successful undeployment.

For further details on using telnet, refer to the following article in the SAP Library Administration Using Telnet.

Installation Guide 124 PUBLIC Uninstalling FS-QUO 10.1.2 Undeploying the SCA Using SUM

The Software Update Manager (SUM) is a multi-purpose tool that supports various processes, such as performing a release upgrade and installing enhancement packages among other things. As such, SUM can be used to undeploy your SCA file.

Context

For full details, refer to the Update of SAP Systems using Software Update Manager guide in the Installation and Upgrade section of the SAP NetWeaver 7.5 Help Portal Page

10.2 Removing Related Configurations from NetWeaver

When you are uninstalling FS-QUO, remove the configuration information in NetWeaver.

Prerequisites

The FS-QUO SCA has been undeployed.

Context

Procedure

1. Delete the JDBC and JMS resources used by FS-QUO in NWA. 2. Reset the related NetWeaver JVM and profile settings in the AS Java Config Tool for offline configuration (configtool) and the SAP Web Dispatcher Web Administration Interface.

Installation Guide Uninstalling FS-QUO PUBLIC 125 10.3 Deleting the FS-QUO Database

Use the Database Deletion Wizard to delete an FS-QUO database for IBM DB2, Oracle, Microsoft SQL Server, or SAP HANA for the Designer Runtime environment.

You can choose to run the Database Deletion Wizard in GUI mode (typical), console mode or unattended mode.

The Database Deletion Wizard is part of the database installer.

It is assumed that the database requirements have been met.

 Note

From the following three sections, perform only the procedure matching your database type, either IBM DB2, Oracle, Microsoft SQL Server, or SAP HANA.

Related Information

Supported Shell Software for FS-QUO [page 14]

10.3.1 Deleting the FS-QUO Oracle Database in GUI Mode

Use the Database Deletion Wizard to delete an FS-QUO Oracle database for the Designer Runtime environment. You can choose to run the Database Deletion Wizard in GUI mode, which provides an interactive, graphical interface to easily delete the database.

Context

To delete the database in GUI mode, perform the following steps:

Procedure

1. On the machine with the database client installed, extract the Database Deletion Wizard executable file from the ZIP file: ○ Windows 64-bit: FS-PRO-db-..-windows-x64.zip (using a Windows unzip utility) ○ UNIX: FS-PRO-db-..-unix.tar.gz (using the tar -xvzf command) 2. Launch the Database Deletion Wizard executable file: ○ Windows 64-bit: FS-PRO-db\bin\deleteDB.exe

Installation Guide 126 PUBLIC Uninstalling FS-QUO ○ UNIX: FS-PRO-db/bin/deleteDB 3. On the Welcome screen, choose Next. 4. On the Select Additional Tasks screen, ensure that the Generate a response file only option isn't selected, and choose Next. 5. On the Database Information form screen, provide all required information and choose Next. Ensure that the Database type is set to Oracle. 6. On the Summary screen, review the summary and choose Next. 7. On the Progress screen, wait until the database deletion is completed. 8. On the Finish screen, review the results and choose Finish to exit.

Results

If the database deletion fails, note the failure message on the Finish screen.

● Check the database deletion logs and correct the problem. ● Then re-attempt the database deletion.

10.3.2 Deleting the FS-QUO Oracle Database in Console Mode

Use the Database Deletion Wizard to delete an FS-QUO Oracle database for the Designer Runtime environment. You can choose to run the Database Deletion Wizard in console mode, which is useful on UNIX-based systems with limited GUI access.

Context

To delete the database in console mode, perform the following steps:

Procedure

Installation Guide Uninstalling FS-QUO PUBLIC 127 ○ UNIX: FS-PRO-db-..-unix.tar.gz (via the command tar -xvzf) 2. Launch the Database Deletion Wizard executable file with the -c option: ○ Windows 64-bit: FS-PRO-db\bin\deleteDB.exe -c ○ UNIX: FS-PRO-db/bin/deleteDB -c 3. On the Create a response file only (no operation will be performed) prompt, choose the default option (n) by pressing Enter .

4. On the Database Information form screen, provide all required information and hit Enter . Ensure that the Database type is set to Oracle.

5. Review the summary information and press Enter . Wait until the database deletion is completed.

6. Once complete, review the results and press Enter to exit.

Results

If the database deletion fails, note the failure message on the Finish screen.

● Check the database deletion logs and correct the problem. ● Then re-attempt the database deletion.

10.3.3 Deleting the FS-QUO Microsoft SQL Server Database in GUI Mode

Use the Database Deletion Wizard to delete an FS-QUO Microsoft SQL Server database for the Designer Runtime environment. You can choose to run the Database Deletion Wizard in GUI mode, which provides an interactive, graphical interface to easily delete the database.

Context

To delete the database in GUI mode, perform the following steps:

Procedure

1. On the machine with the database client installed, extract the Database Deletion Wizard executable file from the ZIP file: FS-PRO-db-..-windows-x64.zip 2. Launch the Database Deletion Wizard executable file: FS-PRO-db\bin\deleteDB.exe

Installation Guide 128 PUBLIC Uninstalling FS-QUO 3. On the Welcome screen, choose Next. 4. On the Select Additional Tasks screen, ensure that the Generate a response file only option isn't selected, and choose Next. 5. On the Database Information form screen, provide all required information and choose Next. Ensure that the Database type is set to Microsoft SQL Server. 6. On the Summary screen, review the summary and choose Next. 7. On the Progress screen, wait until the database deletion is completed. 8. On the Finish screen, review the results and choose Finish to exit.

Results

If the database deletion fails, note the failure message on the Finish screen.

● Check the database deletion logs and correct the problem. ● Then re-attempt the database deletion.

10.3.4 Deleting the FS-QUO Microsoft SQL Server Database in Console Mode

Use the Database Deletion Wizard to delete an FS-QUO Microsoft SQL Server database for the Designer Runtime environment. You can choose to run the Database Deletion Wizard in console mode, which is useful on UNIX-based systems with limited GUI access.

Context

To delete the database in console mode, perform the following steps:

Procedure

Installation Guide Uninstalling FS-QUO PUBLIC 129 3. On the Create a response file only (no operation will be performed) prompt, choose the default option (n) by pressing Enter .

4. On the Database Information form screen, provide all required information and hit Enter . Ensure that the Database type is set to Microsoft SQL Server.

5. Review the summary information and press Enter . Wait until the database deletion is completed.

6. Once complete, review the results and press Enter to exit.

Results

If the database deletion fails, note the failure message on the Finish screen.

● Check the database deletion logs and correct the problem. ● Then re-attempt the database deletion.

10.3.5 Deleting the FS-QUO SAP HANA Database in GUI Mode

Use the Database Deletion Wizard to delete an FS-QUO SAP HANA database for the Designer Runtime environment. You can choose to run the Database Deletion Wizard in GUI mode, which provides an interactive, graphical interface to easily delete the database.

Prerequisites

Currently the Database Deletion Wizard is supported to run only from the SAP HANA database server host.

Context

To delete the database in GUI mode, perform the following steps:

Procedure

1. On the UNIX machine where the SAP HANA database server is installed, extract the Database Deletion Wizard executable file from the ZIP file: FS-PRO-db-..-unix.tar.gz using the tar -xvzf command.

Installation Guide 130 PUBLIC Uninstalling FS-QUO 2. Launch the Database Deletion Wizard executable file: FS-PRO-db/bin/deleteDB 3. On the Welcome screen, choose Next. 4. On the Select Additional Tasks screen, ensure that the Generate a response file only option isn't selected, and choose Next. 5. On the Database Information form screen, provide all required information and choose Next. Ensure that the Database type is set to SAP HANA. 6. On the Summary screen, review the summary and choose Next. 7. On the Progress screen, wait until the database deletion is completed. 8. On the Finish screen, review the results and choose Finish to exit.

Results

If the database deletion fails, note the failure message on the Finish screen.

● Check the database deletion logs and correct the problem. ● Then re-attempt the database deletion.

10.3.6 Deleting the FS-QUO SAP HANA Database in Console Mode

Use the Database Deletion Wizard to delete an FS-QUO SAP HANA database for the Designer Runtime environment. You can choose to run the Database Deletion Wizard in console mode, which is useful on UNIX- based systems with limited GUI access.

Prerequisites

Currently the Database Deletion Wizard is supported to run only from the SAP HANA database server host.

Context

To delete the database in console mode, perform the following steps:

Installation Guide Uninstalling FS-QUO PUBLIC 131 Procedure

1. On the UNIX machine where the SAP HANA database server is installed, extract the Database Deletion Wizard executable file from the ZIP file: FS-PRO-db-..-unix.tar.gz using the tar -xvzf command. 2. Launch the Database Deletion Wizard executable file with the -c option: FS-PRO-db/bin/deleteDB -c 3. On the Create a response file only (no operation will be performed) prompt, choose the default option (n) by pressing Enter .

4. On the Database Information form screen, provide all required information and hit Enter . Ensure that the Database type is set to SAP HANA.

5. Review the summary information and press Enter . Wait until the database deletion is completed.

6. Once complete, review the results and press Enter to exit.

Results

If the database deletion fails, note the failure message on the Finish screen.

● Check the database deletion logs and correct the problem. ● Then re-attempt the database deletion.

10.3.7 Deleting the FS-QUO IBM DB2 Database in GUI Mode

Use the Database Deletion Wizard to delete an FS-QUO IBM DB2 database for the Designer Runtime environment. You can choose to run the Database Deletion Wizard in GUI mode, which provides an interactive, graphical interface to easily delete the database.

Prerequisites

Currently the Database Deletion Wizard is supported to run only from the IBM DB2 database server host.

Context

To delete the database in GUI mode, perform the following steps:

Installation Guide 132 PUBLIC Uninstalling FS-QUO Procedure

1. On the UNIX machine where the IBM DB2 database server is installed, extract the Database Deletion Wizard executable file from the ZIP file using the tar -xvzf command: FS-PRO-db-..-unix.tar.gz 2. Launch the Database Deletion Wizard executable file: FS-PRO-db/bin/deleteDB 3. On the Welcome screen, choose Next. 4. On the Select Additional Tasks screen, ensure that the Generate a response file only option isn't selected, and choose Next. 5. On the Database Information form screen, provide all required information and choose Next. Ensure that the Database type is set to DB2. 6. On the Summary screen, review the summary and choose Next. 7. On the Progress screen, wait until the database deletion is completed. 8. On the Finish screen, review the results and choose Finish to exit.

Results

If the database deletion fails, note the failure message on the Finish screen.

● Check the database deletion logs and correct the problem. ● Then re-attempt the database deletion.

10.3.8 Deleting the FS-QUO IBM DB2 Database in Console Mode

Use the Database Deletion Wizard to delete an FS-QUO IBM DB2 database for the Designer Runtime environment. You can choose to run the Database Deletion Wizard in console mode, which is useful on UNIX- based systems with limited GUI access.

Prerequisites

Currently the Database Deletion Wizard is supported to run only from the IBM DB2 database server host.

Installation Guide Uninstalling FS-QUO PUBLIC 133 Context

To delete the database in console mode, perform the following steps:

Procedure

4. On the Database Information form screen, provide all required information and hit Enter . Ensure that the Database type is set to DB2.

5. Review the summary information and press Enter . Wait until the database deletion is completed.

6. Once complete, review the results and press Enter to exit.

Results

If the database deletion fails, note the failure message on the Finish screen.

● Check the database deletion logs and correct the problem. ● Then re-attempt the database deletion.

Installation Guide 134 PUBLIC Uninstalling FS-QUO 10.4 Uninstalling FS-QUO

10.4.1 Uninstalling FS-QUO Using the Wizard in GUI Mode

The Uninstallation Wizard can typically be run in GUI mode, which provides an interactive, graphical interface to easily uninstall the software.

Context

To uninstall FS-QUO in GUI mode, perform the following steps:

Procedure

1. Launch the Uninstallation Wizard executable file: ○ Windows: \uninstall.exe ○ UNIX: /uninstall 2. On the Welcome screen, choose Next. 3. On the Select Additional Tasks screen, select from the following options: ○ Delete all user-generated files and log files ○ Create a response file only (no operation will be performed) 4. Review the information in the Uninstallation Summary screen and choose Next. 5. Wait until uninstallation is completed on the Progress screen. 6. On the Finish screen, review the results and choose Finish to exit.

Results

When the process completes, the return code will be zero if the uninstallation is successful, or non-zero otherwise.

● In case of failure, check the uninstallation logs and correct the problem. ● Then restart the uninstallation.

10.4.2 Uninstalling FS-QUO Using the Wizard in Console Mode

Alternatively, the Uninstallation Wizard can be run in console mode. The flow in console mode is essentially the same as that of GUI mode, except that messages are displayed in plain text within a command prompt, and the

Installation Guide Uninstalling FS-QUO PUBLIC 135 user uses the keyboard to make choices and provide field values. This mode is useful on UNIX-based systems with limited GUI access.

Context

To uninstall in console mode, perform the following steps:

Procedure

1. Launch the Uninstallation Wizard executable file with the -c option: ○ Windows: \uninstall.exe -c ○ UNIX: /uninstall -c 2. On the Select Additional Tasks prompt, select from the following options: ○ Delete all user-generated files and log files ○ Create a response file only (no operation will be performed) 3. Review the information in the Uninstallation Summary and choose Next. 4. Wait until uninstallation is completed. 5. Review the results and choose Finish to exit

Results

When the process completes, the return code will be zero if the uninstallation is successful, or non-zero otherwise.

● In case of failure, check the uninstallation logs and correct the problem. ● Then restart the uninstallation.

Installation Guide 136 PUBLIC Uninstalling FS-QUO 11 Installing ActiveMQ

ActiveMQ is a message broker created by Apache Software Foundation and fully implements the Java Message Service (JMS) version 1.1. ActiveMQ is required for the Product Configurator Clustering feature but is only required for the Asychronous Publishing feature if the NetWeaver JMS Provider is not used.

If your site isn't already running ActiveMQ 5.0, contact FS-PRO Support to get the version of ActiveMQ that has been validated for the product.

 Note

We recommend that you contact SAP for help with setting up ActiveMQ

Optionally, after installing ActiveMQ, you can change the user name and password for connecting to the ActiveMQ message broker. For more information about changing the user name and password, see http:// activemq.apache.org/security.html .

11.1 Installing ActiveMQ on Windows

Use the following procedure to install the binary distribution and set up ActiveMQ on a Windows system.

Prerequisites

● 40 MB of free disk space for the ActiveMQ installation ● JDK 1.8 is installed ● The JAVA_HOME environment variable must be set to the directory where the JDK is installed.

Context

To install ActiveMQ on Windows, perform the following steps:

Procedure

1. Extract the ZIP file, apache-activemq-5.14.5-bin.zip, into a directory on the server designated for ActiveMQ. This procedure refers to this as the directory.

Installation Guide Installing ActiveMQ PUBLIC 137 2. Configure ActiveMQ to use only the openwire transport connector. In the file \conf\activemq.xml,locate the transportConnectors section.

Remove all of the of the transportConnectors elements that aren't named openwire, and remove the discoveryURI attribute from the transportConnectors element named openwire. 3. Open a DOS window, and at the command prompt, enter the following: cd \bin\win64 InstallService.bat Running InstallService.bat creates a Windows service that lets you close the DOS window without terminating the ActiveMQ process.

Results

The default port for ActiveMQ is 61616. To test if ActiveMQ is running, enter the following command at a DOS console: netstat -an|find "61616"

ActiveMQ is installed on Windows.

11.2 Installing ActiveMQ on UNIX

Use the following procedure to install the binary distribution and set up ActiveMQ on a UNIX system.

Prerequisites

● 40 MB of free disk space for the ActiveMQ installation ● JDK 1.8 is installed ● The JAVA_HOME environment variable must be set to the directory where the JDK is installed.

Context

To install ActiveMQ on UNIX, perform the following steps:

Procedure

1. Extract the ZIP file, apache-activemq-5.14.5-bin.tar.gz , into a directory on the server designated for ActiveMQ.

Installation Guide 138 PUBLIC Installing ActiveMQ This procedure refers to this as the directory. 2. At the command prompt, enter: tar zxvf apache-activemq-5.14.5-bin.tar.gz 3. Configure ActiveMQ to use only the openwire transport connector. In the file \conf\activemq.xml,locate the transportConnectors section.

Remove all of the of the transportConnectors elements that aren't named openwire, and remove the discoveryURI attribute from the transportConnectors element named openwire. 4. Open a console window, and at the command prompt, change the permissions of the ActiveMQ startup script, and launch ActiveMQ, as follows:

cd \bin\

chmod 755 activemq nohup ./activemq

Using nohup allows the ActiveMQ to keep running even when the UNIX console or shell from which ActiveMQ is run is closed. The standard output and error streams are typically redirected to a file called nohup.out in the directory from which the nohup command is run.

Results

The default port for ActiveMQ is 61616. To test if ActiveMQ is running, enter the following command from a UNIX command shell: netstat -an|grep "61616"

ActiveMQ is installed on UNIX.

Installation Guide Installing ActiveMQ PUBLIC 139 12 Next Steps

If you are using the FS-QUO software in an integrated environment with FS-PRO, FS-PM, and FS-QUO, you must complete additional post-installation steps.

For example, SAP JCo version 3.0 is now required by FS-QUO to make RFC and APIF calls to FS-PM and ERP- BP in an integrated landscape. Because of this, you will need to configure RFC Destinations in the NetWeaver Administrator. For more information about configuring your integrated environment, see the Integration Guide.

Installation Guide 140 PUBLIC Next Steps Important Disclaimers and Legal Information

Hyperlinks

Some links are classified by an icon and/or a mouseover text. These links provide additional information. About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information. ● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up. The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code

Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related Language

We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Installation Guide Important Disclaimers and Legal Information PUBLIC 141 www.sap.com/contactsap

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 https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN