Scenario 1, targeted at the Application Integrator, provides a
configured instance of the adapter and all the necessary SCA artifacts, therefore,
you are not required to deploy the package and configure the adapter.
Before you begin
Since
this scenario of the sample provides an instance of the adapter that is already
configured, you simply follow the steps using WebSphere Integration Developer
to deploy and configure the adapter.
Why and when to perform this task
The adapter configuration properties are already set to the appropriate
values, however, you can change the configuration property values, including
the local host of the adapter, to suit your configuration by using the WebSphere
administrative console.
Steps for this task
- Find the EAR, acctoutApp.ear.
- Use WinZip to extract the contents to a directory. You should see
the files listed.
- In WebSphere® Integration
Developer, import the adapter RAR file. Importing the RAR creates a connector
project for the Siebel adapter.
- Update the Java™ build path so that it includes the
Siebel dependency jars.
- In WebSphere Integration
Developer, create a module. Give it the same name as the EAR file without
the “App”. For example, if the EAR is “acctoutApp.ear”, call the module “acctout.”
- Use WinZip to extract the contents of the module JAR file into
the module. For example, extract “acctout.jar” into the module called “acctout”.
In WebSphere Integration
Developer, refresh the module.
- Update the Java build path; go to the Projects tab
and check the box next to the connector project.
- Start the WebSphere Process Server.
- Once the WebSphere Process Server is started, add the project
to the WebSphere Process
Server.
- Start the WebSphere administrative console and ensure that
the application has successfully started.
- If anything has not started successfully, stop the server and
restart.
- Also, ensure that the Siebel_Auth_Alias has been properly
configured with the user ID and password required to log on to the Siebel
instance.
- To create the authentication alias on WebSphere Process Server, select
- Click New and specify the name as Siebel_Auth_Alias.
- Use the assembly editor to edit the authentication alias specified nodeName/Siebel_Auth_Alias with
the appropriate node name after you create it in WebSphere Process Server.
- For importing the inbound application acctinApp.ear file,
repeat steps 1 through 12. In addition, you must create the listener MDB class
and bind it in the acctin assembly diagram.
What to do next
The adapter properties are set to default values. You can choose
to change these, including the local host of the adapter. For the inbound
EAR file, modify the values in the
ActivationSpec. For the outbound
EAR file, modify the values in
ManagedConnectionFactory.