Support Package Upgrade Guide - help.sap.com

Upgrade Guide | PUBLICDocument Version: 1.0 – 2019-09-11

Support Package Upgrade GuideSAP Underwriting for Insurance 4.0 SP05

© 2

021 S

AP S

E or

an

SAP affi

liate

com

pany

. All r

ight

s re

serv

ed.

THE BEST RUN

Content

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2 Product Name Abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3 References to Third-Party Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.4 Related SAP Notes for FS-QUO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.5 Substitution Variable Placeholders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.6 SAP NetWeaver Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2 Preparing to Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.1 System Requirements for FS-QUO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Required FS-IPW Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Integrating with FS-PM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Removal of IBM WebSphere Application Server Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Supported Shell Software for FS-QUO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Database Requirements for FS-QUO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Application Server Requirements for FS-QUO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Java Message Service (JMS) Requirements for FS-QUO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12X-Windows Virtual Frame Buffer Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Hardware Requirements for FS-QUO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Client Requirements for FS-QUO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.2 Backing Up Your Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142.3 Additional Documentation Reference and Assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3 Upgrading FS-QUO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.1 Preserving Customizations and Extensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4 Backing Up Custom Servlet Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

5 Upgrading Designer Runtime. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175.1 Updating the Database Using the Database Migration Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Gathering the Required Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Downloading the Database Migration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Setting the <JAVA_HOME> Environment Variable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Getting a JDBC Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Editing the settings.properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Running the Database Migration Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Verifying the Database Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

5.2 Downloading the FS-PRO Installation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2 PUBLICSupport Package Upgrade Guide

Content

5.3 Upgrading FS-QUO Using the Installer in GUI Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235.4 Upgrading FS-QUO Using the Installer in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255.5 Replacing the Custom Servlet Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265.6 Undeploying the Existing FS-QUO SCA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Undeploying the SCA Using Telnet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Undeploying the SCA Using SUM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

5.7 Disabling Heavy Resource Loading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285.8 Configuring the HttpOnly Flag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295.9 Deploying the FS-QUO SCA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Deploying the SCA Using Telnet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Deploying the SCA Using SUM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

5.10 Making Updates in the Administrative Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325.11 Verifying the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335.12 Troubleshooting the Database Migration Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

6 Updating FS-QUO Contents in Product Configurator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356.1 Uploading the Custom Stem Class and Classpath. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

7 Preserving Content Configuration Changes and Extensions. . . . . . . . . . . . . . . . . . . . . . . . . . . 37

8 Setting Up the Line of Business Bootstrap Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388.1 Configuring the Commercial PnC Bootstrap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Importing the Commercial PnC Bootstrap Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Setting Up Publish Manager in the Product Configurator Administrative Console for the Commercial PnC Bootstrap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41Building the Imported Commercial PnC Bootstrap Products. . . . . . . . . . . . . . . . . . . . . . . . . . . 42Updating the Commercial PnC Bootstrap Product Selection. . . . . . . . . . . . . . . . . . . . . . . . . . . 43Publishing and Deploying Imported Commercial PnC Bootstrap Products into the Designer/Runtime Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

8.2 Configuring the Personal Lines of Business (LoBs) Bootstrap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Importing the Personal LoB Bootstrap Products in a Production Environment. . . . . . . . . . . . . . . 45Importing Sample LoB Products in a Sandbox Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Setting Up Publish Manager in Product Configurator Administrative Console for the Personal LoB Bootstrap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Building the Imported Personal LoB Bootstrap Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Building and Publishing the Data Models for the Personal LoB Bootstrap. . . . . . . . . . . . . . . . . . .52Updating the Personal LoB Bootstrap Product Selection (Sandbox Environment Only). . . . . . . . . 54Publishing the Imported Personal LoB Bootstrap Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

9 Configuring Designer Runtime for Underwriting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579.1 Upgrading the FS-QUO Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579.2 Checking which Flowlet Groups are Currently Installed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589.3 Importing New Flowlet Groups in Designer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Support Package Upgrade GuideContent PUBLIC 3

9.4 Updating Process Flowstores. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639.5 Rebuilding Flowlets with the BatchFlowBuildServlet Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659.6 Synchronizing Product Flowstores. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669.7 Updating Database Objects for Underwriting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Updating the Oracle Database Using the Database Update Wizard in GUI Mode . . . . . . . . . . . . . 68Updating the Oracle Database Using the Database Update Wizard in Console Mode. . . . . . . . . . . 69Updating the SAP HANA Database Using the Database Update Wizard in GUI Mode. . . . . . . . . . . 70Updating the SAP HANA Database Using the Database Update Wizard in Console Mode. . . . . . . . 71Updating the Microsoft SQL Server Database Using the Database Update Wizard in GUI Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Updating the Microsoft SQL Server Database Using the Database Update Wizard in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Updating the IBM DB2 Database Using the Database Update Wizard in GUI mode. . . . . . . . . . . . 75Updating the IBM DB2 Database Using the Database Update Wizard in Console Mode. . . . . . . . . 76

9.8 Pre-Loading Products into Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .779.9 Verifying the FS-QUO Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

10 Next Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79


Content

1 Introduction

1.1 Audience

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

1.2 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 Management for Insurance

FS-PQM n/a

SAP Product Lifecycle Management for Insurance

FS-PRO Product Configurator

SAP Underwriting for Insurance FS-QUO Designer

SAP Workplaces for Insurance FS-IPW n/a

SAP Policy Management FS-PM n/a

1.3 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.

Support Package Upgrade GuideIntroduction PUBLIC 5

1.4 Related SAP Notes for FS-QUO

Before you start the upgrade process, see the SAP Notes in the SAP Support Portal Knowledge Base for additional information and instructions.

To get an updated list of SAP Notes, go to https://support.sap.com/notes and search for FS-QUO issues for this release.

1.5 Substitution Variable Placeholders

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

Substitution Variable Description

<sp> The support package version you are installing or upgrading.

<pl> The patch level of you are installing or upgrading.

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

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

<db_user_prefix> The database user name prefix.

<db_user_name> The database user name prefix, followed by _SYS.

NoteFor 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.

<db_host_name> Database server name.

<db_server_port> Port number.


Introduction

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fnotes


<sql_port> (Applicable to SAP HANA only)

For Single Tenant:

Port = 3<<SAP HANA instance number>>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'

<db_user_password> The password of the database user <db_user_name>.

<jdbc_url> Specifies the JDBC URL of the FS-QUO database once it has been created. The JDBC URL format is specific to the database vendor. For more information refer to the DBMS documentation.

The following are the typical JDBC URL formats:

● Oracle: jdbc:oracle:thin:@<db_host_name>:<db_server_port>:<oracle_SID> or jdbc:oracle:thin:@<db_host_name>:<db_server_port>/<oracle_service_name>

NoteFor Oracle 12c Pluggable Databases, it is recommended to connect through <oracle_service_name>

● Microsoft SQL Server: jdbc:sqlserver://<db_host_name>:<db_server_port>;databaseName=<fs_quo_db_name>

● SAP HANA: jdbc:sap://<db_host_name>:<sql_port>

● IBM DB2: jdbc:db2://<db_host_name>:<db_server_port>/<fs_quo_db_name>

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

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

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

Support Package Upgrade GuideIntroduction PUBLIC 7


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

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

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

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

1.6 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://<host>:<port>/nwa , where:host

Specifies the host where AS Java is installed.

portSpecifies the HTTP port of the Internet Communication Manager (ICM).

It consists of 5<Java instance_number>00 .

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


Introduction

2 Preparing to Upgrade

2.1 System Requirements for FS-QUO

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

2.1.1 Required FS-IPW Version

For this release, no new support package has been issue for FS-IPW. FS-QUO 4.0 SP05 is compatible with FS-IPW 4.0 SP04.

If you are upgrading to FS-QUO 4.0 SP05 from FS-QUO 4.0 SP04, then you do not need to upgrade your FS-IPW 4.0 SP04 application.

However, if you are upgrading your FS-QUO and FS-IPW from a version of the software lower than SP04, you will need to upgrade your FS-IPW application.

The installation instructions for FS-IPW 4.0 SP04 are available on the Help Portal

2.1.2 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.1.3 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.1.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.

Support Package Upgrade GuidePreparing to Upgrade PUBLIC 9

https://help.sap.com/viewer/product/SAP_UNDERWRITING_FOR_INSURANCE/4.0.04/en-US

2.1.5 Database Requirements for FS-QUO

Ensure that you satisfy the database requirements before beginning.

The following database versions are certified and supported:

NoteA 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.

SAP HANA

Certified Version: 2.0 SPS02

Supported Version: 1.0 SPS12

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: 12c Release 1

Supported Version: 11g Release 2

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


Preparing to Upgrade

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/2131662

● PGA set to a minimum of 100 MB● Database character set = AL32UTF8● National character set = AL16UTF16

If your Oracle 12c 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:

● 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 2014

Supported Version: Standard or Enterprise Edition 2012

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

IBM DB2

Certified Version 10.5 FP5 (10.5.0.5) installed on UNIX or Linux

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

db2usersdasadm1db2iadm1db2fadm1


RememberGroup and user names on UNIX systems must be lower case

● Create the following operating system user:<username>_sys (with default user group db2users)

● Add the <username>_sys user to the db2iadm1 group● Set the following environment variables:

db2set db2_compatibility_vector=oradb2set db2_deferred_prepare_semantics=yes

● After creating groups and users and setting variables, restart the IBM DB2 service.

2.1.6 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 SPS07 Install the following usage types:

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

Consult SAP Support Portal for information about specific fix packs.

2.1.7 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 Provider

Relevant to the Integration Framework (IFW) and Web Services features.

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



http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fen%2Findex.html

2.1.8 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.1.9 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)● 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.1.10 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


http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fen%2Findex.html

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/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.

2.2 Backing Up Your Instance

Before you attempt an upgrade of the FS-QUO software, it's a best practice to stop the FS-QUO instance and perform a backup.

The backup should include the <csi_home> directory and the FS-QUO database. Backing up the NetWeaver database is optional, but it isn't required.

2.3 Additional Documentation Reference and Assumptions

For a complete discussion on installing FS-PRO, including system requirements and configuration options, see the SAP Product Lifecycle Management for Insurance Installation Guide for SAP NetWeaver.

It is assumed that all environmental and system requirements have been met prior to performing the upgrade. It is also assumed that FS-PRO has already been upgraded as described in the SAP Product Lifecycle Management for Insurance Upgrade Guide for SAP NetWeaver.



3 Upgrading FS-QUO

Use this checklist to guide you through upgrading FS-QUO.

To upgrade FS-QUO, perform the following tasks:

1. Upgrade the Designer/Runtime environment serving as the underlying platform for FS-QUO.2. Prepare your existing Product Configurator environment with FS-QUO contents and propagate insurance

products and configuration objects to your Designer/Runtime environment.3. Prepare the various insurance products by updating the bootstraps.4. Update your Designer/Runtime environment with the insurance underwriting workflow.

3.1 Preserving Customizations and Extensions

All product customizations and extensions should be preserved in a Software Component Architecture (SCA) file.

Any customizations or extensions in <csi_home> will be overwritten during the upgrade process. You can generate the SCA file for your environment using the Development Toolkit. The newly-generated SCA file is then deployed to NetWeaver. As part of the upgrade, you must also upgrade the Development Toolkit.

The high-level steps for this process are the following:

1. Upgrade the Development Toolkit.2. Capture your customizations and extensions into an SCA file using the Development Toolkit.3. Follow this guide to upgrade your system.4. Deploy your customized SCA file into NetWeaver.

For a full discussion on using the Development Toolkit, including the Development Toolkit upgrade directions, refer to the Working with the Development Toolkit section in the SAP Underwriting for Insurance Developer Guide.

Support Package Upgrade GuideUpgrading FS-QUO PUBLIC 15

4 Backing Up Custom Servlet Definitions

Before upgrading your FS-QUO installation, you need to back up the file containing any custom servlet definitions.

Context

To back up your custom servlets, perform the following task:

Procedure

Back up the following file: <csi_home>/ppms/app/pa/env/config/cservlet_env_def.xml


Backing Up Custom Servlet Definitions

5 Upgrading Designer Runtime

5.1 Updating the Database Using the Database Migration Tool

To upgrade to the current release of FS-QUO, you must first migrate the database.

A database migration tool is provided to migrate Product Configurator and Designer Runtime. This tool applies to all supported databases and can run on both Microsoft Windows and UNIX operating systems.

The FS-PRO-db-migration-<pqm_release>.<sp>.<pl>.zip file contains a special file named settings.properties which contains a mapping of key configuration variables that you will modify as part of the migration process.

RememberBack up your database before you perform this migration process. If the migration fails, don't perform the migration again on the same database. Instead, resolve the problem, reload the backup, and then try again.

5.1.1 Gathering the Required Information

Before you perform the database migration, gather the following information

● Database administrator (DBA) password for the system account (Oracle or SAP HANA) or for the sa account (Microsoft SQL Server)

● Host name and port number of the database server.● SID/Service name (Oracle) or database name (Microsoft SQL Server)● User name of the database (<db_user_name>), as defined in the substitution variable placeholders. Note

that the database user name needs to be configured in uppercase● Password for the database user (<db_user_password>), as defined in the substitution variable

placeholders

You will configure the database migration tool with this information.

Support Package Upgrade GuideUpgrading Designer Runtime PUBLIC 17

5.1.2 Downloading the Database Migration Files

The database migration files and tools are provided in ZIP files.

Context

To get the database migration files, perform the following steps:

Procedure

1. Contact your FS-PRO administrator or consult the SAP Download Center at https://launchpad.support.sap.com/#/softwarecenter .

2. Download the FS-PRO-db-migration-<pqm_release>.<sp>.<pl>.zip file to the database server.

TipIf you are on Windows, and the target database server is UNIX, you can use tools like PuTTY to logon and execute commands.

3. Unzip the file in any working directory.

NoteThe name of the directory cannot include spaces.

5.1.3 Setting the <JAVA_HOME> Environment Variable

The database migration tool requires a Java Runtime Environment (JRE) to run.

Context

To set the <JAVA_HOME><JAVA_HOME> environment variable, perform the following steps:

Procedure

1. Verify that the correct JRE is installed.2. Set the JAVA_HOME environment variable to the JRE location.


Upgrading Designer Runtime

http://help.sap.com/disclaimer?site=https%3A%2F%2Flaunchpad.support.sap.com%2F%23%2Fsoftwarecenter

http://help.sap.com/disclaimer?site=https%3A%2F%2Flaunchpad.support.sap.com%2F%23%2Fsoftwarecenter

3. Run the version command to discover the JRE version. Run the command that is appropriate to your operating system:○ Windows: "%JAVA_HOME%\bin\java" -version○ UNIX: "$JAVA_HOME/bin/java" -version

The JRE version displays.

5.1.4 Getting a JDBC Driver

The database migration tool requires a JRE (Java Runtime Environment) and a corresponding JDBC driver to run.

Context

To get a JDBC driver, perform the following steps:

Procedure

1. Download a JDBC driver that matches the database and jdbc version. Perform the action appropriate to your database type:○ For Oracle 11g migrations, obtain the Oracle JDBC driver JAR file, ojdbc6.jar, which is available for

download from the Oracle Technology Network Software Downloads page.○ For Oracle 12c migrations, download the Oracle 12.1.0.2 JDBC driver from Oracle site. Then log in to the

Oracle support site and download Oracle patch numbers 21623553, 20692348, 20215127, 19632480, and 22385253. Apply the patch to the driver through Oracle support document Doc ID 431463.1 .

○ For Microsoft SQL Server migrations, obtain the Microsoft JDBC Driver 4.0 for SQL Server JAR file, sqljdbc4.jar,which is available for download from the Microsoft Download Center.

○ For SAP HANA migrations, obtain the HANA SPS12 JDBC driver JAR file, ngdbc.jar, which is installed with HANA.

○ For IBM DB2 migrations, obtain the DB2 JDBC driver JAR file db2jcc4.jar, which can be obtained from the IBM support site.

The JDBC driver (in JAR format) is downloaded.2. Copy the JDBC driver file to the drivers directory.

The JDBC driver is available for the database migration tool. You can upgrade the driver at any time.


http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.oracle.com%2Fepmos%2Ffaces%2FDocumentDisplay%3F_afrLoop%3D363395734542212%26id%3D431463.1%26_afrWindowMode%3D0%26_adf.ctrl-state%3D170runy0uh_4

5.1.5 Editing the settings.properties File

The database migration tool is configured using the settings.properties file. You must specify the database location and login credentials in this file before running the tool.

Context

To edit the settings.properties file, perform the following steps:

Procedure

1. In the directory where you placed the migration files, open the settings.properties file in a text editor.

2. Specify a value for the following settings:

csi_db_type Specifies the database type.Enter PPMC which specifies that you are migrating a Designer database.

db_type Specifies the database type. Choose the option that is appropriate for your database type:○ ORACLE—Indicates that the type is Oracle○ MSSQL—Indicates that the type is Microsoft SQL Server.○ HANA—Indicates that the type is SAP HANA.○ DB2—Indicates that the type is IBM DB2.

host Specifies the host name of the database server to connect to.

port Specifies the port number of the database server to connect to.

sid_service_dbname Specifies the SID/Service (Oracle) or database name (Microsoft SQL Server, SAP HANA or IBM DB2).

username Specifies the user name of the database.Don't include _SYS or any other schema suffixes.

sys_password Specifies the password for the <db_user_prefix>_SYS login/schema.

3. Specify any value for the following settings:

pc_password Specifies the password for the <db_user_prefix>_PC login/schema.

ppmc_password Specifies the password for the <db_user_prefix>_PPMC login/schema.

ppms_password Specifies the password for the <db_user_prefix>_PPMS login/schema.

udir_password Specifies the password for the <db_user_prefix>_UDIR login/schema.

usr_password Specifies the password for the <db_user_prefix>_USR login/schema.

seq_password Specifies the password for the <db_user_prefix>_SEQ login/schema.



ps_password Specifies the password for the <db_user_prefix>_PS login/schema.

NoteFor Microsoft SQL Server, the passwords in step 3 are no longer used if the database structure is upgraded. All passwords are consolidated into a single login for all schemas. However, you must still specify the passwords in the settings.properties file because the database migration tool determines whether these passwords are needed only when it connects.

NoteFor Oracle databases, specify the index_tablespace property with the value INDX also.

4. Save the file.

Results

The settings.properties file is edited.

5.1.6 Running the Database Migration Tool

You need to run the database migration tool to upgrade the FS-QUO database.

Prerequisites

Perform the following database task if you are upgrading from version 300.0.0, version 300.1.0 (Support Package 1), version 300.1.1 (Support Package 1 Patch Level 1), version 300.1.2 (Support Package 1 Patch Level 2) or prior:

1. Log in to the database server under the <db_user_name> user.2. Execute the query:

update MIGRATION_VERSION SET SOURCE_CODE_BUILD_VERSION='3.0.0.0' WHERE SOURCE_CODE_BUILD_VERSION in ('300.0.0','300.1.0','300.1.1','300.1.2');

Valid JDBC connect strings for Oracle use the following format:

● jdbc:oracle:thin:@[HOST][:PORT]:SID● jdbc:oracle:thin:@[HOST][:PORT]/SERVICE

However, the Database Migration Tool only handles SID. You can avoid errors with the Oracle server level configuration:

1. Edit the $ORACLE_HOME/network/admin/listener.ora file, and add the following entry, with the "listener" name matching that used by your listener.USE_SID_AS_SERVICE_listener=on


2. Reload or restart the listener by running the command:lsnrctl reload

Context

The Database Migration Tool can migrate all the database types (PC for Product Configurator, PPMC for Designer, and PPMS for Runtime). It works for all supported databases (Oracle, Microsoft SQL Server, IBM DB2 or SAP HANA) and can run on both Microsoft Windows-based and UNIX-based environments.

The tool performs the following actions:

● Reads the settings.properties file to load the information about the database server and login credentials.

● Connects to the database using the specified JDBC drivers and verifies the current version of the database.● Checks the latest version of the migration packages and their associated patches.● After comparison, the tool compiles the needed migration packages and patches, installs them, and

updates the version of the database.

To run the database migration tool, perform the following steps:

Procedure

1. Stop the application server instance where the database is deployed.2. Log in to your database server with administrative privileges.3. Change to the directory that contains the files extracted from the FS-PRO-db-migration-

<pqm_release>.<sp>.<pl>.zip file.

4. Run either of the following commands, as appropriate to your operating system:○ Windows: migrate.bat○ UNIX:

chmod 755 migrate.sh ./migrate.sh

The database migration tool starts running and prompts you for the DBA credentials.5. Enter the credentials for the database admin user (a user with database administrator privileges).

The tool runs to completion. If the migration completes successfully, the following message displays: Package <pqm_release>.<sp>.<pl> appliedIf the database was already migrated, the following message displays: Database is already up to date: <pqm_release>.<sp>.<pl>If the migration fails, error messages display and are written to the dbMigrationTool.log file.

6. Start the application server instance.



5.1.7 Verifying the Database Migration

After you complete the migration process, you can verify that the database migrated successfully.

To verify the database migration, ask your DBA to perform an SQL query on the MIGRATION_VERSION table.

If the database migrated successfully, the latest entry in the table is <pqm_release>.<sp>.<pl>.

5.2 Downloading the FS-PRO Installation Files

You need to download the FS-PRO installation files in order to upgrade FS-QUO.

Context

To get the installer, perform the following steps:

Procedure

1. Log in to Installations and Upgrades on the SAP Support Portal.2. Choose Software Downloads, search for FS-PRO and download the correct ZIP file.

3. Extract the following files from the downloaded ZIP file according to the operating system of your application server:○ Windows 64-bit: FS-PRO-install-<pqm_release>.<sp>.<pl>-windows-x64.exe○ UNIX: FS-PRO-install-<pqm_release>.<sp>.<pl>-unix.bin

5.3 Upgrading FS-QUO Using the Installer in GUI Mode

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

Prerequisites

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

● Java Runtime Environment (JRE) 8.0 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.


http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fsoftware%2Finstallations.html

● In an upgrade, you must stop the FS-QUO application in the application server before you run the installer or the Application Deployment Wizard. Otherwise, you will get file locking problems.

● If you are using the installer to upgrade FS-QUO, back up your file system, database, and application server configuration before you perform the migration.

The following list describes known issues for the FS-PRO installer:

● 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 the installation process, which continues loading (for an install) or unloading (for an uninstall). If this happens, you must manually kill the installation or uninstallation process in the operating system.

Context

To upgrade FS-QUO in GUI mode, perform the following steps:

Procedure

1. Use SAP MMC to stop the server instance.2. Launch the Installation Wizard executable file appropriate for your operating system:

○ Windows 64-bit: FS-PRO-install-<pqm_release>.<sp>.<pl>-windows-x64.exe○ UNIX: FS-PRO-install-<pqm_release>.<sp>.<pl>-unix.bin

3. When prompted to update the existing installation, verify the detected installation directory is correct. If it is, select Yes, update the existing installation and choose Next. Otherwise, select No, install into a different directory, choose Next, enter the correct installation directory on the next page of the Installation Wizard and choose Next.

NoteThe installation directory is also referred to as <csi_home> in this guide.

4. On the Select Components screen, select the appropriate components and choose Next to continue.For details on the components, refer to the context help on the screen.

5. On the Select Additional Tasks screen, choose Next.6. Review the information on the Installation Summary screen, and choose Next to continue.7. On the Progress screen, wait until the installation of files completes. If you are prompted to overwrite a

previous installation, choose Yes.



8. On the Finish screen, review the results and choose Finish to exit.9. Use SAP MMC to start the server instance.

5.4 Upgrading FS-QUO Using the Installer in Console Mode

You can upgrade FS-QUO using the Installation 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

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

● Java Runtime Environment (JRE) 8.0 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.

● In an upgrade, you must stop the FS-QUO application in the application server before you run the installer or the Application Deployment Wizard. Otherwise, you will get file locking problems.

● If you are using the installer to upgrade FS-QUO, back up your file system, database, and application server configuration before you perform the migration.

The following list describes known issues for the FS-PRO installer:

● 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 cannot exit or cancel the installation process, which continues loading (for an install) or unloading (for an uninstall). If this happens, you must manually kill the installation or uninstallation process in the operating system.


Context

To upgrade FS-QUO in console mode, perform the following steps:

Procedure

1. Use SAP MMC to stop the server instance.2. Launch the Installation Wizard executable file appropriate for your operating system, using the -c option:

○ Windows 64-bit: FS-PRO-install-<pqm_release>.<sp>.<pl>-windows-x64.exe -c○ UNIX: FS-PRO-install-<pqm_release>.<sp>.<pl>-unix.bin -c

3. When prompted to update the existing installation, verify the detected installation directory is correct. If it is, select Yes, update the existing installation and choose Next. Otherwise, select No, install into a different directory and choose Next, then enter the correct installation directory on the next prompt of the Installation Wizard.

NoteThe installation directory is also referred to as <csi_home> in this guide.

4. On the Select Components prompt, select the appropriate components and choose Next to continue.5. On the Select Additional Tasks prompt, choose Next to continue6. Review the information on the Installation Summary and choose Next to continue.7. Wait until the installation of files completes. If prompted to overwrite a previous installation, choose Yes.

8. Review the results and choose Finish to exit.9. Use SAP MMC to start the server instance.

5.5 Replacing the Custom Servlet Definitions

The custom servlet definitions must be replaced.

Context

To replace the custom servlet definitions, perform the following steps:

Procedure

After upgrading the <csi_home> directory, replace the file cservlet_env_def.xml you previously backed up back into the <csi_home>/ppms/app/pa/env/config/ directory.



5.6 Undeploying the Existing FS-QUO SCA

As part of the upgrade process, undeploy your existing SCA.

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

5.6.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 5<AS Java Instance Number>08

where <AS Java Instance Number> 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 deployundeploy 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.


https://help.sap.com/saphelp_nwce10/helpdata/en/45/0ad8e787652d6ae10000000a11466f/frameset.htm


5.6.2 Undeploying 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 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

5.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:

TipThe configtool can be found in the following location: \usr\sap\<SID>\J<AS Java Instance Number>\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.



https://help.sap.com/viewer/product/SAP_NETWEAVER_750/7.5.7/en-US

Related Information

SAP NetWeaver Administrator [page 8]

5.8 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:

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.

CautionDon'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]

5.9 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.

NoteIf 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.

5.9.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 5<AS Java Instance Number>08

where <AS Java Instance Number> 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 deploydeploy <SCA file location> 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.

5.9.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

NoteWhen 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.




http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fen%2Ftools%2Fsoftware-logistics-tools.html

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fen%2Ftools%2Fsoftware-logistics-tools.html

https://help.sap.com/viewer/p/SAP_NETWEAVER_750

NoteWhen the application is started, NetWeaver might report a java.io.FileNotFoundException on j2ee/cluster/apps/sap.com/FS-<XXX>.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.

NoteIn 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://<host>:<port>/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.

5.10 Making Updates in the Administrative Console

Context

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 System Environment JavaCompilerOptions .Current value:

-nowarn -classpath ${CSI.home}/system/lib/camilionlib.jar;${APP.home}/pa/custom/class;${APP.home}/runtime/class;${PS.home}/custom/class;${PC.home} /runtime/class;${CSI.home}/system/lib/camilion-apps.jar

Change to the following values:

-nowarn -classpath ${CSI.home}/system/lib/camilionlib.jar;${APP.home}/pa/custom/class;${APP.home}



/runtime/class;${PS.home}/custom/class;${PC.home}/runtime/class;${CSI.home}/system/lib/camilion-apps.jar;${CSI.home}/system/lib/com.sap.fs.pqm.debug.jar

4. Save your changes.

5. Choose System Reload Configuration Settings from the menu bar.6. Choose Reload All Config.

5.11 Verifying the 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://<FS-QUO_server_host>:<FS-QUO_server_https_port>/csiroot/authorIf 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 <pqm_release>.<sp>.<pl>

Results

The installation is verified.


5.12 Troubleshooting the Database Migration Tool

The database migration tool generates log files, which can be used to troubleshoot migration errors or failures.

If you get error messages after running the database migration tool or if the migration fails, verify that you followed all the required procedures. For example, check the following:

● The name of the working directory where you installed the database migration tool doesn't contain spaces.● The required JRE version is installed and configured.● The required drivers are installed in a drivers directory.● The values defined in the settings.properties file are correct.

NoteIf the database migration fails, revert to your database backup before you try to migrate the database again.

The database migration tool generates a file named dbMigrationTool.log that contains all database transactions and errors found. If you get an error, the migration tool tries to revert the database to its pre-migration state.

You can use the dbMigrationTool.log file to troubleshoot the migration process. For help with migrating the database, contact SAP support and send the dbMigrationTool.log file.



6 Updating FS-QUO Contents in Product Configurator

6.1 Uploading the Custom Stem Class and Classpath

Context

To upload the custom class and classpath, perform the following steps:

Procedure

1. Extract the FS-QUO-pc-custom-stems.zip file found in the custom_stems directory of the FS-QUO-exports-<pqm_release>.<sp>.<pl>.zip file into the <csi_home>/ps/custom/class directory for the FS-PRO instance.

NoteSince these are binary files, do not 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://<FS-PRO_pc_server_host>:<FS-PRO_pc_server_https_port>/csiroot/admin

3. Register the following custom class in the FS-PRO Administrative Console’s Function Library by choosing System Register Function Library and populate the fields as follows:

Field Value

Class Name com.sap.fs.quo.core.stem.SubmissionStem

Library Name Submission Stem

Description A submission-related function library

Stem Name SubmissionStem

4. Clear the function cache by choosing System Register Function Library and then choosing the Refresh button.

5. Reset the class loader by choosing System Reset ClassLoader from the menu.

Support Package Upgrade GuideUpdating FS-QUO Contents in Product Configurator PUBLIC 35

6. Choose System Reload Configuration Settings from the menu bar.7. Choose Reload All Config.


Updating FS-QUO Contents in Product Configurator

7 Preserving Content Configuration Changes and Extensions

The upgrade process does not preserve all configuration changes that you made to objects and components.

For example, you might have added new rows and unselected or deleted other rows in your Extended Underwriting Application Configuration object. If you use the upgrade process to import the FS-QUO content to your FS-PRO instance, the new rows are preserved, but the changes to the unselected and deleted rows are not preserved.

In addition, the product import during the upgrade process can create duplicate objects with a new version number. For information about duplicate objects, see the SAP Product Lifecycle Management for Insurance Product Configurator User Guide.

If you have configuration changes and you want to preserve them, there is no single, standardized approach for preserving your customized products. If your customizations are not too extensive and complex, we recommend that you follow this process:

1. Import the applicable bootstrap products, depending on if you are configuring for integration with FS-PM or not to a new, temporary FS-PRO instance.

2. Compare the configurations in the temporary instance with your existing FS-PRO instance, and note the differences.

3. In your existing instance, manually apply the content changes from the FS-QUO release (for example, new rows in an existing component).

4. Export any new objects from the temporary FS-PRO instance and import them to your existing instance (for example, new Mock Sample Products).

As an alternative, you can also do the following:

1. Note all of your customizations.2. Import the new products.3. Reapply your customizations.

You can also follow a hybrid strategy, depending on your implementation, and determine if it would be easier to manually reapply your own changes or alternately manually perform the FS-QUO product’s changes.

Extensions to FS-QUO do not have a fixed migration path. As a general process, extensions can be migrated using the following procedure:

1. Merge any base code changes and recompile.2. Remove all old custom artifacts from <csi_home>/ppms/app/as/custom.3. Test and debug all developed extensions.

For further assistance, contact SAP support.

Support Package Upgrade GuidePreserving Content Configuration Changes and Extensions PUBLIC 37

8 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 or the Line of Business bootstrap.

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

As of FS-QUO 3.0 SP04 and later, the LoB bootstraps have been consolidated into a single file named SAP_Templates_Bootstrap_1-0D.jar.This file contains a variety of bootstraps, pertaining to the various personal lines of business:

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

8.1 Configuring the Commercial PnC Bootstrap

8.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.


Setting Up the Line of Business Bootstrap Products

Context

You need to import the following 3 bootstraps which are located within the FS-QUO-exports-<pqm_release>.<sp>.<pl>.zip archive file:

● P_and_C_Insurance_Bootstrap_1-0D.jar● Underwriting_Application_Bootstrap_1-0D.jar● Mock_GL_Underwriting_Bootstrap_1-0D.jar

To import the Commercial PnC bootstrap products, perform the following steps:

Procedure

1. Extract the product JAR and bootstrap files from the FS-QUO-exports-<pqm_release>.<sp>.<pl>.zip archive file.

NoteThe 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://<FS-PRO_pc_server_host>:<FS-PRO_pc_server_https_port>/csiroot/ii/pc



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.

Support Package Upgrade GuideSetting Up the Line of Business Bootstrap Products PUBLIC 39

NoteDuring 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.

RememberMake sure 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.

NoteThere 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.



8.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.

Context

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

Procedure


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.

The Object Picker window opens, 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: <FS-QUO_server_host>:<FS-QUO_server_p4_port>. For example: fsquo.mycompany.com:50004

○ Context Path: com.sap.engine.services.jndi.InitialContextFactoryImpl4. 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.

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

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.

8.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://<FS-PRO_pc_server_host>:<FS-PRO_pc_server_https_port>/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.

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

4. 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.

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.

7. Repeat steps 2 through 6 above for the Mock GL Underwriting Bootstrap and Underwriting Application Data List imported products.

Next Steps

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

8.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 into FS-PRO at the following address:https://<FS-PRO_pc_server_host>:<FS-PRO_pc_server_https_port>/csiroot/ii/pc


If you haven't changed the password, enter password3. 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. Deselect 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.

8.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 into FS-PRO at the following address:https://<FS-PRO_pc_server_host>:<FS-PRO_pc_server_https_port>/csiroot/ii/pc

2. In the Product 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.



8.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● 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 the 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.

8.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.


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-<pqm_release>.<sp>.<pl>.zip archive file.

NoteThe 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://<FS-PRO_pc_server_host>:<FS-PRO_pc_server_https_port>/csiroot/ii/pc




The Import Product Wizard dialog opens.5. Choose Browse and select the SAP_Templates_Bootstrap_1-0D.jar file.


7. Choose Next>>.





11. Choose Next>>.

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

CautionEnsure that the product is imported successfully.



An import operation automatically recreates the necessary pathing in the Studio Tree for all the exported 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:





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.

8.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.

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

NoteThere 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





The Import Product Wizard dialog opens.4. Choose Browse and select the SAP_Sample_Products_Bootstrap_1-0D.jar file.


6. Choose Next>>.





10. Choose Next>>.

The Import tab appears and displays the progress of the import operation.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:







Next Steps

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

8.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.

Context

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

Procedure


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.

The Object Picker window opens, allowing you to enter the product name. Add 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 Policy4. 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

○ 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 Model5. 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: <FS-QUO_server_host>:<FS-QUO_server_p4_port>. For example: fsquo.mycompany.com:50004

○ Context Path: com.sap.engine.services.jndi.InitialContextFactoryImpl



6. Select Update.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.

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

8. Repeat this procedure for any other desired products.

8.2.4 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.

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


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 bootstraps, perform the following steps:

Procedure

1. In the Product 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.

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

Next Steps

Next, update the product selection in FS-PRO

8.2.5 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● 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


Master Policy


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

Procedure


2. In the Product 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.


8.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


LnA Life


Master Policy


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

Procedure



If you haven't changed the password, enter password3. Open Extended Underwriting Application Configuration.

In the Search field, enter either the full or partial name of a product from above 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. Deselect the rows that aren't related to the products.8. Save your changes on the Values tab.9. Repeat this process for all desired products.

Next Steps

Next, you need to publish and deploy the products.

8.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


Personal PnC


LnA Life



Master Policy


Procedure


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. 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.



9 Configuring Designer Runtime for Underwriting

9.1 Upgrading the FS-QUO Application

You need to upgrade the FS-QUO application, which is an add-on component for the Designer/Runtime environment

Prerequisites

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 do not have access to the NetWeaver Administrator web console, contact your IT department to configure the NetWeaver instance.

If you have customized the FS-QUO <csi_home> content, you must deploy the FS-QUO-install package which is built from the upgraded FS-QUO toolkit instead of the standard package from the assembly.

Context

After your product goes into runtime, FS-QUO generates a Policy Model using the information from the product JAR file and the form and form field data. The Policy Model is an XML representation of the data for a specific Policy transaction. The model is generated by FS-QUO and contains information from the FS-QUO Data Model and the Product Data Model assembled in Product Configurator.

Procedure

1. To get the installer, perform the following steps:

a. Go to Installations and Upgrades on the SAP Support Portal.b. Choose Software Downloads, search for FS-QUO and download the FS-QUO-install-

<pqm_release>.<sp>.<pl>.zip file.

2. Stop the FS-QUO instance using the SAP MMC.3. Extract all files within the downloaded ZIP file into the <csi_home> directory for the FS-QUO Designer/

Runtime instance.

NoteOn UNIX and Linux, use the –a option with the unzip command.

Support Package Upgrade GuideConfiguring Designer Runtime for Underwriting PUBLIC 57


4. Start the FS-QUO instance using the SAP MMC.

9.2 Checking which Flowlet Groups are Currently Installed

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.

Context

A flowstore has one master table by default, and can have multiple child tables, each of which can have child tables of its own.

When you upgrade to a new SP, you must import any new flowlet groups introduced in that SP. If no new flowlet groups are introduced, then update the flowstores only as described in the Updating Process Flowstores [page 63] topic. If you are upgrading more than one SP, for example, from 3.0 SP01 to 3.0 SP03 FP2, then you must import any new flowlet groups from both 3.0 SP02 FP1 and 3.0 SP03 FP2, and update the flowlet groups introduced in 3.0 SP01.

The following table lists all of the flowlet groups currently defined:

CautionThe flowlet groups are imported in the following order.

Flowlet Groups

Import Order Name of Flowlet Name of JAR File Version Introduced

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

3.0 SP00

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

3.0 SP00

3 PAS Client PAS_Client-10006(lp-flowlet-group).jar

3.0 SP00

4 Producer Rep Producer_Rep-10007(lp-flowlet-group).jar

3.0 SP00

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

3.0 SP00


Configuring Designer Runtime for Underwriting


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

3.0 SP00

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

3.0 SP00

8 Policy Processes Policy_Processes-10011(lp-flowlet-group).jar

3.0 SP00

9 Policy Quote Policy_Quote-10012(lp-flowlet-group).jar

3.0 SP00

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

3.0 SP00

11 Delta Tracker Delta_Tracker-10014(lp-flowlet-group).jar

3.0 SP00

12 Display Delta Tracker Display_Delta_Tracker-10015(lp-flowlet-group).jar

3.0 SP00

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

3.0 SP00

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

3.0 SP00

15 Business Partner Business_Partner-10018(lp-flowlet-group).jar

3.0 SP02

16 Document Item Document_Item-10019(lp-flowlet-group).jar

3.0 SP03

17 Access Control Access_Control-11003(lp-flowlet-group).jar

3.0 SP03


To check which flowlet groups are currently installed on your server, perform the following steps:

Procedure

1. Log in to the Designer at the following location: https://<FS-QUO_server_host>:<FS-QUO_server_https_port>/csiroot/author



3. In the Folders tree, select Applications SAP Underwriting Insurance .4. In the right panel, all flowlet groups currently installed should be displayed

Results

In the event you don't have all of the flowlet groups imported, you will need to import the JAR files.

9.3 Importing New Flowlet Groups in Designer

As part of your upgrade, you will need to import any flowlet groups that were introduced in versions subsequent to your last upgrade.

Prerequisites

Check to see which flowlet groups that you already installed in previous releases. See the Checking which Flowlet Groups are Currently Installed topic.

Context

If you have all of the flowlet groups installed, then you can skip this procedure; the next step is for you to update the flowstores.

If some of the flowlet groups are missing from your installation, you will need to import them now.



To import new flowlet groups in Designer, perform the following steps:

Procedure



If you haven't changed the password, enter password3. In the Folders tree, select SAP Underwriting for Insurance.

4. In the detail panel, right-click and choose Import Flowlet Group.5. Browse to the directory where you unzipped FS-QUO-exports-<pqm_release>.<sp>.<pl>.zip, go to

the flowlet_groups directory, select the flowlet JAR file to import, and choose Next.

The table below lists all of the flowlet groups that should be imported and configured. You need to import the JAR files for any of the flowlet groups that don't currently exist on your server.

CautionThe flowlet groups must be imported in the following order:

Flowlet Groups



3.0 SP00


3.0 SP00


3.0 SP00


3.0 SP00


3.0 SP00


3.0 SP00


3.0 SP00




3.0 SP00


3.0 SP00


3.0 SP00


3.0 SP00


3.0 SP00


3.0 SP00


3.0 SP00


3.0 SP02


3.0 SP03


3.0 SP03

6. In the Flowlet Group Details screen, choose Next.7. In the Flowlet Group Validation screen, ensure that there aren't any validation errors and choose Next.8. In the details screen specific for the flowlet group being imported, choose Next to begin the import.9. When asked to specify a target name to rename the imported objects, choose Next.

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.

10. Ensure that there are no errors in the import log, and choose Close.



Related Information

Checking which Flowlet Groups are Currently Installed [page 58]

9.4 Updating Process Flowstores

As part of the upgrade process, you need to update the flowstores that you have already imported as part of a previous installation or upgrade.

Context

Any new flowstores included in the current support package won't be included in the update process; they need to be imported separately from the update task by following the procedure from the Importing New Flowlet Groups in Designer [page 60] topic.

To update your process flowstores, perform the following steps:

Procedure




3. In the Folders tree, select Applications SAP Underwriting Insurance .4. Import all of the flowlet groups which contain the flowstores into the FS-QUO application using the JAR

files in the flowlet_groups directory of FS-QUO-exports-<pqm_release>.<sp>.<pl>.zip.

a. Double-click on the flowlet group in the right panel.b. Right-click on the flowstore in the flowlet group and choose Import.c. Select the JAR file from the browse dialog and choose Next.d. On the Flowstore Details screen, choose Next.e. On the Flowstore List screen, choose Next.f. On the Flowstore Validation screen, choose Next to begin importing.g. After the import completes, download the log file for viewing (in case of errors), or close the dialog if

the import was successful.

CautionThe flowlet groups must be imported in the following order.


Flowlet Groups



3.0 SP00


3.0 SP00


3.0 SP00


3.0 SP00


3.0 SP00


3.0 SP00


3.0 SP00


3.0 SP00


3.0 SP00


3.0 SP00


3.0 SP00


3.0 SP00


3.0 SP00





3.0 SP00


3.0 SP02


3.0 SP03


3.0 SP03

Related Information

Importing New Flowlet Groups in Designer [page 60]

9.5 Rebuilding Flowlets with the BatchFlowBuildServlet Tool

Context

To rebuild the flowlets, perform the following procedure:

Procedure

Run the following URL to invoke a process building all flowlets: https://<FS-QUO_server_host>:<FS-QUO_server_https_port>/csiroot/cservlet/BatchFlowBuildServlet


Results

When the build process completes, you will see error messages in the log regarding child flowstores. These error messages can be safely ignored.

9.6 Synchronizing Product Flowstores

This topic describes how to synchronize your product flowstores to confirm the structure of your database tables matches the flowstore definitions defined in the Designer server.

Context

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. You need to synchronize your product flowstores to 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/adminLog in with the Admin user account.

2. Choose Product Synchronize Product Flowstore from the menu bar.3. In the Product Name field, enter a product name based on the line of business you are configuring for.

Example:○ Commercial PnC: Enter Mock Commercial General Liability Monoline in the Product Name

field.○ Personal PnC: Enter Sample Household Product in the Product Name field.○ Life: Enter Life Capital 2009 92H0000S0002 in the Product Name field.○ Auto: n/a (no sample product)○ Master Policy: Enter SAP Master Policy in the Product Name field.

Leave the Product Version field as 1 and choose Next.

The system will process the flowstores in the product. When it is done, you will see the process time at the end of the log.



4. Choose Next>>.5. In the flowstore tree, select each of the flowstores whose names are displayed in red and then choose

Apply.Any flowstores that aren't displayed in red are already synchronized.

Results

You will see the message Script Applied Successfully when the sync process is completed.

9.7 Updating Database Objects for Underwriting

Some database updates need to be applied to the Designer Runtime database using a database update utility. You can choose to run the Database Update Wizard in GUI mode (typical) or console mode.

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

NoteEnsure 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.


9.7.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:

a. Go to Installations and Upgrades on the SAP Support Portal.b. Choose Software Downloads and search for FS-QUO.c. Download the following ZIP file:

○ Windows: FS-QUO-db-windows-x64-<pqm_release>.<sp>.<pl>.zip○ UNIX: FS-QUO-db-unix-<pqm_release>.<sp>.<pl>.tar.gz

2. Stop the Designer Runtime instance using the SAP MMC.3. Extract the Database Update Wizard executable file from the ZIP file:

○ Windows: FS-QUO-db/bin/updateDB.exe○ UNIX: FS-QUO-db/bin/updateDB

4. Launch the Database Update Wizard executable file:○ Windows: FS-QUO-db/bin/updateDB.exe○ UNIX: 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 Designer Runtime and the Database type to Oracle. Choose Next when all information is provided.For details on the FS-QUO database user name prefix field, refer to the description of the <db_user_name> substitution variable in the Substitution Variable Placeholders [page 6] topic. For details on the other fields, refer to the context help on the screen.

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.

9.7.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

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


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-<pqm_release>.<sp>.<pl>.tar.gz○ Windows: FS-QUO-db-windows-x64-<pqm_release>.<sp>.<pl>.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 <db_user_name> substitution variable in the Substitution Variable Placeholders [page 6] topic. Press Enter when all information is provided.



NoteIf you want 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.


○ 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.

9.7.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 SAP HANA Database Update Wizard can only be run from the HANA database server host.

Context


Procedure


a. Go to Installations and Upgrades on the SAP Support Portal.b. Choose Software Downloads and search for FS-QUO.c. Download the following ZIP file: FS-QUO-db-<pqm_release>.<sp>.<pl>.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/updateDB4. 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. Choose Next when all information is provided.For details on the FS-QUO database user name prefix field, refer to the description of the <db_user_name> substitution variable in the Substitution Variable Placeholders [page 6] topic. For details on the other fields, refer to the context help on the screen.





9.7.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 SAP HANA Database Update Wizard can only be run from the SAP HANA database server host.

Context



Procedure



a. Go to Installations and Upgrades on the SAP Support Portal.b. Choose Software Downloads and search for FS-QUO.c. Download the following ZIP file: FS-QUO-db-<pqm_release>.<sp>.<pl>.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/updateDB4. 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 -c5. 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. Press Enter when all information is provided.


For details on the FS-QUO database user name prefix field, refer to the description of the <db_user_name> substitution variable in the Substitution Variable Placeholders [page 6]topic.









9.7.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


Procedure


a. Go to Installations and Upgrades on the SAP Support Portal.b. Choose Software Downloads and search for FS-QUO.c. Download the following ZIP file: FS-QUO-db-windows-x64-<pqm_release>.<sp>.<pl>.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.exe4. Launch the Database Update Wizard executable file: FS-QUO-db/bin/updateDB.exe5. 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. Choose Next when all information is provided.For details on the FS-QUO database user name prefix field, refer to the description of the <db_user_name> substitution variable in the Substitution Variable Placeholders [page 6] topic. For details on the other fields, refer to the context help on the screen.







9.7.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


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-<pqm_release>.<sp>.<pl>.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.exe4. Launch the Database Update Wizard executable with the -c option: FS-QUO-db/bin/updateDB.exe -c5. 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 <db_user_name> substitution variable in the Substitution Variable Placeholders [page 6] topic. Press Enter when all information is provided.










9.7.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


Procedure


a. Go to Installations and Upgrades on the SAP Support Portal.b. Choose Software Downloads and search for FS-QUO.c. Download the following ZIP file: FS-QUO-db-unix-<pqm_release>.<sp>.<pl>.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/updateDB4. On the UNIX machine where the IBM DB2 database server is installed, launch the Database Update Wizard

executable: FS-QUO-db/bin/updateDB5. 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. Choose Next when all information is provided.For details on the FS-QUO database user name prefix field, refer to the description of the <db_user_name> substitution variable in the Substitution Variable Placeholders [page 6] topic. For details on the other fields, refer to the context help on the screen.







9.7.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



Procedure


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-<pqm_release>.<sp>.<pl>.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/updateDB4. Launch the Database Update Wizard executable with the -c option: FS-QUO-db/bin/updateDB -c5. 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 <db_user_name> substitution variable in the Substitution Variable Placeholders [page 6] topic. Press Enter when all information is provided.










9.8 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 or sample products in your sandbox environment or your own product in your production environment, follow the instructions below to synchronize the applicable product flowstore.

To pre-load products into memory, perform the following steps:

Procedure

1. Run the URL https://<FS-QUO_server_host>:<FS-QUO_server_https_port>/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, as in the following example:○ For the Commercial PnC LoB, select Mock Commercial General Liability Monoline.○ For the Personal LoB, select Sample Household Product, Sample Household Product Traditional

Chinese, Sample Household Product Korean, and Sample Household Product Extended○ For the Life LoB, select Life Capital 2009 92H0000S0002.○ The Auto LoB has no sample product, so this step isn't applicable.

3. Click Submit Query.


Results

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

Next Steps

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

9.9 Verifying the FS-QUO Installation

After you upgrade the flowstores, database and FS-QUO application, you can verify that the entire upgrade completed successfully.

Context

To verify the upgrade, perform the following steps:

Procedure

1. Log into FS-QUO: <FS-QUO_server_host>:<FS-QUO_server_http_port>/csiroot2. Enter uw2 as the user name and password as the password, then click Log In.

3. Choose About .The About SAP Underwriting for Insurance dialog displays.

4. Verify that the following information displays: Version <pqm_release>.<sp>.<pl>



10 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 steps.

If your FS-QUO instance is integrated with SAP Workplaces for Insurance (FS-IPW), your next step will be to upgrade your FS-IPW software. For more information, see the SAP Workplaces for Insurance Upgrade Guide.

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.

Support Package Upgrade GuideNext Steps PUBLIC 79

Important Disclaimers and Legal Information

HyperlinksSome 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 PlatformsSome 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 FeaturesExperimental 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 CodeAny 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 LanguageWe 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.


Important Disclaimers and Legal Information

Support Package Upgrade GuideImportant Disclaimers and Legal Information PUBLIC 81

www.sap.com/contactsap

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN

https://www.sap.com/about/legal/trademark.html

Documents

Support Package Upgrade Guide - help.sap.com