Scope
The Integration Service Center (ISC) manages a hardware and software infrastructure that provides services which support integration between NIH enterprise applications and between IC based applications and NIH enterprise applications. It also provides software development expertise to assist developers in the use of these services. There are currently three components of the ISC: NIH Login, which supports single signon across a multitude of NIH applications; Enterprise Application Integration, which supports Service Oriented and Event Driven Architecture technologies used for integrating applications; and Business Process Management, which provides the capablity to model and implement business processes using standards based methodologies. All components within the ISC infrastructure are protected by a policy server which can enforce authorization requirements. The ISC also provides a set of infrastructure web services that provide access to data from enterprise systems through standards based technologies.
Expected Value
There are several benefits to centralized support and management of appilcation integration services. Providing a single hardware and software infrastructure allows NIH to take advantage of the economies of scale that it provides. NIH enterprise and IC based applications can use the ISC services at a fraction of the cost of individual purchases and decentralized support. As more and more applications use the integration services, the ISC will become a repository for meta data and schemas, ensuring that all NIH applications view data in the same way. The NIH Login service allows nearly any web based NIH application to authenticate users via the NIH Active Directory accounts, removing from the application the burden of maintaining its own userid/password directory. In the future this service will be expanded to allow applications to authenticate against sources external to NIH (e.g. univeristy registries). The application integration services will allow enterprise applications to create standard interfaces and data schemas that can invoked from applications independent of platforms and language.
2007 4th Quarter
- Complete implementation of EAI failover environment in Virginia
- Complete implementation of the "submit requisition to NBS" web service
- Work with NBS eTravel integration developers to determine the best messaging methodologies for their application and to define the required web service interfaces.
- Implement a test environment for the BPM hardware/software
- Train staff on BPM software
2008 1st Quarter
- Establish a production hardware/software environment for BPM
- Work with developers who wish to use the EAI and BPM software
- Begin testing the federated login services
- Continue working with eTravel developers
- Install and configure an XML directory for the EAI enviornment
2008 2nd Quarter
- Support the eTravel web services and interfaces in production
- Work with application developers who wish to use the EAI and BPM software in their development
2008 3rd Quarter
- Work with application developers who wish to use the EAI and BPM software in their development
- Determine feasibility of establishing a UDDI directory.
- Determine feasibility of integration the EAI XML repository with the EA repository.
This plan is subject to change as business conditions change. Please check back often. Contact us if you have questions or concerns about the Program Plan.
Last Updated:
November 16, 2007
