Developing applications, services, and operations

As shown in the following figure, the IBM® InfoSphere® Information Services Director development model is based on a hierarchy of objects that define the flow of development.

Figure 1. Development model
Development model of projects, applications, services, and operations
InfoSphere Information Services Director development requires the definition of:
Projects
A project is a collaborative environment that contains applications, services, and operations. You can define some access rights at the project level such as the users who can design or deploy applications.
Applications
An application is a container for a set of services. Because the application is the unit of deployment, all services within a single application must be deployed or undeployed together.
Services
A service is composed of one or more operations. Creating services is the point of the development process at which you attach bindings. Choose a binding based on the method you use to invoke the operations from your client. Services expose results from processing by information providers such as IBM InfoSphere DataStage® servers and federated servers.
Operations
The business logic for your information service is contained in the operations. The operation describes the actual task performed by the information provider. Examples of operations include an InfoSphere QualityStage® or InfoSphere DataStage job, an IBM InfoSphere Federation Server query or invoking a stored procedure in an IBM DB2® database.