Data Profiling

Back Next

SAP BW

To read data from SAP BW source objects, you must create a SAP BW connection to the source object.

Before you use an SAP BW Reader connection to read SAP BW data, the SAP administrator must verify the required licenses are enabled and perform prerequisite tasks. For more information about the SAP BW Reader connector administration, see the SAP Connector document.

Configure the following SAP BW connection properties to create and run a data profiling task on a SAP BW source object:

Property	Value
Runtime Environment	Runtime environment that contains the Secure Agent that you want to use to read data from SAP BW objects.
Username	SAP user name with the appropriate user authorization. Mandatory parameter to run a profile.
Password	SAP password. Mandatory parameter to run a profile.
Connection type	Type of connection that you want to create. Select one of the following values: Application. Create an application connection when you want to connect to a specific SAP BW server. Load balancing. Create a load balancing connection when you want to use SAP load balancing. Default is Application.
Host name	Required when you create an SAP application connection. Host name or IP address of the SAP BW server that you want to connect to.
System number	Required when you create an SAP application connection. SAP system number.
Message host name	Required when you create an SAP load balancing connection. Host name of the SAP message server.
R3 name/SysID	Required when you create an SAP load balancing connection. SAP system name.
Group	Required when you create an SAP load balancing connection. Group name of the SAP application server.
Client	Required. SAP client number. Mandatory parameter to run a profile.
Language	Language code that corresponds to the language used in the SAP system. Mandatory parameter to run a profile.
Trace	Use this option to track the JCo calls that the SAP system makes. Specify one of the following values: 0. Off 1. Full Default is 0.SAP stores information about the JCo calls in a trace file. You can access the trace files from the following directories: Design-time information: <Informatica Secure Agent installation directory>\apps\Data_Integration_Server\<Latest version>\ICS\main\tomcat Run-time information: <Informatica Secure Agent installation directory>\apps\Data_Integration_Server\<Latest version>\ICS\main\bin\rdtm
Additional parameters	Additional JCo connection parameters that you want to use. Use the following format: <parameter name1>=<value1>, <parameter name2>=<value2>
Port Range	HTTP port range that the Secure Agent must use to read data from the SAP BW server in streaming mode. Enter the minimum and maximum port numbers with a hyphen as the separator. The minimum and maximum port number can range between 10000 and 65535.Default is 10000-65535.
Use HTTPS	Select this option to enable https streaming.
Keystore location	Absolute path to the JKS keystore file.
Keystore password	Password for the .JKS file.
Private key password	Export password specified for the .P12 file.
SAP Additional Parameters	Additional SAP parameters that the Secure Agent uses to connect to the SAP system as an RFC client. You can specify the required RFC-specific parameters and connection information to enable communication between Data Integration and SAP. For example, you can specify the SNC connection parameters as additional arguments to connect to SAP: GROUP=interfaces ASHOST=tzxscs20.bmwgroup.net SYSNR=20 SNC_MODE=1 SNC_PARTNERNAME=p:CN=ZXS, OU=SAP system, O=BMW Group SNC_MYNAME=p:CN=CMDB_SWP-2596, OU=SNC partner system, O=BMW Group SNC_LIB=/global/informatica/104/server/bin/libsapcrypto.so X509CERT=/global/informatica/104/SAPSNCertfiles/ROOT_CA_V3.crt TRACE=2 For information about the SNC parameters that you can configure in this field, see the Informatica How-To Library article. If you have specified the mandatory connection parameters in the connection, those values override the additional parameter arguments.