Enterprise SOA with SAP NetWeaver 2004s

Enterprise SOA currently is a very important topic at SAP and most SAP presentations you get to see (for example at SAPTeched which was starting today in Amsterdam) will probably include information and graphics about enterprise SOA, NetWeaver and the Business Process Platform. However, I made the experience that those graphics are either very simple (don’t provide information about included components, tool names etc.) or they focus on a specific application like Application Server, Exchange Infrastructure or Composite Application Framework. Thus for me it was very hard at the beginning to understand the coherences and differences between NetWeaver applications and to get an overall understanding what enterprise SOA means in terms of SAP tools and applications. Therefore I created my own picture which I extended over time. Of course it does not include all details but the chosen granualirity was a good basis for the discussions I had in the area of enterprise SOA. So here it is, maybe it’s of some help for you as well:

Enterprise SOA with SAP NetWeaver 2004s

The graphic might be a bit complex when you first see it but this is how the application reality in the context of enterprise SOA is. For the most important applications you find the respective development tools at the side in a box with striped background. The graphic also gives an orientation which applications are on the same layer. You see for example that web services can be created with XI or CAF Core, processes with ccBPM or Guided Procedures. So it might be interesting to explore the differences.

In case the graphic is helpful or you have an idea how to improve it, you can of course leave me a comment.

SOA-Thesis: 11 Guided Procedures Part 2

SOA-Thesis: 11 Guided Procedures Part 2

http://youtube.com/watch?v=9hyg6nX46s4

Video: This video shows some results of the thesis "Design and Implementation of a Service-oriented Information System Architecture Based on a Case Study". The implementation was done using SAP NetWeaver technology. During the video series different elements of the architecture are presented: service-enablement of the backend, service development in CAF Core, creation of user interfaces in Visual Composer and implementation of the process with CAF Guided Procedures. Finally a runtime demo of the composite applicaton is given

SOA-Thesis: 10 Guided Procedures Part 1

SOA-Thesis: 10 Guided Procedures Part 1

http://youtube.com/watch?v=DmDHtan77X8

Video: This video shows some results of the thesis "Design and Implementation of a Service-oriented Information System Architecture Based on a Case Study". The implementation was done using SAP NetWeaver technology. During the video series different elements of the architecture are presented: service-enablement of the backend, service development in CAF Core, creation of user interfaces in Visual Composer and implementation of the process with CAF Guided Procedures. Finally a runtime demo of the composite applicaton is given

SOA-Thesis: 98 Demo Part 1

SOA-Thesis: 98 Demo Part 1

http://youtube.com/watch?v=AODZFzMHZ6I

Video: This video shows some results of the thesis "Design and Implementation of a Service-oriented Information System Architecture Based on a Case Study". The implementation was done using SAP NetWeaver technology. During the video series different elements of the architecture are presented: service-enablement of the backend, service development in CAF Core, creation of user interfaces in Visual Composer and implementation of the process with CAF Guided Procedures. Finally a runtime demo of the composite applicaton is given

SOA-Thesis: 01 Introduction

SOA-Thesis: 01 Introduction

http://youtube.com/watch?v=1mXDifFAS7U

Video: This video shows some results of the thesis "Design and Implementation of a Service-oriented Information System Architecture Based on a Case Study". The implementation was done using SAP NetWeaver technology. During the video series different elements of the architecture are presented: service-enablement of the backend, service development in CAF Core, creation of user interfaces in Visual Composer and implementation of the process with CAF Guided Procedures. Finally a runtime demo of the composite applicaton is given.

SAP NetWeaver Portal folder creation

SAP NetWeaver Portal folder creation

http://youtube.com/watch?v=FEckQXyccw8

Video:

Shows how to create a folder in the PCD for storing other objects. This folder will contain any iViews and roles we create, but can also have subfolders created. Please note that right click is used to launch the option to create new objects.

SAP NetWeaver Portal create a transaction iView

SAP NetWeaver Portal create a transaction iView

http://youtube.com/watch?v=h6o9UU7Snh8

Video:

Demonstrates how to create an iView to start an SAP transaction that lists the users logged on to an SAP backend system. (transaction SM04) The system alias is MYALIAS and SAPGUI for HTML will be used. After creating the iView, add it to a role as per the role creation example.

Dynamic User Assignment to Roles in SAP NetWeaver CE 7.1

Dynamic User Assignment to Roles in SAP NetWeaver CE 7.1

http://youtube.com/watch?v=7sdzlNncB5E

Video:

This demo records a session that assigns users dynamically roles in SAP NetWeaver Composition Environment 7.1.

SAP NetWeaver Portal download verify.der

SAP NetWeaver Portal download verify.der

http://youtube.com/watch?v=eZyNWd6iLjM

Video: Part of setting up a single sign on environment between an SAP NetWeaver Portal and an SAP backend system is to download the certificate of the portal. This can be down from the portal using the System Administration function for keystore administration. This video shows how to perform this activity. The file (verify.der) is saved to the c:\ drive where it will be uploaded. The decompression utility in this case is WinRAR, but any other utility will do

SOA-Thesis: 07 Visual Composer Part 1

SOA-Thesis: 07 Visual Composer Part 1

http://youtube.com/watch?v=2NV_oYwmCxQ

Video: This video shows some results of the thesis "Design and Implementation of a Service-oriented Information System Architecture Based on a Case Study". The implementation was done using SAP NetWeaver technology. During the video series different elements of the architecture are presented: service-enablement of the backend, service development in CAF Core, creation of user interfaces in Visual Composer and implementation of the process with CAF Guided Procedures. Finally a runtime demo of the composite applicaton is given.

SOA-Thesis: 99 Demo Part 2

SOA-Thesis: 99 Demo Part 2

http://youtube.com/watch?v=TfkC760545s

Video: This video shows some results of the thesis "Design and Implementation of a Service-oriented Information System Architecture Based on a Case Study". The implementation was done using SAP NetWeaver technology. During the video series different elements of the architecture are presented: service-enablement of the backend, service development in CAF Core, creation of user interfaces in Visual Composer and implementation of the process with CAF Guided Procedures. Finally a runtime demo of the composite applicaton is given. For more information visit

SOA-Thesis: 05 Application Services

SOA-Thesis: 05 Application Services

http://youtube.com/watch?v=4mO4YZZgDyE

Video:

This video shows some results of the thesis "Design and Implementation of a Service-oriented Information System Architecture Based on a Case Study". The implementation was done using SAP NetWeaver technology. During the video series different elements of the architecture are presented: service-enablement of the backend, service development in CAF Core, creation of user interfaces in Visual Composer and implementation of the process with CAF Guided Procedures. Finally a runtime demo of the composite applicaton is given. For more information visit http://www.soa-thesis.de.

Uploading verify.der into an SAP backend system

Uploading verify.der into an SAP backend system

http://youtube.com/watch?v=wBkrI4aazIE

Video:

The second part of the process to share a SAP NetWeaver Portal's certificate with an SAP backend system is to upload it into the SAP system. This is done by logging on to the SAP system and then starting transaction strustsso2 and using the option to import a cerificate. After that, an ACL must be created with the SID and client of the SAP NetWeaver Portal. These are normally the SID of the AS Java and 000, but they can be changed through UME settings.

SAP NetWeaver Portal role creation

SAP NetWeaver Portal role creation

http://youtube.com/watch?v=PGaKnDU1xgg

Video:

This shows how to create a portal role in the SAP NetWeaver portal. The role will contain a two level menu structure and under the second level will be an existing iView that launches YouTube. It is necessary to set one of the folders as an entry point, otehrwise nothing will be displayed! Please note that right click is used to launch the option to create new objects.

NetWeaver SAPSetup Demo - Re-configuring packages

NetWeaver SAPSetup Demo - Re-configuring packages

http://youtube.com/watch?v=kngZ3B9Z06Q

Video:

Demo that explains how administrators can use NWSAPSetupAdmin - the Installation Server Administration tool to reconfigure packages and update workstations with the newer versions of the same.

SAP NetWeaver Portal URL iView creation

SAP NetWeaver Portal URL iView creation

http://youtube.com/watch?v=lVlgaGsdQ78

Video:

Shows how to create a simple URL based iView. This iView will launch the YouTube website. Please note that right click is used to launch the option to create new objects.

SAP NetWeaver Portal system creation

SAP NetWeaver Portal system creation

http://youtube.com/watch?v=70DAmRNJ8-0

Video:

Describes how to create a system definition in the portal system landscape. The SAP backend system with a dedicated host of mybackend.mycompany.com is used, accessing client 123. The SID is TST and the ITS and Web AS use the integrated ICM on port 8000. A system alias MYALIAS is assigned so that iViews can access the system.

SAP NetWeaver Business Intelligence par Artens

SAP NetWeaver Business Intelligence par Artens

http://youtube.com/watch?v=7oHcgkR2b1A

Video:

La solution SAP NetWeaver Business Intelligence permet d'analyser les données de l'entreprise au travers d'interfaces ergonomiqes Web ou Excel. Elle donne également accès à des outils de budgetisation (BPS et IP) et à des applications composites permettant de combiner décisionnel et opérationnel, qualitatif et quantitatif, SAP et non-SAP au sein d'un même écran. Artens est le spécialiste français SAP NetWeaver BI depuis 2001.

How to login to SAP NETWEAVER XI

How to login to SAP NETWEAVER XI

http://youtube.com/watch?v=vLcfKhsRXr4

SAP NetWeaver Portal role assignment

SAP NetWeaver Portal role assignment

http://youtube.com/watch?v=wJM-3grF6Cg

Video:

This shows how to create a new user (testuser) and assign the role firstrole to that user. The user then logs on, changes their password and sees their portal role content.

Setting Up the Mail Server

Use

If you want to distribute business intelligence content using e-mail, you have to set up the mail server in the SAP Web Application Server.

Procedure

1. In the BW system, choose the transaction SAPconnect: Administration (system status) (transaction SCOT).

2. Check the status of the node SMTP (Simple Mail Transfer Protocol):

¡ The node SMTP does not exist:

To create the node, in the menu, choose Node ® Create. Specify a node ID and a description.

¡ The node SMTP is not active:

To activate the node, in the menu, choose Node ® Change. Select the field Node in Operation.

3. In the menu, choose Node ® Change. The screen SAPconnect: General Node Data opens. Ensure that the following values are defined:

¡ Mail Host: for example, mailto.wdf.sap.corp (localhost is generally not a valid mail host because both a mail server and SAP Application Server are generally not installed on a PC at the same time)

¡ Mail Port: Standard value for SMTP is 25

¡ Code page: Standard values are 1100 or 1140

¡ Supported address types

Select the Internet field and choose Setup. The screen SAPconnect: Address Type for Node opens. Enter * in the address area.

4. To maintain the standard domain, in the menu, choose Settings ® Default Domain and enter the appropriate value (for example, sap.com for e-mail addresses, such as @sap.com).

Configuration for Information Broadcasting

Purpose

In order to be able to use information broadcasting, you have to configure the system in various NetWeaver components.

Prerequisites

You have installed the necessary components for information broadcasting. For more information, see service.sap.com/instguides ® SAP NetWeaver ® Release 04 ® Installation ® Installation Guide – SAP Business Information Warehouse 3.5.

Process Flow

1. If you want to distribute Business Intelligence content to the SAP Enterprise Portal, follow the configuration steps for the integration of SAP BW and SAP EP. For more information, see Making Settings for SAP BW 3.5 and SAP EP 6.0 .

2. If users in the Enterprise Portal want to hold discussions, add personal notes or give feedback using the BI content, activate and configure the corresponding collaboration services. For more information, see Collaboration Services.

3. If you want to make it possible for users in the Enterprise Portal to subscribe to KM folders or individual documents, activate and configure the subscription service. For more information, see Subscription Services.

4. If you want to be able to distribute Business Intelligence content by e-mail, set up the mail server in the SAP Web application server. Choose the node SMTP (Simple Mail Transfer Protocol) under SAPConnect: Administration (transaction SCOT). For more information, see Setting Up Mail Servers and SAPconnect (BC-SRV-COM).

5. You can modify the display of precalculated queries by defining the standard Web template for query precalculation in Customizing.

You can also establish the standard Web template for broadcasting here. This determines how the BEx Broadcaster is displayed when it is called from various areas of the Business Explorer. For more information, see Functions of the BEx Broadcaster.

You determine the standard Web templates in the BW system under SAP Reference IMG ® SAP NetWeaver ® SAP Business Information Warehouse ® Reporting-relevant Settings ® BEx Web ® Set Standard Web Templates.

6. If you want to precalculate workbooks (in addition to queries and Web templates), you determine, in Customizing, which precalculation servers are available for the BW system. You make this setting in the BW system under SAP Reference IMG ® SAP NetWeaver ® SAP Business Information Warehouse ® Reporting-relevant Settings ® General Reporting Settings in Business Explorer® Administrate Precalculation Server.

For more information, see Administration of the Precalculation Server and Creating Precalculation Servers.

7. You assign administrator authorizations for broadcasting. To do this, use authorization object S_RS_ADMWB with the field RSADMWBOBJ = BR_SETTING. For more information, see Overview: Authorization Objects.

Result

You have set up the systems according to your needs, enabling you to use information broadcasting. In order to allow end users in your organization to use the scenarios they require, set up the necessary authorizations in system administration and perform the administrative duties. For more information, see Tasks for System Administration.

Making Settings for SAP BW 3.5 and SAP EP 5.0 Locate the document in its SAP Library structure IN BIW

Purpose

A number of settings need to be made in the BW system for the Integration of SAP BW 3.5 and SAP EP 5.0. Some settings in SAP BW and SAP EP are dependent upon each other.

SAP recommends that you retain the given order, especially when maintaining settings in SAP BW and SAP EP.

The report Maintaining Settings for Integration into the SAP Enterprise Portal (report RSPOR_SETUP) is only intended for administrators of SAP BW 3.5 and SAP EP 6.0. However, the documentation in customizing can partially be used for the steps listed below.

The required settings are summarized in Customizing at SAP Reference IMG (transaction code SPRO) ® SAP Customizing Implementation Guides ® SAP NetWeaver ® SAP Business Information Warehouse ® Reporting-Relevant Settings ® BEx Web ® Integration into SAP Enterprise Portal.

Prerequisites

If you are an SAP BW administrator, you have authorizations for the transaction codes RZ10, STRUSTSSO2 and, if necessary, STMS.

As an administrator for SAP EP, you are assigned the portal role portal_admin. You also have access to the file system on the portal server.

Where various people are responsible for the administration of SAP BW and SAP EP, SAP recommends that, from an organizational point of view, administrators work together closely.

Process Flow

Perform the necessary steps in the following order:

1. Maintaining Single Sign-On in SAP BW

2. Creating BW Systems in SAP EP 5.0

3. Exporting the Portal Certificate into SAP EP 5.0

4. Importing the Portal Certificate into SAP BW

5. Importing the SAP Basis Plug-In into SAP BW

The documentation for the individual steps describes the manual process.

Menu Entry "Publishing in Enterprise Portal 5.0" IN BIW

Use

With the Customizing activity Hide Menu Entry „Publishing in Enterprise Portal 5.0“, you can hide the menu entry Publishing in Enterprise Portal 5.0 in the BEx Web Application Designer.

You need this setting for all integration scenarios

Prerequisites

It makes sense to hide the menu entry if SAP EP 5.0 is not available or if the BW system is not connected to SAP EP 5.0. The user will then be unable to execute operations that are only possible with an Enterprise Portal 5.0.

Features

When the option is activated, the menu is hidden the next time you logon to the BW system with the BEx Web Application Designer.

The menu entry Publishing to Enterprise Portal 6.0 cannot be hidden. This menu entry is activated when at least one portal server is maintained in Customizing.

For more information about publishing to Enterprise Portal 6.0, see Publishing Queries and Web Applications.

Check

Start the BEx Web Application Designer. There is no entry with Enterprise Portal 5.0 in the Publish menu.

Maintaining Access Control Lists (ACL) in Knowledge Management IN BIW

Use

BEx Information Broadcasting generates and uses documents and links in Knowledge Management. Knowledge Management protects these documents and links using access control lists (ACL). Individual documents, links and folders can be provided with authorizations.

During precalculation of BEx Web Applications using Information Broadcasting, documents are generated in the BW system in background processing and these are then stored in Knowledge Management for the portal. During background processing, the service user bw_service is used (see ‎Information Broadcasting as Background Processing). You should make sure that users do not have access to all Knowledge Management folders, but only those you deem necessary.

Procedure

Access Control Lists (ACL) are maintained in Knowledge Management. Authorizations can be maintained at the document, link or folder.

1. All repositories and their content can be displayed with the iView Content Administration ® KM Content.

2. The details can be opened using the popup menus.

3. The authorizations can be determined using Settings ® Authorizations. You can only maintain the authorizations if you are the owner of the object.

Maintaining Authorizations IN BIW

Use

The various integration scenarios between SAP BW 3.5 and SAP EP 6.0 are protected by authorizations.

The administrators in SAP BW and Enterprise Portal require authorizations for the transactions and tools in order to make settings.

Procedure

1. In order to use functions of BEx Information Broadcasting, you need to maintain authorizations. You can find more information under Configuration for Information Broadcasting.

2. The use of documents and links in Knowledge Management is protected by access control lists (ACL). You can find more information under Maintaining Access Control Lists (ACL) in Knowledge Management.

3. The BEx tools are protected by the general authorizations in BW. You can find more information under Authorizations for Working with the Business Explorer.

For more current information, see SAP note 702350.

Importing the SAP Basis Plug-In IN BIW

Use

To integrate between SAP BW 3.5 and SAP EP 6.0 (especially for SAP role upload), you need to import the SAP Enterprise Portal Plug-In (PI_BASIS).

As of SAP Web Application Server 6.40, the SAP Enterprise Portal Plug-In is part of SAP Basis Plug-In. For more information, see SAP note 723189.

Procedure

1. Download the SAP Basis Plug-In (PI_BASIS) from the SAP Software Distribution Center in the SAP Service Marketplace (quick link SWDC).

2. Start the Transport Management System(transaction code STMS).

3. Import the SAP Basis Plug-In into the BW system.

Check

You can do a check when you upload BW roles into the portal. For more information, see Integration Using Role Upload.

For more information, see SAP note 655941.

Maintaining User Assignments in BIW

Use

You use the user assignments to assign a user in the BW system to a user in the portal.

User assignment depends on the logon method that is specified in Create a BW System in the Portal . With the UIDPW logon method, the user assignment must always be maintained because the password is required for a successful logon. This is also valid for identical technical user names.

With the SAPLOGONTICKET logon method, the user assignment is not necessary if the technical user name in the portal is identical with the technical user names in the BW system. With differing technical user names, user assignment is also necessary with the SAPLOGONTICKET logon method, especially when the scenario Publishing to the Enterprise Portal.

For more information about central user management, see Configuring User Management.

In SAP EP 5.0 user assignments are only used to link a user in SAP EP with a user in SAP BW. With the integration of SAP EP 6.0 with SAP BW 3.5 user assignment is also used to link a user in SAP BW with a user in SAP EP (inverse user assignment). For this reason, unique assignments are required for both directions. Thus several users in SAP EP cannot be assigned to the same user in SAP BW.

BEx Information Broadcasting uses the bw_service user in SAP EP. You must either create a user bw_service in SAP BW or maintain a user assignment for bw_service to another user in SAP BW. The service user bw_service is automatically created in SAP EP when there is a call from SAP BW to SAP EP. For example, this happens when the setting step Creating an RFC Destination for SAP EP 6.0 is checked. The user bw_service may not be created manually in SAP EP. Ensure that the user bw_service, like all users, has at least read authorization for the BW system in the portal system landscape.

For more information, see Security.

Procedure

Assigning Read Authorization

First ensure that all portal users that use information broadcasting at least have read authorization for the BW system created in the portal.

1. Start the iView System Administration ® System Configuration ® System Landscape.

2. Navigate to the previously created system, open the context menu and choose Open ®Authorizations.

3. Search for the user or the user group or role, add it and issue read authorization.

Assigning Users

...

1. Log on to the portal.

2. Start the iView User Management ® User Assignments.

3. From the dropdown box, choose User.

4. Enter a user or select Start for All Users.

5. Choose Start.

6. Choose a user and choose Edit.

7. Choose the system alias of the BW system (see Creating BW Systems in the Portal).

8. Enter the technical user name in BW.

9. Enter the appropriate password.

10. Save your entries.

11. Once user assignments have been you have to restart the SAP Enterprise Portal.

You can also alternatively create the portal user bw_service with the same name in user management of the SAP BW (transaction code SU01). On the Logon Data tab pave, ensure that the user has a Service user type.

Alternatively, in the SAP Enterprise Portal, you can create a user assignment for the portal user bw_service on a BW user with a different name. This also has to have a Service user type.

Repository Manager for BW Metadata

Definition

Repository manager for metadata in the SAP Business Information Warehouse.

Use

The repository manager for BW metadata allows you to integrate the metadata created in SAP BW (InfoCubes, queries, Web templates, workbooks and so on) and their associated documents into Knowledge Management in the SAP Enterprise Portal as write-protected documents. Furthermore, the repository manager for BW metadata allows you to access online links created with BEx Information Broadcasting.

The repository manager for BW metadata allows you to access automatically generated HTML-based documents for metadata. The documents correspond to the information in the Metadata Repository in the Administrator Workbench. Additionally you can create manual documents for metadata that can be integrated into Knowledge Management using the Repository Manager for BW Documents.

Structure

The parameters of the repository manager for BW metadata are explained in the following. When you choose Show Advanced Options, you get a complete list of parameters A plus sign (+) indicates the advanced setting options.

For performance reasons, we recommend that you deactivate the following parameters:

§ Show objects data is received from (data flow before)

§ Show objects data is sent to (data flow after)

§ Show usage (where-used list)

The where-used list and the data flow list a large number of objects for central objects so that the online documentation is extensive. This can cause building the online documentation to take quite a bit of time. See also Tab Page: Online Documentation.

Parameters of the repository manager for BW metadata

Parameter	Obligatory	Description
Name	Yes	Name of the repository manager
Description	No	Description of the repository manager
Prefix	Yes	URI prefix for which the repository manager for BW metadata is registered. This entry lists the repository in the master directory. The URIs for all resources managed by this repository manager have this common prefix. The prefix is used to identify the repository manager that is responsible for a resource with a particular URI. Note: The prefix has to be entered with a diagonal slash, for example, /bw_metadata. The prefix in the BW system has to agree with the one in the portal.
Active +	No	You can activate or deactivate the repository manager by setting this parameter.
Hide in root folder +	No	This parameter specifies whether the repository is listed in the master directory. If you activate this parameter, the repository is not listed in the master directory.
Repository services	No	Identification of the Repository Services that you want to use for a repository.
Property search manager	Yes	Selection of the manager for the property search. Choose com.sap.ip.bi.km.repository.manager.mo.MoPropertySearchManager.
Security manager	Yes	This parameter cannot be changed and specifies the security manager BW Metadata Security Manager. This controls access to the repository content. The BW Metadata Security Manager provides a connection to the BW system and checks whether authorization exists to display metadata.
Lock Manager	No	Leave this field empty.
Send Events +	No	This parameter specifies whether the repository sends events when operations like “delete” or “refresh content” are performed. The parameter has to be activated if you want the repository to send events. This is necessary, for example, when using services like the subscription service.
Show objects from which data is received	No	In data flow before: If you activate this parameter, links to the online documentation for the object from which the current object receives data are displayed.
Show objects data is sent to	No	In data flow after: If you activate this parameter, links to the online documentation for the objects to which the current object sends data are displayed.
Show technical names	No	If you activate this parameter, the technical names of the BW objects upon which the documents are based are displayed. If you deactivate the parameter you can still see the technical names of the BW objects using the tool tip.
Show usage	No	Where-used list: If you activate this parameter, links to the online documentation for the objects that the current object uses are displayed.
Lifetime metadata cache	No	Here you can set the lifetime of cache elements for metadata in seconds. If you enter the value 0, the cache is deactivated.
Lifetime property cache	No	Here you can set the lifetime of cache elements for the properties of the objects in seconds. If you enter the value 0, the cache is deactivated.
Lifetime security cache	No	Here you can set the lifetime of cache elements for the user-specific access authorizations in seconds. The security cache is deleted automatically in the background according to the time specification entered here. If you enter the value 0, the cache is deactivated. If a number of users are accessing the repository manager for BW metadata, we recommend that you deactivate the cache and set the value at 0 to avoid too great a memory consumption.
Alias of BW System	Yes	Here you enter the alias of the BW system that you specified in the portal system landscape directory when you set up the BW system. See Creating BW Systems in the Portal.
Prefix of BW document repository	No	If you are using the repository manager for BW metadata as well as the repository manager for BW documents, you can enter its prefix here. The two repository managers are now connected and you are able to see not only the metadata and its documentation, but also the corresponding documents.

Example

Configuration of a Repository Manager for BW Metadata

Name = BWMetadataRepositoryManager

Description = BW Metadata AB

Prefix = /bw_metadata

Active = activated

Hide in Root Folder = deactivated

Repository Services = comment, properties

Property Search Manager = com.sap.ip.bi.km.repository.manager.mo.MoPropertySearchManager

Security Manager = BWMetadataSecurityManager

Send Events = activated

Show Objects data is received from = deactivated

Show Objects data is sent to = deactivated

Show technical Names = deactivated

Show usage = deactivated

Lifetime Metadata Cache = 7200 seconds

Lifetime Property Cache = 7200 seconds

Lifetime Security Cache = 0 seconds

Maximum Connections per User = 5

Alias of BW System = SAP_BW

Prefix of BW Document Repository = /bw_documents