Setting connection properties for the J2C Bean wizard

To set connection properties for the J2C Bean 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.

1. From the Adapter Style 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 Discovery Configuration window is displayed.
2. Optional: Event monitoring is available to your application only if you have Business Monitor or WebSphere® Business Events installed in your environment.
   • Use the following procedure, to generate and monitor common base events and manage these events with the Common Event Infrastructure (CEI) services using Business Monitor:
     1. Select the Enable Inbound Event Monitor check box and then click Next. The Event and JMS configuration window is displayed.
     2. In the Event type field, select WebSphere Business Monitor.
     3. In the Queue connectionFactory JNDI name field, accept the default value, jms/cei/EventQueueConnectionFactory.
     4. In the Queue JNDI name field, accept the default value, jms/cei/EventQueue.
     5. Click Advanced to add advanced properties.
     6. In the Remote JNDI provider configuration section, specify the naming provider URL host name and port name values in the Naming provider URL Host and Naming provider URL port fields to connect to the remote WebSphere Application Server from the wizard.
     7. In the Connection authentication configuration section, type the user name in the User name field to connect to the server from the wizard.
     8. In the Connection authentication configuration section, type the password in the Password field to connect to the server from the wizard.
     9. Click Next. The Discovery Configuration window is displayed.
   • Use the following procedure, to generate and monitor common base events and manage these events using WebSphere Business Events:
     1. Select the Enable Inbound Event Monitor check box and then click Next. The Event and JMS configuration window is displayed.
     2. In the Event type field, select WebSphere Business Events.
     3. In the Topic connectionFactory JNDI name field, accept the default value, jms/WbeTopicConnectionfactory .
     4. In the Topic JNDI name field, accept the default value, jms/WBE/CbeListener.
     5. Click Advanced to add advanced properties.
     6. The Remote JNDI provider configuration field is used to configure the remote topics.

        If the bus in the local cell has the same name as the bus in remote cell, the application always connect to the local cell. It does not use any of the provider endpoints specified on the connection factory, so the Remote Topic Configuration information that you enter is ignored. For more information about remote Topic Configuration, refer to http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.pmc.doc/tasks/tjn0033_.html .

     7. In the Naming provider URL Host field, specify the naming provider URL host name to connect to the remote WebSphere Application Server from the wizard.
     8. In the Naming provider URL port field, specify the naming provider URL port name to connect to the remote WebSphere Application Server from the wizard.
     9. In the Connection authentication configuration section, type the user name in the User name field to connect to the server from the wizard.
     10. In the Connection authentication configuration section, type the password in the Password field to connect to the server from the wizard.
     11. Click Next. The Discovery Configuration window is displayed.
3. From the Discovery Configuration window, specify the configuration properties:
   1. In the Host name field, type the name (or IP address) of your SAP server.
   2. Optionally, change the default value for System number.
   3. Type your client ID (or use the default value if your client ID is 100).
   4. 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.
   5. Type the name and password you use to access the SAP server.

      The password is case-sensitive.

   6. 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.
4. Optional: To set additional advanced properties, click Advanced.

5. To set RFC tracing properties, perform the following steps:
   1. Expand SAP RFC trace configuration and select RFC trace on.
   2. 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.
   3. Select a tracing level from the RFC trace level list.
   4. 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 <RAD_ROOT>.. This is the top-level folder of your IID installation. For example, C:\IBM\IID7.5

6. Optional: To enable bidirectional support for the adapter at run time:
   1. In the Bidi properties area, select Bidi transformation.
   2. Set the ordering schema, text direction, symmetric swapping, character shaping, and numeric shaping properties to control how bidirectional transformation is performed.
7. 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:
   1. 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.
   2. 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.
   3. 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

8. Optional: To change the location of the log files for the wizard or the amount of information included in the logs, click Specify the level of the logging desired, and then provide the following information:
   1. In Log file output location, specify the location of the log file for the wizard.
   2. 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.
9. Click Next.