Creating a Model Connection

Prerequisites

If you are configuring a model as a data source for Reports and Dashboards, you are a member of the BUIJ_APP_ALL role in SAP NetWeaver Administrator. For more information, see the Installation Guide for SAP Strategy Management on the SAP Help Portal.

Procedure

Select Administration Manage Models.
Click New under the Model Connections list. The Model Connection text box appears in the Connection Settings section.
In the Model Connection text box, type a model connection name. Specify only alphanumeric characters (a-z, 0-9) up to a maximum size of 64 characters. You must not use special characters in the name, including the following: (/) forward slash, (\) back slash, (<) less than, (>) greater than, (') single quote, (") double quote, (,) comma, (:) color, and (;) semicolon. You can use underscores (_).
In the PAS System Name text box, type the name of the server where Application Server is installed. If Interactive Publisher is installed on a different server than SAP NetWeaver, then enter the IP address for Application Server.
In the PAS System Logon text box, type the name of a user on the Application Server system. On Windows, this user must be a member of the administrators group. On Linux/UNIX, this user must have permission to run the scripts and programs in the Application Server installation directory.
In the Password text box, type the password for the user.
In the Port text box, type the communications port for the UNIX or Windows server machine running Application Server. The default is 8325.

Note The machine where the application is installed must have access rights to this port. If you can telnet <hostname> 8325 from a DOS window, then you have the appropriate access rights.
In the Min text box, type the number of instances of Application Server to start up with this model connection. The default setting is 0, which means that no instances start until the first URL query is submitted.
In the Max text box, type the maximum number of instances of Application Server to allow for this model connection. The default setting is 5. You can set up to 255 instances.

You must specify a maximum number of Application Server instances that is equal to or lower than the number defined for the Application Server user. For example, if an Application Server user is allowed 5 instances, you must enter a number that is no higher than 5. To find out the maximum number of instances available to an Application Server user, issue the SUPERVISOR SHOW USERS command in Application Server. To change the number of instances available to an Application Server user, issue the SUPERVISOR CHANGE USER command with the MAXLOGIN keyword. For information about these commands, see the Application Server online Help.
In the PAS Model text box, type the name of the Application Server model to use for this model connection.

Note
You cannot use a model that contains text variables.

Note
You must already have an Application Server model created. If you do not have a model created, you can use the sample model provided with the Application Server installation. For information about configuring your system to use the sample model and model connection, see the Server Configuration Help for SAP Strategy Management on the SAP Help Portal. Then choose Setting Up the Demonstration Implementation.
In the PAS User text box, type the Application Server user who has access to the Application Server model who you want to add to this model connection.

Note
Make sure the Application Server user is a user of the model you are adding to the model connection definition.

Note
If you are running Application Server on a Linux/UNIX server, the UNIX or Linux user specified in the PAS User text box must have appropriate access to the $ORACLE_HOME directories, particularly $ORACLE_HOME/lib32. It is highly recommended to grant read and execute access to the directory structure under $ORACLE_HOME to ensure that there are no problems with Application Server connections to Oracle. You can run the $ORACLE_HOME/install/changePerm.sh script to ensure that the account used for client/server connections has the appropriate access privileges to the Oracle client software. This script establishes Read access to most of the directories in $ORACLE_HOME.
In the Password text box, type the password for the Application Server user. If the user is Guest, you do not need to specify a password.
In the INI File text box, type the name of the Application Server initialization file to use. The default filename created at installation is lsserver.ini.
In the Service text box, type the service parameter specified in the lsserver.ini file. The default service name is PILOT.
Select Configure Model Connection for Reporting if you want users to use the data from this model when creating reports and dashboards.
Click Test Connection. You see a message stating that the Application Server connection is made, you are logged in, and the Application Server USE database was found.
By default, the Everyone option is selected in the Groups and Users section and all users are added to the model connection when you create it. Do any of the following to add users to this model connection:
- Keep the default setting of allowing all users ( Everyone) to use this model connection. You can skip the rest of the steps in this topic and click Save. Only one Application Server user can use the Everyone setting for a model connection. If you attempt to create a second Application Server user with the Everyone setting, you receive a message telling you that you must select groups or users.
- Select System Groups to assign system groups.
- Select Users to assign individual users. The list displays the first 500 users. If there are more users to display, click Get full user list. A message box explains that the retrieval may take more than 60 seconds. The Users list is updated to contain the entire list of users.
  
  From the left-hand list, select a user or system group and click Add to add it to the right hand list.
Click Save.

Now a scorecard administrator (a user in a role with permission to create scorecards) associates a model connection with a context using Start of the navigation path Administration Next navigation step Manage Scorecards Scorecard Defaults Scorecard End of the navigation path section.