In this section:
This section explains how to reconfigure the channel you created earlier to include the indexing process flow, and how to deploy that channel to start indexing your data.
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:
To reconfigure the channel, we will:
Once the channel is deployed, it is operational and the transaction indexing process begins.
This section explains how to create a new route that uses the indexing process flow you created in Creating the Indexing Process Flow.
The Routes pane opens on the right, displaying a list of available routes. The following image is an example of this pane.
The New Route Definition fields open, as shown in the following image.
The new route Construct Route pane opens. This pane lists the components registered to the route. Currently it is empty.
The Select Component Type pane opens, as shown in the following image. This pane lists the components available to the new route.
The Select a Process Definition pane opens, as shown in the following image.
The Construct Route pane opens again and lists the indexing process flow as a component of the route, as shown in the following image.
The new route now resides in the Registry.
This section explains how to modify the original channel to incorporate the new route containing the indexing process flow and to replace the outlet to direct the documents to the search engine.
The Channel Definitions pane opens, as shown in the following image, and lists the channels available in the Registry.
The Channel Construct pane opens, showing the components (inlet, route, outlet) of the selected channel. This pane with our example channel, RetailDB, is shown in the following image.
As a reminder, we want to delete the route and outlet so that we can replace them with the indexing process flow and the default outlet.
The route and outlet are removed from the channel.
The Select component type pane opens, as shown in the following image.
The select one or more route definitions pane opens, listing the available routes.
The Construct Channel pane opens showing the new route as a component.
The Select component type pane opens.
The select one or more outlet definitions pane opens, listing the available outlets.
Note: The default outlet is an empty container, which allows the emitter to be defined by the listener.
The Construct Channel pane opens showing the default outlet as a component. The following image shows the new components of our example channel, RetailDB.
The original channel has been modified to include the indexing process flow and to direct the documents moving through the process flow according to the listener definition.
This section explain how to build the modified channel and deploy it for use.
Note: If you are not in the Construct Channels pane, at the top of the iWay Service Manager console, select Registry, and in the left pane, under Conduits, select Channels. Select the modified channel and click Build.
The build results pane opens, displaying the status of the build. The following image is an example of this pane.
The Channel Management pane opens, displaying a list of deployed channels.
The status mark turns to a green check, as shown in the following image, to indicate the channel is started.
Magnify is now configured and deployed. This means the listener and indexing process flow are on alert to feed new and updated information from the data source to the search engine.
To archive an iWay workflow you must create a package, which includes an iWay Channel and all of its referenced components, such as the process flow and transformation.
The archive package is a zip file that can be saved, migrated and imported into other instances of iWay Service Manager.
Both the Bulk and Incremental process flows share the same transformation and can be overwritten.