sap lumira, server for teams administration guide · 5.1 managing members ... 5.2 managing groups...

SAP Lumira, server for teamsDocument Version: 1.29 – 2015-11-19

SAP Lumira, server for teams Administration Guide

Content

1 About this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.1 Who should read this guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2 What this Guide Contains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Installing SAP Lumira, server for teams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.2 Performing the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.3 Verifying your Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Launching SAP Lumira, server for teams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.4 Updating to higher version of SAP Lumira, server for teams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3 Overview of SAP Lumira, server for teams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4 User License Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

5 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125.1 Managing Members. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Creating a Member. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Adding Members to Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Assigning Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Assigning Members to Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Resetting the Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Deleting a Member. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Changing Member Type for a Member. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

5.2 Managing Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Creating a New Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17Editing a Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Viewing the Description for a Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Deleting a Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

5.3 Managing Sessions and Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Adding a License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Adding a License for Expired Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Deleting or Replacing the License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Ending a Member's Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

5.4 Configuring SAP Lumira, server for teams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Configuring the SAP Lumira, server for teams to Import AD Users . . . . . . . . . . . . . . . . . . . . . . .22Configuring Proxy Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Network and Communication Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2 © 2015 SAP SE or an SAP affiliate company. All rights reserved.SAP Lumira, server for teams Administration Guide

Content

Configuring SAP Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Configuring Extensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Configuring Drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

6 Maintaining SAP Lumira, server for teams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

7 Starting and Stopping SAP Lumira, server for teams services. . . . . . . . . . . . . . . . . . . . . . . . . 39

8 Uninstalling SAP Lumira, server for teams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

9 Troubleshooting Installation Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419.1 Logging and Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

SAP Lumira, server for teams Administration GuideContent © 2015 SAP SE or an SAP affiliate company. All rights reserved. 3

1 About this Guide

1.1 Who should read this guide

This guide is intended for administrators who want to install, configure, and manage SAP Lumira, server for teams.

1.2 What this Guide Contains

This guide contains:

● An overview of SAP Lumira, server for teams● Information on how to install SAP Lumira, server for teams● Information on how to manage members, groups, sessions and licenses● Information on how to configure and maintain SAP Lumira, server for teams


About this Guide

2 Installing SAP Lumira, server for teams

This section explains how administrators can install, and modify SAP Lumira, server for teams.

2.1 Prerequisites

Prerequisites

Before starting the installation, SAP Lumira, server for teams installation wizard runs a prerequisite check for the following system requirements:

● Installation package is only available for a 64-bit operating system.● You have administrator rights.● You have minimum drive space of 4 GB.● You have RAM of 4 GB.

RecommendationWe recommend that you have at least 8 GB RAM.

● You have not installed SAP Business Intelligence Platform Server or SAP Crystal Server or Information Platform Service on the same machine.

NoteSAP Lumira Desktop, SAP Lumira, server for teams, and other SAP BusinessObjects Enterprise clients can exist on the same machine.

● Local ports like 2638, 6400, 6405, and 6410 are free on Windows system. If the specified ports are not available, then the installer checks for three random four-digit local ports.

Context

● English is the only language supported for the installation process for SAP Lumira, server for teams.● SAP Lumira, server for teams supports non-English operating system and browsers.● You can access the SAP Lumira, server for teams from a non-English browser, irrespective of whether it is

installed on an English or non-English Operating System.● If you are accessing SAP Lumira, server for teams from a non-English browser, you can still execute all the

operations that are available on the English browser.

SAP Lumira, server for teams Administration GuideInstalling SAP Lumira, server for teams © 2015 SAP SE or an SAP affiliate company. All rights reserved. 5

Related Information

Troubleshooting Installation Issues [page 41]

2.2 Performing the Installation

Procedure

1. Download SAP Lumira, server for teams from SAP Service Marketplace.

NoteA complete list of supported operating systems, web browsers, SAP Lumira versions and hardware-related information is included in the Product Availability Matrix (PAM), available on the SAP Service Marketplace site at: https://support.sap.com/pam

2. Right-click on the setup.exe file and choose Run as administrator.

NoteYou require administrator rights to run the installation successfully.

The SAP Lumira, server for teams setup program checks whether the prerequisites are met. Once this is confirmed, the License Agreement screen opens. If any prerequisites are not met, a prerequisites screen opens, indicating which prerequisite has not been met. Close the wizard, ensure that the missing prerequisite is met, and then run the setup.exe file again to restart the installation.

3. Review the license agreement, and select the I accept the License Agreement check box, and click Next.

The Configure Destination Folder screen opens.4. If you want to change the default installation location, enter your chosen destination path or click on the ...

button to choose the directory from the file browser dialog box.5. Enter a password for the administrator account.

NoteThe password consists of at least:○ Six characters long.○ Two of the following character groups: upper case, lower case, numbers, and special characters

○ Invalid password characters: {space}{tab}○ Valid password characters: ! #“&’<>@\|()[]{}^$*+?.;

6. Confirm the password and choose Next to begin the installation.7. Once the installation completes, choose Finish to complete the installation and launch the application.

The Windows user who installs SAP Lumira, server for teams is the Super User (ADMINISTRATOR User). Members with administrator rights cannot delete the ADMINISTRATOR User's account.


Installing SAP Lumira, server for teams

http://help.sap.com/disclaimer?site=https://support.sap.com/pam

The ADMINISTRATOR User should remember the password entered, as this password cannot be reset by other members, even if they have administrator rights.

NoteYou can install, uninstall and access SAP Lumira, server for teams through a virtualized environment. The supported virtualized environments are citrix, hyper v and VMware.

Related Information

Troubleshooting Installation Issues [page 41]

2.3 Verifying your Installation

After installation, you can verify the installation by performing the following tests:

1. An entry for SAP Lumira, server for teams is created under Control Panel Programs Programs and Features SAP Lumira, server for teams .

2. After installing SAP Lumira, server for teams, three shortcuts are created in Windows start menu: StartAll Programs SAP Business Intelligence SAP Lumira, server for teams .○ Launch SAP Lumira, server for teams○ Start services○ Stop services

Note

For Windows 2012 and Windows 8.1, an entry for SAP Lumira, server for teams is created under All Apps View SAP Business Intelligence Launch SAP Lumira, server for teams . You can change the default start screen to App View by performing the following steps:1. Right-click on the taskbar and choose Properties.2. Choose the Navigation tab.3. Select Show the Apps view automatically when I go to Start.4. Choose Apply.5. Choose OK.


2.3.1 Launching SAP Lumira, server for teams

Procedure

1. Choose Start All Programs SAP Business Intelligence SAP Lumira, server for teams Launch SAP Lumira, server for teams .

You are directed to SAP Lumira, server for teams Log On page.2. Enter your member name, password, and authentication type.

Log on as the ADMINISTRATOR User by typing Administrator in the member name field and entering the administrator password that you entered when installing the program.

3. Choose Log On.

Results

SAP Lumira, server for teams launches.

2.4 Updating to higher version of SAP Lumira, server for teams

After updating SAP Lumira, server for teams, the software cannot be reverted to an earlier version. However, you can upgrade from an earlier version of SAP Lumira, server for teams to the current version.

Procedure

1. Right-click on the setup.exe file and choose Run as administrator.The License Agreement page appears.

2. Review the license agreement, and select I accept the License Agreement.3. Choose Next.4. Specify the Administrator password for the existing deployment.5. Choose Next.6. Choose Finish to complete the installation.

Note○ If you are updating to the higher version, the following data is retained:

○ The documents that you have created.


Installing SAP Lumira, server for teams

○ The documents Shared by me and Shared with me.○ The users and groups that you have created.

○ When you update SAP Lumira, server for teams from an existing version to higher versions the documents that were Shared with you or Shared by you retains the behavior of the older version.


3 Overview of SAP Lumira, server for teams

SAP Lumira is an application that helps you to visualize and create stories about data. Using SAP Lumira, you can manipulate, edit, format, and refine data to create and share visualizations that represents data graphically.

SAP Lumira, server for teams is a complete departmental data discovery solution. It is easy, quick and simple to set up and administer, and can be used to analyze and visualize business data, and to share insights with team members.


Overview of SAP Lumira, server for teams

4 User License Information

SAP Lumira, server for teams is currently available in the following versions – Trial and Licensed.

In the trial version, you can use the product for free up to 30 days. The default license key has only five Named user licenses. You can use all product functionalities that are available to a licensed member. To upgrade your product to the licensed version after the 30 days trial duration, visit http://www.support.sap.com or send a mail to [email protected].

Two types of members are created in SAP Lumira, server for teams: Named and Concurrent.

Named user license:

Named user licenses are associated with specific users. This kind of license allow users to access the system based on their user name and password. This provides Named users with access to the system, regardless of how many other users are connected. A Named user license must be available for each user account created using this option. A Named user is generally created when high priority user like an analyst want to create visualizations from data.

NoteA maximum capacity of five Named users are available in the trial version of SAP Lumira, server for teams.

Concurrent user license:

New user accounts are configured to use Concurrent user licenses. Concurrent licenses specify the number of users who can connect to SAP Lumira, server for teams services at the same time. This type of licensing is very flexible because a small concurrent license can support a large user base.

NoteConcurrent licenses are not available for the SAP Lumira, server for teams trial version.

Related Information

Creating a Member [page 13]

SAP Lumira, server for teams Administration GuideUser License Information © 2015 SAP SE or an SAP affiliate company. All rights reserved. 11

http://help.sap.com/disclaimer?site=http://www.support.sap.com

5 Getting Started

When you launch SAP Lumira, server for teams, you can start working immediately from the home page. The ADMINISTRATOR User can view two sections of the home page: My Items and Administration.End users can only view the My items section after logging on to SAP Lumira, server for teams. You can use the left-side menu for quick access to these application components and resources.

Table 1:

Left side Menu option Description

My Items Shared with me This is a list of all Lumira documents that have been shared with you by other members. This is the default landing page for members who have been sent any documents by other team members.

Shared by me This is a list of all Lumira documents that you have shared with other members.

All This is a repository of all Lumira documents that you have sent, received, created. This is the default landing page if the Shared with me inbox is empty.

Administration Members This section contains the options to create members, add members to groups, assign roles, reset passwords, and delete members.

Groups This section contains the option to create, edit, and delete groups.

Sessions and Licenses This section contains the option to manage members sessions and licenses.

Maintenance This section provides information about the status of the Lumira server for teams, server RAM usage, the number of CPUs, and server information such as operating system, version, document count, and the logging directory location. You can also restart the SAP Lumira, server for teams server here.

Configuration This section contains the option to configure HTTPS/SSL, drivers, proxy settings, and member authentication.

5.1 Managing Members

As an administrator, you can create members and groups, add members to groups, assign roles, reset passwords, and delete members.


Getting Started

5.1.1 Creating a Member

Procedure

1. Log on to SAP Lumira, server for teams as an Administrator.

2. From the left-hand panel, under Administration, select Members.3. Choose Create New Member.4. Enter a name or email address for member.

You can enter multiple names or email addresses separated by commas to create multiple members at the same time.

5. Enter and confirm a password.

After creating members, you need to communicate password details to the newly created members.

NoteIf you create multiple members, then you need to communicate the same password to all the members.

6. Select the required Member Role.The member roles that you can select are End User and Admin.

7. Select the required Member Type.The member types that you can select are Named and Concurrent.

NoteConcurrent license are not available for SAP Lumira, server for teams trial version.

8. Choose Create.The new member is validated during creation. By default, the Member Role of the new member is End User and the User Type assigned is Named. All members are by default assigned to Everyone group.

NoteThe user has to change his/her password when logging on to SAP Lumira, server for teams for the first time.

Related Information

User License Information [page 11]Assigning Roles [page 14]

SAP Lumira, server for teams Administration GuideGetting Started © 2015 SAP SE or an SAP affiliate company. All rights reserved. 13

5.1.2 Adding Members to Groups

All newly created members are assigned to the Everyone group by default. However, members with Admin roles are assigned to two default groups: Everyone and Administrators.

Context

You cannot assign members to the default groups. Before assigning members to a new group, you need to create the group.

Procedure


2. From the left-hand panel, under Administration, select Members.3. Select the member(s) that you want to add to group(s).4. Choose Add to Group.

The Add to Group dialog box appears.5. Select the group(s) that you want to add the member(s) to.6. Choose Done.

Related Information

Creating a New Group [page 17]

5.1.3 Assigning Roles

As an administrator, you can assign roles to members. For example, if a member is an End user, you can assign him/her the Administrator role, or vice-versa.

Procedure


2. From the left-hand panel, under Administration, select Members.

3. Select the member that you want to assign a role to and choose .


Getting Started

4. Select Make Admin to assign the Admin role to the end user.If the selected member currently has the Admin role, and you want to assign him/her the End user role,

choose , and select Make End User.

NoteAs other members with the Admin role cannot reset the password of the ADMINISTRATOR User, the ADMINISTRATOR User must remember his/her user name and password.

5.1.4 Assigning Members to Groups

As an administrator, you can assign members to groups.

Procedure



3. Select a member and choose .4. Select Edit Groups.5. Select the group(s) that you want to assign the member to.6. Choose Done .

The member is assigned to the group(s) selected in step 5.

5.1.5 Resetting the Password

As an administrator, you can reset members' password.

Procedure



3. Select the member whose password you want to reset and choose .4. Select Reset Password.

The Reset Password dialog box appears.


5. Enter and confirm a new password.6. Choose Reset.

NoteInform the member about the password change. The End user/ Admin user needs to change the password next time s/he log on to SAP Lumira, server for teams. As an administrator, you cannot reset the password for the ADMINISTRATOR User.

5.1.6 Deleting a Member

As an administrator, you can delete members.

Procedure



3. Select the member who you want to delete and choose .4. Select Delete Member.

The Delete member confirmation dialog box appears.5. Choose Delete.6. If you want to delete multiple members, then select multiple members and choose Delete Member on top

of the page.

NoteWhen a member is deleted, all the sessions related to this member are terminated. All documents created by the member however remain intact, and the ADMINISTRATOR User becomes the owner of these documents.

5.1.7 Changing Member Type for a Member

You can change the member type of a member from named to concurrent, and vice versa.

Procedure



Getting Started

2. Under Administration in the left-hand, select Members.3. Select the member who you want to change the member type for. To change the member type for multiple

members at the same time, select multiple members.4. Choose the Change Member Type button.5. If you want to change named user to concurrent user, select Make Concurrent.

NoteYou need to make sure that at least one concurrent user license is available in the Session and License page.

6. If you want to change concurrent user to named user, select Make Named.

NoteYou need to make sure that enough named user licenses are available in the Session and License page.

7. Choose Done.8. Navigate to the Sessions and Licenses page to view the changed member type for a member.

5.2 Managing Groups

As an administrator, you can create, edit, and delete groups.

5.2.1 Creating a New Group

Procedure

1. Log on to SAP Lumira, server for teams as an Administrator .

2. From the left-hand panel, under Administration, select Groups.3. Select Create New Group.4. Enter a name for the new group.5. In the Add Members field, double-click the text box.

The members list appears. to the group by entering multiple member names separated by commas.

NoteUnlike SAP Lumira, Edge edition 1.0 release where the member name was only email address, in SAP Lumira, server for teams 1.25 and above releases, you can choose to add member name or email address.

6. Select the required members from the list.


7. (Optional) Enter a description for a group.8. Choose Done.

Creating groups provides the flexibility to share documents with many members at the same time.

5.2.2 Editing a Group

As an administrator, you can edit the group name and its members. You can either add new members to the group or remove members from the group. You can create an empty group and add new members to it.

Procedure

1. Log on to SAP Lumira, sever for teams as an Administrator.

2. From the left-hand panel, under Administration, select Groups.

3. Select the group that you want to edit, and choose .4. Select Edit Groups.5. To edit the group name, enter a new group name.6. To edit group members, select new members or remove existing members.7. (Optional) Edit the description that you have previously added.8. Choose Done.

NoteYou cannot create sub-groups.

5.2.3 Viewing the Description for a Group

Procedure

1. Log on to SAP Lumira, server for teams as an Administrator.2. Under Administration in the left-hand panel, select Groups.

3. Select the group that you want to edit, and choose .4. Select Info.

You can now view the description for the group.


Getting Started

5.2.4 Deleting a Group

As an administrator, you can delete a group when it is no longer required.

Procedure

1. Log on to SAP Lumira, server for teams as an Administrator .

2. From the left-hand panel, under Administration, select Groups.3. Select the group that you want to delete.

The Delete Group confirmation dialog box opens.4. Choose Delete.5. If you want to delete multiple groups, then select multiple groups and choose Delete Group on top of the

page.

NoteWhen you delete a group, all relationships between the members of the group and the group in question are deleted, but the members themselves are not deleted.

5.3 Managing Sessions and Licenses

As an administrator, you can manage concurrent sessions and licenses. You can monitor active members and active sessions. You can also terminate a member's session if required.

NoteUnlike the SAP Lumira, Edge edition 1.0 release, where you would obtain the information on number of members created, and number of member licenses available for named members and concurrent members in the form X out of Y, in the SAP Lumira, server for teams 1.25 and above releases, you obtain the following information:

● The number of available concurrent member licenses.● The number of named users in the form X out of Y.

The following describes different options listed in the sessions and licenses page:

Table 2:

Section Description

Concurrent Sessions Displays the number of active concurrent members and sessions.


Section Description

Named Members Members created/Named user licenses available (Example: 2/5).

Concurrent Licenses Number of licenses available for concurrent member (Example: 2).

Days to License Renewal Displays the number of days for your license expiry.

5.3.1 Adding a License

As an administrator, you can add a license.

Procedure


2. From the left-hand panel, under Administration, select Sessions and Licenses.3. Choose Add License.

NoteWhen you upgrade SAP Lumira, Edge edition 1.0 to higher versions, you need to enter a new license key, as the existing license will not be valid after the upgrade.

4. Enter the license key.5. Choose Add.

5.3.2 Adding a License for Expired Licenses

Context

If the SAP Lumira, server for teams license is expired, then as an administrator when you try log on, you can only see an option to add a license. In such a case perform the following:

Procedure

1. Enter the license key .2. Choose Add.


Getting Started

3. If the license type (OEM/non-OEM) that you entered is compatible with the existing expired license(s), then key is successfully added.

4. If the license that you entered is not compatible with existing expired license and there is only one expired trial license, then when you choose Add, you see a Replace option instead of ADD.

5. Choose Replace.

You license is successfully replaced.

NoteIf there are 1 (non-trial) or multiple (trial or non-trial) expired licenses, then when you try to enter a valid license of a different type, system displays that there is a mismatch in the license Therefore, you cannot add that license.

For example, previously if you had OEM license, and now you are trying to replace that license with non-OEM license, in such a case system displays a type mismatch error and you cannot proceed with adding the license.

5.3.3 Deleting or Replacing the License

Procedure

1. Log on to SAP Lumira, server for teams as an Administrator.2. From the left-hand panel, under Administration, select Sessions and Licenses.3. Choose View License.4. Select the license.5. Choose <cogwheel>6. If you want to delete the license, then Choose Delete.

NoteDelete option appears disabled if it is the last valid (un-expired) license key.

7. If you want to replace the license, choose the Replace Option.

NoteOnly if SAP Lumira, server for teams consists of single license, then you see the Replace option instead of Delete. Replace dialog appears. It lists the old license key that you want to replace and consists of a text box to enter a new license.

8. Enter the new license key.9. Choose Replace.


5.3.4 Ending a Member's Session

Procedure


2. From the left-hand panel, under Administration, select Sessions and Licenses.3. Choose the member whose session you want to end and choose End Session.

The End Session dialog box appears.4. Choose End.

Results

The session ends for the member.

5.4 Configuring SAP Lumira, server for teams

You can configure the following options:

● HTTPS/SSL: For more information, see Configuring HTTPS/SSL for SAP Lumira, server for teams. [page 30]

● Drivers: In this section, you can see the number of drivers installed. For more information, see Installing Drivers [page 36].

● Proxy Settings: For more information, see Configuring Proxy Settings [page 28].● Member authentication: Enterprise is the authentication type by default. You can also configure the AD

authentication type. For more information, see Configuring the SAP Lumira, server for teams to Import AD Users [page 22].

:

5.4.1 Configuring the SAP Lumira, server for teams to Import AD Users

Prerequisites

Before you configure the Windows AD security plug-in for Kerberos, you must have completed the following tasks:


Getting Started

● Setting up the Service Account on Active Directory(AD) Domain Controller [page 25].● Granting the Service Account Rights [page 27].● Configuring the Servers to use the Service Account [page 25]● You have installed SAP Lumira, server for teams in the same domain as windows AD.

Context

Procedure

1. Log on to SAP Lumira, server for teams as an Administrator.2. In the left pane, choose Configuration.3. In the Member Authentication pane, under Active Directory, choose Settings.4. Enable the Windows Active Directory.5. Provide the following details:

a. Domain Name: The domain must be specified as the FULL DOMAIN NAME in ALL CAPS or a child domain name from where most users will be logging onto the SAP Lumira, server for teams. This should match the default domain specified in the Kerberos configuration files that are used to configure the application server.

b. User Name (Service account name along with domain name)c. Password (Service account password)d. Kerberos Authentication Principal Name(<service account name>:<Domain name>)

6. Choose Next.7. In the Add Groups field, add the groups, which needs to be imported (along with users in the group) to SAP

Lumira, server for teams.8. Enter the Kerberos Configuration File location .

You need to provide the location of the krb5.ini file, which is created in the following manner:1. Create krb5.ini file.2. Save the krb5.ini file into the C:\WINNT location on the SAP Lumira, server for teams.

Following is the Sample ‘krb5.ini’ file:

Sample Code

[libdefaults] default_realm = 2K8ADDOMAIN.COMdns_lookup_kdc = truedns_lookup_realm = truedefault_tgs_enctypes = rc4-hmacdefault_tkt_enctypes = rc4-hmacudp_preference_limit = 1[realms]DOMAIN.INTERNAL ={kdc = VMDOMCONTLR.2K8ADDOMAIN.COMdefault_domain = 2K8ADDOMAIN.COM}


NoteAfter you have modified the above file, or even the path provided for the above file, then you need to restart the SAP Lumira, server for teams to reflect your changes.

9. Enter the JAAS Login Configuration File location.

You need to provide the bscLogin.conf file location, which is created in the following manner:

1. Create bscLogin.conf file.2. Save the bscLogin.conf file into the C:\WINNT location on the SAP Lumira, server for teams.

Following is the Sample bscLogin.conf file:

Sample Code

com.businessobjects.security.jgss.initiate { com.sun.security.auth.module.Krb5LoginModule required debug=true;};

NoteAfter you have modified the above file, or even the path provided for the above file, then you need to restart the SAP Lumira, server for teams to reflect your changes.

10. Choose one of the following:a. Create Now : This option imports all the AD users to SAP Lumira, server for teams instantlyb. Create on first logon: This option imports all the AD users to SAP Lumira, server for teams during their

next logon.

NoteAfter importing the AD users to SAP Lumira, server for teams, the enterprise administrator should to provide them the respective roles. Otherwise, by default, all the AD users are assigned with end user roles during their next logon.

11. Choose Named/Concurrent user.12. Choose Done

Note○ If you have chosen Named user, then you get the following message: Number of users created

should be within the license limit.○ The AD group that you have imported also gets created as a group in SAP Lumira, server for teams.


Getting Started

5.4.1.1 Configuring the Servers to use the Service Account

Procedure

1. Choose Start Run... .2. In the Run dialog box, enter services.msc.3. Choose OK.

Services dialog box appears.4. Right click the Server Intelligent Agent, choose Properties.5. In the Properties dialog box, Choose LogOn.6. Select the Account radio button.7. Enter the service account name and domain.8. Enter the service password.9. Choose Apply.10. Choose Ok.11. Restart the Service Intelligent Agent (SIA).

5.4.1.2 Setting up the Service Account on Active Directory Domain Controller

Context

To configure the SAP Lumira, server for teams to work with Windows AD (Kerberos) authentication, you require a service account. You can either create a new domain account or use an existing domain account. The service account will be used to run the team servers.

After setting up the account, you will need to set up an SPN for the account. This SPN is used to import AD user groups into the SAP Lumira, server for teams.

You need to set up a new service account to successfully enable Windows AD authentication using the Kerberos protocol. This service account will be used to primarily allow users in a given AD group to log on to SAP Lumira, server for teams. The following task is performed on the AD domain controller machine.

Procedure

1. Create a new service account with a password on the primary domain controller.2. Select the Password never expiries Check box.


3. In order to support AD and Kerberos, you must grant the service account the right to act as part of the operating system. To grant the service account rights, see Granting the Service Account Rights [page 27].

4. Use the setspn -a command to add the service principal names (SPN) to the service account you created in Step 1. Specify service principal names (SPNs) for the service account, as well as the server, fully qualified domain server and IP address for the machine on which BI launch pad is deployed.

Sample Code

setspn -a BICMS/VM7CLNT64.2K8ADDOMAIN.COM biservice

○ BICMS is your CMS name, generally of the name BOEXI40SIA<machine name>○ VM7CLNT64 is the machine name on which SAP Lumira, server for teams is installed.○ biservice is your service account .○ 2K8ADDOMAIN is your domain. (This is used as Kerberos Authentication Principal Name,while

configuring the SAP Lumira, server for teams to import AD users.

Sample Code

setspn -a HTTP/VM7CLNT64 biservice

Sample Code

setspn -a HTTP/VM7CLNT64.2K8ADDOMAIN.COM biservice

setspn –is the HTTP/<IP address of a machine on which SAP Lumira server for teams is installed>5. Run setspn -l <servicename> to verify that the service principal names were added to the service account.

The output for the command should include all the registered SPNs as shown below:

Sample Code

Registered ServicePrincipalNames for CN=biservice,OU=boe,OU=BIP,OU=PG,DC=DOMAIN,DC=com:HTTP/<ip address of server>HTTP/<servername>.DOMAIN.comHTTP/<servername><servername>/<servicename>DOMAIN.comA sample output is provided below:C:\Users\Admin>setspn -L bossosvcacctRegistered ServicePrincipalNames forCN=bossosvcacct,OU=svcaccts,DC=domain,DC=com:BICMS/bossosvcacct.domain.comHTTP/Tomcat HTTP/Tomcat.domain.com

6. To change the user configuration of your service account, perform the following:a. In your active directory domain controller, Navigate to your service account.b. Right click the account, select Properties.c. Choose the Delegation tab.d. Select the trust this user for delegation to any service (Kerberos only) radio button.


Getting Started

e. Choose Ok.

5.4.1.3 Granting the Service Account Rights

In order to support AD and Kerberos, you must grant the service account the right to act as part of the operating system. This must be done on each machine where SAP Lumira, server for teams is installed.

Context

To grant the service account rights, perform the following:

Procedure

1. Navigate to Start Control Panel Administrative Tools Local Security Policy .2. Expand Local Policies, then choose User Rights Assignment.3. Double-click Act as part of the operating system.4. Choose Add.5. Enter the name of the service account that you created. (Example:2K8ADDOMAIN/biservice)6. Choose OK.7. Ensure that the Local Policy Setting check box is selected, and choose OK.8. Repeat the above steps on each machine, where SAP Lumira, server for teams is installed.

NoteIt is important that the Effective Right ends up being checked after Act as part of the operating system is selected. Typically, you need to restart the server for this to occur. If, after restarting the server, this optionis still not on, your Local Policy settings are being overridden by your Domain Policy settings.

5.4.1.4 Verifying your Configuration using Knit

Procedure

1. Navigate to C: Program Files (x86) SAP Lumira Edge Lumira Edge Win64_x64 sapjvm bin folder on the Lumira Edge server .

2. Execute kinit <service account> in a command prompt.

For example, execute kinit biservice in a command prompt. Here, biservice is the service account that you have created.


3. If a new ticket is stored, then the file is correct.

5.4.2 Configuring Proxy Settings

Proxy server is a server (a computer system or an application) that acts as an intermediary for requests from clients seeking resources from other servers. A client connects to the proxy server, requesting some service, such as a file, connection, documents, or other resource available from a different server and the proxy server evaluates the request as a way to simplify and control its complexity.

Procedure

1. Log on to SAP Lumira, server for teams as an Administrator.2. In the left pane, choose Configuration.3. In Proxy Settings pane, choose Settings.4. Enable the Proxy Server.5. Enter HTTP Proxy Server.6. Enter HTTP Proxy Port.7. Enter HTTP Proxy User.8. Enter HTTP Proxy Password.9. Choose Done.

5.4.3 Network and Communication Security

The network and communication security is provided by the administrator to the end user by configuring HTTPS/SSL support to the end user’s account. End user needs to configure Secure Socket Layer (SSL) for SAP Lumira Desktop to communicate securely with SAP Lumira, server for teams.


Getting Started

5.4.3.1 Configuring SSL for SAP Lumira Desktop

To work with a certificate, you need to install the certificate to the SAP Lumira JRE keystore. After adding the certificate to the JRE keystore, you can create a connection.

5.4.3.1.1 Installing the certificate to JRE keystore/trust store

Prerequisites

Before installing the certificate to the JRE keystore or trust store, do the following:

● Make sure that SAP Lumira is not running.● Obtain your certificate information from the browser while connected to the SAP Lumira, server for teams

web application.● When installing the certificate, place it in the Trusted Root Certification Authorities store.● Ensure you have access to keytool.exe that is included with the Java Development Kit (JDK).

Procedure

1. In a command window, navigate to <INSTALLDIR>\SAP Lumira\Desktop\jre\lib\security.

2. Type the following: "C:\Program Files\Java\jre7\bin\keytool.exe" -importcert -alias lumiraedge -file server.cer -keystore cacerts○ alias: the name of the server where SAP Lumira, server for teams is hosted○ file: your certificate file○ Include the path to your installation of keytool.exe. This example shows the default installation path.

Example"C:\Program Files\Java\jre7\bin\keytool.exe" -importcert -alias lumiraedge -file server.cer -keystore cacerts

3. Start SAP Lumira.

4. Navigate to File Preferences Network Settings.5. In the SAP Lumira server for teams section, use HTTPS and the appropriate port number in the URL, and

then click OK.


5.4.3.2 Configuring HTTPS/SSL for SAP Lumira, server for teams

For support with configuring HTTP/SSL, the end user enlists the help of the administrator. Before configuring HTTPS/SSL on your SAP Lumira, server for teams, make sure that you have already created a PCKS12 file or JKS keystore, and that you have copied or moved the file to the machine that is hosting the SAP Lumira, server for teams.

Procedure

1. Log on to SAP Lumira, server for teams.2. Select Configuration from the left-hand panel under Administration.

3. Choose HTTPS Settings.The HTTPS Settings dialog box opens. Choose Enable HTTPS configuration.

4. In the Bind to Hostname or IP Address field, specify the hostname that the certificates were issued for and that SAP Lumira, server for teams will bind to. HTTPS services will be provided through the IP address that you specify.

5. In the HTTPS Port field, specify a port number for SAP Lumira, server for teams to provide the HTTPS service. You have to make sure that this port is free. If you plan to allow users to connect to SAP Lumira, server for teams from outside a firewall, you also have to make sure that this port is open on the firewall.

6. In the Certificate Store File Location field, specify the path where you copied or moved the certificate file store or Java keystore file to.

7. In the Private Key Access Password field, specify the password. PKCS12 certificate stores and JKS keystores have private keys that are password protected in order, to prevent unauthorized access. You have to specify the password for accessing the private keys, so that SAP Lumira, server for teams can access the private keys.

8. We recommend using either a certificate file store or a keystore that contains a single certificate, or where the certificate that you want to use is listed first. If you are using a certificate file store or keystore that contains more than one certificate however, and that certificate is not the first one in the filestore, you have to specify the alias for the certificate in the Certificate Alias field.

9. If you want SAP Lumira, server for teams to only accept HTTPS requests from certain clients, you have to enable client authentication. Client authentication does not authenticate users. It ensures that SAP Lumira, server for teams only serves HTTPS requests to certain clients.1. Check Enable Client Authentication.2. In the Certificate Trust List File Location, specify the location of the PCKS12 file or JKS keystore that

contains the trust list file.

NoteThe Certificate Trust List type must be the same as the Certificate Store type.

3. In the Password field, type the password that protects access to the private keys in the Certificate Trust List file.

4. In the Maximum HTTP header size field, specify the HTTP header size. The default value is 32768.


Getting Started

NoteIf you enable client authentication, and a browser or web service consumer is not authenticated, the HTTPS connection is rejected.

10. Choose Create.

5.4.4 Configuring SAP Authentication

SAP authentication enables SAP users to log on to the BI platform using their SAP user names and passwords, without storing passwords in the BI platform. SAP authentication also allows you to retain information about user roles in SAP and to use role information in the platform to assign rights for performing administrative tasks or accessing content.

Context

You have to execute the following procedure to enable SAP authentication for SAP Lumira server for teams.

Procedure

1. Log on to SAP Lumira, server for teams as Administrator.2. In the Administration pane, Choose Configuration.3. In the User Authentication pane, under SAP Authentication, choose Settings.4. Enable SAP Authentication.5. In the SAP System text field, enter the three-character syste ID (SID) of your SAP system (for example

ABC).

The SAP system name must contain three characters only.6. In the Client text field, enter the client number (for example 10).7. If you choose Load Balancing under Server, enter the following:

a. Message Serverb. Logon Groupc. In the User name, Password, and Language fields, enter the user name, password, and language code

for the SAP account that you want the SAP Lumira, server for teams to use when it logs on to SAP.English is the default language.

NoteYou have to make the relevant entries in the services file on your Lumira, server for teams machine to enable load balancing.


8. If you choose Application Host, under Server option, enter the following:a. Application Serverb. System Numberc. In the User name, Password, and Language fields, enter the user name, password, and language code

for the SAP account that you want the SAP Lumira, server for teams to use when it logs on to SAP.

English is the default language.9. Choose Connect.10. In the Role Import option, select the required role.

By importing SAP roles into SAP Lumira, server for teams, you allow role members to log on to the system with their usual SAP credentials. For each role that you import, SAP Lumira, server for teams generates a group. Each group is named according to the following convention: <SystemID~ClientNumber@NameOfRole>. You can view the new groups in the Groups section of SAP Lumira, server for teams.

NoteThis group cannot be modified by other users in SAP Lumira, server for teams.

Consider two main categories of users when importing roles to the system:

Table 3:

Users Description

Concurrent users With concurrent users, you can configure and import all users at the same time to avoid delays and faster logon experience.

Named users With named users, you can configure and import users only during their first logon. This means that only users who want to access the system are imported.

11. Click Update Now option to import the roles.12. In the User Type option, select the required user type.

Specify whether new user accounts use concurrent user licenses or named user licenses.

Table 4:

License Description

Concurrent license Concurrent license specify the number of people who can connect to SAP Lumira, server for BI Platform at the same time. This type of licensing is very flexible because a small number of concurrent licenses can support a large user base.

For example, depending on how often and how long users access the system, a 100-user concurrent license could support 250, 500, or 700 users.


Getting Started

License Description

Named license Named user licenses are associated with users and allow people to access the system based on their user name and password. This provides named users with access to the system regardless of how many other people are connected.

NoteThe option you select does not change the number or type of user licenses installed in the SAP Lumira, server for teams. You must have the appropriate licenses available on your system.

13. Enter the following:

Table 5:

Section Description

Max. number of failed attempts to access entitlement system

Enter the number of times SAP Lumira, server for teams should attempt to contact an SAP system to comply with authentication requests.

ExampleIf you set the value to -1, then SAP Lumira, server for teams can reach the entitlement system any number of times.

ExampleIf you set the value to 0, then SAP Lumira, server for teams can reach the entitlement system only once.

Time duration for keeping entitlement system disabled Enter the number of seconds for the SAP Lumira, server for teams to wait before resuming attempts to authenticate users against the SAP system.

For example, if Max .number of failed attempts to access entitlement system is set to 3, SAP Lumira, server for BI platform allows a maximum of three failed attempts to authenticate users against any SAP system. A fourth failed attempt stops the system from attempting to authenticate users against the system in question for the amount of time specified.

Max. concurrent connections per system Specify how many connections to keep open in your SAP system at the same time.

For example, if you type 2, the SAP Lumira, server for teams keeps two connections open to SAP.


Section Description

Number of uses per connection Specify the number operations that you need for your SAP system per connection.

For example, if Max concurrent connections per system is set to 2 and Number of uses per connection is set to 3 once there are three logons on one connection, SAP Lumira, server for teams closes and restarts that connection.

14. Choose Done.

You have enabled SAP Authentication in SAP Lumira, server for teams. You can now choose SAP as one of the authentication types from the logon screen for SAP Lumira, server for teams.

5.4.5 Configuring Extensions

5.4.5.1 Installing Visualizations Extensions

Context

As a member with the Administrator role, you can install visualization extensions. This allows you to view and refresh Lumira documents created using visualization extensions in SAP Lumira, server for teams.

Procedure

1. Log on to SAP Lumira, server for teams as Administrator.2. In the left pane, choose Configuration.3. In the Extensions pane, choose Edit.

NoteIf you are adding extensions for the first time, the system displays the Add option instead of Edit .

4. Browse to the folder containing the zip file.5. Choose Install.6. Choose the extensions that you want use in Lumira documents.

Your extension is added to SAP Lumira, server for teams and is ready to use.


Getting Started

5.4.5.2 Unistalling Visualization Extensions

As a member with the Administrator role, you can uninstall visualization extensions.

Procedure

1. Log on to SAP Lumira, server for teams as Administrator.2. In the left pane, choose Configuration.3. In the Extensions pane, choose Edit.4. Choose the visualization extension that you want to uninstall.

NoteYou can uninstall multiple extensions at the same time.

5. Choose Uninstall.6. Choose Done.

5.4.5.3 Installing Data Access Extensions

Context

As a member with the Administrator role, you can install data access extensions. This allows you view and refresh Lumira documents created using data access extensions in SAP Lumira, server for teams.

Procedure

1. Log on to SAP Lumira, server for teams as Administrator.2. In the left pane, choose Configuration.3. In the Extensions pane, choose Edit.

NoteIf you are adding extensions for the first time, the system displays the Add option instead of Edit .

4. Browse to the folder containing your zip file.5. Choose Install.6. Choose the extensions that you have used to create Lumira documents.7. Choose Done.


After the data access extensions are installed, you are prompted to restart. Once you restart the system, your data access extensions are added to SAP Lumira, server for teams and are ready to use.

5.4.5.4 Uninstalling Data Access Extension

As a member with the Administrator role, you can uninstall data access extensions.

Procedure

1. Log on to SAP Lumira, server for teams as Administrator.2. In the left pane, choose Configuration.3. In the Extensions pane, choose Edit.4. Choose the data access extension that you want to uninstall.5. Choose Uninstall.6. Choose Done.

5.4.6 Configuring Drivers

5.4.6.1 Installing Drivers

As a member with Admin role, you can install drivers. If the driver is not installed, you receive an error message stating Unable to connect. Check your data access driver

Procedure

1. Log on to SAP Lumira, server for teams as Administrator.2. In the left pane, choose Configuration.3. In the Drivers pane, choose Edit.4. Choose the data source for which you want to install the driver.5. Choose Install.6. Choose the appropriate driver file.7. Choose Open.8. Choose Done.

After the driver is installed you are prompted to restart. You can see a green tick mark before the database name (before installation this was a red cross). If the driver has not been configured, your views the un-refreshed data/visualization. You can select multiple files/jars to configure the drivers.


Getting Started

NoteYou can only refresh your document, if drivers for data source are installed.

5.4.6.2 Uninstalling Drivers

As a member with Admin role, you can uninstall drivers.

Procedure

1. Log on to SAP Lumira, server for teams as Administrator2. In the left pane, choose Configuration.3. In the Drivers pane, choose Edit.4. Choose the data source for which you want to install the driver.5. Choose Uninstall.6. Choose Done.


6 Maintaining SAP Lumira, server for teams

As an administrator, you can restart the SAP Lumira, server for teams server if required. Under Maintenance section.

The Restart option is available for the SAP Lumira, server for teams server. Before the restart takes place, a message is displayed informing you that all active sessions will be closed if you proceed. The restart process will not begin until you confirm that you want to proceed. Members cannot perform any functionality in SAP Lumira, server for teams during the restart process. Once the restart process has completed, the members need to log on again to SAP Lumira, server for teams.

You can obtain the latest information about the server by clicking on the Refresh button.


Maintaining SAP Lumira, server for teams

7 Starting and Stopping SAP Lumira, server for teams services

Context

● To start SAP Lumira, server for teams services, choose Start All Programs SAP Lumira, server for teams Start Services .

● To stop SAP Lumira, server for teams services, choose Start All Programs SAP Lumira, server for teams Stop Services .

SAP Lumira, server for teams Administration GuideStarting and Stopping SAP Lumira, server for teams services © 2015 SAP SE or an SAP affiliate company. All rights reserved. 39

8 Uninstalling SAP Lumira, server for teams

To remove SAP Lumira, server for teams from your system, use the Uninstall option in the Windows Control Panel.

Procedure

1. Choose Start Control Panel Programs and Features. 2. Select SAP Lumira, server for teams 1.29.3. Right-click and select Uninstall.

The Application Maintenance page appears.4. Select Remove, and choose Next.

The uninstallation starts.5. Choose Finish to complete the uninstallation..

SAP Lumira, server for teams is removed from the system.

NoteIf you have updated SAP Lumira, server for teams from 1.28 to 1.29, then uninstalling it removes the complete set up from the machine. It doesn’t downgrade it to 1.28.

Results

After the uninstallation process, some of the files under the folders mentioned below remain in the system (together with the corresponding paths):

● Auditing files: <TEAM_SERVER_INSTALLDIR>\Lumira Edge\Auditing● Input / Output Repository files: <TEAM_SERVER_INSTALLDIR>\Lumira Edge\FileStore● DAT files and LOG files: <TEAM_SERVER_INSTALLDIR>\sqlanywhere\database.backup<xyz>

ExampleThe file format is <INSTALLDIR>\sqlanywhere\database.backup1208201414485607.

If you want to remove the files, you can remove these manually.


Uninstalling SAP Lumira, server for teams

9 Troubleshooting Installation Issues

1. If the 'Suppressed reboot' issue occurs, you have to reboot the system and try the installation process again. If the issue persists after rebooting, follow the steps below in order to clear the Windows Registry and resolve the issue.

○ Go to Start Run .The Run Dialog box appears.

○ Type regedit and choose OK.○ Navigate to \HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager

\.○ Double-click on the PendingFileRenameOperations and delete the content of Value Data.○ Choose OK.○ Launch the installer again.

2. During installation, the system attempts to search for available ports with no user intervention until the required free ports are found. If no ports are available, the prerequisite dialog box displays the message “One or more required ports are unavailable, refer to the installation log for more information”.To resolve this, you need to consult your IT department to free some ports, and then restart the installation.

3. See the installation logs for any installation failures:○ \<TEAM_SERVER_INSTALLDIR>\SAP Lumira Edge\InstallData\logs\

NoteYou can go to the below location to see other logs:○ \<TEAM_SERVER_INSTALLDIR>\SAP Lumira Edge\Lumira Edge\logging\

4. You cannot install SAP Lumira, server for teams if SAP Business Intelligence Platform Server or SAP Crystal Server or Information Platform Service is already installed on the same system.

5. The installation process is paused if the Windows Installer Service is disabled or is not available. You must install Windows Installer Service and enable the service before proceeding with SAP Lumira, server for teams installation. To enable Windows Installer Service, you need to consult your IT department.

9.1 Logging and Tracing

To configure SAP Lumira, server for teams tracing using the BO_trace.ini file, perform the following steps:

1. Open the BO_trace.ini file.The default location in Windows is: <INSTALLDIR>\Lumira Edge\conf\. By default, the BO_trace.ini file is configured to enable tracing and logging of errors.

2. Append the following lines to the BO_trace.ini file to enable information for logging and tracing.[from_subunit("com.sap.hilo") || from_subunit("com.sap.teamserver") || from_subunit("com.sap.bi")] sap_trace_level = trace_info; sap_log_level = log_info;

SAP Lumira, server for teams Administration GuideTroubleshooting Installation Issues © 2015 SAP SE or an SAP affiliate company. All rights reserved. 41

3. Save and close the BO_trace.ini file.The following logging and tracing levels are possible:○ sap_trace_level can have trace_error , trace_debug or trace_info○ sap_log_level can have log_error , log_debug or log_info

Performing the above mentioned steps will enable the logs.4. All the log files are created under the logging folder.

To check for the logs, go to <INSTALLDIR>\Lumira Edge\logging\ wacs_<machinename>.WebApplicationContainerServer_trace.<xyz>

ExampleThe file format is wacs_INLN50870361A.WebApplicationContainerServer_trace.000001.


Troubleshooting Installation Issues

Important Disclaimers and Legal Information

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

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

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

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

SAP Lumira, server for teams Administration GuideImportant Disclaimers and Legal Information © 2015 SAP SE or an SAP affiliate company. All rights reserved. 43

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

www.sap.com/contactsap

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

http://www.sap.com/contactsap

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

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

sap lumira, server for teams administration guide · 5.1 managing members ... 5.2 managing groups...

Documents