NetWeaver Full Details

Authorizations in Change Management Service

2009-11-12T06:04:00.001-08:00

To grant authorizations, Change Management Service (CMS) uses the User Management Engine (UME) in SAP J2EE Engine.

You can use CMS to perform the following UME actions. These UME actions allow you to create UME roles with special authorizations. For examples of roles in CMS, see Roles in Change Management Service .

The following UME actions are defined:

UME Actions in CMS

UME Action	Permitted Functions
CMS.Display	This UME action grants you access to CMS. This UME action serves as the basis for all further UME actions.
CMS.ExportOwn	Release your own activities in SAP NetWeaver Developer Studio
CMS.ExportForeign	Release other users’ activities in SAP NetWeaver Developer Studio
CMS.Transport	Check-In Add to queue Unlock queue entries Restore system state Import Import check: Assemble Forward to another track (the authorization for this function is checked in the target track)
CMS.CriticalFunctions	Delete queue entries Lock/Unlock Import Queue
CMS.Approve	Confirm/Reject
CMS.ConfigureDomain	Save domain Update CMS
CMS.CreateTrack	New Save (new track) Save as
CMS.ModifyTrack	Save (existing track) Add/Delete runtime systems Delete Add/Delete track connections
CMS.OverAllTracks	UME action that allows you to edit all tracks, independently of track-specific UME actions
CMS.UserAdmin	UME action for processing track-specific UME actions
CMS.Administrate	Composite UME action that includes all other UME actions

The UME actions CMS.Export and CMS.Configure have now been replaced by more configurable authorization modules.

Previous UME action

Replaced by the following UME actions

CMS.Export

CMS.ExportOwn

CMS.ExportForeign

CMS.Configure

CMS.ConfigureDomain

CMS.CreateTrack

CMS.ModifyTrack

Roles in Change Management Service

2009-11-12T06:03:00.001-08:00

For individual descriptions of the UME actions that you can use for your work in Change Management Service (CMS), see Authorizations in Change Management Service.

The following is a list of useful roles in CMS:

CMS Role Types

Role	Assigned UME Actions	Privileges of the Role
Guest	CMS.Display	Display import queues and transport histories in the Transport Studio Display details of queue entries and logs. Display configuration files in Landscape Configurator
Developer	CMS.Display CMS.ExportOwn	Has all Guest privileges. Release own activities in SAP NetWeaver Developer Studio
Quality Manager	CMS.Display CMS.Approve CMS.ExportForeign	Has all privileges of Guest. Approve and reject software components in Transport Studio. Release foreign (third-party) activities in Developer Studio
Operator	CMS.Display CMS.Transport CMS.CriticalFunctions	Has all privileges of Guest. Perform test imports, check-in, assemble, unlock queue entries, restore system state Perform the critical functions Delete Queue Entries, Add to Queue, Import Older Versions, Forward to Another Track.
Configurator	CMS.Display CMS.CreateTrack CMS.ModifyTrack	Has all privileges of Guest. Perform all configuration functions at track level in Landscape Configurator
Administrator	CMS.Administrate	Combines all CMS privileges in one role

Users who have been assigned the CMS administrator role should also have J2EE Engine Administrator rights. All users who are CMS administrators should therefore be assigned to the J2EE Administrator group as well.

To configure the domain in CMS you need to create a CMS User. As well as the administrator rights for Component Build Service (CBS) and Design Time Repository (DTR), this user also needs the write permission for System Landscape Directory (SLD).

Configuring the Change Management Service

2009-11-12T05:58:00.000-08:00

Use

Using the Change Management Service (CMS) with SAP NetWeaver usage type PI is optional. You can use it to transport Integration Builder objects. If you want to use CMS, you must perform some configuration steps first.

You can configure CMS for either repository objects or directory objects independently from each other.

The following sections only cover a basic and initial configuration of CMS for use with PI.

Do not use CMS and the Change and Transport System (CTS) at the same time, except when you migrate from CMS to CTS or vice versa.

Deploying the CMS Component

The CMS component is part of the SAP NetWeaver Development Infrastructure (DI). You find the sources for the DI deployment on SAP Service Marketplace at service.sap.com under SAP Support Portal ® Downloads ® SAP Software Distribution Centre ® Download ® Support Packages and Patches ® Entry by Application Group ® SAP NetWeaver ® SAP NETWEAVER ® SAP NETWEAVER 7.0 ® Entry by Component.

1. Choose Development Infrastructure.

2. Select the following components:

○ DI Change MGMT. Server 7.00

○ DI Component Build Server 7.00

○ DI Design Time Repository 7.00

3. Download the most current Software Component Archive (SCA) of each component.

4. Deploy the downloaded SCAs with your Software Deployment Manager (SDM).

Defining CMS Communication Users in PI (optional)

Different PI systems probably use different Integration Builder service users and passwords for communicating with CMS. If you want each of these systems to use the same service user name and password for CMS communication, but you do not want to modify each system’s service users, you can specify dedicated service users for CMS communication. To do so, use the following parameters in the exchange profile:

com.sap.aii.repository.serviceuser.name.cms

com.sap.aii.repository.serviceuser.pwd.cms

com.sap.aii.directory.serviceuser.name.cms

com.sap.aii.directory.serviceuser.pwd.cms

Do the following to avoid that passwords can be read as plain text in the exchange profile:

...

1. Export the exchange profile.

2. Change type from pwd to string in the file that contains the parameters

com.sap.aii.repository.serviceuser.pwd.cms

com.sap.aii.directory.serviceuser.pwd.cms

3. Import the modified file with option overwrite.

4. Delete the file that contains the readable passwords.

If you do not specify these parameters, the names and passwords of the Integration Builder service users (for example, PIDIRUSER and PIREPUSER) specified with the following parameters will be used:

com.sap.aii.repository.serviceuser.name

com.sap.aii.repository.serviceuser.pwd

com.sap.aii.directory.serviceuser.name

com.sap.aii.directory.serviceuser.pwd

Maintaining CMS Communication Users in CMS

To maintain the CMS communication user in CMS, perform the following steps:

...

1. Access the User Management area of the J2EE Engine of your CMS system and define the following roles and actions:

○ Role CMSDeveloper with actions CMS.Display and CMS.Export

○ Role CMSAdministrator with action CMS.Administrate

2. Choose the User Administration tab page of the J2EE Engine of your CMS system and define the dedicated service users for CMS communication you specified in the previous section as CMS users with role CMSDeveloper.

If you have not specified any dedicated service users for CMS communication, use the Integration Builder service users (for example, PIREPUSER and PIDIRUSER).

These service users are used by PI to send data to CMS. Therefore, their passwords must be the same in CMS and PI.

Make sure that the passwords you define for these two users in CMS match the passwords in your PI system. To do so, log on with both users to the J2EE login screen to make sure that the passwords are correct and that they do not need to be changed.

3. Define a CMS Administrator user with the role CMSAdministrator.

It is assumed that the CMS Administrator performs the customizing and the later transports. If you need to distribute administration tasks (for example, approval, transports) to different users, you have to define additional roles and users.

All users you created during the CMS setup must change their passwords at initial logon or must have set the flag No password change required.

Be aware that passwords are case sensitive.

Configuring a CMS Domain in CMS

...

Use the Landscape Configurator and configure

● the CMS domain

● the CMS server

● the System Landscape Directory (as External Server)

Perform the following steps

...

1. Configure a CMS domain for PI in CMS as described in Configuring a Domain.

2. Configure the CMS server as follows:

...

a. Insert the CMS URL (server name and port of the CMS system)

b. Create a CMS user. The user allows CMS to connect to the PI systems.

This user (for example LSADMIN) must be maintained as service user in all PI systems (including SLD) with the same password. It requires the following ABAP roles:

■ SAP_XI_CMS_SERV_USER

■ SAP_SLD_ORGANIZER

Either restart the J2EE Engine after you have added the roles to the CMS user or wait until the group assignment has been transferred to the J2EE Engine.

Within CMS, it is assumed that there is only one central SLD for all Integration Builder systems of the CMS domain. If more than one SLD is used by the Integration Builder systems, you should choose the master SLD for the domain definition.

A CMS track can only be defined if all software component versions relevant for the track are available within the SLD of the CMS domain.

If you have installed the SLD on a standalone J2EE Engine (and not on an AS-Java including PI), you have to perform the following steps:

...

1. Use the Visual Administrator and open the component sap-com/com.sap.lcr*sld

2. Add the CMS user (for example LSADMIN) to the security role LcrInstance WriterAll or to the group SAP_SLD_ORGANIZER.

Activating CMS in the Integration Builder

Set or enhance the following exchange profile parameters to activate CMS for use with the Integration Builder. The CMS transport option will then be displayed in the Integration Repository and in the Integration Directory.

Normally, these parameters must be set only in systems that are planned to be inserted into the development tracks. In all other systems, the transport should be organized by CMS.

Integration Repository

To be able to use CMS for repository objects, perform the following steps:

...

1. Ensure that the following parameters are available and set to true in your development and consolidation systems; do not change these parameters in production systems:

○ com.sap.aii.ibrep.core.cms.enableClTransport=true

Determines that the option of transporting change lists with CMS is provided on the user interface.

○ com.sap.aii.ibrep.core.cms.enableTransportWizard=true

Determines that the CMS transport is provided by the export wizard.

2. Add the following value to com.sap.aii.ib.client.properties:

○ com.sap.aii.ibrep.core.cms.*

Do not replace existing values here. Just add the new one.

Integration Directory

To be able to use CMS for directory objects; perform the following steps:

...

1. Ensure that the following parameter is available and set to true in your development system:

○ com.sap.aii.ibdir.core.cms.enableTransportWizard=true

Determines that the CMS transport is provided by the export wizard.

The transport of change lists with CMS is not supported for the Integration Directory.

2. Add the following value to com.sap.aii.ib.client.properties:

○ com.sap.aii.ibdir.core.cms.*

Do not replace existing values here. Just add the new one.

3. Ensure that the following parameter is available and set to true in your consolidation system:

○ com.sap.aii.ibdir.core.cms.enableClTransport=true

Determines that the option of transporting change lists with CMS is provided on the user interface.

Do not change any of these parameters in production systems.

Defining Development Tracks in CMS

For information on defining a development track for PI in CMS,

Specify the tracks as follows:

● For the Integration Repository, specify http://:/rep/

● For the Integration Directory, specify http://:/dir/

Configuring the Change and Transport System

2009-11-12T05:57:00.000-08:00

Use

Using the Change and Transport System (CTS) with SAP NetWeaver usage type PI is optional. You can use it to transport objects of the Enterprise Services Repository and the Integration Directory. If you want to use CTS, you must perform some configuration steps first.

You can configure CTS for either repository objects or directory objects independently from each other.

The following sections only cover a basic and initial configuration of CTS for use with PI.

More information: Transporting Objects from SAP NetWeaver PI by Using CTS.

Do not use CTS and the Change Management Service (CMS) at the same time, except when you migrate from CTS to CMS or vice versa.

More information about CMS: Configuring the Change Management Service.

Defining CTS Communication Users in PI (optional)

Different PI systems probably use different repository and directory service users and passwords for communicating with CTS. If you want each of these systems to use the same service user name and password for CTS communication, but you do not want to modify each system’s service users, you can specify dedicated service users for CTS communication. To do so, use the following parameters in the exchange profile:

com.sap.aii.repository.serviceuser.name.cms

com.sap.aii.repository.serviceuser.pwd.cms

com.sap.aii.directory.serviceuser.name.cms

com.sap.aii.directory.serviceuser.pwd.cms

These properties are used to change the user and password for CTS and CMS at the same time.

Do the following to avoid that passwords can be read as plain text in the exchange profile:

...

1. Export the exchange profile.

2. Change type from pwdto string in the file that contains the parameters

com.sap.aii.repository.serviceuser.pwd.cms

com.sap.aii.directory.serviceuser.pwd.cms

3. Import the modified file with option overwrite.

4. Delete the file that contains the readable passwords.

If you do not specify these parameters, the names and passwords of the repository and directory service users (for example, PIREPUSER and PIDIRUSER) specified with the following parameters will be used:

com.sap.aii.repository.serviceuser.name

com.sap.aii.repository.serviceuser.pwd

com.sap.aii.directory.serviceuser.name

com.sap.aii.directory.serviceuser.pwd

Configuring the CTS-Based Export

The following properties are used to configure the CTS-based export:

● com.sap.aii.[ibrep|ibdir].core.cts.enableClTransport = [true|false]:

This property specifies whether the CTS-based transport should be offered within the change lists area

● com.sap.aii.[ibrep|ibdir].core.cts.enableTransportWizard = [true|false]:

This property specifies whether the CTS-based transport should be offered within the Transport Wizard area

To activate one of these properties, add (not replace) the following string to the client property com.sap.aii.ib.client.properties:

● ‘, com.sap.aii.ibdir.core.cts.*, com.sap.aii.ibrep.core.cts.*’

com.sap.aii.ibrep.core.cts.enableTransportWizard=true

com.sap.aii.ibrep.core.cts.enableClTransport=true

com.sap.aii.ibdir.core.cts.enableClTransport=true

Transporting Objects from SAP NetWeaver XI by Using CTS

2009-11-12T05:56:00.000-08:00

Use

With the Change and Transport System (CTS) you can transport the following objects from SAP NetWeaver XI with the CTS transport request.

● Integration Repository design objects

● Integration Directory configuration objects

● ABAP Mappings

ABAP proxies for Integration Repository message interfaces are usually created in another SAP system that belongs to the Integration Repository. A transport in which message interfaces from the Integration Repository and corresponding ABAP proxies are to be transported in a transport request is therefore not possible with the procedure described here.

More information: Non-ABAP Transports in Change and Transport System (BC-CTS)

Prerequisites

There are two variants for SAP NetWeaver XI transports using CTS with the following system prerequisites:

● For systems based on SAP NetWeaver XI 7.0 (after SPS13), transports can only be executed using CTS without having to manually copy the transport files. This case is described in this documentation.

● For systems based on SAP NetWeaver 2004 (after SPS14), you can implement CTS on a separate system based on SAP NetWeaver 7.9 SPS12 as Transport Server and execute transports in this way. In this case, however, the export files must be copied manually into a transport server directory. Also, up to SAP NetWeaver 7.0 SPS11, you must define two transport routes.

○ One for ABAP objects of SAP NetWeaver XI system (SAP system in TMS: virtual system)

○ One for non-ABAP objects of SAP NetWeaver XI system (SAP system in TMS: non-ABAP system)

More information see the SAP Developer Network under https://www.sdn.sap.com/irj/sdn/xi ® How-to Guides ® End-to-End Process Integration ® Enabling Platform Interoperability ® How to Transport Repository and Directory Content Using CTS+ (SDN user required).

In addition the CTS transport must be activated for each SAP NetWeaver XI system that is to be connected with the CTS transport landscape.

Procedure

...

1. Consider in advance which systems are to be involved in your transport landscape for the transport of objects from SAP NetWeaver XI. A basic configuration is necessary for all these systems to be able to operate CTS with SAP NetWeaver XI tools.

2. You must configure source and target systems to automate the transfer of objects from SAP NetWeaver XI to CTS in source system export and to be able to control the import of objects into target systems using CTS.

3. To execute transports, use SAP NetWeaver XI tools for exporting objects in a transport request for CTS and CTS tools for performing transports.

Transports Using the Change and Transport System (New)

2009-11-12T05:53:00.000-08:00

Technical Data

Function is	New
For release	Software Component ● Component: SAP NetWeaver ● Release: 7.0 ● Support Package: 13
Assignment to application component	BC-CTS BC-XI
Country Setting	Valid for all countries

Use

In this Support Package and higher, you can include the following SAP NetWeaver XI objects in one Change and Transport System (CTS) transport request and transport them together:

● Integration Repository design objects

● Integration Directory configuration objects

● ABAP Mappings

This also enables you to use some of the advantages of CTS that were previously not supported when transporting SAP NetWeaver XI objects, for example the modeling of complex transport landscapes.

Concept of the Monitoring Architecture

2009-10-13T19:44:00.000-07:00

Purpose

The alerts are displayed in a tree structure in the alert monitor, and assigned a severity and a color (yellow for a warning, red for a problem). You can see the current status of your system and process alerts here. The alert monitor is based on the monitoring architecture, which was introduced in SAP R/3 4.0:

The CCMS monitoring architecture is not a monolithic monitoring and administration program. Rather, it offers a flexible framework into which extensive monitoring and administration functions can easily be added.

The elements of the monitoring architecture function largely independently of each other and can, particularly, be further developed and adjusted independently of each other.

· Data Supplier

A data supplier is a program that delivers data to the monitoring architecture. It belongs to one of the individual system components and creates monitoring objects that report values to the monitoring architecture. The monitoring architecture is delivered with the data suppliers for the most important components of your SAP system and its environment and can therefore be immediately used.

Data suppliers pass their information to the monitoring architecture. The monitoring architecture provides an infrastructure for gathering and managing system information. The monitoring architecture therefore constantly compares the values reported by the data suppliers for the monitored objects with threshold values and displays an alert if a value exceeds or falls below a threshold value.

· Data Consumers

A data consumer is a program that reads data from the monitoring architecture; it displays the information transferred to the monitoring architecture by the data suppliers. SAP delivers both the standard data consumer and other special monitors that all use the data delivered by the monitoring architecture.

· Monitoring Objects and Attributes

A monitoring object describes an object that is to be monitored. A monitoring attribute represents a type of information that is to be reported for a monitoring object. Monitoring objects include, for example, the CPU in your host system, the database, and SAP services, such as background processing. Monitoring attributes for a CPU object could be CPU utilization and the average CPU workload for the last five minutes.

The alert monitor also provides the administration methods that you need to monitor the system. In this way, you can set threshold values for alerts and add or adjust auto-reaction and analysis methods: if an alert is triggered, auto-reaction methods react automatically, and you can use an analysis method to investigate the cause of an alert without leaving the alert monitor. The monitoring architecture also contains tools for administering and archiving the alerts.

Data Transfer Using SAP XI

2009-10-13T19:42:00.000-07:00

Purpose

You can realize cross-system business processes using the SAP Exchange Infrastructure (SAP XI). Within the overall architecture of SAP NetWeaver, SAP XI performs the tasks of process integration.

The integration of SAP XI and SAP BW allows you to use SAP XI to send data from various sources to the delta queue of SAP BW.

The integration of SAP XI and SAP BW offers the following advantages:

· Central maintenance of message flow between logical systems of your system landscape.

· Options for transformation of message content between sender and recipient

Mappings help you to adapt values and structures of your message to the recipient. In this way, you can transfer different types of files to a SAP BW system using interface mapping. However, in any case, it is necessary to transform the data into a format that corresponds to the interface of the function module that is generated in SAP BW and used for data transfer. The function module contains a table parameter with a flat structure. This means that the data have to be transformed so that they fit to a flat structure in SAP BW.

· Using proxy communication with SAP BW

Proxies are executable interfaces generated in the application systems for communication with the SAP XI Integration Server. We recommend the use of proxies for communication with SAP BW because they guarantee Full Quality of Service (Exactly Once in Order). They also guarantee that the data is delivered only once and in the correct sequence. The SAP XI Integration Server keeps the serialization as it was established by the sender.

Prerequisites

You are familiar with the concept, architecture and functions of SAP XI. You can find more information under SAP Exchange Infrastructure in the NetWeaver documentation.

You have integrated SAP BW and SAP XI. You can find more information on this in the configuration guide of SAP XI on the SAP Service Marketplace at the Internet address service.sap.com/instguides.

Process

...

1. Create a XML DataSource in SAP BW based on a file-data source. When you generate the DataSource, an RFC-capable function module is generated for data transfer. You can find more information under XML DataSource and Creating XML DataSources.

2. Activate the data transfer to the delta queue of SAP BW by initializing the delta process. You can find more information under Activating Data Transfer to the Delta Queue.

3. You create an inbound and an outbound message interface in the Integration Repository of SAP XI.

You can find more information under Design of Interfaces and Proxy Generation in the documentation for SAP XI.

If there is already an interface for data exchange in a system, you can import the interface description into the Integration Repository. You can find more information under Connection with Adapters and Imported Interfaces in the documentation for SAP XI.

The interface description in SAP BW is available in the form of the RFC-capable function module for the inbound message interface that was generated for your DataSource. To create the inbound message interface, you can import the function module into the SAP XI Integration Repository. You can find additional information under Import of Idocs and RFCs.

¡ If you are using an existing SAP XI scenario, the outbound message interface is already in the Integration Repository. Then you only need to create the inbound message interface.

¡ If you want to implement a new scenario, create an outbound message interface in addition to the inbound message interface.

4. You implement proxy generation for your inbound message interface in SAP BW.

An ABAP object interface (inbound or server proxy) is generated in SAP BW for the inbound message interface.

You can find more information under ABAP Proxy Generation in the documentation for SAP XI.

We recommend proxy communication with SAP BW because it guarantees Full Quality of Service (Exactly Once in Order).

5. You implement the generated ABAP object interface using an ABAP object class in SAP BW for recipient processing.

You can find more information under ABAP Proxy Objects in the documentation for SAP XI.

The proxy runtime calls this processing automatically after receiving the appropriate message.

The document How to…Integrate BW to XI describes such an implementation. You can find the document on the SAP Service Marketplace at the Internet address service.sap.com/bw ® Services & Implementation ® HOW TO... Guides ® Guide List SAP BW 3.x.

6. If you have newly created the outbound message interface, you implement the data transfer according to your application case.

7. You implement the configurations in the Integration Directory of SAP XI that are relevant for message exchange. At the time of configuration, you set up the cross-system process for a concrete system landscape. The relevant objects are structure, organized and stored in the Integration Directory in the form of configuration objects.

You can find more information about the steps that you perform in SAP XI under Configuration and Design in the SAP XI documentation.

Result

You can now send data to the Integration Server of SAP XI, which transfers this data to SAP BW at runtime using proxy communication . In SAP BW, the data is written to the delta queue. From there, you can collect the data using the usual staging methods for deltas in SAP BW and then post it to the data targets.

The following graphic illustrates how the interface-based processing of messages works:

Using SAP EarlyWatch Alert

2009-10-13T19:39:00.000-07:00

This process identifies potential problems early, avoids bottlenecks and monitors the performance of your systems. SAP EarlyWatch Alert monitors your most important business processes and systems.

The SAP EarlyWatch Alert in the SAP Solution Manager is a service provided by SAP.

Prerequisites

You have:

● set up RFC connections between your satellite systems and the SAP Solution Manager system, and an RFC connection between the SAP Solution Manager and the SAP Service Marketplace.

● checked the availability of the required tools for the SAP service session (ST-A/PI add-on), with the report RTCCTOOL.

● activated Alert Monitoring for all SAP satellite systems, and the central SAP Solution Manager of your solution, and set up the Automatic Session Manager (ASM) in the Service Data Control Center (SDCC) of your satellite systems (SAP note 91488).

● set up your systems in a solution landscape in the SAP Solution Manager.

Process Flow

...

1. You configure the SAP EarlyWatch Alert scheduling in the SAP Solution Manager.

You have:

○ scheduled the service sessions for your solution, in the SAP Solution Manager Solution Directory

The default value is Mondays. You should retain this value.

○ activated or deactivated the download of SAP EarlyWatch Alert data from the SAP Solution Data Manager for your solution systems.

2. You have activated the SAP EarlyWatch Alert monitoring for your solution systems.

3. Data collectors in the satellite systems aggregate analysis-relevant system and performance data weekly.

4. The system downloads this data to the SAP Solution Manager with the SAP Solution Data Manager (SDCCN).

5. The job SM:EXEC SERVICES triggers the processing of the data in a system session.

6. Further processing is in accordance with the following rules, which SAP has specified in the system:

○ Red status: Critical/Error

i. Analyze the report. The SAP Solution Manager system sends the data to SAP.

ii. SAP Support analyzes the problems and contacts you if necessary, to discuss further action.

iii. If you consider the alert to be critical, discuss further action with SAP.

iv. Take the agreed action.

○ Yellow status: Critical/Warning

...

i. Analyze the report.

○ Gray status: Status unknown

...

i. Check why the system status could not be determined.

○ Green status: No error

The system sends initial and monthly sessions to SAP via the SAP Service Marketplace, regardless of the analysis of the weekly SAP EarlyWatch Alert reports.

Authorization For Web Services and Security

2009-09-23T00:00:00.000-07:00

Standard Roles

● SAP_BC_WEBSERVICE_SERVICE_USER

Role for background users of the Web service runtime

● SAP_BC_WEBSERVICE_ADMIN_TEC

Role for technical administrator of Web services

Monitoring sequences, messages, logging, tracing

Monitoring of payload for component SAP_BASIS

Administration of tracing and logging, RFC

Defining, executing Web Services

Administration of the Internet Communication Framework

Administration of the RFC destination

Administration of the Task Watcher and the Event Handler

● SAP_BC_WEBSERVICE_ADMIN_BIZ

Roles for the Business Administrator

● SAP_BC_WEBSERVICE_CONSUMER

Web Service user

● SAP_BC_WEBSERVICE_OBSERVER

User role for viewing all information on Web Services

● SAP_BC_WEBSERVICE_DEBUGGER

With debugging authorization

● SAP_BC_WEBSERVICE_ADMIN

Administration authorizations for Web Services in AS ABAP, out of date, but still valid

Assigning Authorizations to Users

To assign such authorizations for special Web services, proceed as follows:

...

1. In the role maintenance transaction (transaction PFCG), enter the name of a role, and then choose Change.

2. Under the Menu tab, choose Other.

3. Choose the radio button Authorization Defaults for Services.

4. Enter a name for the service. In the Type of Ext.Service field, choose the WS value. In the Service field, choose the required Web service.

5. Save your entry.

SOA Manager

2009-09-22T23:58:00.000-07:00

You can use the SOA Manager to administer and configure service providers and consumer proxies for a local system.

Communication Between a Consumer Proxy and a Provider Proxy

Communication between the service consumer and the service is established between the consumer proxy’s logical port the provider proxy’s endpoint. To access a particular service endpoint, a service consumer with a particular runtime configuration sends a call using a logical port.

The logical port of the service consumer contains a reference to the unique address (URL) of the service’s endpoint on the provider system. The logical port also contains the authorization needed to call the service methods.

Note

A logical port can send a call to only one service endpoint. However, a service endpoint can be called through more than one logical port.

End of the note.

Prerequisites

The service and proxy definitions that you want to configure are available as development objects in the back-end system.
You have Administrator authorization.
For more information, see: Authorizations

Procedure

To set up the SOA Manager for local access, you do not need to perform any special steps.

To start the SOA Manager, use the transaction code SOAMANAGER:

Note

To work with the central SAP NetWeaver Administrator from within the SOA Manager, you first need to assign a host and a port.

Go to the Technical Configuration tab.
Choose System Global Settings.

An overview if configuration information is displayed.
Go to the Central WS Administration Access tab.
Choose Edit / Display.
Specify the host of the central NetWeaver Administrator and the HTTP port number used by the NetWeaver Administrator.
Save.

SOAP Framework

2009-09-22T23:42:00.000-07:00

Purpose

The SOAP Framework enables you to create and use Web services based on the SOAP protocol.

The development of the Web Service Framework has resulted in significant changes and enhancements being made to Web Services for ABAP between SAP Web AS Release 620 and Release 640. Since these enhancements could not be realized with the existing SOAP architecture, SOAP Runtime 620 was replaced by the SOAP Framework from Release 640.

If you used SOAP Runtime for Web services in 620, we recommend that you use the Web Service Framework to create these services again. This will enable you to implement the enhanced and easier to use functions available in the Web Service Framework.

Features

The following Web service functions have been added in Release 640:

· You can create Web services that are based on function modules, function module groups, BAPIs, and XI messages.

· You can generate a proxy for each Web service.

· You can use new authorizations to activate and administer Web services:

¡ Role = SAP_BC_WEBSERVICE_ADMIN

· Each Web service is represented as a separate ICF service in the Internet Communication Framework, with the accompanying wide range of options (authorizations, logon checks, and so on).

· You can publish all Web services in a shared directory (UDDI).

· You can use transaction WSADMIN for the easy handling of all administration tasks for Web services.

Restrictions

The following constraints apply when you use SOAP Framework 640:

· The SOAP Actor concept is not supported. The receiver side always adopts the role of the ultimate receiver, This means that no intermediaries can be realized in the context of SOAP.

· The optional use of SOAP encoding (section 5.1 of the SOAP specification) is not available. Although the representation of data in the SOAP Runtime is very similar to SOAP encoding, some of the required points, such as support for array types, are missing.

· No attachments: The specification SOAP with Attachments for transporting SOAP calls that use MIME documents with attached binary elements (such as JPEG pictures) is not supported.

· Only HTTP transport: Only HTTP (and HTTPs) is available for SOAP transport binding. Other protocols, such as SMTP, are not supported.

Creating Web Services

In Release 620, the following steps were required to create a SOAP-based Web service and an accompanying Web Service Description (WSD):

Create a function module that can run remotely.
Start the Web service browser.
Find the function module and generate a WSDL, or
Put function modules into groups and generate a common WSDL.

In the Web Service Framework, you can create Web services manually or by using an assistant:

· Manual:

1. Create a virtual interface for RFCs, function groups, or BAPIs (transaction SE80).

You can set name handling to uppercase or mixed case. Check which applies to you.

2. Create a Web service definition (transaction SE80).

3. Activate and configure a Web service based on a WSD (transaction WSCONFIG).

Importing the SAP Basis Plug-In

2009-07-12T08:52:00.000-07:00

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.

For more information, see SAP note 655941.

Setting Up the Repository Manager for BW Documents and BW Metadata

2009-07-12T08:50:00.000-07:00

Documents and metadata created in SAP BW (especially documentation for metadata) can be integrated into the Knowledge Manager of the SAP Enterprise Portal using the Repository Manager. There they are displayed together with other documents for the end user in a directory structure.

The documents are located in the BW system. The Repository Managers enable access to these documents within the portal using Knowledge Management. The variegated functions of Knowledge Management can be applied to these documents (feedback, rating, text search and so on).

The Repository Managers for BW documents and BW metadata are especially useful for two scenarios:

· BEx Web Application as a Link in Knowledge Management .

· BW documents and BW metadata.

Note that Repository Managers cannot be used for navigating in Knowledge Management unconditionally. Because of the flat folder hierarchy, a directory can contain a very large number of objects (for example, all queries for a system) and displaying the documents in a KM navigation iView can lead to problems in terms of performance.

For more current information, see SAP note 702350.

Procedure

1. Log on to the portal.

2. Start the iView System Administration ® System Configuration ® Knowledge Management ® Content Management.

3. Choose Content Management ® Repository Managers.

4. Under Classes, choose BW Document Repository.

5. Create a new instance of the BW Document Repository and choose New.

6. Enter settings as required. For more information on what the individual parameters mean, see Repository Manager for BW Documents.

7. Choose OK to save the settings.

8. Under Classes, choose BW Metadata Repository.

9. Create a new instance of the BW Metadata Repository and choose New.

10. Enter settings as required. For more information on what the individual parameters mean, see Repository Manager for BW Metadata.

11. Choose OK to save the settings.

Check

Start the iView Content Administration ® KM Content. Open the Knowledge Management folder for the BW documents and the folder for the BW metadata. The names of the folders correspond to the prefixes entered above.

Exporting the Portal Certificate in BW

2009-07-12T08:49:00.000-07:00

The portal certificate is needed for displaying content from SAP BW in the portal and has to be imported in the BW system (see Importing Portal Certificate).

Procedure

To export the portal certificate from the J2EE engine, follow these steps:

1. Start the SAP J2EE Engine Administrator with \admin\go.bat.

2. Connect to the portal server.

3. Choose /Server<…>/Services/Key storage from the tree.

4. Select the view TicketKeystore under Views.

5. If the SAPLogonTicketKeypair-cert is not available under Entries, generate a portal certificate using the following steps. Otherwise you can continue with the export under step 9.

6. Under Entry, choose Create.

Enter the following values in Key and Certificate Generation:

¡ Subject properties: Every key has to have a value under Value.

The value CN=Common Name is displayed as the owner in transaction STRUSTSSO2 and serves to identify the certificate. SAP recommends that you use from the portal server.

¡ Entry name: SAPLogonTicketKeypair (the entry SAPLogonTicketKeypair-cert is generated automatically)

¡ Store certificate: X

¡ Algorithm: DSA

7. Choose Generate to generate the certificate.

8. Highlight SAPLogonTicketKeypair-cert under Entries.

9. Under Entry, choose Export.

10. Export the portal certificate as _certificate.crt in file format X.509 Certificate (*.crt).

Result

The exported portal certificate can then be imported into the BW system. For more information, see Importing the Portal Certificate.

If you want to connect multiple portals with the same system ID to a BW system, you have to maintain the login.ticket_client parameter:

Configuring User Management in BW

2009-07-12T08:48:00.000-07:00

You need to make several settings in user management of the portal to enable single sign-on between SAP BW 3.5 and SAP EP 6.0.

The SAP reference system is required for communication from the BEx tools in the portal. Maintenance of a SAP reference system is only necessary when the technical user names in SAP BW and SAP EP are different and user assignment is necessary. You can makes sure that the user names are identical using the central user management. For more information on the SAP EP side of this, see User Management Engine and UME Data Sources. On the SAP BW side, you can find more information about centralized user management at Directory Services (BC-SEC-DIR).

For more information, see Security.

Procedure

1. Log on to the portal.

2. Start the iView System Administration ® System Configuration ® Configuration for User Management.

3. Choose the Security Settings tab page.

4. Under SAP reference system, enter the standard system alias of the BW system (see Creating a BW System in the Portal).

5. Save your entries.

Only one system can be specified as the SAP reference system. The SAP reference system does not have to be the BW system. However, if it is not the BW system, the technical user name of the BW system has to be identical with the technical user name of the SAP reference system.

If you want to connect multiple portals with the same system ID to a BW system, you have to maintain the login.ticket_client parameter:

...

1. Log on to the portal.

2. Start the iView System Administration ® System Configuration ® Configuration for User Management.

3. Select the Direct Editing tab page.

4. Insert the following line: login.ticket_client=

5. Save your entries.

You can select any value between 000 and 999 as the . The client is necessary if several portals with identical portal SIDs are connected. The client has to be entered when you import the portal certificate into the BW system on future occasions.

After making changes to user management in SAP EP, you have to restart the J2EE Engine with SAP EP.

Creating BW Systems in the Portal

2009-07-12T08:46:00.000-07:00

The BW system must be set up in the portal so that content from SAP BW can be displayed in it. The system is entered into the Portal System Landscape Directory.

This setting is required for all integration scenarios (see Integration from the Viewpoint of Administrators and Authors).

Procedure

1. Log on to the portal.

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

The systems are maintained with the Portal Content Studio. For more information about using the Portal Content Studio, see Integration Using the Portal Content Studio.

3. Choose New ® System in the context menu of the Portal Catalog.

4. Depending on the system landscape, choose either the R/3 with Load Balancing (SAP_R3_LoadBalancing) or Dedicated Application Server for R/3-System (SAP_R3_Dedicated) as a template.

5. Maintain the most important properties with the property category Display All.

¡ Logon method: SAPLOGONTICKET or UIDPW

¡ Type of user assignment: admin,user

¡ Logical system name: CLNT

This is the recommended convention for logical system names, consisting of the system ID and the client.

¡ Remote host type: 3

¡ SAP client:

¡ SAP system ID (SID) (R/3 name):

¡ System type: SAP_BW

¡ System name: CLNT

¡ WAS description:

¡ WAS host name: :

¡ WAS path: /sap/bw/bex

¡ WAS protocol: http or https

All system entries refer to the BW system.

You can determine the WAS hostname, WAS path and WAS protocol settings using function module RSBB_URL_PREFIX_GET (transaction code SE37).

To use Drag&Relate, maintain the following properties:

¡ Admin User-ID (DQE):

¡ Admin password (DQE):

The Distributed Query Engine (DQE) executes the requests to the BW system with the Admin User above.

If you are using R/3 with Load Balancing (SAP_R3_LoadBalancing), you must also maintain the following properties:

¡ Group:

¡ Message server:

¡ Server port:

The server port is frequently maintained by system administrators on the local PC in the c:\windows\system32\drivers\etc\services file. The server port of the system is entered into the file as sapms.

If you are using a Dedicated Application Server for R/3 System (SAP_R3_Dedicated), you must also maintain the following properties:

¡ Application host:

¡ Gateway host:

¡ Gateway service:

¡ SAP system number:

The report Maintaining Settings for Integration into SAP Enterprise Portal (RSPOR_SETUP) determines most of the mandatory values for the above properties automatically.

6. Maintain an alias for the system in the System Aliases view.

A system alias in the format CLNT must exist, where is the system ID and is the client for the system. CLNT is predefined. In addition to the system alias in the format above, you can also maintain other system aliases.

During integration of SAP BW 3.5 and SAP EP 6.0, the system alias in SAP 3.5 must be entered into the table Connected Portals (see Maintaining Portal Server Settings for EP 6.0).

In order to use the example role Business , an alias must be maintained in SAP_BW. Multiple system aliases can be defined for a BW system.

7. Save your entries.

Check

With the Connection Tests you can check the settings above. However, only the SAP Web AS Connection and the Connection Test for Connectors.

Importing the BW Certificate

2009-07-12T08:45:00.002-07:00

The BW certificate must be imported into the portal so that content from the portal can be displayed in SAP BW, such as the portal roles in the BEx Web Application Designer, for example.

Prerequisites

Before the BW certificate can be imported into the portal, it has to be exported from the BW system. For more information, see Exporting the BW Certificate.

Procedure

Follow these steps to import the BW certificate into the J2EE engine:

1. Start the SAP J2EE Engine Administrator with %INSTALLATION_ROOT%\admin\go.

2. Connect to the portal server.

3. In the tree, choose /Server<…>/Services/Key Storage.

4. Select the view TicketKeystore under Views.

5. Under Entry, click Load.

6. Open the file _certificate.crt.

Perform the following steps so that the SAP J2EE Engine accepts the SAP Logon Tickets from the BW system as an external system.

...

1. Start the SAP J2EE Engine Administrator with %INSTALLATION_ROOT%\admin\go.

2. Connect to the portal server.

3. In the tree, choose /Server<…>/Services/Security Provider.

4. Choose Ticket as Component.

5. Choose the Authentication tab page.

6. Change the options for the com.sap.security.core.server.jaas.EvaluateTicketLoginModule parameter and insert the following values:

○ trustedsys=, (for example, BWP, 000)

○ trustediss= (for example, CN= BWP, OU=I0020114583, OU=SAP Web AS, O=SAP Trust Community, C=DE)

○ trusteddn= (for example, CN= BWP, OU=I0020114583, OU=SAP Web AS, O=SAP Trust Community, C=DE)

is a number for all three entries, but must be incremented by one for every external system.

and are the system ID and the client of the BW system.

and correspond to the Own Certificate value in the transaction Trust Manager for Single Sign-On with Logon Ticket (transaction code STRUSTSSO2). The value trustediss corresponds to the value Issuer; the value trusteddn corresponds to the value Owner.

As of SAP BW 3.5 SP 11 in SAP NetWeaver SP Stack 11, you have to perform the following steps to use the Send SAP Logon Ticket option (see Creating an RFC Destination for SAP EP 6.0):

...

1. Start the SAP J2EE Engine Administrator with %INSTALLATION_ROOT%\admin\go.

2. Connect to the portal server.

3. In the tree, choose /Server<…>/Services/Security Provider.

4. Choose evaluate_assertion_ticket as Component.

5. Choose the Authentication tab page.

6. Change the options for the com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule parameter and insert the following values:

○ trustedsys=, (for example, BWP, 000)

○ trustediss= (for example, CN= BWP, OU=I0020114583, OU=SAP Web AS, O=SAP Trust Community, C=DE)

○ trusteddn= (for example, CN= BWP, OU=I0020114583, OU=SAP Web AS, O=SAP Trust Community, C=DE)

The values correspond to the above values under Component Ticket.

Exporting the BW Certificate

2009-07-12T08:45:00.001-07:00

The BW certificate must be generated in and exported from the BW system so that it can be imported into the portal afterwards. The BW certificate is needed in the portal so that portal contents can be displayed in SAP BW.

The various scenarios are described in detail from a security viewpoint under Security.

Prerequisites

You have set up Single Sign-On. For more information, see Maintaining Single Sign-On.

Procedure

1. Start the transaction Trust Manager for Single Sign-On with Logon Ticket (transaction STRUSTSSO2).

2. Choose your certificate. Your own certificate is located in the System PSE area in the Own Certificate field. When you double click on the field value, the certificate is displayed in the Certificate area. You can proceed with step 3 once the certificate appears in that area.

If your own certificate is not available, generate a certificate using create in the context menu of system PSE and distribute it using PSE ® Distribute All to all application servers for the BW system. There may be a time delay when distributing the certificate. If necessary, check whether the certificate has been successfully distributed.

3. In the menu, choose Certificate ® Export.

4. Enter the file path _certificate.crt ( is the system ID of the BW system).

5. Choose Binary as the file format.

The file _certificate.crt is used for the step Import BW Certificate in the settings in SAP EP 6.0.

Check

You can look at the _certificate.crt file using Windows Explorer.

BW Security

2009-07-12T08:43:00.000-07:00

In information broadcasting and integration of SAP BW and SAP EP you take the following scenarios into consideration in regard to security.

· Calling BEx Web Applications from the Enterprise Portal

· Information Broadcasting as Background Processing

· Information Broadcasting in the Web

· Publishing to the Enterprise Portal

You need special authorizations to be able to use information broadcasting. System administrators need authorization object S_RS_ADMWB with the field RSADMWBOBJ = BR_SETTING. Users that precalculate business intelligence content and would like to schedule things require the authorization object S_RS_BCS. For more information, see Overview: Authorization Objects and Authorizations for Working with a Query.

You can also use single sign-on for integration of SAP EP and SAP BW. BEx Web Applications are usually called from the Enterprise Portal. SAP EP supports and issues SAP logon tickets. Due to the close integration of SAP BW 3.5 and SAP EP 6.0, users can also start in SAP BW, where single sign-on is also supported. The following graphic illustrates the interaction between SAP BW and SAP EP in terms of single sign-on:

Maintaining Single Sign-On in BW

2009-07-12T08:41:00.000-07:00

You need Single Sign-On tickets (SSO tickets) that are generated in the BW system to include portal content in the BEx Web Application Designer. In order to call BEx Web Applications in the portal, the BW system has to accept SSO tickets from the portal.

This setting is required for all integration scenarios . The various scenarios are described in detail from a security viewpoint under Security.

Procedure

1. Install SAPSECULIB on each application server of the BW system to use Single Sign-On (SSO).

It is not necessary to install the SSO software on the client PC.

2. Set the following profile parameter using the Maintaining Profiles transaction (transaction code RZ10):

¡ login/create_sso2_ticket=2

The profile parameter generates SSO tickets in the BW system that are required for communication from SAP BW 3.5 to SAP EP 6.0. The value 2 means that the certificate is self-signed.

¡ login/accept_sso2_ticket=1

The profile parameter means that the BW system accepts SSO tickets from other systems (for example, from portals) if the certificate has been imported.

For more information, SAP Note 354819.

Check

A check is only possible after all security settings have been completed.

Maintain Portal Server Settings for SAP EP 6.0

2009-07-12T08:40:00.000-07:00

In the Maintain Portal Server Settings for EP 6.0 Customizing activity, you have to make a number of settings in the Connected Portals table (technical name: RSPOR_T_PORTAL).

The Connected Portals table is completely buffered. After maintaining this table, you need to initialize the table buffer on the SAP BW application servers. This can be done in the SAP GUI with /$tab.

You need these settings for all integration scenarios.

Procedure

...

1. Start the transaction Table View Maintenance (transaction code SM30).

2. Enter RSPOR_T_PORTAL as the table.

3. Choose Maintain.

4. To create a new entry, choose New Entries.

5. Maintain the connected portal:

¡ RFC destination:

¡ Name of the system: (see Creating BW Systems in the Portal )

¡ Default:

¡ Portal URL Prefix: , for example, http://:

¡ RM prefix for BW metadata: , for example /bw_metadata

¡ KM Service URL:

6. Save your entries.

Settings for the Connected Portal

RFC Destination and Name of the System

Maintenance of a RFC destination using transaction SM59 is necessary for integration between SAP BW 3.5 and SAP EP 6.0. Enter this RFC destination into the Connected Portals table (RSPOR_T_PORTAL) so that the RFC destination is recognized as a connected portal.

Communication between the BW system and the SAP Enterprise Portal takes place through the RFC destination. An RFC destination corresponds to a connected portal. The Name of the System field corresponds to the alias on the BW system. The alias is defined in SAP Enterprise Portal 6.0. The iViews in the Enterprise Portal can be clearly assigned to a BW system using the name of the system.

Check the information under Importing a Portal Certificate and Exporting a Portal Certificate in regard to multiple portals.

Settings for Information Broadcasting

In addition to the RFC destination and the name of the system, you can also maintain the fields Default, URL Prefix, KM Metad.RM Prefix and KM Service URL in the Connected Portals table (RSPOR_T_PORTAL). These fields have to be maintained for Information Broadcasting. The BEX Broadcaster needs this information in order to be able to provide input help for folders in Knowledge Management . To store online links to queries or BEx Web applications in Knowledge Management, the prefix for the Repository Manager for BW metadata is needed. These fields are not required for other scenarios.

You need to select exactly one portal in the table to designate it as the standard portal. The designated portal is used for selecting a folder in the BEx Broadcaster.

You can overwrite the standard portal with the parameter ID RSPOR_DEFAULT_PORTAL (SET/GET-Parameter).

...

1. In the SAP GUI, choose System ® User Profile ® Own Data in the menu.

2. In the Parameter tab page, enter the parameter ID RSPOR_DEFAULT_PORTAL and the appropriate parameter value. The parameter value is the name of the RFC destination from the Connected Portals table.

The URL Prefix field contains the URL to the portal, including protocol, host name and port.

Maintain the Repository Manager prefix for BW metadata in the KM Metad. field. RM Prefix. This prefix is determined while you are setting up the Repository Manager.

You can use another service for input help for folders in Knowledge Management as needed with the KM Service URL. At the moment there is only one service, so this field remains empty.

If you do not maintain the table, the associated menu entries for publishing in the BEx Web Application Designer and BEx Query Designer will be deactivated.

Check

Start the BEx Web Application Designer. In the Publish menu, the entry with Enterprise Portal 6.0 is activated.

Creating an RFC Destination for SAP EP 6.0

2009-07-12T08:35:00.000-07:00

Maintenance of a RFC destination using Display and Maintenance of RFC Destinations (transaction SM59) is necessary for integration between SAP BW 3.5 and SAP EP 6.0.

This setting is required for all integration scenarios .

Prerequisites

Before you create an RFC destination in the BW system you have to Create an RFC Destination in the J2EE Engine.

Procedure

Using the Maintaining Portal Server Settings for EP 6.0 Customizing activity, you can enter this RFC destination into the RSPOR_T_PORTAL table so that the BW system recognizes the RFC destination as a connected portal. Communication between the BW system and the SAP Enterprise Portal takes place through the RFC destination.

1. Start the transaction Display and Maintenance of RFC Destinations (transaction code SM59).

2. Choose Create.

3. Maintain the RFC destination:

¡ RFC destination:

¡ Connection type: T for TCP/IP connection

¡ Description:

¡ Technical settings

§ Activation type: Registered server program

§ Program ID: _PORTAL_

§ Gateway host:

§ Gateway service: sapgw

¡ Logon/security

§ Send SAP logon ticket: Activate

4. Save your entries.

Settings for the RFC Destination

Name of the RFC destination

The name of the RFC destination for an Enterprise Portal should be selected carefully.

The name of the RFC destination is saved in the Information Broadcasting settings. Saving is necessary to be able to uniquely identify the used, connected Enterprise Portal for integration with Knowledge Management.

The broadcast settings can be transported between BW systems. For this reason, the name of the RFC destination should be identical in the source and target systems.

The name recommended by SAP for the RFC destination to the connected portal is SAP_EP.

Connection type

Select a connection type T for TCP/IP Connection.

Description of the RFC destination

You can maintain the description of the RFC destination language dependently. The language-dependent description is used when publishing iViews from the BEx Web Application Designer and BEx Query Designer if multiple portals are connected to the BW system.

Activation type

Select Registered Server Program as the activation type.

Registered server program

The server program is set up under the program ID on the J2EE engine. The recommended naming convention is _PORTAL. You can find more information under Creating RFC Destinations in the J2EE Engine.

Gateway options

Under Gateway Options, enter the gateway host and the gateway service with which the J2EE engine communications with the BW system. The gateway host, an application server for the BW system, and the gateway service can be comprised generically of sapgw. You can determine the parameters for the gateway with the Gateway Monitor transaction (transaction code SMGW) using Goto ® Parameter ® Display.

Send SAP logon ticket

The option Send SAP Logon Ticket will be possible from SAP BW 3.5 SP 11 with SAP NetWeaver 04 SP Stack 11. You can avoid the use of the portal user bw_service by using this option. For more information.

If the RFC destination is also set up on the page for the J2EE engine, you can check the connection with the Connection button.

Creating RFC Destinations in the J2EE Engine

2009-07-12T08:34:00.000-07:00

The RFC destination in the J2EE engine is an RFC server that is called by the BW system as an RFC client. The connection is necessary to display portal content in SAP BW. The RFC destination is then used when creating the RFC Destination for SAP EP 6.0.

You need this setting for all integration scenarios.

Procedure

Follow these steps to create an RFC destination in the J2EE engine:

1. Start the SAP J2EE Engine Administrator with \admin\go

2. Connect to the Portal Server.

3. In the tree, select /Server<…>/Services/Jco RFC Provider.

4. Maintain an RFC destination:

¡ Program ID: _PORTAL_ (see Creating an RFC Destination for SAP EP 6.0 in the Registered Server Program section)

¡ Gateway host: (see Creating an RFC Destination for SAP EP 6.0 in the Gateway Options section)

¡ Gateway service: sapgw

¡ Number of processes (1..20): 20

¡ Application server host: see Gateway host

¡ System number:

¡ Client:

¡ Language: EN

¡ User: (User in the BW system)

¡ Password:

5. Transfer the RFC destination to the available RFC destinations with the Set button.

6. Start the RFC server with the Start button.

Check

The RFC destination can be checked with the Display and Maintenance of RFC Destinations (transaction SM59) (see Creating an RFC Destination for SAP EP 6.0 in the Checking section).

What's New in BI with SAP NetWeaver 7.0

2009-07-08T06:35:00.000-07:00

This list provides an overview of the changes made to the BI documentation since SAP NetWeaver '04.

Ramp-Up Start (Support Package Stack 04)

Data Warehousing

New Features and Changes	Link to Documentation
Changed terminology	Release note: Terminology in Warehouse Management (Changed)
The Data Warehousing Workbench replaces the Administrator Workbench.	Data Warehousing Workbench
The following functional enhancements have been made for the DataStore object: · New type of DataStore object · Enhanced settings for performance optimization of DataStore objects	Write-Optimized DataStore Objects Performance Optimization for DataStore Objects
Functional enhancements have been made in the definition of InfoSets.	InfoSets Special Features of InfoCubes in InfoSets Temporal Join
The transformation replaces the transfer and update rules.	Transformation
New database functions support you in optimizing performance.	Partitioning Clustering Multidimensional Clustering
Functional changes have been made to the documents.	Documents
New authorization objects have been added.	Release note: Authorization Objects and Role Templates (Changed) Overview: Authorization Objects
Remodeling of InfoProviders supports you in information lifecycle management.	Remodeling InfoProviders
Repartitioning and reclustering support you in information lifecycle management.	Repartitioning Reclustering
The following changes and new features apply to the DataSource: There is a new object concept for the DataSource. Options for direct access to data have been enhanced. From BI, remote activation of DataSources is possible in SAP source systems.	DataSource (New Object Concept) Direct Access to DataSources (Enhanced) Remote Activation of DataSources (New)
The data transfer process distributes the data within BI. It replaces the InfoPackage for updating data from the PSA, and the Data Mart Interface for updating data from one InfoProvider to another.	Data Transfer Process
Functional changes have been made to the Persistent Staging Area (PSA).	Persistent Staging Area (Changed) Persistent Staging Area
The InfoPackage is only used for loading into the PSA when the new concepts (transformation, DataSource, data transfer process) are used.	InfoPackage (Changed)
BI supports real-time data acquisition.	Real-Time Data Acquisition
The process chains have been functionally enhanced.	Process Chain
BI provides functions for background management of BI processes.	BI Background Management
BI provides functions for archiving request administration data.	Archiving Request Administration Data

BI Platform

New Features and Changes	Link to Documentation
Time-dependent hierarchies can be analyzed temporally in a query with a key date derivation type.	Time-Dependent Hierarchies
In addition to relational aggregates, the BI accelerator allows you to improve the performance of BI queries when reading data from an InfoCube.	Aggregates and BI Accelerator
Quantity conversion enables key figures with different units to be converted into a uniform unit of measure.	Quantity Conversion
There is a new concept for analysis authorizations (previously: reporting authorizations).	Analysis Authorizations

Support Package Stack 05

SAP NetWeaver 7.0 SP Stack 05 contains the following new features and enhancements:

BI Suite: Business Explorer

New Features and Changes

Link to Documentation

The Business Explorer provides a newly implemented version of the tools. There is also a new tool, the BEx Report Designer. Within enterprise reporting you can use this tool to create formatted reports that are optimized for presentation and printing.

BI Suite: Business Explorer

Enterprise Reporting

BI Platform

New Features and Changes

Link to Documentation

Business planning with SAP NetWeaver Business Intelligence provides a complete solution that is integrated into the BI system and can be used to create and use planning scenarios and other applications. This solution is called BI Integrated Planning.

This planning tool uses the same data basis as BW-BPS and can run in parallel in a system.

Business Planning

You use the TREX search engine to search for BI metadata in different modes: the simple search is a pure text search; the advanced search provides a function for searching by attribute and a function for searching according to specific restrictions, as well as a full-text search.

On the Metadata Indexing tab page for the BI metadata search in the Administration functional area of the Data Warehousing Workbench, you can use Metadata Search/ Documents to check the required settings and to index metadata.

BI Metadata Search

Tab Page: Metadata Indexing

Support Package Stack 06

SAP NetWeaver 7.0 SP Stack 06 contains the following new features and enhancements:

Data Warehousing

New Features and Changes	Link to Documentation
The open hub destination now has its own maintenance interface and can be connected to the data transfer process as an independent object.	Open Hub Destination
A unified maintenance interface for DataSources makes it easier to create and change DataSources in BI. You can create and update DataSources for file source systems, UD Connect, DB Connect, and Web services here. You can display DataSources from SAP source systems and define various properties for the DataSources. Emulation supports the display of 3.x DataSources in DataSource maintenance and the use of the 3.x DataSource in a data flow with transformations. The migration of 3.x DataSources supports the conversion of old data flows to a data flow with transformation and data transfer processes. This allows you to use real-time data acquisition, for example.	DataSource
The BI accelerator monitor is used for the technical administration and maintenance of the BI accelerator. It provides an overview of the current status of the BI accelerator.	Using the BI Accelerator Monitor
When errors occur it can be useful to record system responses in the form of traces for the BI accelerator. SAP support has tools to evaluate these traces.	Traces for BI Accelerator
In the Translation functional area of the Data Warehousing Workbench, you can collect all the dependent objects for one or more metadata objects in the BI system and then translate their short and long texts. With the integration into the translation planner and the translation environment (transaction SE63), this procedure has changed.	Translating Text for BI Objects

BI Platform

New Features and Changes	Link to Documentation
A trace is a self-contained quantity of logged user actions. The trace tool environment (transaction RSTT) has special tools to record and play back traces (trace tool) as well as to process automatic regression tests (computer-aided test tool). The trace tool environment replaces the OLAP trace tool (transactions RSRTRACE and RSRCATTTRACE) and provides all of the functions necessary for a clearly enhanced application area.	Trace Tool Environment
The following enhancements and changes have been made in the area of manual planning in BW-BPS: ● +/- sign determination when you enter plan data has been improved. ● BW-BPS uses the lock management concept of BI Integrated Planning. ● Handling comparison columns in the planning layout: Reference data and plan data that is to be edited are handled separately so that reference data is not locked.	Automatic Sign Assignment (Result section) Locking Transaction Data (Lock Management section) Customizing with Reference to the Locking Concept (section on handling comparison columns in the planning layout)
You can use the BW-BPS Status and Tracking System (STS) with BI Integrated Planning. This is useful if you are already using BW-BPS with the Status and Tracking System but want to use additional functions from BI Integrated Planning.	Integrating BI Integrated Planning
An example of how to integrate a BEx Web application has been added to the documentation on the Web Interface Builder in BW-BPS, along with information about the enhancement options provided by class CL_UPWB_BSP_APPL.	Web Interface Builder Integration of BEx Web Applications Creating IFRAMEs for BEx Web Applications Filter Values from BW-BPS Variables Filter Values from Row Selection in Planning Layouts Enhancements for Web Interfaces

BI Suite: Business Explorer

New Features and Changes

Link to Documentation

Query Design: BEx Query Designer

● A newly implemented variable editor allows variables to be defined and edited. In addition, new functions are available such as replacing a variable with another variable or defining noncontextual variables.

● Quantity conversion: In the properties of the selections and restricted key figures, you can set a target quantity for the structural component.

● Publishing to the portal: You can publish queries directly to the Portal Content Directory (PCD) as iViews from the menu bar.

Variables

Selection/Formula Properties

Functions in the Query Menu

BEx Web

Web Application Design: BEx Web Application Designer

● The parameters for the Chart Web item have been simplified. In the Chart Designer, you can assign values from the current color palette using direct input. The documentation has been extended to include the new Gantt diagram and MTA chart types.

● In the Web Application Designer, a migration tool is available. You use this to migrate Web templates from SAP BW 3.x format to SAP NetWeaver 7.0 format.

● The Properties Pane Web item allows you to display and change the properties of a Web item.

● Depending on the business case, you need to address some basic questions when creating Web applications. These questions allow you to use the BEx Web Application Designer and BEx Web Design API to design Web applications that match your requirements. In addition, examples are given of typical aspects of Web application design.

● Enterprise Reporting

● You can use the BEx Report Designer to easily and intuitively create reports that are optimized for presentations and printing.

Tasks for System Administration

You can reorganize and delete bookmarks.

BI Patterns

The documentation has been extended to include the Information Consumer Pattern.

Chart, Assigning Colors and Chart Types

Migration Tool and Migrating Web Templates

Properties Pane

Creating a Web Application and Web Application Examples

---------------------------------------------------------------

Functions of the Report Designer, Working with the Report Designer, Creating Reports with the Report Designer

---------------------------------------------------------------

Reorganization of Bookmarks

---------------------------------------------------------------

Information Consumer Pattern

General Services in BEx

You can create print versions of BI applications. To do this, you first export the selected Web application or workbook to PDF format. You can then print the PDF version. A dialog is provided to support you in creating print versions. You use this dialog to specify the layout of the print version.

Creation of Print Versions of BI Applications

Information Broadcasting

The documentation has been extended and includes information about using text variables.

Use of Text Variables

Integrating Content from BI into the Portal

● You can publish queries from the BEx Query Designer, Web applications from the BEx Web Application Designer, and reports from the BEx Report Designer as iViews to the Portal Content Directory (PCD).

● BEx Web applications or queries can be displayed as iViews in various portals with the help of various concepts.

○ Portal from SAP NetWeaver 7.0

○ SAP Enterprise Portal 6.0

○ Portal from third-party provider

Publishing Queries, Web Applications, and Reports

Integration of Content from BI into Other Portals

BEx Analyzer

In the BEx Analyzer, you can execute a report on the Web without starting the Web Application Designer.

You can drill down and collapse the characteristics in a report by double-clicking them. You can change the position of a design item in a workbook using drag and drop.

Analysis & Reporting: BEx Analyzer

Navigating in Analysis Mode

Workbook Settings

Support Package Stack 07

SAP NetWeaver 7.0 SP Stack 07 contains the following new features and enhancements:

Data Warehousing

New Features and Changes	Link to Documentation
New authorization objects have been added.	Release note: Authorization Objects (New)
The migration of update rules, 3.x InfoObjects, and transfer rules is supported.	Migrating Update Rules, 3.x InfoSources, and Transfer Rules
Near-line storage has been added to information lifecycle management.	Data Archiving Process
A where-used list for requests makes it possible to display dependent target requests for a source request.	Where-Used List for Requests
The Administration functional area of the Data Warehousing Workbench has been enhanced.	Release note: Data Warehousing Workbench (Enhanced)
The documentation for TLOGO objects has been updated.	Transportable Object Types
On the Metadata Indexing tab page for the BI metadata search in the Administration functional area of the Data Warehousing Workbench, you can use Metadata Search/ Documents to check the settings required for the BI metadata search and to index the metadata. The user interface has been redesigned.	BI Metadata Search Tab Page: Metadata Indexing
The entry section for technical content has been updated.	Technical Content
Certification of partner content allows you to officially document the technical quality of your content for your customers.	Partner Content

BI Platform

New Features and Changes	Link to Documentation
Processing of subqueries can now be performed independently of the type of InfoProvider.	Processing Queries; see also Not Using Parallel Processing.
Using the new BIA index maintenance wizard, you can create and activate a BI accelerator index, each in one step, and then fill or delete it as necessary. The relevant parts of the BI accelerator documentation have been modified accordingly.	Using the BIA Index Maintenance Wizard
Functions have been added to the BI accelerator monitor (Goto menu, BI Accelerator menu).	Using the BI Accelerator Monitor Global Parameters for Indexing BI Accelerator Index Design
Numerous new tests for the BI accelerator are now available in the analysis and repair environment.	Checking BI Accelerator Indexes (Transaction RSRV)
The area of BI query runtime statistics has been documented in detail.	BI Query Runtime Statistics Analysis of Statistics Data Maintenance of Statistics Properties
The documentation for BI Integrated Planning has been extended.	Authorizations for BI Integrated Planning For modeling planning scenarios in the planning modeler: ● Changing Variable Values in the Planning Modeler ● Standard Planning Function Types, in particular Forecasting Creation of Planning Applications ● Creating Planning Applications in the BEx Analyzer ● Creating Planning Applications in the BEx Web Application Designer ● As part of the Web Design API: Commands for Planning Applicationss Performing Manual Planning ● In the BEx Analyzer: Functions for Manual Planning Transport of Planning Objects
The documentation of the BW-BPS Web Interface Builder has been revised and enhanced with respect to the design templates and the new BW-BPS design.	Design Templates for Web Interfaces Using Your Own Style Sheet (New Design)

BI Suite: Business Explorer

New Features and Changes

Link to Documentation

Query Design: BEx Query Designer

Changes have been made to the definition of noncontextual variables in the variable editor. Only exit variables can be marked as noncontextual.

Details

BEx Web

Web Application Design: BEx Web Application Designer

There is now a new Script Web item, which can be used to insert JavaScript functions into Web templates.

In the Dropdown Box Web item, the Fixed List of Options: Manual Update (STATIC_OPTION_LIST_MANUAL) data binding type has been added.

The examples "Creating Planning Applications in the BEx Web Application Designer" and "Using JavaScript in the Dropdown Box Web Item" have been added to the examples for Web applications.

Web Design API

Various data provider commands and their parameters have been documented in more detail.

You can now use parameters to call Web applications.

To enhance Web applications, a JavaScript API is now available, with which you can also execute commands within JavaScript functions to achieve a more flexible design for your Web Application.

The heatmap (also smart map) and milestone trend analysis (MTA) chart types are now documented.

Enterprise Reporting

Reports from the Report Designer are displayed in the portal (Web) using the standard Web template for reports.

Using conditional formatting, individual characteristic values can be highlighted in a report with a dynamic section.

In the BEx Report Designer, you can create a balance sheet that contains assets and liabilities next to each other.

Script

Data Binding Type STATIC_OPTION_LIST_MANUAL

Creating Planning Applications in the BEx Web Application Designer

Using JavaScript in the Dropdown Box Web Item

---------------------------------------------------------------
Basic Data Provider Commands

Data Provider Commands for Axes

Data Provider Commands for Characteristics

Data Provider Commands for Documents

Commands for Planning Applications

Start Broadcaster

Using Parameters to Call Web Applications

JavaScript

Chart Types

Standard Web Template for Reports

Creating Conditional Formatting

Balance Sheet: Arranging Assets and Liabilities Beside Each Other

General Services in BEx

The search functions in the BEx open dialog now include an advanced search in BI object attributes as an additional search method.

You can now overwrite existing BI objects when you save new BI objects.

There are some restrictions you need to note when using the various BEx tools and runtimes from SAP BW 3.x and SAP NetWeaver 7.0.

Search Function

The Save Dialog

Runtime and Design-Time Cross-Dependencies: SAP BW 3.x and SAP NetWeaver 7.0

Support Package Stack 08

As of SAP NetWeaver 7.0 SP Stack 08, you can find more information about new features in and enhancements to the documentation, as well as new functional features and changes, under Release Notes by NetWeaver Systems and Standalone Engines in the relevant sections:

● Release Notes for Usage Type BI

● Release Notes for Usage Type BI Java

Business Intelligence(BI)

2009-07-08T06:32:00.000-07:00

Purpose

The reporting, analysis, and interpretation of business data is of central importance to a company in guaranteeing its competitive edge, optimizing processes, and enabling it to react quickly and in line with the market. With Business Intelligence (BI), SAP NetWeaver provides data warehousing functionality, a business intelligence platform, and a suite of business intelligence tools with which an enterprise can attain these goals. Relevant business information from productive SAP applications and all external data sources can be integrated, transformed, and consolidated in BI with the toolset provided. BI provides flexible reporting, analysis, and planning tools to support you in evaluating and interpreting data, as well as facilitating its distribution. Businesses are able to make well-founded decisions and determine target-orientated activities on the basis of this analysis.

Integration

The following figure shows where BI is positioned within SAP NetWeaver. In addition, the subareas that are covered by the BI documentation are listed. These are described in detail below.

Integration with Other SAP NetWeaver Components

BEx Information Broadcasting allows you to publish precalculated documents or online links containing business intelligence content to the portal. The Business Explorer portal role illustrates the various options that are available to you when working with content from BI in the portal. For more information, see Information Broadcasting.

The BEx Broadcaster, the BEx Web Application Designer, the BEx Query Designer, KM Content, SAP Role Uploads, and the Portal Content Studio are used to integrate BI contents into the portal. For more information, see Integrating BI Content into the Portal.

The documents and metadata created in BI (metadata documentation in particular) can be integrated using the repository manager in knowledge management. The BI Metadata Repository Manager is used within BEx Information Broadcasting. For more information, see BI Document Repository Manager and BI Metadata Repository Manager.

You can use SAP NetWeaver Exchange Infrastructure (SAP NetWeaver XI) to send data from SAP and non-SAP sources to BI. In BI, the data is placed in the delta queue where it is available for further integration and consolidation. Data transfer using SAP NetWeaver XI is SOAP-based. For more information, see Data Transfer Using SAP XI.

Integration with BI Content Add-On

With BI Content, SAP delivers preconfigured role and task-based information models and reporting scenarios for BI that are based on consistent metadata. BI Content provides selected roles within a company with the information they need to carry out their tasks. The information models delivered cover all business areas and integrate content from almost all SAP and selected external applications. For more information, see BI Content.

Features

Subareas of BI

Area	Description
Data Warehousing	Data warehousing in BI represents the integration, transformation, consolidation, cleanup, and storage of data. It also incorporates the extraction of data for analysis and interpretation. The data warehousing process includes data modeling, data extraction, and administration of the data warehouse management processes. The central tool for data warehousing tasks in BI is the Data Warehousing Workbench.
BI Platform	The business intelligence platform serves as the technological infrastructure and offers various analytical technologies and functions. These include the Analytics Engine, the Metadata Repository, Business Planning and Simulation, and special analysis processes such as data mining.
BI Suite: Business Explorer	The SAP NetWeaver Business Intelligence Suite, the Business Explorer (BEx), provides flexible reporting and analysis tools for strategic analyses, operational reporting, and decision-making support within a business. These tools include query, reporting, and analysis functions. As an employee with access authorization you can evaluate past or current data on various levels of detail, and from different perspectives, not only on the Web but also in MS Excel. You can use BEx Information Broadcasting to distribute Business Intelligence content from SAP BW by e-mail either as precalculated documents with historical data, or as links with live data. You can also publish it to the Enterprise Portal. The Business Explorer allows a broad spectrum of users access to information in the SAP BW using the Enterprise Portal, the Intranet (Web application design) or mobile technologies.
Development Technologies	● BI Java SDK You use the BI Java SDK to create analytical applications with which you access both multidimensional (Online Analytical Processing or OLAP) and tabular (relational) data. You can also edit and display this data. BI Java Connectors, a group of four JCA-enabled (J2EE Connector Architecture) resource adapters, implement the BI Java SDK APIs and allow you to connect applications that you have created with the SDK to various data sources. ● Open Analysis Interfaces The Open Analysis Interfaces make various interfaces available for connecting front-end tools from third-party providers. ● Web Design API The Web Design API allows you to implement highly individual scenarios and demanding applications with customer-defined interface elements.

Successful Connection Setup and Data Transfer

2009-06-12T09:05:00.000-07:00

When the connection is set up and data transferred without any errors, you can see the following entries in the log file:

Operation Without SNC

Thu Jun 14 16:08:04 2007 CONNECT FROM C9/ host 10.66.66.90/19114 (host1.company.corp)

Thu Jun 14 16:08:04 2007 CONNECT TO S9/17 host 10.21.83.41/3299 (host2)

Thu Jun 14 16:08:06 2007 ESTABLISHED S9/17

Thu Jun 14 16:21:06 2007 DISCONNECT C9/17 host 10.66.66.90/19114 (host1.company.corp)

Thu Jun 14 14:28:40 2007 CONNECT FROM C19/ host 10.66.66.90/12127 (host1.company.corp)

Thu Jun 14 14:28:40 2007 CONNECT TO S19/11 host 10.21.72.60/3299 (host3), *** NATIVE ROUTING ***

Thu Jun 14 14:28:41 2007 ESTABLISHED S19/11 , *** NATIVE ROUTING ***

Thu Jun 14 14:58:43 2007 DISCONNECT S19/11 host 10.21.72.60/3299 (host3), *** NATIVE ROUTING ***

Operation with SNC

When using SNC for data communication between two SAProuters there are two different mechanisms for setting up the connection.

SNC Forwards Setup

With this mechanism, client-side SAProuter initiates the SNC connection/encryption. The SAProuter on the client-side has an entry of the type KT in the router permission table for the server-side SAProuter and therefore establishes the SNC connection. The SNC name is written to the 'CONNECT TO' log when the connection to the server-side SAProuter is established. The 'ESTABLISHED' log displays the recipient side of the SNC communication once the connection has been set up successfully.

Client Side

Thu Jun 14 17:13:22 2007 CONNECT FROM C9/ host 10.66.66.90/30888 (host1.company.corp)

Thu Jun 14 17:13:25 2007 CONNECT TO S9/17 host 10.18.211.3/3299 (10.18.211.3) (p:CN=D039768, O=SAP-AG, C=DE)

Thu Jun 14 17:13:25 2007 ESTABLISHED S9/17 (-/SNC)

Thu Jun 14 17:19:12 2007 DISCONNECT C9/17 host 10.66.66.90/30888 (host1.company.corp)

Server Side

Thu Jun 14 17:13:22 2007 CONNECT FROM C9/- host 10.18.211.3/1150 (host2)

Thu Jun 14 17:13:25 2007 CONNECT TO S9/17 host 10.66.66.91/3253 (binmain)

Thu Jun 14 17:13:25 2007 ESTABLISHED S9/17 (SNC/-)

Thu Jun 14 17:19:12 2007 DISCONNECT C9/17 host 10.18.211.3/1150 (host2)

SNC Backwards Setup

The server-side SAProuter can also initiate SNC. This is what happens if the incoming connection from the client-side SAProuter does not use SNC (see above) but the server-side SAProuter requires it due to the relevant entries in the route permission table. In this scenario, the SNC handshake is triggered by the server-side SAProuter later on. This means that there is no SNC name in the 'CONNECT TO' entry in the log on the client side.

Client Side

Thu Jun 14 16:55:21 2007 CONNECT FROM C9/- host 10.18.211.3/1065 (host2)

Thu Jun 14 16:55:21 2007 CONNECT TO S9/17 host 10.18.211.3/3299 (10.18.211.3)

Thu Jun 14 16:55:21 2007 ESTABLISHED S9/17 (-/SNC)

Thu Jun 14 16:56:42 2007 DISCONNECT S9/17 host 10.18.211.3/3299 (10.18.211.3)

Server Side

Thu Jun 14 16:55:21 2007 CONNECT FROM C9/- host 10.18.211.3/1066 (host2)

Thu Jun 14 16:55:21 2007 CONNECT TO S9/17 host 10.66.66.91/sapdp53 (host4.company.corp)

Thu Jun 14 16:55:21 2007 ESTABLISHED S9/17 (SNC/-)

Thu Jun 14 16:56:42 2007 DISCONNECT S9/17 host 10.66.66.91/3253 (host4.company.corp)

Connection Setup Errors

2009-06-12T09:04:00.000-07:00

The following errors can occur during the connection setup:

Connect fails because the server is not running
TCP/IP connect takes too long (longer than the timeout -W value)
Route setup takes too long (longer than the timeout -W value)
No route permission for the connection
Error on the subsequent host

These errors are described below with possible solutions.

Connect fails (server not running)

The log file contains the following entries:

SAProuter Log File
`Thu Jun 14 13:18:22 2007 CONNECT FROM C9/- host 10.66.66.90/35169 (host2.company.corp)` `Thu Jun 14 13:18:22 2007 CONNECT TO S9/17 host 10.66.66.91/3299 (host1)` `Thu Jun 14 13:18:22 2007 CONNECT ERR S9/17 connection refused` `Thu Jun 14 13:18:22 2007 DISCONNECT S9/17 host 10.66.66.91/3299 (host1)`

The client issues the error message below.

Syntax

SAProuter Error Message

***********************************************************************
*  LOCATION    SAProuter 39.1 (SP3) on 'ld8060'
*  ERROR       partner '10.66.66.91:3299' not reached
*
*  TIME        Thu Jun 14 13:18:22 2007
*  RELEASE     710
*  COMPONENT   NI (network interface)
*  VERSION     39
*  RC          -92
*  MODULE      nixxi.cpp
*  LINE        3068
*  DETAIL      NiPConnect2: 10.66.66.91:3299
*  SYSTEM CALL connect
*  ERRNO       111
*  ERRNO TEXT  Connection refused
*  COUNTER     4
***********************************************************************

End of the code.

Background and Further Analysis

On the server side, there is no program running that listens to the IP address 10.66.66.91 and port 3299 (LISTEN). Check that the host name/IP address and server name/port number are correct. If they are correct, the right server is being reached but it appears that the program to which the connection should be established is not running. Check that the SAProuter and the system or corresponding program on the server is running and is using the correct port (OS command netstat -an).

TCP/IP connect takes too long (longer than the timeout -W value)

The log file contains the following entries:

SAProuter Log File
`Thu Jun 14 13:22:01 2007 CONNECT FROM C10/- host 10.66.66.90/41060 (host2.company.corp)` `Thu Jun 14 13:22:01 2007 CONNECT TO S10/18 host 1.1.1.1/3299` `(1.1.1.1)` `Thu Jun 14 13:22:06 2007 CONNECT ERR S10/18 could not establish connection within 5s` `Thu Jun 14 13:22:06 2007 DISCONNECT S10/18 host 1.1.1.1/3299 (1.1.1.1)`

The client issues the error message below.

Syntax

SAProuter Error Message

***********************************************************************
*  LOCATION    SAProuter 39.1 (SP3) on 'ld8060'
*  ERROR       connection to 1.1.1.1:3299 timed out
*
*  TIME        Thu Jun 14 13:22:06 2007
*  RELEASE     710
*  COMPONENT   NI (network interface)
*  VERSION     39
*  RC          -5
*  MODULE      nirout.cpp
*  LINE        6548
*  DETAIL      RTPENDLIST::timeoutPend: could not establish connection within
*              5s (ROUTED)
*  COUNTER     6
***********************************************************************

End of the code.

Background and Further Analysis

In this example, the TCP/IP connection from the SAProuter to the next node (the next SAProuter, a system, or another network component) could not be established within a specified timeout period. This error can occur if the server host is down or the IP address of the host cannot be reached. It can also be due to the network failing to establish the TCP/IP connection within 5 seconds (the timeout value defined in option -W). You might be able to solve this problem by using a greater value for option -W.

For more information, see: Expert Options in SAProuter Options.

Route setup takes too long

The SAProuter is able to connect to the next host using TCP/IP, but the next host takes too long to establish the route to the destination. It receives no NI_PONG (confirmation that the route has been established) within the -W timeout period.

The log file contains the following entries:

SAProuter Log File
`Thu Jun 14 13:34:19 2007 CONNECT FROM C15/- host 10.66.66.90/41070 (host2.company.corp)` `Thu Jun 14 13:34:19 2007 CONNECT TO S15/23 host 10.21.72.60/3299` `(host3)` `Thu Jun 14 13:34:24 2007 CONNECT ERR S15/23 no route completion within 5s; check SAProuter on 'host3'` `Thu Jun 14 13:34:24 2007 DISCONNECT S15/23 host 10.21.72.60/3299` `(host3)`

The client issues the error message below.

Syntax

SAProuter Error Message

***********************************************************************
*  LOCATION    SAProuter 39.1 (SP3) on 'ld8060'
*  ERROR       connection to host3:3299 timed out
*
*  TIME        Thu Jun 14 13:34:24 2007
*  RELEASE     710
*  COMPONENT   NI (network interface)
*  VERSION     39
*  RC          -5
*  MODULE      nirout.cpp
*  LINE        6537
*  DETAIL      RTPENDLIST::timeoutPend: no route completion within 5s
*              (ROUTED)
*  COUNTER     17
***********************************************************************

End of the code.

Background and Further Analysis

Find out why the subsequent SAProuter was unable to establish the connection within 5 seconds (in this example). It might be due to slow name resolution, for example. The log and trace files should provide further information on this. In the case of connections using multiple SAProuters in a WAN environment, increase option -W. If multiple SAProuters are involved in setting up a connection and the network response times are relatively high, the default value of 5 seconds is not sufficient to enable the connection to the target system to be established.

For more information, see: Expert Options in SAProuter Options.

No route permission for the connection

The SAProuter rejects the connection because the route permission table does not allow it.

The log file contains the following entries:

SAProuter Log File
`Thu Jun 14 14:18:20 2007 CONNECT FROM C10/- host 10.66.66.90/63669 (host2.company.corp)` `Thu Jun 14 14:18:20 2007 PERM DENIED C10/- host 10.66.66.90 (host2.company.corp) to host1/3254` `Thu Jun 14 14:18:20 2007 DISCONNECT C10/- host 10.66.66.90/63669 (host2.company.corp)`

The client issues the error message below.

Syntax

SAProuter Error Message

************************************************************************ 
*  LOCATION    SAProuter 39.1 (SP3) on 'ld8060'
*  ERROR       ld8060: route permission denied (host2.company.corp to
*              host1, 3254)
*
*  TIME        Thu Jun 14 14:18:20 2007
*  RELEASE     710
*  COMPONENT   NI (network interface)
*  VERSION     39
*  RC          -94
*  COUNTER     5
***********************************************************************

End of the code.

Background and Further Analysis

Checking the Route Permission Table

Error on the subsequent host

This error does not occur on the local SAProuter. Instead, it occurs on a subsequent host. Messages of the following type appear in the log of the local SAProuter:

SAProuter Log File
`Thu Jun 14 14:42:53 2007 CONNECT FROM C10/- host 10.66.66.90/30005 (host2.company.corp)` `Thu Jun 14 14:42:53 2007 CONNECT TO S10/18 host 10.21.72.60/3299 (host3)` `Thu Jun 14 14:42:54 2007 CONNECT ERR S10/18 NIEROUT_INTERN on 'SAProuter 37.15 on hs0126'` `Thu Jun 14 14:42:54 2007 DISCONNECT S10/18 host 10.21.72.60/3299 (host3)`

The client issues the error message below.

Syntax

SAProuter Error Message

************************************************************************  LOCATION    SAProuter 37.15 on hs0126
*  ERROR       partner not reached (host 10.66.66.91, service 3298)
*
*  TIME        Thu Jun 14 14:42:54 2007
*  RELEASE     640
*  COMPONENT   NI (network interface)
*  VERSION     37
*  RC          -93
*  MODULE      nixxi.cpp
*  LINE        8724
*  DETAIL      NiPConnect2
*  SYSTEM CALL SiPeekPendConn
*  ERRNO       239
*  ERRNO TEXT  Connection refused
*  COUNTER     5
***********************************************************************

End of the code.

SAProuter Log File
`Thu Jun 14 14:40:28 2007 CONNECT FROM C9/- host 10.66.66.90/24016 (host2.company.corp)` `Thu Jun 14 14:40:28 2007 CONNECT TO S9/17 host 10.21.72.60/3299 (host3), * NATIVE ROUTING ` `Thu Jun 14 14:40:28 2007 CONNECT ERR S9/17 NIEROUT_PERM_DENIED on 'SAProuter 39.0 on 'host3'', NATIVE ROUTING ` `Thu Jun 14 14:40:28 2007 DISCONNECT S9/17 host 10.21.72.60/3299 (host3), NATIVE ROUTING *`

Syntax

SAProuter Error Message

***********************************************************************
*  LOCATION    SAProuter 39.0 on 'host3'
*  ERROR       host3: route permission denied (host2.company.corp to
*              host1, 3253)
*
*  TIME        Thu Jun 14 14:40:28 2007
*  RELEASE     710
*  COMPONENT   NI (network interface)
*  VERSION     39
*  RC          -93
*  COUNTER     3
**********************************************************************

End of the code.

Background and Further Analysis

Check the log and trace files on the SAProuter where the error occurred if the information already provided is not sufficient. The SAProuter error message that is normally displayed on the client contains information on the error. The LOCATION line tells you the location of the error.

Connection Terminations

2009-06-12T09:03:00.000-07:00

Connection terminations can be triggered from both the client side and the server side

Connection Terminations from the Server Side

The following entries appear in the log file when a connection termination is triggered from the server side (if the local SAProuter is the client).

SAProuter Log File
`Thu Jun 14 16:08:47 2007 CONNECT FROM C18/- host 10.66.66.90/24761 (host2.company.corp)` `Thu Jun 14 16:08:47 2007 CONNECT TO S18/10 host 10.21.83.41/3299 (host2)` `Thu Jun 14 16:08:47 2007 ESTABLISHED S18/10` `Thu Jun 14 16:08:58 2007 DISCONNECT S18/10 host 10.21.83.41/3299 (host2)`

The client issues the error message below.

Syntax

SAProuter Error Message

************************************************************************  LOCATION    SAProuter 39.0 on 'host2'
*  ERROR       connection to partner '10.21.72.60:3298' broken
*
*  TIME        Thu Jun 14 16:08:58 2007
*  RELEASE     710
*  COMPONENT   NI (network interface)
*  VERSION     39
*  RC          -95
*  MODULE      nixxi.cpp
*  LINE        4660
*  DETAIL      NiIRead: P=10.21.72.60:3298; L=???
*  SYSTEM CALL recv
*  ERRNO       232
*  ERRNO TEXT  Connection reset by peer
*  COUNTER     17
***********************************************************************

End of the code.

SAProuter Log File
`Thu Jun 14 16:09:50 2007 CONNECT FROM C19/- host 10.66.66.90/24847 (host2.company.corp)` `Thu Jun 14 16:09:50 2007 CONNECT TO S19/11 host 10.21.72.60/3298 (ldp007)` `Thu Jun 14 16:09:50 2007 ESTABLISHED S19/11` `Thu Jun 14 16:10:02 2007 DISCONNECT S19/11 host 10.21.72.60/3298 (ldp007) RST`

The client issues the error message below.

Syntax

SAProuter Error Message

***********************************************************************
*  LOCATION    SAProuter 39.1 (SP3) on 'host1'
*  ERROR       connection to partner '10.21.72.60:3298' broken
*
*  TIME        Thu Jun 14 16:10:02 2007
*  RELEASE     710
*  COMPONENT   NI (network interface)
*  VERSION     39
*  RC          -95
*  MODULE      nixxi.cpp
*  LINE        4660
*  DETAIL      NiIRead: P=10.21.72.60:3298; L=10.66.66.90:24848
*  SYSTEM CALL recv
*  ERRNO       104
*  ERRNO TEXT  Connection reset by peer
*  COUNTER     10
***********************************************************************

End of the code.

Connection Terminations from the Client Side

The following entries appear in the log file when a connection termination is triggered from the client side (if the local SAProuter is the server).

Thu Jun 14 16:13:20 2007 CONNECT FROM C20/- host 10.66.66.90/24849 (host2.company.corp)

Thu Jun 14 16:13:20 2007 CONNECT TO S20/12 host 10.21.83.41/3299 (host2)

Thu Jun 14 16:13:20 2007 ESTABLISHED S20/12

Thu Jun 14 16:13:43 2007 DISCONNECT C20/12 host 10.66.66.90/24849 (host2.company.corp) RST

There is no error message with errInfo because the error is on the client side.

Background and Further Analysis

The DISCONNECT entry in teh log file tells you the side where the connection termination was triggered. You can use this information to find the node/program that first closed the connection. The trace file for this program contains more information on the cause of the connection termination.

In some cases, the connection between the two programs can be terminated without either side triggering the termination. For example, this is the case if two SAProuters with a direct TCP/IP connection both record that the other side triggered the connection termination. This means that an active network component between the two programs terminated the TCP/IP connection. The network component concerned is often a firewall or a router with an idle timeout. If this occurs, check the network.

The DISCONNECT log entry also tells you whether or not the connection was closed in a TCP/IP-compliant manner. 'RST' at the end of the line indicates and RDT package or a retransmit timeout. This means that the other side or an active network component between the two sides of the TCP/IP connection ended the connection incorrectly. This can be caused by the program crashing, the connection being closed to early at application level, or a firewall.