Scenario 1 of the ALE inbound sample application provides a configured
instance of the adapter and all the necessary SCA artifacts, so you are not
required to deploy the package and configure the adapter. Simply import the
.EAR file using WebSphere® Integration
Developer to your WebSphere Integration Developer workspace.
Why and when to perform this task
After you uncompress
the
nonemdsample.zip file, perform the following steps
to extract the contents of
AleCustomerInboundApp.ear and
to import the RAR file.
Steps for this task
- Uncompress the file AleCustomerInboundApp.ear to
a directory of your choice. The CWYAP_SAPAdapter.rar file
and various JAR files are now listed in the directory.
- If the connector project is not
already defined in your WebSphere Integration Developer workspace, import
the latest CWYAP_SAPAdapter.rar file in WebSphere Integration
Developer. Importing the RAR file creates a connector project for
the adapter.
- In WebSphere Integration
Developer, create a module and assign it the same name as the EAR file without
the letters “App.” For example, if the EAR file is AleCustomerInboundApp.ear,
then the module name in this case should be AleCustomerInbound.
- Extract the contents of the module JAR file into the module. If
prompted, do not overwrite the .classpath or .runtime files. For example, extract AleCustomerInbound.jar into
the module you just created called AleCustomerInbound.
- In WebSphere Integration
Developer, switch to the Business Integration perspective, right-click on
the module, and select Refresh from the pop-up menu.
You should now see all the .xsd files in the Data
Types folder.
- Do the following to associate the module with the SAP connector
project:
- Right-click the module and select Properties from
the pop-up menu.
- Select Java build path from the left-side
menu.
- Click the Projects tab and select the check box for the connector
project you created in 2
- Do the following to associate the AleCustomerInboundApp project
with the SAP connector project.
- In the Java™ perspective, right-click the AleCustomerInboundApp
project.
- Select Project References from the left-side
menu.
- Select the check box for the connector project you created in 2.
- Within the AleCustomerInboundApp project, locate the file application.xml and
open it using Deployment Descriptor Editor.
- In the Modules section, click Details.
- On the next panel, click on Add and add
CWYAP_SAPAdapter.rar.
- Press Ctrl+S to
save your changes.
- Select from the WebSphere Integration Developer menu to rebuild
the projects.
- Start up WebSphere Process Server.
- Add the project to WebSphere Process Server.
- Go to the administrative console and ensure that the application
has successfully started running.
- If any processes are not running properly, stop and restart the
server.
- Ensure that the SAP_Auth_Alias has been properly configured with
the userID and password required to log on to the SAP application.
- Using Business Object Editor, manually edit the file SapDebmas03.xsd in
the Data Types folder as follows: replace the <sapasi:MsgType/> tag
with <sapasi:MsgType>DEBMAS</sapasi:MsgType>. For details about editing business objects using the Business Object
Editor, refer to the WebSphere Integration Developer documentation.
What to do next
The adapter configuration properties are already set to the appropriate
values in the adapter instance that is provided with the example. However,
you must change the values of the following properties to suit your configuration:
Configuration
properties to set for your configuration
Property |
Type |
Globalized |
Description |
ApplicationServerHost |
String |
Yes |
When configuring the adapter to run without load balancing,
specifies the IP address or the name of the application server that the adapter
logs into. In both cases, the adapter assumes that the name of the gateway
host is the same as the value specified for this property. |
Password |
String |
Yes |
Password for the adapter’s user account on the SAP system. |
Username |
String |
Yes |
Name of the adapter’s user account on the SAP system. |
To change these values, use the WebSphere Process Server Administrative
Console.