Quick steps for the ALE Module

Before you configure the ALE Module, create the following persistent WebSphere MQ queues:

Refer to the MQ Series documentation for information on creating MQ Queues.

Next, configure the following connector-specific properties:

Property Name Default Value Value Needed
Modules none Ale
AleEventDir none %CROSSWORLDS%\connectors\SAP\ale
SAPtid_QueueManager none <Queue Manager name>
SAPtid_Queue none <Queue name>
SAPALE_Event_Queue none <Event Queue name>
SAPALE_Wip_Queue none <WIP Queue name>
SAPALE_Archive_Queue none <Archive Queue name>
SAPALE_UnSubscribed_Queue none <UnSubscribed Queue name>
SAPALE_Error_Queue none <Error Queue name>
RfcProgramId none <Program ID name defined in SAP Transaction sm59>
NumberOfListeners 1 1 (for single-threaded)

For remote WebSphere Queues, also configure the following properties:

Property Name Default Value Value Needed
SAPtid_QueueManagerLogin none <Queue Manager login>
SAPtid_QueueManagerPassword none <Queue Manager password>
SAPtid_QueueManagerHost none <Queue Manager host>
SAPtid_MQPort none <MQ port>
SAPtid_MQChannel none <MQ channel>

Generating a business object in the ALE Module

To generate a business object in the ALE Module:

  1. Start the SAP ODA.
  2. Start the business object designer.
  3. In the business object designer, choose File > New. The wizard starts.
  4. Select Configure Discovery:
    1. Enter the host address for the machine where Discovery is running.
    2. Choose Add Host.
    3. Choose OK.
  5. In Step 3 of the wizard, expand IDoc Types.
    1. Expand Generate From System.
    2. Expand Basic IDoc Types.
    3. Right-click Select by Name...
    4. Select Search for Items...
    5. Type orders03. Choose OK.
  6. Highlight ORDERS03. Choose Next.
  7. Choose Next.
  8. Choose OK. The business object generates.
  9. Select "Save a copy of business object definitions to a separate file" and select "Open new business object definition to a separate window". Choose Finish.

Editing the business object

To edit the business object:

  1. Choose the General tab.
  2. Change Create Application-specific information message type to MsgType = ORDERS.
  3. Open %CROSSWORLDS\repository\SAP\BO_SAPIDocControl.txt and save it to the Repository directory.
  4. Add the parent object name to the Supported Business Objects section of the configuration file.
  5. Register the RFC Server Module with the SAP Gateway, using SAP transaction SM59.
  6. Ensure the following:

Preparing the ALE Module for testing

To set up the ALE Module for testing, use Port Connector:

  1. Copy the SAP configuration file. Rename the copied file portconnector.cfg.
  2. Open portconnector.cfg in Connector Configurator.
  3. Change the following properties in the Standard tab:
  4. Save changes. Close portconnector.cfg.
  5. Open sapconnector.cfg.
  6. Save the change. Start mySAP.com.

Testing request processing for the ALE Module

To test the ALE Module:

  1. Open Test Connector.
  2. Choose File > Create/Select Profile.
  3. Choose File > New Profile.
  4. Select Browse.
    1. Choose Open.
    2. For Connector Name, enter PortConnector.
    3. For Broker Type, enter WMQI.
    4. Choose OK.
  5. Highlight PortConnector. Choose OK.
  6. Choose File > Connect.
  7. Create a business object instance:
    1. For BO Type, select sap_order03.
    2. Choose Create.
    3. In Enter Name, type new object. Choose OK.
  8. Change the verb to Create.
  9. Right-click Control Record. Choose Add Instance.
  10. Expand Control Record. Populate these fields:
  11. Start the connector.
  12. In Test Connector, choose Request > Send. Check the log for a success message.

Testing event processing in the ALE Module

To test event processing in the ALE Module:

  1. Go to transaction we19, Test Tool for IDoc processing.
  2. Populate the field with an existing IDoc. Choose IDoc > Create.
  3. Choose StandardOutboundProcessing to send an IDoc to the test connector.
  4. In the pop-up window, choose the check mark.
  5. To verify that the IDoc was sent from SAP, check the mySAP.com connector log file for a success message. If the event exists in transaction sm58, then it was not sent correctly.
  6. View the message that was sent to the SAPALE_Archive_Queue to verify that the ProcessingStatus was successful. If you do not see a success message, check the SAPALE_Error_Queue to see if a failure occurred.

Copyright IBM Corporation 1997, 2004. All Rights Reserved.