To set connection properties for the external service wizard so
that it can access the SAP server,
specify information such as, the user name and password you use to
access the server as well as the name or IP address of the server.
Before you begin
Make sure you have successfully added the software dependency
files (the sapjco3.jar and associated files).
About this task
Specify the connection properties that the
external service wizard needs
to establish a connection to the
SAP server and
discover functions or data.
To specify the connection properties,
use the following procedure.
Procedure
- From the Select the Processing Direction window,
Select Inbound (if you are going to send data
from the SAP server)
or Outbound (if you are going to send data
to the SAP server)
and click Next. The Specify the Discovery Properties window
is displayed.
- From the Specify the Discovery Properties window,
specify the configuration properties:
- In the Host name field, type
the name (or IP address) of your SAP server.
- Optionally, change the default value for System
number.
- Type your client ID (or use the default value if your
client ID is 100).
- If necessary, change the default setting for Language
code by clicking Select and selecting
a value from the list.
The default value in the Code
page field is related to the value in the Language
code field. For example, if the language code is EN
(English), the code page number is 1100.
If you change the language code to TH (Thai), the
code page number changes to 8600.
Note: You will only get a listing of IDocs in the language
selected. The error messages will be displayed in the specified language.
- Type the name and password you use to access the SAP server.
The password is case-sensitive.
- Choose an interface from the following SAP
interface name options:
- Advanced Event Processing (AEP), ALE, ALE pass-through IDoc or
BAPI for Inbound, or
Figure 1. SAP interfaces
- inbound
- Advanced Event Processing (AEP), ALE, ALE pass-through IDoc, BAPI,
BAPI work unit, BAPI result set or Query interface for SAP Software
for Outbound
Figure 2. SAP interfaces - outbound
Note: This option is not available if you are modifying existing
artifacts.
- Optional: To set additional
advanced properties, click Advanced.
- To set RFC tracing properties,
perform the following steps:
- Expand SAP RFC trace configuration and
select RFC trace on.
- Select the Write JCo traces into adapter
logs checkbox to enable JCo API traces to be generated
in the broker trace file. These traces will then be interleaved with
the adapter traces. Each JCo API trace logged into the broker trace
file will have the string [JCoAPI]. All JCo API traces
are logged at the INFO message log level.
- Select a tracing level from the RFC trace
level list.
- Click Browse and select a location
to which the RFC trace files will be saved.
Note: Enabling
RFC tracing in turn enables CPIC tracing as well. CPIC tracing cannot
be disabled individually.
Note: To avoid tracing files getting
created in multiple locations, create an environment variable (for
example RFC_TRACE_DIR) and set it to a valid folder.
If a value
is set for the environment variable RFC_TRACE_DIR, all RFC will be
generated in the folder set in the environment variable RFC_TRACE_DIR
All
CPIC traces will be generated in the current working directory.
If
the environment variable RFC_TRACE_DIR is not set, traces generated
are saved under the folder <IID_ROOT><RAD_ROOT>.. This is the top-level
folder of your IID installation. For example, C:\IBM\IID7.5
- Optional: To enable
bidirectional support for the adapter at run time:
- In the Bidi properties area,
select Bidi transformation.
- Set the ordering schema, text direction, symmetric swapping,
character shaping, and numeric shaping properties to control how bidirectional
transformation is performed.
- To configure Business Object name generated by the adapter
for the BAPI Modules, expand Business Object naming configuration and
select the required options from the following:
- Check the Generate
business objects according to SAP naming conventions checkbox
to have the adapter to generate all the Business Object names same
as that of the SAP XI standard. This option is applicable only for
BAPI outbound processing.
- By default, the Enforce the same naming convention
for business objects checkbox is selected to have the
adapter generate all the Business Object names without appending any
hashcode. The hashcode is appended to the namespace of each Business
Object instead of the name.
- Do not check the Enforce the same naming
convention for business objects checkbox to have the adapter
append the hashcode to the subsequent Business Object that has the
same name. This is done to avoid duplication.
For more information on naming conventions, refer to Naming conventions for BAPI business objects
- Optional: To change
the location of the log files for the wizard or the amount of information
included in the logs, click Change
the logging properties for the wizard,
and then provide the following information:
- In Log file output location,
specify the location of the log file for the wizard.
- In Logging level, specify the
severity of errors that you want logged.
Note: This log
information is for the wizard only; at run time, the adapter writes
messages and trace information into the standard log and trace files
for the server.
- Click Next.
Results
The
external service wizard contacts
the
SAP server,
using the information you provided (such as user name and password)
to log in. You see the
Find Objects in the Enterprise System window.
What to do next
Specify search criteria that the
external service wizard uses
to discover functions or data on the
SAP server.