This section explains how to reconfigure the original channel (created in Configuring an iWay Channel), which was used to extract the data source document structure. We reconfigure the original channel because it contains and has generated information that is necessary to the indexing process, such as, the name of the channel. The same channel must be used because the xml files created earlier contain the name of the channel, and the xPaths used in the config are connected to these files.

Basically, reconfigurIng the channel allows you to include the indexing process flow as the new route of the channel and to redirect the output of the channel to the search engine rather than a directory. All tasks are preformed in the iWay Service Manager console.

As a reminder, the original channel was configured with the following elements:

• Inlet. Contained the data source listener. In our example, the inlet name and the listener name was the same, RetailDB.
• Route. Was the default route, move, which moved the document from the inlet and listener to the outlet without additional processing.
• Outlet. Was named RetailDB_Outlet and contained a file emitter (named RetailDB_FileEmitter) that deposited XML files into the designated directory.

To reconfigure the channel, we will:

• Create a new route that uses the indexing process flow (named Retail_Route).
• Modify the original channel, as follows:
  • Undeploy the original channel.
  • Delete the original route and outlet from the channel.
  • Add the new indexing process flow route to the channel.
  • Add the iWay Service Manager default outlet (default.outlet).
• Build the new channel.
• Deploy the new channel.

Once the channel is deployed, it is operational and the transaction indexing process begins.