SSM10 Administrator's Guide

Administrator's Guide SAP BusinessObjects Strategy Management Application Server 10.
0 Series
Target Audience Technical Consultants System Administrators Solution Consultants Support Specialist
PUBLIC Document version: 1.1 2011-09-14
SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com
Copyright 2011 SAP AG. 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 AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. in the United States and in other countries. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group 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.
Disclaimer
Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAPs Support Services and may not be modified or altered in any way.
2/62
PUBLIC
2011-09-14
Document History
CAUTION
Before you start the implementation, make sure you have the latest version of this document. You can find the latest version on SAP Service Marketplace at http://service.sap.com/ instguidesEPM-STM. The following table provides an overview of the most important document changes.
Version Date Description
1.0 1.1
2011-06-16 2011-09-14
First version no changes. Corrected text about XRAY s
2011-09-14
PUBLIC
3/62
Table of Contents
Chapter 1 Chapter 2 Chapter 3 3.1 3.1.1 3.1.2 3.1.3 3.2 3.3 3.3.1 3.3.2 3.3.3 Chapter 4 4.1 4.2 4.2.1 4.2.2 4.2.3 4.2.4 4.2.5 4.3 4.3.1 4.3.2 4.3.3 4.3.4 4.4 4.5 4.5.1
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Technical System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Monitoring Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trace and Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Development Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tracing During Runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Trace Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activity and Resource Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Microsoft Process Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Server Monitoring Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . Management of Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administration Tools of Software Components . . . . . . . . . . . . . . . . . . . . . . . . Starting and Stopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using SAP SM Listener Daemon Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . Starting the SAP SM Listener on Microsoft Windows . . . . . . . . . . . . . . . . . . . . Modifying the Account Used by Listener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing Client/Server Session Listings from the Windows Taskbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping the SAP SM Listener Service on Microsoft Windows . . . . . . . . . . . . . Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dumping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring Backed Up Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading a Dumped Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required Manual Periodic Tasks to Maintain the Application . . . . . . . . . . . . . Updating the Latest Date for Data in the Model . . . . . . . . . . . . . . . . . . . . . . . . 11 11 12 14 14 15 16 16 16 16 19 19 19 19 21 22 23 23 24 25 25 26 26 26 27 27
4/62
PUBLIC
2011-09-14
4.5.2 4.5.3 4.6 Chapter 5 5.1 5.2 5.3 5.3.1 5.3.2 5.3.3 5.3.4 5.3.5 5.3.6 5.3.7 Chapter 6 6.1 6.2 6.3 6.4 Chapter 7 7.1 7.2 7.3 7.3.1 7.3.2 7.4 7.4.1 7.4.2 7.4.3 7.4.4
Maintaining Correct User Status After a Model Update . . . . . . . . . . . . . . . . . . 28 Model Changes and Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Architecture Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Cluster Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up a Strategy Management Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Strategy Management Services . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Strategy Management Services to the Cluster . . . . . . . . . . . . . . . . . . . Updating the Java System Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Moving .INI Files to the Shared Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating the Application Server Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up a Link ID for Certain Implementations . . . . . . . . . . . . . . . . . . . . . . Software Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transporting Models on Like Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transporting Models on Different Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . Support Packages and SAP Notes Implementation . . . . . . . . . . . . . . . . . . . . . . Release and Upgrade Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Testing and Troubleshooting Client/Server Connections . . . . . . . . . . . Testing Client/Server Connections on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . Connection for Two Installations of Application Server . . . . . . . . . . . . . . . . . Troubleshooting Client/Server Connections on UNIX . . . . . . . . . . . . . . . . . . Reviewing the Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Trace Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Testing Client/Server Connections on a Microsoft Windows Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging Client/Server Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Testing SAP SM Listener and the TCP/IP Protocol . . . . . . . . . . . . . . . . . . . . . . Testing Connections Between the Client and Server . . . . . . . . . . . . . . . . . . . . Configuring Microsoft Windows User Permissions for Client/Server Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 31 31 32 32 33 33 34 34 35 35 37 37 37 38 38 41 41 42 42 42 44 44 45 45 45 46
Chapter 8 8.1
Support Desk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Remote Support Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2011-09-14
PUBLIC
5/62
8.2 8.3 Chapter 9 9.1 9.2 9.3 9.4 9.5 9.6 9.7 9.8 9.9 9.10 Chapter 10
CA Wily Introscope Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Problem Message Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Application Server Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . Application Server Environment Variables on UNIX . . . . . . . . . . . . . . . . . . . . UNIX Environment Variables and Shells Scripts . . . . . . . . . . . . . . . . . . . . . . . Identifying the Shell Used by a Native UNIX Account . . . . . . . . . . . . . . . . . . . Environment Variables in Native UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Environment Variables in Native UNIX Using the C Shell . . . . . . . . . . . . . . . . Environment Variables in a Client/Server UNIX . . . . . . . . . . . . . . . . . . . . . . . Changing File Locations in Lsstcp.sh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reviewing UNIX File Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing File Privileges in UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the DBHOME Environment Variable . . . . . . . . . . . . . . . . . . . . . . . 51 51 52 52 53 54 55 55 56 57 58
Related Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
6/62
PUBLIC
2011-09-14
Getting Started
1 Getting Started
This guide provides a starting point for managing SAP BusinessObjects Strategy Managements Application Server. It contains specific information for various tasks and lists the tools that you can use to implement them. Application Server is a highly scalable, Time-Intelligent multidimensional Online Analytical Processing (OLAP) server that brings you the ability to quickly analyze all aspects of your business without having to understand all the data relationships behind the scenes. Application Server is available on Windows and UNIX platforms.
2011-09-14
PUBLIC
7/62
This page is left blank for documents that are printed on both sides.
Technical System Landscape
2 Technical System Landscape
The following table lists where you can find more information about the technical system landscape.
Topic Guide or Tool Quick Link on SAP Service Marketplace
http://service.sap.com/instguidesEPM-STM
System Landscape Master Guide for SAP BusinessObjects Strategy Management Installation Guide for SAP Installation and BusinessObjects Strategy Management configuration Security Guide for SAP BusinessObjects Security Strategy Management
http://service.sap.com/instguidesEPM-STM http://service.sap.com/securityguide SAP BusinessObjects SAP BusinessObjects Enterprise Performance Management (EPM) SAP BusinessObjects Strategy Management Security Guide None
Administration
Online Help in the Application Server Administrator system.
2011-09-14
PUBLIC
9/62
3 3.1
Monitoring Application Server Trace and Log Files
3 Monitoring Application Server
3.1 Trace and Log Files

Logging in Application Server can be enabled in the following areas: End-toend tracing SAP SM Listener For the Application Server sessions
Logging Severity Levels and End-to-End Tracing
You can add the NCSTRACE=1 parameter to lsserver.ini to enable end-to-end tracing and heartbeat availability monitoring. This is useful when installing and configuring Solution Manager for diagnostic purposes. To perform end-to-end tracing, you need to use the SAP Client plug-in for Internet Explorer and start a transaction using the normal procedures for end-to-end tracing. To enable logging for diagnostic purposes, add the NCSLOG=INFO | WARNING | ERROR | FATAL line to lsserver.ini. Specify the appropriate severity level by using a value of either INFO, WARNING, ERROR, or FATAL. If you specify INFO, you get the most information (all INFO, WARNING, ERROR, and FATAL status messages). If you set it to WARNING, ERROR, or FATAL, you only get messages of that type. The generated files are <uuid>.GLF files, which you can view using a text editor or SAPs log viewing tool. The files exist in \Logs directory of the Application Server installation directory. Since model connections generate their own log or trace file, this setting is useful for pre-production, but not for production systems. To turn off logging, you can comment out the line. Application Server logs are located in the \<install-dir>\SAP BusinessObjects\Strategy Management\ApplicationServer\LOGS directory.
NOTE
You must restart the JPIP session to allow the changes in lsserver.ini to take effect. To do so, access the JPIP session monitor using the Tools utility at http://<nw_server>:<port>/strategy/ tools.
Logging connection information during model development
Information in the SAP SM Listener log file contains connection information. To enable debug output from the SAP SM Listener, add the following lines to the lssagent.ini file located in the Microsoft Windows directory on the server where Application Server is installed:
[Agent]
2011-09-14
PUBLIC
11/62
3 3.1
Debug=Y Logfile=C:\temp\lssagent.log
You access the lssagent.log file by opening it in a text editor. It is located in the path you specified for Logfile in the lssagent.ini file.
LSSTLD.LOG
When you start the SAP SM Listener daemon on UNIX, the log file LSSTLD.LOG is created in the <install-dir>\lss directory. This file contains diagnostic messages and tracks client/server connection requests. An entry is added to LSSTLD.LOG each time lsstld detects a request for a connection. A second line is added listing the requested service name if the connection is successful. If the connection is rejected, a message identifying the cause of the failure is appended to the log. For more information, see Using SAP SM Listener Daemon Server on UNIX [page 19]. For more information about this log file used for troubleshooting, see Testing and Troubleshooting Client/Server Connections [page 41].
LSSLOG LSSLOG is created by the lsstcp executable in the UNIX user accounts Home directory when you make
a client/server connection. The LSSLOG file contains information about the version, the environment, the process number, and the time of connection. This file also contains error message information if there are problems in establishing a client/server connection. For more information about this log file used for troubleshooting, see Testing and Troubleshooting Client/ Server Connections [page 41].
LSSTRACE
You can record all Application Server API calls in a file using the trace facility. You should only use the trace facility for diagnostic purposes because it can slow down processing. To enable LSSTRACE, locate the lsstcp.sh script and open it for editing. Change the LSSTRACE value from null to the name of the trace file you want to create or to YES. Application Server writes client/ server API calls to a file called LSSTRACE in your Home directory.
3.1.1 Development Tracing

Using the TRACE command in Application Server Administrator, you can enable tracing in any Application Server procedure.
Features
SYNTAX TRACE [COMMANDS|TIMING|OUTPUT|BOTH] {<destination> [APPEND]OFF|UPDATE}
12/62
PUBLIC
2011-09-14
3 3.1
Monitoring Application Server Trace and Log Files Description
Keyword
COMMANDS
Copies either commands from the command window or any job to a printer or destination.
NOTE
TIMING
OUTPUT
BOTH <destination>
APPEND
OFF UPDATE
You can have both TRACE COMMANDS and TRACE BOTH active at one time. For example, you can enter a command in the form TRACE COMMANDS testproc to capture only the commands you enter in the procedure TESTPROC, and a command in the form TRACE BOTH tracecheck to capture both commands and output in the document TRACECHECK. To turn off these commands, you need to enter TRACE COMMANDS OFF and TRACE BOTH OFF. Specifies the time it takes to execute the commands from the command window or any job to a printer or destination. In the output, the timing is displayed first, and then the command. If you specify TRACE TIMING TERMINAL, timing information appears after the command output. Copies output (data, error messages, reassurance messages) to destination. Copies both commands and output to the destination (default). One of the following destinations: TERMINAL Your terminal. PRINTER The default printer on your system. <setname> [;<database>|;EXTERNAL <setname> Name of a set. If you copy commands, Application Server creates a procedure. If you copy output or both commands and output, Application Server creates a document. <database> Name of database where the set is located. If no database is specified, Application Server uses the Use database. EXTERNAL Indicates the set is a text file not in an Application Server database. If the set is a DOS file, its name cannot have an extension. When specifying a path and filename for the destination on UNIX, make sure that you do not exceed 53 bytes. Overrides the default and adds the trace to the end of an exporting file or set, without overwriting it. Turns off a TRACE command. Enter TRACE OFF to end a trace. When used, each command and its output is sent to the destination when it is executed instead of being buffered.
Example
Issue the following command to trace all commands and output to a text file:
TRACE BOTH <setname>; EXTERNAL
2011-09-14
PUBLIC
13/62
3 3.1
3.1.2 Tracing During Runtime

You can use tracing while the application is running by turning tracing on or off. There is no severity setting that allows you to just log the errors. The three files that are generated provide different levels of information. The trace files are named by the username and model you are accessing as follows:
<modelname><app_server_user><unique_stamp>_time.txt
Contains all commands and the response times to process the commands in the same session
<modelname><app_server_user><unique_stamp>_both.txt
Contains all commands and the results/output from those commands

<modelname><app_server_user><unique_stamp>_cmd.txt
Contains all commands issued by the application

Procedure
1. 2. 3. 4.
Start the Tools utility at this URL:

http://<nw_server>:<port>/strategy/tools
Select Application Tracing, and then select Enable for the PAS Trace setting. This enables tracing of the communication between the application and the Application Server model. Select the Back function on the Internet Explorer browser window to return to the Tools utility. Select JPIP Session Monitor and then select Restart JPIP. This restarts JPIP to ensure that a new session is established with tracing enabled.
NOTE
When you have finished tracing, select Disable to turn off tracing.
More Information
Viewing Trace Files [page 14]
3.1.3 Viewing Trace Files

You can view Application Server trace files in a text editor or using the PAS Query tool.
Prerequisites
To view trace files using a text editor, you have access to the server where Application Server is installed. To view trace files using the PAS Query tool, you know the name of the trace file you want to view.
Procedure
1. 2. 3.
Start the Tools page by issuing this URL in the Address box of a Web browser window:
http://<nw_server>:<port>/strategy/tools
Choose JPIP Session Monitor. Restart the JPIP session by clicking Restart JPIP.
14/62
PUBLIC
2011-09-14
3 3.2
Monitoring Application Server Database Monitors NOTE
4.
5.
You restart the JPIP Session to unlock the trace files so you can view them. To view trace files using a text editor, navigate to the\<install-dir>\ApplicationServer\home directory on the system where Application Server is installed and open the trace files in a text editor. To view trace files using the PAS Query tool, do the following: 1. Access the Tools utility at http://<nw_server>:<port>/strategy/tools and choose PAS Query. 2. In the Context dropdown list, select the model connection to work with. 3. At the end of the context string in the Address box, enter:
DQL=TYPE document <modelname><app_server_user><unique_stamp>_both.txt
When you are finished capturing, disable the Pas Trace using the Tools Application Tracing
utility.
3.2 Database Monitors

You can monitor the Application Server database using Application Server commands. This table shows the commands you can use:
Application Server Command
DIRECTORY SHOW DATABASE <database> SHOW DBSTATS
Detailed Description
SUPERVISOR SHOW DATABASE <database> EXHIBIT DATABASES <options> CREATE DATABASE MULTIPLE <number>
XRAY <database>
XRAY t <database>
XRAY s <database>
Displays the sets in a database. Provides summary information about attached databases. Displays statistical information about the current database and buffer setting recommendations. Displays information about databases and their partitions. Displays information about Application Server databases. When creating a database, MULTIPLE specifies the number of values that can be added to a time series before the record size is increased. The default is 6, which means that 6 values can be added to the time series. As these are filled, the database does not change in size. When a seventh point is added, the database almost doubles in size as space is set aside for an additional six points of data. A MULTIPLE setting is valid only for variables that are single or double precision floating (4 or 8 bytes, nonsparse). Used at the operating system level on the server, this command evaluates all the basic structures within the Application Server database and performs an integrity check. If you suspect that a database is corrupt, XRAY might be able to find the location of the corruption. Used at the operating system level on the server, this command provides a complete analysis of the database structure. Lists information about all internal sets in an Application Server database. Used as a diagnostic tool to determine the structure and content of a model.
2011-09-14
PUBLIC
15/62
3 3.3
Monitoring Application Server Activity and Resource Monitors Detailed Description

XRAY f <database>
SUPERVISOR XRAY <database> RECORDS | NOTREE
Used at the operating system level on the server, this command reclaims lost space in an Application Server database. An Application Server command that validates records in the database. RECORDS validates all the records in the database. This option is time consuming for large databases and you should use it with care. If you do not use the RECORDS option, Application Server does not check each record, and runs much faster, but provides somewhat less validity checking. NOTREE switches off the checking of B-Trees. Use this option to do a brief check on a large database.
3.3 Activity and Resource Monitors 3.3.1 Using Microsoft Process Explorer
Application Server provides a monitor for online display of the current activity at the component level as well as the current utilization of resources and current blocking situations due to locking situations. The following information is available in the Microsoft Sysinternals Process Explorer. Peak memory consumption in MB CPU consumption in milli sec Number of accesses to the persistence layer
Procedure
1. 2.
Open the Process Explorer window, and select the lsstcp.exe process from the list. Click the Performance tab to review the performance.
3.3.2 Monitoring Tools

To monitor activity and resources for Application Server, you must use the monitoring tools provided by your operating system, such as Task Manager in Microsoft Windows or the top utility in UNIX/ Linux, which displays top CPU-using processes.
3.3.3 Application Server Monitoring Commands

Use the monitoring tools provided by your operating system, such as Task Manager in Microsoft Windows or the top utility in UNIX/Linux, which displays top cpu-using processes. Use the following commands to monitor system activity as it relates to Application Server databases.
ROLLUP
Use the Rollup editor to monitor growth in the following ways:
16/62
PUBLIC
2011-09-14
3 3.3
Monitoring Application Server Activity and Resource Monitors Detailed Description
SHOW SPARSITY
SHOW DBSTATS
Display the quadrants and their rollup instructions and their percentage that they are already consolidated. Remove time-series combinations that Application Server does not need for reporting and analysis to avoid unnecessary consolidation. This reduces the size of the database and increases calculation speeds. Specify that certain member combinations are consolidated on the fly as needed. Combinations are consolidated whenever any commands are issued that require data about the combinations. The aggregations are not saved in the database. Shows the sparsity of time series on a variable-by-variable and quadrant-by-quadrant basis Displays statistical information about the current database and buffer setting recommendations
2011-09-14
PUBLIC
17/62
4 4.1
Management of Application Server Administration Tools of Software Components
4 Management of Application Server
4.1 Administration Tools of Software Components

Transaction/Tool Detailed Description Prerequisites
Application Server Administrator See the online Help in the Application You must be a known user in Server Administrator program for Application Server to use this information. program.
4.2 Starting and Stopping

Tool
sh tldgo sh tldstop NET START LSSAGENT
NET STOP LSSAGENT
Start
Stop
Starts the SAP SM Listener daemon service on the UNIX server. Stops the SAP SM Listener daemon service on the UNIX server. Starts the SAP SM Listener service on a Microsoft Windows server from a command prompt. Stops the SAP SM Listener service on a Microsoft Windows server from a command prompt. Starts the SAP SM Listener service from the Desktop on the Microsoft Windows server from Control Panel Administrative Tools Services program. Right-click on the service and choose Start from the floating menu. Stops the SAP SM Listener service from the Desktop on the Microsoft Windows server from Control Panel Administrative Tools Services program. Right-click on the service and choose Stop from the floating menu.
4.2.1 Using SAP SM Listener Daemon Server on UNIX

In the Installation Guide for SAP BusinessObjects Strategy Management, you were instructed to follow postinstallation steps for setting up Application Server after installing the product on UNIX. The first step instructed you to start the SAP SM Listener daemon (Listener), called lsstld. The Listener program is a UNIX daemon, which is a process that runs continually without being connected to a terminal. In this case, lsstld is listening for Application Server TCP/IP connections on the specific port number (the default is 8325). The client machines running Application Server use WINSOCK support for client/ server communications to UNIX servers. You can do the following: Start the Listener Set up the Listener to automatically start when UNIX is started
2011-09-14
PUBLIC
19/62
4 4.2
Management of Application Server Starting and Stopping
Stop the Listener

Procedure
Starting Listener Daemon Server on UNIX
The following steps start the SAP SM Listener. Once you are sure that the software is installed correctly, you can add the commands to your systems startup files so that the SAP SM Listener starts up automatically whenever the system is restarted. 1. Log on as root to allow the listener process to establish sessions on behalf of the UNIX user accounts. 2. Change to the directory where Application Server is installed. For example:
cd /<install-dir>/lss
3.
Run the shell script to start the Listener:

sh tldgo
When lsstld is initialized, it creates the log file LSSTLD.LOG in the current directory, and displays the following messages:
SYNTAX ******************************************************************** lsstld: daemon initialization started at Mon Dec 20 08:59:15 2010 lsstld: daemon initialization completed at Mon Dec 20 08:59:15 2010 ********************************************************************
The LSSTLD.LOG file tracks client/server connection requests. An entry is added to LSSTLD.LOG each time lsstld detects a request for a connection. A second line is added listing the service name if the connection is successful. If the connection is rejected, a message identifying the cause of the failure is appended to the log. In this sample LSSTLD.LOG, connection requests to the Application Server service names LSS80 and LSSJAPAN are successful. The last two connection requests fail because a UNIX logon ID/password confirmation was not validated and the service name LSS80 was not defined.
SYNTAX ********************************************************************* Application Server TCP/IP listener daemon log lsstld daemon initialization started at Tue Dec 21 10:46:25 2010 The user name is root, UID=0, GID=3, SHELL=/bin/ksh. The home directory is /. The lsserver service was found in /etc/services. The port number is 8325. Socket 5 was successfully created. The listen address is bound to the socket. The socket is now listening for remote connections. lsstld daemon initialization completed at Tue Dec 21 10:46:25 2010 ********************************************************************* Connection request from IP address 999.999.99.999, using port 1039 at Tue Dec 21 10:46:48 2010 Connection request from 999.999.99.999 accepted. Calling service LSS80. Connection request from IP address 999.999.99.999, using port 1034 at Tue Dec 21 11:03:01 2010 Connection request from 999.999.99.999 accepted. Calling service LSSJAPAN. Connection request from IP address 999.999.99.999, using port 1042
20/62
PUBLIC
2011-09-14
4 4.2
Management of Application Server Starting and Stopping at Tue Dec 21 13:54:45 2010 The login ID/password combination was rejected by crypt! Connection request from 999.999.99.999 rejected! Connection request from IP address 999.999.99.999, using port 1043 at Tue Dec 21 14:02:40 2010 The LSS80 service was not found in the lssmap file!
Setting up Listener Daemon To Start When UNIX Is Started
You can add commands to your systems startup files so that the Application Server listener starts up automatically whenever the system is started. 1. Find the system-specific startup file. Usually, this is located in /etc. 2. Add these lines:
cd /<install-dir>/lss <install-dir>/lss/tldgo > /dev/console
If the lsstld process is not active after system restart, check the LSSTLD.LOG file in the directory where Application Server is installed.
Stopping the Listener Daemon
In some situations, you may need to stop the Listener daemon when you need to prevent connections to the UNIX server where Application Server is installed. For example, if you are running a system backup or updating a dimensional model, you might need to stop the Listener. These steps describe how to stop the Listener. 1. Log on as root. 2. Change to the directory where Application Server is installed:
cd /<install-dir>/lss
3. 4.
Enter the following command to stop lsstld:

sh tldstop
The following message appears:

Application Server TCP/IP running with Process ID: 99999 Do you really want to stop this listener (Y/N) [Y]
5.
Press
Enter
to stop the Listener daemon, or type N and then press
Enter
to cancel the request.
4.2.2 Starting the SAP SM Listener on Microsoft Windows

After the installation of Application Server, the SAP SM Listener service is automatically started by default on the Microsoft Windows server. The Listener program listens for WINSOCK TCP/IP Application Server client connections. The Listener service validates the user's rights to log on to the server and start the data communication process. Although the Listener is started by default, follow these steps if you ever need to start the SAP SM Listener on your own.
2011-09-14
PUBLIC
21/62
4 4.2
Procedure
Starting the SAP SM Listener Service from the Desktop
1. 2. 3.
On your Microsoft Windows Desktop of the Microsoft Windows server, choose Start Control Panel . Choose Administrative Tools, and then choose Services to display the Services window. Right-click on SAP SM Listener and choose Start.
Starting the SAP SM Listener Service from the Command Prompt
1. 2.
Open a Command prompt window. Issue the following command:

NET START LSSAGENT
4.2.3 Modifying the Account Used by Listener

By default, the SAP SM Listener is installed as a Microsoft Windows service that has the appropriate privileges to use the Microsoft Windows Server Logon API calls. The service uses the LocalSystem account, which has the appropriate privileges by default. The service is installed with the Log on as a system account option. If you set up the SAP SM Listener to log on with an account other than the system account, then you must also make sure that the user has Log on Locally rights.
Procedure
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13.
On your Microsoft Windows Desktop of the Microsoft Windows server, choose Start Control Panel . Choose Administrative Tools, and then choose Services to display the Services window. Right-click on SAP SM Listener and choose Properties to display the SAP SM Listener Properties dialog box Click the Log On tab. Change the Log on as properties to the account you want the agent to use. Click OK. Close the Services window. Now that you have changed the agent to use a different account, you must set privileges for the new account. In Administrative Tools, choose Computer Management to display the Computer Management window. Select a user you want the agent to use. Close the Computer Management window. In Administrative Tools, choose Local Security Policy to display the Local Security Settings window. In the Local Policies folder, choose User Rights Assignment. Add the following three rights to the account you have selected for the SAP SM Listener service: Act as part of the operating system
22/62
PUBLIC
2011-09-14
4 4.2
Replace a process level token Increase quotas
4.2.4 Removing Client/Server Session Listings from the Windows Taskbar

By default, the system account is set up with the Allow the service to interact with the desktop option. This option displays an icon on the Microsoft Windows server taskbar for every Application Server client/server session. You can remove this option from the toolbar if you do not want it displayed.
Procedure
1. 2. 3. 4. 5. 6. 7.
On your Microsoft Windows Desktop of the Microsoft Windows server, choose Start Control Panel . Choose Administrative Tools, and then choose Services to display the Services window. Right-click on SAP SM Listener and choose Properties to display the SAP SM Listener Properties dialog box. Click the Log On tab. Deselect the Allow Service to Interact with Desktop option. Click OK. Restart the SAP SM Listener to implement your changes.
4.2.5 Stopping the SAP SM Listener Service on Microsoft Windows

If you make modifications to the Startup parameters of the SAP SM Listener service, then you must restart the SAP SM Listener service to implement your changes. If you make changes to any of the LSSAGENT.INI or LSSERVER.INI file parameters that affect the SAP SM Listener service, then you must stop and restart the SAP SM Listener service.
Procedure
Stopping the SAP SM Listener Service from the Desktop
1. 2. 3.
On your Microsoft Windows Desktop of the Microsoft Windows server, choose Start Control Panel . Choose Administrative Tools, and then choose Services to display the Services window. Right-click on SAP SM Listener and choose Stop.
Stopping the SAP SM Listener Service from the Command Prompt
1. 2.
Start a Command prompt window. Issue the following command:

NET STOP LSSAGENT
2011-09-14
PUBLIC
23/62
4 4.3
Management of Application Server Backup and Restore
4.3 Backup and Restore

Before making extensive modifications to a model, we recommend using operating system utilities to back up your model. Backup and restore of Application Server databases can be performed by backing up files at the system level, and using DUMP and LOAD Application Server commands in the Application Server Administrator. Data Storage Locations:
Data Location
Application data
Relational data SAP NetWeaver BW cube data User data Configuration data
User databases in Application Server CGLIB database in Application Server contains user-defined hierarchy information, if implemented Relational data files (in a Hybrid OLAP implementation) SAP NetWeaver BW cube MASTERDB database in Application Server Lsdal.cnf located in the \Microsoft Windows directory. Contains database connection settings, for example, Microsoft SQL Server, Oracle). Lsdal.ini located in the \Microsoft Windows directory. Contains Application Server connection settings to data sources, and BAPI connections to BW. Lsserver.ini located in the \Microsoft Windows directory. Contains Application Server directory settings and database settings.
\<install-dir>\SAP BusinessObjects\Strategy Management \ApplicationServer\logs
Logs files Trace files
\<install-dir>\SAP BusinessObjects\Strategy Management \ApplicationServer\home
Backup:
DUMP
SUPERVISOR DUMP
Transfers the Use database to one or more external text files (dump files). Creates an external file on your system containing all the Supervisor commands needed to re-create MASTERDB. Application Server encrypts user passwords on the dump file.
Restore:
LOAD SUPERVISOR LOAD
Loads a database from an external dump file of any size. Restores MASTERDB from an external dump file or tape.
24/62
PUBLIC
2011-09-14
4 4.3
Management of Application Server Backup and Restore
4.3.1 Backing Up
Procedure
1.
2.
3. 4. 5.
On a Microsoft Windows server, back up the following files located in \Program Files (x86)\SAP BusinessObjects\Strategy Management\ApplicationServer\data. On a Linux/UNIX server, the files are located in the data directory in the installation location. CGLIB (Contains User-Defined Hierarchies if using an UDH implementation) MASTERDB (Catalog of models, users, and other important system information) Databases created in Application Server Relational files used in a Hybrid OLAP implementation SAP NetWeaver BW cubes used in an SAP NetWeaver BW Connector implementation If you customized any files that are put down by the installation, copy those files to a temporary location. For example, if you created your own timesets in APLIB, copy APLIB to a temporary location. If you are using the Access LSLink subsystem to retrieve data from a relational data source and you have an lsdal.ini file, copy lsdal.ini and lsdal.cnf to a backup location. If you are running Application Server on a Microsoft Windows client or Microsoft Windows server, back up the Lsserver.ini file located in the Microsoft Windows directory. If you are running Application Server on a Linux/UNIX server, copy the following shell scripts to a temporary location:
batchlss.csh lsstcp.sh runlss.csh runlss.ksh batchlss.ksh
4.3.2 Dumping
Procedure
1.
2. 3.
If you have manually generated dimensions, review the dimension sets and make sure the CLASS and LEVEL statements exist before any rules for consolidation in the databases you want to dump. If you do not place the statements properly, the database does not load to the current database version of Application Server. For example, place them directly after the INPUTS, OUTPUTS, and RESULT dimension members and before the first consolidation rule for consolidated members. Log on to Application Server as the administrator. Make sure that you have file privileges to write to the databases in MASTERDB. Enter the following commands, where <database> is the database you want to dump and <databasedmp> is the dump file to contain the contents of the database.
USE <database>
2011-09-14
PUBLIC
25/62
4 4.4
Management of Application Server System Copy DUMP <databasedmp>
4.
If you want to completely remove the database so that you can do a clean restore, issue the following command:
SUPERVISOR REMOVE DATABASE <database>
4.3.3 Restoring Backed Up Files

Procedure
1. 2.
If you backed up any files, copy them back to their appropriate directories. If running Application Server on a Linux/UNIX server, copy the shell scripts back to their appropriate directories.
4.3.4 Loading a Dumped Database

Prerequisites
You are logged into Application Server as the administrator.

Procedure
1.
In Application Server Administrator, create the database you removed by issuing the following command, making sure you use all the correct settings for observations and members:
SUPERVISOR CREATE DATABASE <database>
2.
Enter the following commands to load the dumped data into the database:
USE <database> LOAD <databasedmp>
For more information about the DUMP and LOAD commands, see the Application Server Help on SAP Service Marketplace at http://service.sap.com/instguidesEPM-STM. Then choose Application Server Command Reference Alphabetical listing of Application Server commands DUMP (Supervisor) . Go to Application Server Command Reference Alphabetical listing of Application Server commands LOAD (Supervisor) . For more information about backing up and restoring, see the Server Upgrade Guides on SAP Service Marketplace at http://service.sap.com/instguidesEPM-STM.
4.4 System Copy

You can perform a system copy by stopping Application Server sessions that access the database and then do a physical backup at the system level. Optionally, you can use Application Server commands to dump the database to a text file, save the text file, and load it. If possible, we recommend re-creating your database from source data using Application Server procedures.
26/62
PUBLIC
2011-09-14
4 4.5
Management of Application Server Required Manual Periodic Tasks to Maintain the Application
See the online Help in the Application Server Administrator program to learn about the DUMP and LOAD commands.
4.5 Required Manual Periodic Tasks to Maintain the Application

This table shows the periodic tasks to be considered when periodically loading new data into your dimensional model:
Task When to Perform the Task
Load new data into the dimensional model or rebuild the dimensional model For information about loading data into a dimensional model using the LOAD command, see the Application Server Help on SAP Service Marketplace at http://service.sap.com/ instguidesEPM-STM.
Every organization acquires new data at their own periodicity. This task must be performed whenever you routinely acquire new data, such as weekly, monthly, or quarterly. Whether you periodically load new data into the dimensional model or periodically rebuild the dimensional model to load new data is an individual preference of each organization. Update the latest date for which there is data in the dimensional After you load new data or rebuild the model dimensional model with newly acquired data. Maintain correct user status after a model update or Security After you load new data or rebuild the procedure update dimensional model with newly acquired data.
4.5.1 Updating the Latest Date for Data in the Model

Certain tabs in the strategy management application depend on the existence of a document in the USE database called LASTDATE. This document contains the latest date for which current data is loaded in the model. For example, if the model contains daily information, and if that information is loaded through the 1st of May, then the contents of the document LASTDATE would be one line containing the string 01 May2011. Every time you update the model with new data, you need to change the date in the LASTDATE document accordingly.
Prerequisites
The dimensional model is built.

Procedure
1. 2.
Log on to Application Server. Issue the following command:

USE <database> DOCUMENT LASTDATE <database> is the name of the dimensional model to set the latest date.
2011-09-14
PUBLIC
27/62
4 4.5
Management of Application Server Required Manual Periodic Tasks to Maintain the Application
3.
In the Document editor, type the last date for which there is data in this database. Specify one of the following date formats: dd mmm yyyy For example: 01 may 2011 yyyy/mm/dd For example: 2011/05/01 yyyy/mm For example: 2011/05
4.5.2 Maintaining Correct User Status After a Model Update

When you update a dimensional model with new data or when you modify the Security procedure, you must perform certain steps to ensure that users remain in sync after the updates.
Prerequisites
You are the strategy management administrator.

Procedure
Do one of the following to remove all Work databases: Physically delete the Work databases. The dimensional models are typically are stored in the HOME directory on the machine where Application Server installed. The database files typically start with DB* or have names that are a concatenation of the authenticated user and model name (for example: TOMJUICE). Restart Interactive Publisher using the JPIP Session Monitor available in the Tools utility at http:// <nw_server>:<port>/strategy/tools. For more information, see the Administrator's Guide for SAP BusinessObjects Strategy Management Interactive Publisher and Application Components.
4.5.3 Model Changes and Reports

Model Updates That Require You to Re-create Reports
If you modify a dimensional model in any of these ways, users receive errors when opening saved reports or dashboards that use the dimensional model and when using these items in reports: Deleting measures Removing dimensions or dimension members Deleting an attribute that is or is not used in the report
Model Updates That do not Affect Reports
You can modify a dimensional model in the following ways without affecting reports that use the dimensional model:
28/62
PUBLIC
2011-09-14
4 4.6
Management of Application Server User Management
Adding attributes Adding dimensions
4.6 User Management

User management is performed in Application Server Administrator using the Supervisor commands in this table.
Application Server Commands
CREATE USER CHANGE USER REMOVE USER EXHIBIT USER
Creates a new user record in MASTERDB. Creates a new user record in MASTERDB. Creates a new user record in MASTERDB. Exhibits users in MASTERDB.
Use the pwreset executable located in the \Program Files (x86)\SAP BusinessObjects\Strategy Management\Application Server directory to reset a forgotten or changed administrator or supervisor password. On Linux/UNIX, pwreset is in the same directory as the lss executable. The pwreset executable clears the password from MASTERDB so the administrator of Application Server can set a new password. The administrator can log into Application Server as Supervisor without a password and reset the password using the CHANGE USER command. The syntax is:
pwreset -inifile <inifile> [-u <username>]
if you specify -u <username>, the password for that user is cleared from MASTERDB. If you omit the -u <username> keyword, the password for the Supervisor user is cleared from MASTERDB. The inifile option is not valid for UNIX/Linux. For example, pwreset.exe -inifile lsserver.ini -u tsmith resets the password for the user tsmith.
2011-09-14
PUBLIC
29/62
5 5.1
High Availability Architecture Considerations
5 High Availability
SAP BusinessObjects Strategy Management is meant for large user deployments. To maximize system availability for large user deployments, you can implement a High Availability (HA) configuration. This allows certain system maintenance activities to occur without taking the application offline, and also provides an infrastructure to recover quickly from unexpected machine failures. While there are many reasons why a high availability configuration is desirable, this section focuses on the configuration and deployment of the strategy management system in a high availability environment.
5.1 Architecture Considerations

The SAP BusinessObjects Strategy Management application consists of several components working together. The components with relevance to high availability are Interactive Publisher and Application Server.
5.2 Recommended Cluster Configuration

There are multiple ways to install a high availability configuration of SAP NetWeaver CE. This depends on the number of nodes participating in the cluster as well as the configuration of the database component. For purposes of this discussion, the following specifications are used: A 64-bit version of Microsoft Windows Server 2003 for the operating system Microsoft SQL Server for the SAP NetWeaver CE System Database Microsoft SQL Server installed in a cluster configuration This scenario adheres to the guidelines of the Installation Guide for SAP NetWeaver Composition Environment on Windows: MS SQL Server. The SAP NetWeaver CE configuration has several options for installation and configuration. The choice of configuration for SAP NetWeaver CE and the SQL Server database should not matter as long as they are valid and supported configurations as defined by the installation guide. The steps described in this discussion provide guidance for Interactive Publisher and Application Server.
2011-09-14
PUBLIC
31/62
5 5.3
High Availability Configuration Process
5.3 Configuration Process

To configure your system for high availability, you create a separate resource cluster that collects all the associated strategy management resources together and permits them to be moved from node to node as a group.
Prerequisites
Software Microsoft Cluster (MSCS) configuration using the Windows Server family Microsoft SQL Server installed a high availability configuration SAP NetWeaver on Windows: MS SQL Server using high availability (MSCS) options Hardware Fault Tolerant Disk Subsystem Two or more physical nodes
Process
1. 2. 3. 4. 5. 6. 7.
Set up the strategy management cluster. For more information, see Setting Up a Strategy Management Cluster [page 32]. Install strategy management services. For more information, see Installing the Strategy Management Services [page 33]. Add strategy management services to the strategy management cluster. For more information, see Adding Strategy Management Services to the Cluster [page 33]. Update the Java System Properties. For more information, see Updating the Java System Properties [page 34]. Move .INI files to the shared disk. For more information, see Moving .INI Files to the Shared Disk [page 34]. Update the shortcut for the Application Server program. For more information, see Updating the Application Server Shortcut [page 35]. Set up a Link ID for certain implementations. For more information, see Setting Up a Link ID for Certain Implementations [page 35].
5.3.1 Setting Up a Strategy Management Cluster

Install Application Server and Interactive Publisher in their own group, which has a dedicated shared Physical Disk resource and a dedicated IP resource.
Procedure
1.
To create a new resource cluster in the Cluster Administrator, select File New Group . Specify a group name, for example SSM, and click Next.
32/62
PUBLIC
2011-09-14
5 5.3
2. 3.
4. 5.
Select the nodes where the strategy management services run and click Add to add them to the group. Then click Finish. The SSM group is created. Obtain an available IP Address from your network team and assign a unique name for use within your network. Create a new IP Address resource cluster in the Cluster Administrator by selecting the new SSM Group and choosing File New Resource . Select the Resource Type IP Address and enter the other parameters. This example uses the name SAP SSM IP. Click Next. Enter the available IP Address and appropriate Subnet mask, and select the appropriate network. Click Finish. Repeat the steps for the Physical Disk.
5.3.2 Installing the Strategy Management Services

Procedure
1. 2. 3. 4. 5.
Log into one of the physical nodes and bring the new physical disk online using the Cluster Administrator. If the SSM group is not assigned to your current node, right-click the SSM group name and move it to your current node. Run the SSM Service installation (xSSMSrv0x_0.exe) and select the disk associated with the SSM physical group as the destination. After installation, move the disk to the alternate node and log onto the second node. Repeat the SSM Service installation and specify the same target disk. It will overwrite the files, but this is expected behavior.
5.3.3 Adding Strategy Management Services to the Cluster

You must make the strategy management services cluster-aware.
Prerequisites
The programs and services are created on each individual node.

Procedure
1.
2. 3. 4.
In the Cluster Administrator, right-click the SSM Group, and create a new resource. In the New Resource dialog box, select the resource type Generic Service. Assign it the name SAP SSM Listener, and click Next. Select the possible owners and click Add. Then click Next. Add the Physical Disk and IP Address as Resource Dependencies, and click Next. Enter lssagent as the service name and click Next.
2011-09-14
PUBLIC
33/62
5 5.3
5.
In the Registry Replication dialog, click Add and enter the key: SOFTWARE\Wow6432Node\SAP\SSM \InternetPub. Then click Finish.
5.3.4 Updating the Java System Properties

Procedure
1. 2. 3. 4. 5. 6.
Start the SAP NetWeaver Administrator. Log on as administrator with the global password you provided when you installed SAP NetWeaver. Select Configuration. Click the Infrastructure tab. Select Java System Properties. In the Templates section, select the template that corresponds to your strategy management installation. 7. Click the Applications tab in the Details section. 8. In the Name column, type strategy and press Enter to list the strategy applications. 9. Select the name xapps~cpm~sm~strategymanagement. 10. In the Name column of Extended Details, enter the strategy management network name and press Enter . For example, pgepmssm. 11. Change template.strategy to the directory on the Cluster Disk. For example, T:\Program files (x86)\SAP BusinessObjects\Strategy Management\InternetPub.
5.3.5 Moving .INI Files to the Shared Disk

Procedure
1. 2. 3. 4. 5.
Create the system environment variables LSLINKINI and LSLINKCNF on both nodes. Specify the directory only, for example, T:\. Copy LSDAL.INI from the c:\windows directory to T:\. Copy LSDAL.CNF from the c:\windows directory to T:\ Copy lsserver.ini from c:\windows to the Cluster Disk (e.g. t:\lsspgx.ini). In the administration application, update the model connection definition by specifying t: \lsspgx.ini as the INI file. Also update the model connection to specify the SSM Cluster Network Name (e.g. pgepmssm) as the PAS System Name.
34/62
PUBLIC
2011-09-14
5 5.3
5.3.6 Updating the Application Server Shortcut

Procedure
1. 2. 3.
Open the properties for the Application Server program, and add the text "inifile t: \lsspgx.ini" to the strategy management target shortcut on both nodes. Make sure the strategy management cluster is on the local node (this is dependent on the cluster disk resource T:). Open lsspgx.ini in a text editor, and add this section:
[pgepmssm] tcp_protocol=winsock username=pipadmin password=abcd1234 PROTOCOL=TCP SERVICE=PILOT CURSOR=LSSCMPTR
5.3.7 Setting Up a Link ID for Certain Implementations

If you use Entry and Approval or Model Designer, you must have a special Link ID called ssm_cb_ea to use for any of these connections. If you followed the instructions in the Installation Guide, you were instructed to create the special Link ID after installing the strategy management components. Now you must modify a setting to adapt it for high availability.
Prerequisites
You have set up client access to the SAP NetWeaver System database. For more information, see the Installation Guide for SAP BusinessObjects Strategy Management on SAP Service Marketplace at http:// service.sap.com. Choose Setting Up Client Access to the SAP NetWeaver System Database. When using SQL Server as the system database, the 32bit ODBC drivers for SQL Server are installed on the Windows server where Application Server is installed. The Application Server procedures are copied from the \Strategy Management\InternetPub\procs\sqlsrvr_procs directory to the parent directory \Strategy Management\InternetPub\procs\. You have created a special Link ID called ssm_cb_ea. For more information, see the Installation Guide for SAP BusinessObjects Strategy Management on SAP Service Marketplace at http://service.sap.com. Choose Creating a Link ID for Certain Implementations.
Procedure
1. 2.
In Administrative Tools, make a copy of the Data Sources (ODBC) shortcut, and name it Data Sources (ODBC) (32-bit). Right-click the 32-bit shortcut and select Properties.
2011-09-14
PUBLIC
35/62
5 5.3
3. 4. 5.
In the Data Sources (ODBC) (32-bit) dialog box, edit the target to be %SystemRoot%\syswow64
\odbcad32.exe
Repeat the task on the other node(s). When you created the ssm_cb_ea link ID in Application Server Administrator, you specified a value in the WorkStation ID text box of the Link ID Properties dialog box. The default value is the name of the current host. Change the value to the name of the cluster resource for SQLServer (for example, PGEPMSQL).
36/62
PUBLIC
2011-09-14
6 6.1
Software Change Management Transporting Models on Like Systems
6 Software Change Management
Software Change Management standardizes and automates software distribution, maintenance, and testing procedures for complex software landscapes and multiple software development platforms. These functions support your project teams, development teams, and application support teams. This section provides additional information about the most important software components. The following topics are covered: Transport Enables and secures the distribution of software changes from the development environment to the quality assurance and production environment. Support Packages and SAP Notes Implementation Provide standardized software distribution and maintenance procedures. Release and Upgrade Management Reduces the time, cost, and risk associated with upgrades.
6.1 Transporting Models on Like Systems

Process
1. 2. 3.
From the source system where Application Server is installed, copy any customized files to the same location on the destination system using an operating system tool for copying. From the source system where Application Server is installed, copy the dimensional models to the same location on the destination system. On the source system, start the Application Server Administrator and issue the SUPERVISOR ADD DATABASE command to add the database to MASTERDB.
NOTE
If you have procedures to recreate databases, then copy the procedures to the destination system, make sure the external data sources and Link IDs are available in the new system, and re-create the databases on the destination system by running the build procedures. For details, see the Server Upgrade Guides on SAP Service Marketplace at http://service.sap.com/ instguidesEPM-STM.
6.2 Transporting Models on Different Systems

You can transport a dimensional model from one system to a different platform (for example, from Solaris to HP or to Microsoft Windows).
2011-09-14
PUBLIC
37/62
6 6.3
Software Change Management Support Packages and SAP Notes Implementation
Process
1.
From the source system where Application Server is installed, copy any customized files to the same location on the destination system using an operating system tool for copying. 2. From the source system where Application Server is installed, issue a SUPERVISOR SHOW DATABASE and record all the settings for the database. 3. From the source system where Application Server is installed, dump the databases. 4. Copy the dump files to the destination system using an operating system tool for copying. 5. On the source system, start the Application Server Administrator and issue the SUPERVISOR CREATE DATABASE command to create a database for the dumped database. Use all the settings you recorded from the SUPERVISOR SHOW DATABASE command. 6. On the source system, load the database by using it and then loading it. For information about backing up and restoring Application Server by dumping and loading, see the Server Upgrade Guides on SAP Service Marketplace at http://service.sap.com/instguidesEPM-STM. Then choose Backup and Restore [page 24].
6.3 Support Packages and SAP Notes Implementation

You can find the available support packages by going to SAP Service Marketplace at http:// service.sap.com/swdc Download Support Packages and Patches A Index S SAP STRATEGY MANAGEMENT . The steps to apply a Support Package or a Hot Fix exist in the SAP Note for the Support Package or Hot Fix. Critical limitations for a release are described in the Restrictions Note. The Central Note, and every Support Package Note and Hot Fix Note have a Related Notes tab that contains a link to the Restrictions Note.
6.4 Release and Upgrade Management

Releases of Application Server are located on SAP Service Marketplace at http://service.sap.com/ swdc Download Installations and Upgrades Entry by Application Group SAP Application Components SAP Strategy Management . For information about using the procedures and commands to upgrade your system from a previous version or to transport from one system to another, see the Server Upgrade Guides on SAP Service Marketplace at http://service.sap.com/instguidesEPM-STM.
Methods of displaying the Application Server version
In Application Server, choose Help About . While logging into Application Server, the startup banner shows the version.
38/62
PUBLIC
2011-09-14
6 6.4
Software Change Management Release and Upgrade Management
Use the VERSION command in Application Server. Using the PAS Query tool (http://<nw_server>:<port>/strategy/tools), click PAS Query, select the model connection and then specify &result=version in the Address box. Example output:
Interactive Publisher Version <x>.<x>.<x> for Microsoft Windows Copyright (C) <year> SAP AG Reference <xxxx> on <date> <time> Application Server Version <x>.<x>.<x> for Microsoft Windows Copyright (C) <year> SAP AG Reference <xxxx> on <date> <time> This software program is licensed by SAP AG for use pursuant to the terms and conditions of a license agreement.
2011-09-14
PUBLIC
39/62
7 7.1
Testing and Troubleshooting Client/Server Connections Testing Client/Server Connections on UNIX
7 Testing and Troubleshooting Client/ Server Connections
7.1 Testing Client/Server Connections on UNIX

Once Application Server is installed on the UNIX machine, and you have started the Listener daemon, you must test whether it is possible to run a client/server connection between a client machine and the host on which Application Server is installed. Even before even beginning client/server testing, you should ensure that the product functions correctly in native mode. These tests run smoothly if you followed the steps to start the Listener daemon. However, there are occasions when problems occur and some troubleshooting is required. This section covers steps to help resolve connection problems.
Procedure
Testing Installation and Connectivity
To test the installation and connectivity, Run the runlss.csh or runlss.ksh scripts from within a telnet session to make sure the product functions as expected.
Testing the Connectivity by Running Natively on UNIX
If you ran the scripts in a telnet session and a client/server connection does not work, do the following to run lsstcp.sh script natively on UNIX and verify whether the scripts are processing correctly: 1. Edit the lsstcp.sh script and change the last line so that the lss program is executed instead of the lsstcp program. 2. Change this line from:
exec $LSSHOME/lsstcp $1
to
exec $LSSHOME/lss
3.
Review the LSSTLD.LOG file, which is generated and updated by the Application Server listener daemon. It is created in the same directory as the lsstld executable. At the top of this log file is information about when the listener was started, which user started the listener, the socket the listener is listening on, when the listener initialization was completed, and connection attempts by users. The following excerpt from a sample log file shows a successful connection attempt. The log file shows the IP address of the user who made the connection, the time of connection, whether the request was accepted, and the service in the lssmap file being called.
2011-09-14
PUBLIC
41/62
7 7.2
Testing and Troubleshooting Client/Server Connections Connection for Two Installations of Application Server Connection request from IP address 207.41.233.125, using port 2870 at Fri Aug 24 12:06:17 2008 Connection request from 207.41.233.125 accepted. Calling service Application Server80.
4.
If the messages in the LSSTLD.LOG file show a successful connection, skip the rest of this section. If the messages show an unsuccessful connection, see the section about troubleshooting.
7.2 Connection for Two Installations of Application Server

The file lssmap is installed with the Application Server software and contains entries based on the installation. When the Application Server TCP/IP Listener daemon, lsstld, receives a request for a connection, it reads the lssmap file, searching for an entry that matches the string passed from SERVICE= entry in the LSSERVER.INI file on the client. The file maps the requested service name to the shell script that is run to set environment variables and execute the Application Server kernel, lsstcp. There may be a situation in which you want to add other entries. For example, you might want to be able to connect to two installations of Application Server, one in a production scenario and the other in a test scenario. The format of lssmap entries is:
SYNTAX service name*shell script name
where the * delimiter is required.

Example
LSS80*<installdir>/lss/lsstcp.sh LSSTEST*<installdir>/lss/beta/lsstcp.sh
In this example, LSS80 and LSSTEST are the names of two services that run shell scripts from two different directories. The Listener daemon executes the script specified for the service.
7.3 Troubleshooting Client/Server Connections on UNIX

This section includes information that might be useful if you have trouble establishing client/server connections. Specifically, it includes information about the Application Server trace facility, the log files LSSTLD.LOG and LSSLOG, and the lssmap file that the Listener daemon uses.
7.3.1 Reviewing the Log Files

If a user has trouble connecting to the UNIX server, check the log files, which may contain diagnostic messages related to connection problems.
42/62
PUBLIC
2011-09-14
7 7.3
Testing and Troubleshooting Client/Server Connections Troubleshooting Client/Server Connections on UNIX
Procedure
1. 2.
Open the LSSTLD.LOG file in an editor. This file is located in the /<installdir>/lss directory. If the messages in the LSSTLD.LOG file explain a problem, identify the problem, try to correct it, and run the test again. The following example shows an entry in the LSSTLD.LOG file that contains an error. The log file excerpt indicates that the connection attempt failed, and the listener provides information about why the connection failed. In this case, the error message indicates that either the UNIX username or password provided by the user is incorrect. That is, the listener could not authenticate the user.
Connection request from IP address 207.41.234.130, using port 1058 at Fri Aug 24 11:14:44 2004 The login ID/password combination was rejected by crypt! Connection request from 207.41.234.130 rejected!
The following example shows another problem connection. In this case, the service specified in the users lsserver.ini file on their client machine is not found in the lssmap file on the host machine.
Connection request from IP address 207.41.234.130, using port 1060 at Fri Aug 24 11:21:57 2004 The DEVENV service was not found in the lssmap file!
3.
There are times when the connection attempt fails and there is no obvious information available in the LSSTLD.LOG file. If everything in the LSSTLD.LOG file appears to be correct but a connection cannot be made, you should review the LSSLOG file. LSSLOG is created by the lsstcp executable in the UNIX user accounts home directory when they make a client/server connection. The LSSLOG file contains information about the version, the environment, the process number, and the time of connection. This file also contains error message information if there are problems in establishing a client/server connection. If you still cannot determine any obvious problems in either the LSSTLD.LOG or LSSLOG files, you should insert debugging information into the lsstcp.sh shell script. For example, you can add several lines to lsstcp.sh to determine how far in the file the script execution reaches before failing. Or, send all environment variable information to an external file. For example, you might add the following line to send the current date and time to a file called testfile located in the UNIX user accounts home directory. You would add this line at the top of the lsstcp.sh script to make it immediately obvious whether the script is being executed:
date > testfile
4.
Further down in the file, just before the line that executes lsstcp, you would add the following line. This line appends the current date and time to the same file, testfile, as the first sample line. This second line shows you how far the script is executing.
date >> testfile
2011-09-14
PUBLIC
43/62
7 7.4
Testing and Troubleshooting Client/Server Connections Testing Client/Server Connections on a Microsoft Windows Server
5.
6.
You can also include in the lsstcp.sh script file a line that displays the values of all environment variables that are set. This is useful because it shows you whether items in the lsstcp.sh script file are being set correctly. It also shows you whether all needed environment variables are set correctly. You can test this by inserting the following line immediately before the line that executes lsstcp:
env > testfile
7.
If you continue to experience problems that might be permissions related, you should perform your client/server connection with the UNIX user account root instead of as your regular user. Because the root user on UNIX has no security restrictions, a successful connection by root can rule out any problems not related to permissions.
7.3.2 Using the Trace Facility

If you have problems with Application Server, you can record all Application Server API calls in a file using the trace facility. You should only use the trace facility for diagnostic purposes because it can slow down processing.
Procedure
1. 2.
Open the lsstcp.sh file in an editor. Change the LSSTRACE value from null to the name of the trace file you want to create or to YES. For example:
LSSTRACE=YES
Application Server writes client/server API calls to a file called LSSTRACE in your Home directory.
7.4 Testing Client/Server Connections on a Microsoft Windows Server

Once Application Server is installed on the Microsoft Windows server machine, you must verify that your connections and processes are running properly. The Installation Guide for SAP BusinessObjects Strategy Management provides some general steps to test the connections. This section discusses the following issues that are specific to the Application Server software on the Microsoft Windows Server platforms using the TCP/IP protocol for client/server connections: Logging client/server connections Testing connections
44/62
PUBLIC
2011-09-14
7 7.4
Testing and Troubleshooting Client/Server Connections Testing Client/Server Connections on a Microsoft Windows Server
7.4.1 Logging Client/Server Connections

You can log all client/server connection attempts through an option in the LSSAGENT.INI file. This log file can be useful for auditing who is connecting to the server, at what time, and for examining error messages as to why connection attempts failed.
Procedure
1.
Modify the LSSAGENT.INI file that is located in the Microsoft Windows directory on the Microsoft Windows server. Change the DEBUG= line as shown:
[Agent] Logfile=c:\lssagent.log DEBUG=Y NOTE
2.
The Y is case sensitive. Stop and then restart the SAP SM Listener service so that the LSSAGENT.INI file changes take effect.
7.4.2 Testing SAP SM Listener and the TCP/IP Protocol

Procedure
1. 2.
Verify that the SAP SM Listener service is started. Go to the Control Panel and choose Administrative Tools Services . Locate the SAP SM Listener service and make sure that is started. Verify that the TCP/IP protocol is installed. Go to the Control Panel and choose Administrative Tools Network Connections . Right click Local Area Connection and select Properties to determine if TCP/IP Internet Protocol Transport is installed.
7.4.3 Testing Connections Between the Client and Server

Procedure
1. 2. 3. 4.
Open the Lsserver.ini file in a text editor. It is located in the Microsoft Windows directory. Change the [<localhost>] to the name or the IP address of the system you are connecting to. For the username= entry, type:
admin
Leave the EncryptedPassword= entry empty or type a question mark (?). You are prompted for the password when you try to connect.
[<localhost>] tcp_protocol=winsock username=admin EncryptedPassword=? PROTOCOL=TCP
2011-09-14
PUBLIC
45/62
7 7.4
Testing and Troubleshooting Client/Server Connections Testing Client/Server Connections on a Microsoft Windows Server SERVICE=PILOT CURSOR=LSSCMPTR
5.
6. 7. 8. 9. 10.
Verify that the Application Server Administrator software has been correctly installed on the Microsoft Windows client machine. On your Microsoft Windows Desktop, choose Start Programs SAP BusinessObjects Strategy Management Application Server Administrator . The program is started and a Logon dialog box appears. In the User name text box, type the following user name, which is created at installation:
admin
Do not enter any values in the Password box. The Server box should be filled in with the name you specified for [<localhost>]. Click OK. Verify that the username and password specified in the client side Lsserver.ini file match the entry in the User Manager (or User Manager for Domains) utility. Remember that Microsoft Windows passwords are case sensitive.
NOTE
You can create a remote server connection that stores your password in encrypted format in Lsserver.ini rather than allow prompts for your password. See the explanation of the Lsserver.ini file in the Server Configuration Guide for SAP BusinessObjects Strategy Management.
7.4.4 Configuring Microsoft Windows User Permissions for Client/Server Connection

The Microsoft Windows username and password that are specified in the client side LSSERVER.INI file require the Log on Locally access right on the Microsoft Windows server where Application Server is installed. This is needed to create a client/server process for its session. If the username that you are using is a locally defined user on the Microsoft Windows server, and is a member of the Users group, then it has this access right by default. If, however, you are using a Microsoft Windows domain username, this is a member of the Domain Users group on the Microsoft Windows server. In this case, you need to assign the Log on Locally access right to the individual username, or the Domain Users group.
Procedure
1. 2. 3. 4.
In Administrative Tools, choose Local Security Policy to display the Local Security Settings window. In the Local Policies folder, choose User Rights Assignment. Choose the Log on locally policy. Grant either the user, or a group containing the user, the Log on Locally access right.
46/62
PUBLIC
2011-09-14
8 8.1
Support Desk Management Remote Support Setup
8 Support Desk Management
Support Desk Management enables you to set up an efficient internal support desk for your support organization that seamlessly integrates your users, internal support employees, partners, and SAP Active Global Support specialists with an efficient problem resolution procedure. For support desk management, you need the methodology, management procedures, and tools infrastructure to run your internal support organization efficiently.
8.1 Remote Support Setup

The SAP Support team supports you throughout the entire lifecycle of your solutions, from the business blueprint through configuration to production operation. It provides central access to tools, methods, and preconfigured content that you can use during the evaluation, implementation, and productive operation of your systems. SAP support needs to be able to work remotely for highest efficiency and availability. Therefore all required support tools must be remotely accessible for SAP support, SAP uses the remote connection with SAProuter for a specific problem that you log by creating a customer message in the SAP Support Portal.
Prerequisites
You are a member of the Java role SAP_JAVA_SUPPORT, which is a read-only role provided with SAP NetWeaver AS Java for the purpose of using Solution Manager Diagnostics. For more information, see the SAP NetWeaver AS Java Guides on SAP Service Marketplace at http://service.sap.com/ instguides.
Features
SAP can provide remote support for your implementation using the following components: SAProuter: SAProuter is an SAP program that acts as an intermediate station (proxy) in a network connection between SAP systems, or between SAP systems and external networks. SAProuter controls the access to your network (application level gateway), and, as such, is a useful enhancement to an existing firewall system (port filter). SAProuter runs on the firewall host serving and serves as the entry point to your network. SAProuter can be used to open a support connection from SAP to your SAP system. SAP support personnel can use the connection use to access your system. SAProuter controls and monitors these connections. You must specifically grant access
2011-09-14
PUBLIC
47/62
8 8.2
Support Desk Management CA Wily Introscope Integration
to the requestor for each connection. For more information about SAProuter, see the following SAP Notes: 1072324 and 812732. SAP Service Desk: You can use the Service Desk component to process your internal support messages. You can forward these messages to SAP Support. In this scenario, your internal support desk acts as the first level of strategy management support and escalated tickets go directly to SAP Support. For more information about the Service Desk, see https://service.sap.com/runSAP RunSAP Roadmaps (Access) Run SAP Roadmap . .Then in Run SAP, choose Design Operations End User Support Concept Incident Management .
More Information
For information about SAProuter, see SAP Note 486688. This SAP Note refers to for specific settings or parameters that are necessary. SAP Note 812386 provides further assistance.
8.2 CA Wily Introscope Integration

To enable application analysis (including performance monitoring), CA Wily Introscope (IS) is integrated into SAP Solution Manager Diagnostics (SMD). SAP provides CA Wily IS instrumentation for SAP BusinessObjects Strategy Management. IS for Microsoft .NET is an application management solution for managed .NET applications, running on Microsofts Common Language Runtime (CLR) environment. CA Wily IS offers Dashboards for performance and stability analysis. In addition, the Investigator provides a detailed view on all applications and environment metrics reported by the IS agent to the IS Enterprise Manager, which is the CA Wily IS server and part of SAP Solution Manager. User-specific interaction can be traced in CA Wily IS using the Transaction Trace. Metrics, which are collected and reported through tracers defined in Probe Builder Directives .pbd files, define the information that is collected at runtime. The CA Wily IS .NET agent collects this information and reports it to the Enterprise Manager. The Enterprise Manager stores these metrics in its own database. You can view performance metrics using the IS Workstation or the IS WebView application.
Prerequisites
To enable IS for Strategy Management, install and configure the CA Wily IS .NET agent on the strategy management application server hosts. For more about information about setting up and configuring CA Wily Introscope for strategy management, see SAP Note 1126554 as well as SAP Note 797147 and its attached FAQ document. For more information about the installation, configuration, and use of SAP Solution Manager Diagnostics, visit the SAP Service Marketplace at http://service.sap.com/diagnostics.
48/62
PUBLIC
2011-09-14
8 8.3
Support Desk Management Problem Message Handover
Procedure
1. 2. 3. 4. 5. 6.
Log on to Root Cause Analysis workcenter of SAP Solution Manager (transaction code solman_workcenter). Select System Analysis from the detail navigation menu. Choose the query that contains the Strategy Management system or find it in All Technical Systems. Select the Strategy Management system from the systems selection table. Choose CA Wily Introscope and log on to the CA Wily IS WebView. Choose Start Introscope, then log on to the Introscope WebView. Do any of the following: Select the Console tab to view Wily Dashboards. Select the Investigator tab to view the Wily Investigator tree. Select the Transaction Viewer tab to view Wily Transaction Trace.
8.3 Problem Message Handover

You can log problem messages on the SAP Support Portal on SAP Service Marketplace at http:// service.sap.com/. Provide a detailed and reproducible problem description. The following component strings are available:
Component String
EPM-SM EPM-SM-APP EPM-SM-EAI EPM-SM-PAS EPM-SM-PIP
Component
SAP BusinessObjects Strategy Management Applications Excel Add-In Application Server Interactive Publisher
2011-09-14
PUBLIC
49/62
9 9.1
Application Server Environment Variables Application Server Environment Variables on UNIX
9 Application Server Environment Variables
9.1 Application Server Environment Variables on UNIX

Environment variables are set in the [Microsoft Windows] section of LSSERVER.INI under Microsoft Windows, and by using the appropriate shell syntax under UNIX. Optionally, DBHOME, DBPATH, USERNAME, PASSWORD, LSSFILES, SHAREDMEMORY, and MAXSETS variables can be placed in the [Server] section of LSSERVER.INI. They are exported to the server, which may be Microsoft Windows or UNIX, at startup. These override earlier server settings.
NOTE DBHOME, DBPATH, SHAREDMEMORY, and DEFAULTMEMORY settings are only valid in the [Microsoft Windows] section of LSSERVER.INI if you are running standalone or if you set these parameters
on the server machine running a client/server configuration to NT. If you set this on the client machine, it does not affect the server machine.
Features
Variable
DBHOME
Description
LSSFILES=n SHAREDMEMORY=NO DEFAULTMEMORY=n
MAXSETS=
DBHOME
DBPATH
VISUAL EDITOR
Default directory for creating new files. DBHOME is searched when external files are referenced. Replaces HOME, which was used in earlier releases. Maximum number of files that can be opened. The default is 64. Switch off shared memory headers for SHARED and READ databases. Default memory to use per Application Server session in kilobytes (1024 bytes). If not set, it is infinite. You can override this setting by using the SET MEMORY command from the command line, or from within a procedure. Increases the maximum number of internal sets that can be used in an across/down list. If you receive a message stating that you have an insufficient number of STLIB sets available, then increase the value for MAXSETS. The default value is 1,000. As for Microsoft Windows, it is the default directory for creating new files. DBHOME is searched when external files are referenced. Colon-separated list of directories to search for external files (after the current directory and DBHOME). The name of the System editor. Alternative name for the System editor.
2011-09-14
PUBLIC
51/62
9 9.2
Application Server Environment Variables UNIX Environment Variables and Shells Scripts
9.2 UNIX Environment Variables and Shells Scripts

Environment variables define the location of Application Server databases and files. For Application Server to execute properly in a client/server session or in a native UNIX interactive session, environment variables must be set to specify accurate file locations. You use either of the following UNIX shell scripts to set the values for environment variables. In a client/server setup, use the lsstcp.sh shell script located in the <installdir>/lss directory to set the environment variables required by Application Server. The lsstcp.sh script runs when a client/server connection is established. It initializes environment variables and runs the Application Server TCP/IP process. In a native UNIX execution, C shell users use the runlss.csh script located in the <installdir>/ lss directory to set the environment variables required by Application Server. In a native UNIX execution, Korn and Bourne shell users use the runlss.ksh script located in the <installdir>/lss directory to set the environment variables required by Application Server. Use native UNIX for Application Server production batch jobs that run routine tasks such as data loads and consolidations. Whatever shell script you use, make sure that the definitions for all databases and external files reflect your installation configuration. The Application Server files are installed in the <installdir>/lss directory. In the shell scripts, the environment variable $LSSHOME is defined to reference the <installdir>/lss directory. The install.sh script generates all required scripts with the directory name based on your installation location. By default, Application Server files such as MASTERDB and TBDB exist in the <installdir>/lss directory. The LSSHOME environment variable is set to the <installdir>/lss directory. Environment variables for Application Server databases use LSSHOME. When you create a database or move one to another directory, update the environment variable in the UNIX shell script.
9.3 Identifying the Shell Used by a Native UNIX Account

Procedure
1. 2.
Log on to the native UNIX account. Enter:

echo $SHELL
Result
If the Response Is:
/bin/csh /bin/sh /bin/ksh
The Shell Is:
The Script Is:

runlss.csh runlss.ksh runlss.ksh
C Bourne Korn
52/62
PUBLIC
2011-09-14
9 9.4
Application Server Environment Variables Environment Variables in Native UNIX
9.4 Environment Variables in Native UNIX

You can run Application Server in native UNIX using Telnet from a client machine. When you type an Application Server user name and password in the logon screen, a non-Microsoft Windows textbased interactive session begins. Use Application Server in native UNIX for production batch runs of routine tasks such as loading and consolidating data. The runlss.ksh shell script runs under the Korn or Bourne shell to start a native UNIX Application Server session. The runlss.ksh shell script sets environment variables for Application Server. Once a variable is defined, it must be exported.
Procedure
1. 2.
Run the runlss.ksh shell script. The runlss.ksh script sets environment variables for Application Server. In the shell script, define a variable and export it. The following lines set the directory Application Server:
LSSHOME=<installdir>/lss export LSSHOME
3.
If you create a new database or file, you must define its location in an environment variable in the shell scripts. Include a line that specifies the database name and location and a line that exports the database. In the example below, SALES1 is a new database name that is in the default location set by $LSSHOME. If you put Application Server databases in a directory different from the directory defined by $LSSHOME, use the full path to the database in place of the $LSSHOME environment variable. In the example below, SALES2 is in the /proddb directory rather than <installdir>/lss, which is the LSSHOME directory.
APLIB=$LSSHOME/APLIB SALES1=&LSSHOME/SALES1 SALES2=/proddb/SALES2 DEMO=$LSSHOME/DEMO INITIAL=$LSSHOME/INITIAL JUICE=$LSSHOME/JUICE.ENG LOCKFILE=$LSSHOME/LSSLOCK MASTERDB=$LSSHOME/MASTERDB SMREPORT=$LSSHOME/SMREPORT TBDB=$LSSHOME/TBDB.ENG export APLIB SALES1 SALES2 DEMO INITIAL JUICE LOCKFILE export MASTERDB SMREPORT TBDB
The following line executes Application Server:

exec $LSSHOME/lsstcp
2011-09-14
PUBLIC
53/62
9 9.5
Application Server Environment Variables Environment Variables in Native UNIX Using the C Shell
9.5 Environment Variables in Native UNIX Using the C Shell

You can run Application Server in native UNIX using Telnet from a client machine. When you type an Application Server user name and password in the logon screen, a non-Microsoft Windows textbased interactive session begins. Use Application Server in native UNIX for production batch runs of routine tasks such as loading and consolidating data. You can run the runlss.csh shell script under the C shell to start a native UNIX Application Server session. The runlss.csh shell script sets environment variables for Application Server. Once you define a variable, it does not need to be exported.
Procedure
1.
Run the runlss.csh shell script. Runlss.csh sets environment variables for Application Server. The following line sets the location of Application Server:
setenv LSSHOME /<installdir>/lss
2. 3.
In the shell script, define a variable as needed. If you create a new database or file, you must define its location in an environment variable in the shell script. Include a line that specifies the database name and location and a line that exports the database. In the example below, SALES1 is a new database name that is in the default location set by $LSSHOME. If you put Application Server databases in a directory different from the directory defined by $LSSHOME, use the full path to the database in place of the $LSSHOME environment variable. In the example below, SALES2 is in the /proddb directory rather than <installdir>/lss, which is the LSSHOME directory. Use the following lines in the runlss.csh shell script to set the location of Application Server databases:
setenv APLIB $LSSHOME/APLIB setenv SALES1 $LSSHOME/SALES1 setenv SALES2 /proddb/SALES2 setenv INITIAL $LSSHOME/INITIAL setenv JUICE $LSSHOME/JUICE.ENG setenv LIBDB $LSSHOME/LIBDB setenv LOCKFILE $LSSHOME/LSSLOCK setenv MASTERDB $LSSHOME/MASTERDB setenv SMREPORT $LSSHOME/SMREPORT setenv TBDB $LSSHOME/TBDB.ENG

$LSSHOME/lss
54/62
PUBLIC
2011-09-14
9 9.6
Application Server Environment Variables Environment Variables in a Client/Server UNIX
9.6 Environment Variables in a Client/Server UNIX

Use the lsstcp.sh shell script located in the <installdir>/lss directory to set the environment variables required by Application Server and export the variables in a client/server UNIX configuration. The lsstcp.sh script runs when a client/server connection is established. It initializes environment variables and runs the Application Server TCP/IP process. The lsstcp.sh shell script contains the LSSTRACE and LSSLOG environment variables, used for logging diagnostic information. If the LSSTRACE file that Application Server creates in the UNIX account's home directory has a file name value or a value of TRUE, Application Server traces each internal function call. This can be useful if you are working with Customer Support to analyze unexplained behavior. However, when LSSTRACE=TRUE, the size of the log file increases rapidly and performance is degraded. If LSSLOG is uncommented and has a file name value or a value of TRUE, Application Server provides a log that is a duplicate of the LSSLOG already in the UNIX account's home directory.
9.7 Changing File Locations in Lsstcp.sh

Procedure
1. 2.
Run the lsstcp.sh shell script. The lsstcp.sh script sets environment variables for Application Server. In the shell script, define a variable and export it. The following lines set the directory for Application Server:
LSSHOME=/<installdir>/lss export LSSHOME
3.
If you create a new database or file, you must define its location in an environment variable in the shell scripts. Include a line that specifies the database name and location and a line that exports the database. In the example below, SALES1 is a new database name that is in the default location set by $LSSHOME. If you put Application Server databases in a directory different from the directory defined by $LSSHOME, use the full path to the database in place of the $LSSHOME environment variable. In the example below, SALES2 is in the /proddb directory rather than /<installdir>/lss, which is the LSSHOME directory.
APLIB=$LSSHOME/APLIB SALES1=&LSSHOME/SALES1 SALES2=/proddb/SALES2 DEMO=$LSSHOME/DEMO INITIAL=$LSSHOME/INITIAL JUICE=$LSSHOME/JUICE.ENG LOCKFILE=$LSSHOME/LSSLOCK
2011-09-14
PUBLIC
55/62
9 9.8
Application Server Environment Variables Reviewing UNIX File Privileges MASTERDB=$LSSHOME/MASTERDB SMREPORT=$LSSHOME/SMREPORT TBDB=$LSSHOME/TBDB.ENG export APLIB SALES1 SALES2 DEMO INITIAL JUICE LOCKFILE export MASTERDB SMREPORT TBDB

exec $LSSHOME/lsstcp $1
9.8 Reviewing UNIX File Privileges

The UNIX file access options are read, write, and execute. These privileges are assigned for the distinct domains of user (the owner), group, and other. This section summarizes the default permissions: All installed databases allow read and write access to all users. TBDB is the Application Server system database. It contains system components such as diagnostic information and messages, and must not be changed. TBDB is read-only. Executable modules lsstcp, lsstld, lss, and xray are installed with read and execute access for all users. When you create a new database, the default access is rw-r--r--. The owner has read and write access to the file and all others have read-only access. To allow others to access the database, you must change the privileges. All generated scripts have read, write, and execute access for all users. Make sure that the correct permissions are set on all of the Application Server files and that appropriate permissions are set all the way up the directory chain from where Application Server is installed. For example, all users must be able to write to MASTERDB to log on to Application Server. However, even if the specific file permissions allow this, if the directory in which MASTERDB resides does not allow all users write access, you will have problems. Check this before attempting to connect client/server with an Application Server session on UNIX.
Procedure
You can check the file privileges by entering:

cd <installdir>/lss ls -l
UNIX displays file information, including access privileges, similar to these default permissions set by the Application Server installation script:
SYNTAX -rw-rw-rw-rw-rw-rw-rw-rw-rw1 root sys 2667008 2010-12-20 19:29 APLIB 1 root sys 2664960 2010-12-20 19:29 APLIB.ANSI 1 root sys 147456 2010-12-20 19:29 CGLIB
56/62
PUBLIC
2011-09-14
9 9.9
Application Server Environment Variables Changing File Privileges in UNIX -rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-r--r--r--r--r--r--r--r--r--r--r--r--r--r--r--r--r--r--r--r--r--r--r--r--rwxrwxrwx -rwxrwxrwx -rwxrwxrwx -r-xr-xr-x -rwxrwxrwx -r-xr-xr-x -rwxrwxrwx -r-xr-xr-x -rwxrwxrwx -rwxrwxrwx -rwxr-xr-x -rwxr-xr-x -rwxrwxrwx -rwxrwxrwx -rwxr-xr-x drwxrwxrwx -r-xr-xr-x 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 1 root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys 147456 184320 184320 4374528 4374528 4767744 4423680 0 0 50176 50176 147456 147456 364544 362496 339968 339968 361472 357376 339968 339968 90 638 703 3906131 84 3811127 1015 28537 617 678 3830516 3739220 493 757 352514 4096 355588 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 2010-12-20 19:29 19:29 19:29 19:29 19:29 19:30 19:30 19:29 19:29 19:29 19:29 19:29 19:29 19:30 19:30 19:29 19:29 19:30 19:29 19:30 19:30 20:38 20:38 20:38 19:29 20:38 19:29 20:38 19:29 20:38 20:38 19:29 19:29 20:38 20:38 19:29 20:38 19:29 CGLIB.ANSI INITIAL INITIAL.ANSI JUICE.ENG JUICE.ENG.ANSI JUICE.JPN JUICE.JPN.SHIFTJIS LSSLOCK LSSLOCK.ANSI MASTERDB MASTERDB.ANSI SMREPORT SMREPORT.ANSI TBDB.DEU TBDB.DEU.ISO8859-1 TBDB.ENG TBDB.ENG.ANSI TBDB.FRA TBDB.FRA.ISO8859-1 TBDB.JPN TBDB.JPN.SHIFTJIS batch1 batchlss.csh batchlss.ksh lss lssmap lsstcp lsstcp.sh lsstld runlss.csh runlss.ksh sgtrans sgttcp tldgo tldstop upgradedb workfile xray
The first column in the list represents the file protections for the owner, the group, and all others. The first character position indicates a file (-) or a directory (d). The other 9 positions are divided into 3character sections. Each section has a location for defining access for read (r), write (w), and execute (x) privileges. A dash (-) means that type of access is denied. For example, a file with privileges -rw-rwrw- has read and write access for all users on the UNIX system, owner, group, and all others.
9.9 Changing File Privileges in UNIX

Default access privileges for Application Server are enough for most sites. If you need to change privileges, be careful not to block access to certain files. All users must always have read/write access to MASTERDB and LSSLOCK or else logon attempts fail.
Procedure
You can change the file access in native UNIX using the chmod command:
2011-09-14
PUBLIC
57/62
9 9.10
Application Server Environment Variables Modifying the DBHOME Environment Variable SYNTAX chmod <entity ><operator ><privilege ><filename>
Variable
<entity>
Description
<operator>
<privilege>
<filename>
Specifies whom you are changing the access privileges for. Entity can be either u (user), g (group), o (other), or a (all). Specifies whether you are adding or removing the access privilege. Operator can be + (add) or - (remove). Specifies the access privilege you are changing. Privilege can be either r (read), w (write), or x (execute). Specifies the file whose access you are changing.
The following commands change the file access of the TESTDB database. Write access is added for group and read access is removed for other. TESTDB now has access privileges of -rw-rw--.
chmod g+w TESTDB chmod o-r TESTDB
9.10 Modifying the DBHOME Environment Variable

The DBHOME environment variable defines the Application Server home directory, which is the location of external files such as output buffer files, trace files, database dump files, and Work databases. By default, the installation creates the DBHOME environment variable and specifies a path of / <installdir>/lss/workfile. If you want to change the workfile location to a different path, you can modify DBHOME in the lsstcp.sh script.
Procedure
Modify the following information in lsstcp.sh:

DBHOME=/<installdir>/<newlocation>/workfile export DBHOMEexport DBHOME
58/62
PUBLIC
2011-09-14
10
Related Guides
10 Related Guides
You can find more information about installation and configuration in the Master Guide, Installation Guide, and Upgrade Guide. For more information, see SAP Service Marketplace at http:// service.sap.com/instguidesEPM-STM.
2011-09-14
PUBLIC
59/62
Typographic Conventions
Example
<Example>
Description
Example Example Example

Example
Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, Enter your <User Name>. Arrows separating the parts of a navigation path, for example, menu options Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP Note, for example, SAP Note 123456 Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options. Cross-references to other documentation or published works Output on the screen following a user action, for example, messages Source code or syntax quoted directly from a program File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE Keys on the keyboard
http://www.sap.com /example
123456 Example
Example
EXAMPLE
EXAMPLE
Documentation in the SAP Service Marketplace
You can find this document at the following address: http://service.sap.com/instguidesEPM-STM
60/62
PUBLIC
2011-09-14
SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com
Copyright 2011 SAP AG. 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 AG. The information contained herein may be changed without prior notice.

SSM10 Administrator&#39;s Guide

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

SSM10 Administrator&#39;s Guide

Hochgeladen von

Copyright:

Verfügbare Formate

Administrator's Guide SAP BusinessObjects Strategy Management Application Server 10.

PUBLIC Document version: 1.1 2011-09-14

First version no changes. Corrected text about XRAY s

Support Desk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Remote Support Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Technical System Landscape

2 Technical System Landscape

Online Help in the Application Server Administrator system.

Monitoring Application Server Trace and Log Files

3 Monitoring Application Server

3.1 Trace and Log Files

Monitoring Application Server Trace and Log Files

3.1.1 Development Tracing

Monitoring Application Server Trace and Log Files Description

Monitoring Application Server Trace and Log Files

3.1.2 Tracing During Runtime

Contains all commands and the results/output from those commands

Contains all commands issued by the application

Start the Tools utility at this URL:

Viewing Trace Files [page 14]

3.1.3 Viewing Trace Files

Monitoring Application Server Database Monitors NOTE

3.2 Database Monitors

Monitoring Application Server Activity and Resource Monitors Detailed Description

Application Server Command

SUPERVISOR XRAY <database> RECORDS | NOTREE

3.3.2 Monitoring Tools

3.3.3 Application Server Monitoring Commands

Use the Rollup editor to monitor growth in the following ways:

Monitoring Application Server Activity and Resource Monitors Detailed Description

Application Server Command

Management of Application Server Administration Tools of Software Components

4 Management of Application Server

4.1 Administration Tools of Software Components

4.2 Starting and Stopping

NET STOP LSSAGENT

4.2.1 Using SAP SM Listener Daemon Server on UNIX

Management of Application Server Starting and Stopping

Stop the Listener

Run the shell script to start the Listener:

Setting up Listener Daemon To Start When UNIX Is Started

Enter the following command to stop lsstld:

The following message appears:

to stop the Listener daemon, or type N and then press

to cancel the request.

4.2.2 Starting the SAP SM Listener on Microsoft Windows

Management of Application Server Starting and Stopping

Starting the SAP SM Listener Service from the Command Prompt

Open a Command prompt window. Issue the following command:

4.2.3 Modifying the Account Used by Listener

1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13.

Management of Application Server Starting and Stopping

Replace a process level token Increase quotas

4.2.4 Removing Client/Server Session Listings from the Windows Taskbar

4.2.5 Stopping the SAP SM Listener Service on Microsoft Windows

Stopping the SAP SM Listener Service from the Command Prompt

Start a Command prompt window. Issue the following command:

Management of Application Server Backup and Restore

4.3 Backup and Restore

Logs files Trace files

\<install-dir>\SAP BusinessObjects\Strategy Management \ApplicationServer\home

Management of Application Server Backup and Restore

Management of Application Server System Copy DUMP <databasedmp>

4.3.3 Restoring Backed Up Files

SSM10 Administrator's Guide

SSM10 Administrator's Guide