In this section: |
You can listen for Siebel Integration Object events by configuring ports and channels. There are two methods to create an event in iWay Explorer, through the iWay Adapters tab or the iWay Events tab. This section describes both methods.
For Siebel Integration Objects, you can bypass the iWay Events tab and create an event port directly from the iWay Adapters tab.
To create an event port from the iWay Adapters tab:
The following image shows the Create iWay Event Port pane that opens on the right where you can create a port.
The following image shows the navigation pane on the left and the Specify Disposition pane that opens on the right and has information about the disposition type, a field for the disposition URL, a Help button, and three action buttons.
The following procedures describe how to create an event port from the iWay Events window for various dispositions using iWay Explorer.
The following dispositions are available when using the servlet iWay Explorer in conjunction with an iBSP implementation. You can switch between an iBSP and a JCA implementation by choosing one or the other from the drop-down menu in the upper right of the iWay Explorer.
Note: The MAIL disposition option will be supported in a future release.
The following dispositions are available when using iWay Explorer in conjunction with a JCA connector implementation.
To create an event port for Siebel Integration Objects, you must first indicate the location of the XDR schema for that object. For more information, see Creating an Event Port.
You also can create an event port directly from the iWay Adapters tab. For more information, see Creating an Event Port From the iWay Adapters Tab.
To create a specific event port for the File disposition:
The following image shows the Create New Port pane that opens on the right.
When pointing iWay Explorer to an iBSP deployment, use the following format:
ifile://[location]; errorTo=[pre-defined port name or another disposition url]
For example:
ifile://D:\in\x.txt;errorTo=ifile://D:\error
When pointing iWay Explorer to a JCA deployment, provide the full path to the directory.
The following table includes the name and description of each parameter.
Parameter |
Description |
---|---|
location |
The destination and filename of the document where event data is written, for example, D:\in\x.txt. |
errorTo |
Predefined port name or another disposition URL to which error logs are sent. Optional. |
The event port appears under the ports node in the left pane. In the right pane, a table appears that summarizes the information associated with the event port you created.
You are ready to associate the event port with a channel. For more information, see Creating a Channel.
You can call iWay Business Services created through the iWay Business Services Provider (iBSP).
To create an event port for iBSP:
The Create Event Port pane opens on the right.
The name is used to build a repository entry as well as to identify the connection.
ibse:svcName.mthName; responseTo=[pre-defined port name or another disposition url]; errorTo=[pre-defined port name or another disposition url]
The following table includes the name and description of each parameter.
Parameter |
Description |
---|---|
svcName |
Name of the service created with iBSP. |
mthName |
Name of the method created for the Web service. |
responseTo |
Location where responses to the Web service are posted. A predefined port name or another full URL. Optional. |
errorTo |
Location where error documents are sent. A predefined port name or another full URL. Optional. |
The event port appears under the ports node in the left pane. In the right pane, a table appears that summarizes the information associated with the event port you created.
You are ready to associate the event port with a channel. For more information, see Creating a Channel.
To create an event port for a JMS queue:
The Create Event Port pane opens on the right.
When pointing iWay Explorer to an iBSP deployment, use the following format:
jmsq:myQueueName@myQueueFac;jndiurl=[myurl]; jndifactory=[myfactory];user=[user];password=[xxx]; errorTo=[pre-defined port name or another disposition url]
When pointing iWay Explorer to a JCA deployment, use the following format:
jms:jmsqueue@jmsfactory;jndiurl=;jndifactory=;
The following table includes the name and description of each parameter.
Parameter |
Description |
---|---|
queue |
JNDI name of a queue to which events are emitted. |
Connection Factory |
A resource that contains information about the JMS Server. |
jndiurl |
The URL to use to contact the JNDI provider. The syntax of this URL depends on which JNDI provider is being used. This value corresponds to the standard JNDI property, java.naming.provider.url |
jndifactory |
Is JNDI context. INITIAL_CONTEXT_FACTORY and is provided by the JNDI service provider. |
user |
A valid user name required to access a JMS server. |
password |
A valid password required to access a JMS server. |
errorTo |
Location where error documents are sent. A predefined port name or another full URL. Optional. |
The event port appears under the ports node in the left pane. In the right pane, a table appears that summarizes the information associated with the event port you created.
You are now ready to associate the event port with a channel. For more information, see Creating a Channel.
To create an event port for MSMQ:
The Create Event Port pane opens on the right.
The name is used to build a repository entry as well as to identify the connection.
msmq:/host/private$/qName; errorTo=[pre-defined port name or another disposition url]
The following table includes the name and description of each parameter.
Parameter |
Description |
---|---|
host |
Machine name where the Microsoft Queuing system is running. |
Queue Type |
Private queues are queues that are not published in Active Directory. They appear only on the local computer that contains them. Private queues are accessible only by Message Queuing applications that recognize the full path name or format name of the queue. For private queues, enter Private$. |
qName |
Name of the private queue where messages are placed. |
errorTo |
Location where error documents are sent. A predefined port name or another full URL. Optional. |
The event port appears under the ports node in the left pane. In the right pane, a table appears that summarizes the information associated with the event port you created.
You are ready to associate the event port with a channel. For more information, see Creating a Channel.
To create a port for a SOAP disposition:
The Create New Port pane opens on the right.
soap:[wsdl-url];soapaction=[myaction]; method=[web service method];namespace=[namespace]; responseTo=[pre-defined port name or another disposition URL]; errorTo=[pre-defined port name or another disposition url]
The following table includes the name and description of each parameter.
Parameter |
Description |
---|---|
wsdl-url |
The URL to the WSDL file that is required to create the SOAP message. For example: http://localhost:7001/ibse/IBSEServlet/
test/webservice.ibs?wsdl where:
This value can be found by navigating to the iWay Business Services tab and opening the Service Description link in a new window. The WSDL URL appears in the Address field. You also can open the WSDL file in a third party XML editor (for example, XMLSPY) and view the SOAP request settings to find this value. |
soapaction |
The method that will be called by the SOAP disposition. For example: webservice.method@test@@ where:
This value can be found by navigating to the iWay Business Services tab, opening the Service Description link in a new window, and performing a search for soapAction. You can also open the WSDL file in a third party XML editor (for example, XMLSPY) and view the SOAP request settings to find this value. |
method |
The Web service method you are using. This value can be found in the WSDL file. |
namespace |
The XML namespace you are using. This value can be found in the WSDL file. |
responseTo |
The location to which responses are posted, which can be a predefined port name or another URL. Optional. A predefined port name or another disposition URL. The URL must be complete, including the protocol. |
errorTo |
The location to which error logs are sent. Optional. A predefined port name or another disposition URL. The URL must be complete, including the protocol. |
The event port appears under the ports node in the left pane. In the right pane, a table appears that summarizes the information associated with the event port you created.
To create an event port for an HTTP disposition:
The Create Event Port pane opens on the right.
When pointing iWay Explorer to an iBSP deployment, use the following format:
ihttp://[myurl];
responseTo=[pre-defined port name or another disposition url];
The following table includes the name and description of each parameter.
Parameter | Description |
---|---|
url | Is the URL target for the post operation, for example http://myhost:1234/docroot |
responseTo | Is the location where responses are posted (optional). |
When pointing iWay Explorer to a JCA deployment, use the following format:
http://host:port/uri
The following table includes the name and description of each parameter.
Parameter | Description |
---|---|
host:port | Is the combination of the name of the host on which the Web server resides and the port on which the server is listening for the post operation. |
uri | Is the Universal Resource Identifier (URI) that completes the URL specification. |
The event port appears under the ports node in the left pane. In the right pane, a table appears that summarizes the information associated with the event port you created.
The port appears under the ports node in the left pane.
To create an event port for an MQSeries disposition using iWay Explorer:
The Create Event Port pane opens on the right.
When pointing iWay Explorer to an iBSP deployment, use the following format:
mqseries:/qManager/qName;host=[hostname]; port=[port];channel=[channnelname]; errorTo=[pre-defined port name or another disposition url]
When pointing iWay Explorer to a JCA deployment, use the following format:
mq:qmanager@respqueue;host=;port=;channel=
The following table includes the name and description of each parameter.
Parameter |
Description |
---|---|
qManager |
Is the name of the queue manager to which the server must connect. |
qName or respqueue |
Name of the queue where messages are placed. |
host |
The host on which the MQ Server is located (MQ Client only). |
port |
The number to connect to an MQ Server queue manager (MQ client only). |
channel |
The case-sensitive name of the channel that connects with the remote MQ Server queue manager (MQ client only). The default channel name for MQSeries is SYSTEM.DEF.SVRCONN. |
errorTo |
Location where error documents are sent. This can be a predefined port name or another full URL. Optional. |
The newly created event port appears under the port section of the event adapter in the left pane.
The following procedures provide information on how to modify or delete an event port.
To edit an existing event port:
The following image shows the Edit Port pane that opens on the right. It includes a field for typing the port name, a field for typing a description, a drop-down list for selecting the disposition protocol, and a field for specifying the disposition. It also includes a Help button and two action buttons.
Note: The Edit Port pane does not allow you to change the name of the port, only the parameters.
To delete an existing event port:
A confirmation dialog box opens.
The event port disappears from the list in the left pane.
When using iWay Explorer to connect to Siebel and listen for events, a default event port is available at all times as shown in the following image.
The default event port can be used for testing purposes or when you do not want to route event data to a specific port you configured. The default port is enabled when you start a channel that does not have a specific event port assigned.
The default event data is actually a file disposition that writes to an out.xml file in the following output directory:
ifile://./eventOut/out.xml
iWay Software |