1

Exchange Profile
Author: Paul Mdaille
2
SAP AG 2004
After completing this unit, you will be able to:
Describe the Exchange Profile and how it is used in
the Exchange Infrastructure
Detail some of the important settings in the
Exchange Profile
Import the Exchange Profile from a file.
Export the Exchange Profile to a file.
Ex c hange Pr of i l e: Uni t Obj ec t i ves
3
SAP AG 2004
Before the Exchange Infrastructure can be made
operational, the Exchange Profile must be imported
and maintained.
As the Technical Project Team member, you are
responsible for doing this
Ex c hange Pr of i l e: Busi ness Sc enar i o
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 parameters
are initialized automatically during the installation phase, but in some cases the administrator may need to
maintain them.
For instance, business systems need to retrieve the location of the Integration Builder for Proxy
Generation. 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 valid
user name and password (A user in J2EE security role administer is required. By default this J 2EE role
is 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 Ex c hange Pr of i l e
5
After logging on to the Exchange Profile URL, the administrator can perform the following actions in the
Exchange 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
Ex c hange Pr of i l e Ac t i ons
View and
Change
Exchange
Profile
Settings
Change
Exchange
Profile
Connection
Parameters
Reset
Locked
Exchange
Profile
Entries
Import
Exchange
Profile
Settings
From File
Export
Exchange
Profile
Settings To
File
6
The Exchange Profile settings are initially stored in an xml file (created during installation); these must be
loaded 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 of
user 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 highly
recommend to delete the file after importing or to save it by using high security standards, such as
encryption.
SAP AG 2004
I mpor t i ng t he Ex c hange Pr of i l e
Import the Exchange Profile After Installation
1. Maintain connection to the Integration Server
2. Navigate to the Import page
3. Browse to:
/usr/sap/<SID>/SYS/global/exchange_profile.xml
4. Choose Import Data
The exchange_profile.xml contains sensitive
information 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 file
in case it ever needs to be reloaded. For this reason, export the file every time you change settings. From
the 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 maintenance
screen.
Note: As the file exchange_profile.xml contains secure information like passwords, it is highly
recommend to delete the file after exporting or save it by using high security standards, such as
encryption.
SAP AG 2004
Ex por t i ng t he Ex c hange Pr of i l e
8
Use the link Connection to connect to the main database of the Exchange Infrastructure. Enter the RFC
connect parameters to the Integration Server (as explained earlier). After the connection parameters are
set, 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 take
effect.
Most of the parameters are in fact for SAP internal use only, and therefore should not be changed during a
customer installation. Some of the relevant settings for customer installations are discussed on the
following slides.
SAP AG 2004
Mai nt ai ni ng Ex c hange Pr of i l e Set t i ngs
9
After any modification, the integration server will have to be restarted in order for the changes to take
effect.
For full details, see the SAP Exchange Infrastructure 3.0 Configuration Guide, available at
http://service.sap.com/instguides.
SAP AG 2004
Ex c hange Pr of i l e Set t i ngs (I )
com.sap.aii.connect landscape.httpsport
com.sap.aii.connect landscape.httpport
Connection parameters of the System Landscape
Directory server (listening for WBEM requests).
WBEM is the communication standard under CIM.
They are both defined by the Distributed
Management 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.httpport
Connection parameters of the directory server
com.sap.aii.connect.directory.name
com.sap.aii.connect.repository.rmiport
com.sap.aii.connect.repository.httpsport
com.sap.aii.connect.repository.httpport
Connection parameters of the repository server:
1. Host name
2. HTTP port number
3. HTTPS port number (optional)
4. RMI port number (used for communication with
the WebStart Client)
com.sap.aii.connect.repository.name
Connections (I)
10
After any modification, the integration server will have to be restarted in order for the changes to take
effect.
For full details, see the SAP Exchange Infrastructure 3.0 Configuration Guide, available at
http://service.sap.com/instguides.
SAP AG 2004
Ex c hange Pr of i l e Set t i ngs (I I )
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 ABAP
part 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 the
Integration Server.
com.sap.aii.connect.integrationserver.name
com.sap.aii.connect.rwb.r3.client
Connection parameters for the ABAP
part 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 the
Runtime 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 to
specific XI components by adding a list of SLD instance names inparentheses after the use case. In this case, the setting only
applies 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 system
BXI/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 to
setting the parameter secure_connections, you also have to configure the HTTPS ports of the involved components in the
Connections 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
c om.sap.ai i .c onnec t .sec ur e_c onnec t i ons
The parameter com.sap.aii.connect.secure_connections has the following
syntax:
<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 plain
HTTP.
12
For parameters relating to the J Coconnection from the J2EE engine to its R/3 instance, see the associated J Co
documentation of the related proeperties(i.e., jco.client.client, jco.client.ashost, and jco.client.sysnr).
After any modification, the integration server will have to be restarted in order for the changes to take
effect.
SAP AG 2004
I nt egr at i on Bui l der Set t i ngs (I )
Activates the Locking and Authorization
Service (this should always be " true" ).
com.sap.aii.ib.server.lockauth.activation
This flag determines whether fast RFC
should be used for connecting to the R/3
part of the SAP Web AS.
com.sap.aii.ib.server.connect.webas.r3.usefastrfc
SAP system number . This is
automatically filled during installation.
com.sap.aii.ib.server.connect.webas.r3.sysnr
SAP application server . This is
automatically filled during installation.
com.sap.aii.ib.server.connect.webas.r3.ashost
SAP client Filled with " 000" during
installation.
com.sap.aii.ib.server.connect.webas.r3.client
JCo connection from the J2EE engine to " its" R3 instance (used by the locking service):
Comma-separated list of languages used
for content documentation.
com.sap.aii.ib.client.content.languages
Comma-separated list of installed
languages.
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 areretrieved by the J2EE components of the
Exchange Infrastructure when the system is started.
If you make changes to user names and passwords, you have to make them in transaction SU01 first and
then 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 J ava mappingprograms or "xsl" for XSLT programs,
you can register additional mapping types of SAP Partners. Theseadditional mapping types enable you
to 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 in
the 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 20
characters and should only contain the characters a,...,z and A,...,Z, the numbers 0,...,9, and the
underscore "_". The caption should not exceed 25 characters. Thecaption 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
I nt egr at i on Bui l der Set t i ngs (I I )
See notes below com.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 the
Integration Repository (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 the
Integration 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 areretrieved by the J2EE components of the
Exchange Infrastructure when the system is started.
If you make changes to user names and passwords, you have to make them in transaction SU01 first and
then again in the exchange profile. See SAP note 721584 for further details.
For full details, see the SAP Exchange Infrastructure 3.0 Configuration Guide, available at
http://service.sap.com/instguides.
SAP AG 2004
Fur t her Cust omer Set t i ngs (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 by
application systems. This user
should exist on the main Integration
Server and also be associated with
the appropriate RFC destination on
application systems using SM59
(XIAPPLUSER).
com.sap.aii.applicationsystem.serviceuser.name
ApplicationSystem
com.sap.aii.mapping.parserFactory
Customers may want to use a
different XML/XSLT engine such as
XALAN/Xerces for processing
mappings.
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 the
Integration 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 areretrieved by the J2EE components of the
Exchange Infrastructure when the system is started.
If you make changes to user names and passwords, you have to make them in transaction SU01 first and
then again in the exchange profile. See SAP note 721584 for further details.
For full details, see the SAP Exchange Infrastructure 3.0 Configuration Guide, available at
http://service.sap.com/instguides.
SAP AG 2004
Fur t her Cust omer Set t i ngs (I I )
com.sap.aii.adapterframework.serviceuser.certificate
com.sap.aii.adapterframework.serviceuser.language
com.sap.aii.adapterframework.serviceuser.pwd
This user is used by the Adapter
Framework when connecting to other
servers (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
Application server of the SAP Web
AS on which the central PMI, central
CCMS and central Alert Server run.
Required for JCO connections and
HTTP connections to the monitoring
server.
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 the
Runtime Workbench (XIRWBUSER)
com.sap.aii.rwb.serviceuser.name
RuntimeWorkbench
16
SAP AG 2004
You should now be able to:
Describe the Exchange Profile and how it is used in
the Exchange Infrastructure
Detail some of the important settings in the
Exchange Profile
Import the Exchange Profile from a file.
Export the Exchange Profile to a file.
Ex c hange Pr of i l e: Uni t Summar y