The second sample application that is discussed in this section is a simple application that enqueues (pushes) data to a newly-created Watson Explorer Engine search collection that is based on the default-push collection that is provided with Watson Explorer Engine. The data is created manually within the application. The application then queries that collection to ensure that the enqueued data was indeed indexed and can be successfully located by a search.
As introduced in Components of an End-User Watson Explorer Engine Application, traditional Watson Explorer Engine applications, such as the one discussed in the previous section of this chapter, crawl a remote data source and return data from that source so that it can be indexed and eventually searched. Applications that follow this model are commonly referred to as pull applications because they retrieve data from a remote source for indexing. Applications such as the one discussed in this section are referred to as push applications, because they manually enqueue data or URLs by pushing them to a Watson Explorer Engine server. The crawler on that server performs any additional data retrieval and processing that is required, and then passes the normalized data on to the indexer for indexing. The sample application that is discussed in this section directly enqueues data that it creates; the sample application discussed in the next section (Example: XmlPush Application) enqueues data that is read from files and which is therefore associated with the URL of each file.