02 Exchange Profile

8/12/2019 02 Exchange Profile

http://slidepdf.com/reader/full/02-exchange-profile 1/16

1

Exchange Profile

Au thor : Pau l Médail le



2

© SAP AG 2004

After complet ing this uni t, you will be able to:

Describe the Exchange Profi le and how it is used inthe Exchange Infrastructure

Detail some of the important settings in theExchange Profil e

Import the Exchange Profile from a file.

Export the Exchange Profile to a file.

Exchange Profile: Unit Objectives



3

© SAP AG 2004

Before the Exchange Infrastructure can be madeoperational, the Exchange Profile must be importedand maintained.

As the Technical Project Team member, you areresponsible for doing this

Exchange Profile: Business Scenario



4

The Exchange Profile is an XML document, stored in the main database of the Exchange Infrastructure,that contains the parameters that define some basic technical settings of the XI. Most of these parametersare initialized automatically during the installation phase, but in some cases the administrator may need tomaintain them.

For instance, business systems need to retrieve the location of the Integration Builder for ProxyGeneration. This information is stored in the Exchange Profile, and accessed via an RFC call.

The Exchange Profile is accessed by pointing a browser to the URL:

http://<host>:<port>/exchangeProfile

Where <host> and <port> refers to the Integration Server host and its java port. You must supply a validuser name and password (A user in J2EE security role administer is required. By default this J2EE roleis mapped to SAP role SAP_XI_ADMINISTRATOR_J2EE on SAP Web AS 6.40). This URL

provides a web-based interface for editing the exchange profile.

© SAP AG 2004

The Exchange Profile



5

After logging on to the Exchange Profile URL, the administrator can perform the following actions in theExchange Profile maintenance interface:

XI Profile: Maintain configuration settings in the Exchange Profile.

Export: Export the Exchange Profile to a local file.

Import: Perform the (initial) import of the file to the database.

Reset Lock: Reset locked Exchange Profile entries.

Connection: Maintain the connection parameters (host, system number, client, user, password,language) for the Integration Server for connection to the System Landscape Directory.

© SAP AG 2004

Exchange Profile Actions

View andChange

ExchangeProfile

Settings

ChangeExchange

ProfileConnectionParameters

ResetLocked

ExchangeProfileEntries

ImportExchange

ProfileSettingsFrom File

ExportExchange

ProfileSettings To

File



6

The Exchange Profile settings are initially stored in an xml file (created during installation); these must beloaded into the database after installation.

On your SAP Integration server host, open the following URL:

http://<J2EE_host>:<J2EE_Port>/exchangeProfile

Logon as XISUPER with the appropriate password.

Choose Connection; The Server Settings page appears

Enter the required information for the SAP Exchange Infrastructure host (Use the logon information ofuser XILDUSER).

Choose Set . You are returned to the Exchange Profile page.

Choose Import . You are taken to the Import Profile page.

Choose Browse and select the following file:

/usr/sap/<SID>/SYS/global/exchange_profile.xml

Choose Import Data , and the profile will be loaded into the database.

Note: As the file exchange_profile.xml contains secure information like passwords, it is highlyrecommend to delete the file after importing or to save it by using high security standards, such asencryption.

© SAP AG 2004

Importing the Exchange Profile

Import the Exchange Profile After Installation

1. Maintain connection to the Integration Server 2. Navigate to the Import page3. Browse to:

/usr/sap/<SID>/SYS/global/exchange_profile.xml4. Choose “ Import Data”

The exchange_profile.xml contains sensitiveinformation and must be stored securely after

import!



7

An Administrator can save a local XML copy of the Exchange Profile. This gives you a backup of the filein case it ever needs to be reloaded. For this reason, export the file every time you change settings. Fromthe Exchange Profile screen, choose Export .

In the Export screen, click the Export Data button; you will be prompted to save or open the (zipped)copy of the file. This can now be opened and viewed at the local computer.

After the export, click on Exchange Infrastructure Profile to return to the Exchange Profile maintenancescreen.

Note: As the file exchange_profile.xml contains secure information like passwords, it is highlyrecommend to delete the file after exporting or save it by using high security standards, such asencryption.

© SAP AG 2004

Exporting the Exchange Profile



8

Use the link Connection to connect to the main database of the Exchange Infrastructure. Enter the RFCconnect parameters to the Integration Server (as explained earlier). After the connection parameters areset, the profile main page is displayed again, now showing the database content as a tree structure.Individual parameters can now be selected from the left-hand pane, and edited on the right.

After any modification, the integration server will have to be restarted in order for the changes to takeeffect.

Most of the parameters are in fact for SAP internal use only, and therefore should not be changed during acustomer installation. Some of the relevant settings for customer installations are discussed on thefollowing slides.

© SAP AG 2004

Maintaining Exchange Profile Settings



9


For full details, see the SAP Exchange Infrastructure 3.0 Configuration Guide , available athttp://service.sap.com/instguides.

© SAP AG 2004

Exchange Profile Settings (I)

com.sap.aii.connect landscape.httpsport

com.sap.aii.connect landscape.httpport

Connection parameters of the System LandscapeDirectory server (listening for WBEM requests).WBEM is t he communi cation st andard u nder CIM.They are both defined by the DistributedManagement Task Force (see www .dmtf.org ).

com.sap.aii.connect.landscape.name

com.sap.aii.connect.directory.rmiport

com.sap.aii.connect.directory.httpsport

com.sap.aii.connect.directory.httpportConnection parameters of t he directory s erver

com.sap.aii.connect.directory.name

com.sap.aii.connect.repository.rmiport

com.sap.aii.connect.repository.httpsportcom.sap.aii.connect.repository.httpport

Connection parameters of the repository server:1. Host name

2. HTTP por t number3. HTTPS port number (optional)4. RMI port number (used for communication with

the WebStart Client)

com.sap.aii.connect.repository.name

Connections (I)



10



© SAP AG 2004

Exchange Profile Settings (II)

com.sap.aii.connect.integrationserver.r3.httpsport

com.sap.aii.connect.integrationserver.r3.client

com.sap.aii.connect.integrationserver.r3.sysnr Connection parameters for the ABAPpart of the Integration Server.

com.sap.aii.connect.integrationserver.r3.httpport

com.sap.aii.connect.integrationserver.httpsport

com.sap.aii.connect.integrationserver.httpport Connection parameters of theIntegration Server.

com.sap.aii.connect.integrationserver.name

com.sap.aii.connect.rwb.r3.clientConnection parameters for the ABAPpart of the Runtime Workbench.

com.sap.aii.connect.rwb.r3.sysnr

com.sap.aii.connect.rwb.httpsport

com.sap.aii.connect.rwb.httpport Connection parameters of theRuntime Workbench.

com.sap.aii.connect.rwb.name

Connections (II)



11

Basically the parameter is a comma-separated list of use cases. Currently there are only two use cases:Messaging:

Internal transport of payload messages between XI components (for example, between the Integration Server and adapters).

All:

Includes all communications.

If only the use case is given, the setting applies to all components in the XI landscape. It is also possible to restrict the selection tospecific XI components by adding a list of SLD instance names in parentheses after the use case. In this case, the setting onlyapplies for communications which involve one of the listed instances.

Example 1: com.sap.aii.connect.secure_connections = messaging

All components use secure communication for messaging.Example 2: com.sap.aii.connect.secure_connections =

No secure communication is used (only standard HTTP); this is the default setting.

Example 3: com.sap.aii.connect.secure_connections = messaging, all(af.BXI.pwdf0591, af.Y6D.ld0050)

Secure communication is used for messaging (on all systems) and for all connections from or to the adapters on systemBXI/pwdf0591 and Y6D/ld0050.

The SLD instance name of the Integration Server uses the system number instead of the system ID as <SID>. In addition tosetting the parameter secure_connections, you also have to configure the HTTPS ports of the involved components in theConnections section of the exchange profile (see preceding slides).

After any modification, the integration server will have to be restarted in order for the changes to take effect.

© SAP AG 2004

com.sap.aii.connect.secure_connections

The parameter com.sap.aii.connect.secure_connections has the followingsyntax:

<secure_connections> ::= <entry> ("," <entry>)*<entry> ::= <usecase> ( "(" <component_list> ")" )?<usecase> ::= "messaging" | "all"<component_list> ::= <sld_instance_name> ("," <sld_instance_name> )*<sld_instance_name> ::= <application_id> " ." <SID> " ." <DBHOST><application_id> ::= "repository" | " directory" | " af" | " runtime" ...

The parameter secure_connections specifies where the internal XI

communication should use secure communication (HTTPS) instead of plainHTTP.



12

For parameters relating to the JCo connection from the J2EE engine to its R/3 instance, see the associated JCodocumentation of the related proeperties (i.e., jco.client.client, jco.client.ashost, and jco.client.sysnr).


© SAP AG 2004

Integration Builder Settings (I)

Acti vates the Locking and Author izat ionService (this shoul d always be "tr ue").

com.sap.aii.ib.server.lockauth.activation

This flag determines whether fast RFCshould b e used for connecting to the R/3part of t he SAP Web AS.

com.sap.aii.ib.server.connect.webas.r3.usefastrfc

SAP system number . This isautomatically filled during installation.

com.sap.aii.ib.server.connect.webas.r3.sysnr

SAP application server . This isautomatically filled during installation.

com.sap.aii.ib.server.connect.webas.r3.ashost

SAP client Filled with " 000" duringinstallation.

com.sap.aii.ib.server.connect.webas.r3.client

JCo connection from th e J2EE engine to "its " R3 instance (used by the locking service):

Comma-separated list of languages usedfor content documentation.

com.sap.aii.ib.client.content.languages

Comma-separated list of installedlanguages.

com.sap.aii.ib.client.login.languages



13

After the installation, the service users already exist together with a password in the exchange profile(properties of the Exchange Infrastructure). From there they are retrieved by the J2EE components of theExchange Infrastructure when the system is started.

If you make changes to user names and passwords, you have to make them in transaction SU01 first andthen again in the exchange profile. See SAP note 721584 for further details.

For parameter com.sap.aii.repository.mapping.additionaltypes:

Besides the standard mapping types like "class" for Java mapping programs or "xsl" for XSLT programs,you can register additional mapping types of SAP Partners. These additional mapping types enable youto call mapping programs of SAP partners, by calling a BAdI registered under the same mapping type.In the Integration Builder, the additional mapping types can be selected in the Interface Mapping Editor

when you create an interface mapping. You can enter a link to a mapping program of a SAP Partner inthe Interface Mapping, which is passed to the BAdI during the execution.

You have to specify a key and a caption for an additional mapping type. The key field is restricted to 20characters and should only contain the characters a,...,z and A,...,Z, the numbers 0,...,9, and theunderscore "_". The caption should not exceed 25 characters. The caption is separated from the key by"|". Different additional mapping types are separated by ";".

Example: PA_TYPE|Partner Mapping;pa_trafo|Partner Transformation

Note: Use the value "none", if no additional mapping types are used.

© SAP AG 2004

Integration Builder Settings (II)

See notes belowcom.sap.aii.repository.mapping.additionaltypes

com.sap.aii.repository.serviceuser.certificate

com.sap.aii.repository.serviceuser.language

com.sap.aii.repository.serviceuser.pwd This is the service user used by theIntegration Repositor y (XIREPUSER).

com.sap.aii.repository.serviceuser.name

IntegrationBuilder.Repository

com.sap.aii.directory.serviceuser.certificate

com.sap.aii.directory.serviceuser.language

com.sap.aii.directory.serviceuser.pwd This is the service user used by theIntegration Directory (XIDIRUSER).

com.sap.aii.directory.serviceuser.name

IntegrationBuilder.Directory



14

After the installation, the service users already exist together with a password in the exchange profile(properties of the Exchange Infrastructure). From there they are retrieved by the J2EE components of theExchange Infrastructure when the system is started.



© SAP AG 2004

Further Customer Settings (I)

IntegrationServer

com.sap.aii. applicationsystem.serviceuser.certificate

com.sap.aii.applicationsystem.serviceuser.language

com.sap.aii.applicationsystem.serviceuser.pwd

This is the service user used byapplication systems. This usershould exist on the main IntegrationServer and also be associated withthe appropriate RFC destination onapplication syst ems using SM59(XIAPPLUSER).

com.sap.aii.applicationsystem.serviceuser.name

Appl ic ationSystem

com.sap.aii.mapping.parserFactory

Customers may want to use adifferent XML/XSLT engine such asXALAN/Xerces for processingmappings.

com.sap.aii.mapping.transformerFactory

IntegrationServer.MappingRuntime

com.sap.aii. integrationserver.serviceuser.certificate

com.sap.aii. integrationserver.serviceuser.language

com.sap.aii. integrationserver.serviceuser.pwd

This is the service user used by theIntegration Server (XIISUSER).

com.sap.aii.integrationserver.serviceuser.name



15

Settings relating to the Runtime Workbench must be completed in order to configure Central Monitoring.After the installation, the service users already exist together with a password in the exchange profile(properties of the Exchange Infrastructure). From there they are retrieved by the J2EE components of theExchange Infrastructure when the system is started.



© SAP AG 2004

Further Customer Settings (II)

com.sap.aii.adapterframework.serviceuser.certificate

com.sap.aii.adapterframework.serviceuser.language

com.sap.aii.adapterframework.serviceuser.pwd This user is used b y the AdapterFramework when connecting to otherservers (XIAFUSER).

com.sap.aii.adapterframework.serviceuser.name

AdapterFramework

com.sap.aii.rwb.server.centralmonitoring.httpport

com.sap.aii.rwb.server.centralmonitoring.r3.sysnr

com.sap.aii.rwb.server.centralmonitoring.r3.client

Appl ication server of the SAP Web AS on which the central PMI, centralCCMS and central Alert Server run.Required for JCO connections andHTTP connections to the monit oringserver.

com.sap.aii.rwb.server.centralmonitoring.r3.ashost

com.sap.aii.rwb.serviceuser.certificate

com.sap.aii.rwb.serviceuser.language

com.sap.aii.rwb.serviceuser.pwd This is the service user used by theRuntime Workbench (XIRWBUSER)

com.sap.aii.rwb.serviceuser.name

RuntimeWorkbench



16

© SAP AG 2004

You should now be able to:Describe the Exchange Profi le and how i t is used inthe Exchange Infrastructure

Detail some of the important settings in theExchange Profil e

Import the Exchange Profile from a file.

Export the Exchange Profile to a fi le.

Exchange Profile: Unit Summary

02 Exchange Profile

Documents

Transcript of 02 Exchange Profile