NIH Enterprise Architecture Home

Artifact Type: Pattern

A design idea that can be reused and leveraged across NIH.

Technology Architecture

Pattern: 47 related definitions

Pattern

Active Directory Pattern:
The NIH Enterprise Active Directory is a shared enterprise directory for NIH within the DHHS Forest. NIH is a multi-faceted enterprise serving a broad...
Application Program Interface (API) Pattern:
An Application Program Interface (API) is a set of calling conventions that defines how a service is invoked through software. An API enables client programs...
Broker / Operational Data Store (ODS) / Warehouse Pattern:
An Operational Data Store (ODS) is an informational database that typically stores detailed data about business events in order to support operational...
Business Partner Boundary Services Pattern:
This boundary is between NIHnet and a business partner. The business partner domain is assumed to be untrusted primarily because it is not under direct...
CAN/MAN/WAN Pattern:
CAN, MAN, and WAN, which represent one pattern are extensions of the networking capabilities performed by the LAN over a wider geographic distance. A CAN...
Complex Resource Scheduling Pattern:
Complex resource scheduling allows users to invoke their email client software to schedule resources for meetings, events (which could include a scientific/research...
Composite Applications Pattern:
A composite application seems to the user like a new application. It has some new functionality itself, plus functionality from multiple existing applications....
Data Consistency Pattern:
Modern enterprises generally have redundant versions of data regarding customers, products, orders, employees, and other entities; NIH is no exception....
Data Reporting Pattern:
This solution presents multiple options for data reporting at NIH. An NIH user can access NIH data repositories including individual databases (Oracle,...
Document Management Service Pattern:
This pattern shows how document management tools can be used to provide computerized production, storage, management and distribution of documents. Generally...
Enterprise Messaging Pattern:
The Enterprise Messaging Pattern is of a future-state of a single consolidated NIH-wide e-mail system, Central e-Mail Services (CES), which combines the...
Enterprise Service Bus (ESB) Pattern:
An Enterprise Service Bus (ESB) is a streamlined, distributed integration middleware infrastructure that combines Extensible Markup Language (XML) and...
Event Driven Architecture (EDA) Pattern:
Event-Driven Architecture (EDA) uses unidirectional messaging to communicate among two or more, largely independent peer procedures. The communication...
Federation Pattern:
The goal of NIH’s Federated Identity service is to give a person the ability to use the same user name, password, or other personal identification to access...
High-Level Enterprise Systems Management (ESM) Pattern:
This High-Level Enterprise Systems Monitoring (ESM) Pattern represents a work in progress and will continue to change as the ESM market matures and its...
High-Level Security Pattern:
The following diagram presents the security architecture patterns in an overall context. Each pattern is a definition of the security services and mechanisms...
Internet Boundary Services Pattern:
This pattern defines the boundary architecture between NIHnet and the public Internet. This boundary is where the majority of external access to internal...
LAN High Availability Configuration Pattern:
LAN High Availability Configuration Solution is for expected uptime of 99.999 percent or higher. At the device level, neighboring user devices are connected...
LAN Minimum Configuration Pattern:
LAN minimum configuration solution is for basic connectivity with expected minimum uptime of 99.5 percent. This configuration should be implemented for...
Large Scale Integration Pattern:
The Large Scale Integration Pattern illustrates the vision for the overall application integration topology at NIH. It could be decomposed into hundreds...
Level 1 System Boundary Services Pattern:
This boundary applies to Level 1 servers. These servers are generally used to provide information to external organizations and to the general public....
Level 2 System Boundary Services Pattern:
This boundary addresses Level 2 systems. These systems are generally available to NIH employees and business partners who are involved in day to day NIH...
Level 3 System Boundary Services Pattern:
This pattern addresses the requirements of the most sensitive systems within NIH. These systems contain information that is subject to HIPAA and privacy...
Network Availability Management Pattern:
Availability Management is an Enterprise Systems Management (ESM) discipline. Network Availability Management includes the administrative services performed...
Network Availablity Management - IC High-Level Logical Design Pattern:
The IC high-level logical design pattern for network availability management illustrates how monitoring systems will monitor clients, servers, printers...
Network Load Balancing End-node Configuration Pattern:
Load balancing technology is used to balance workload across servers to improve availability, performance, and scalability. Network Load Balancers are...
Network Load Balancing In-line Configuration Pattern:
Load balancing technology is used to balance workload across servers to improve availability, performance, and scalability. Network Load Balancers are...
NIH Wireless User with VPN Pattern:
NIH Wireless User with VPN Pattern Printer-Friendly Version Description The Logical Design Pattern for NIH Wireless User with VPN shows the logical view...
NIHnet/ICnet Boundary Services Pattern:
NIHnet/ICnet Boundary Services Pattern Printer-Friendly Version Description This boundary is between the NIHnet backbone and any IC sub network (ICnet)....
Remote Access Pattern:
Remote access provides the ability to securely log on to the network from a distant location through resources that are not managed by NIH. NIH personnel...
Remote Access/Wireless Boundary Services Pattern:
The remote access boundary applies to all forms of remote access including Internet or business partner VPN, dial in remote access, and wireless. By definition,...
Secure Email Middleman Pattern:
This pattern depicts an alternative method for NIH and external users to exchange secure emails that are received and read by external users when PKI-based...
Service Implementation Pattern:
The Service Implementation Pattern illustrates three alternative approaches to implementing services: Development of a completely new service implementation...
Service Orchestration Pattern:
Service Orchestration introduces state and flow control to create dynamic relationships between services that are determined at runtime, rather than the...
Service-Oriented Architecture (SOA) Security Pattern:
The SOA Security Pattern addresses security along four dimensions: Authentication – It must be possible for the service provider to ascertain the identity...
Service-Oriented Architecture (SOA) Pattern:
A service-oriented architecture (SOA) is an application topology in which the business logic of the application is organized in modules (services) with...
Shared Virtual Workspace Pattern:
This pattern shows how shared virtual workspace technologies provide formal, structured synchronous and asynchronous collaboration through, or instead...
Standalone Instant Messaging Pattern:
Instant messaging (IM) can be incorporated into other collaborative products such as portals, shared virtual workspaces and/or desktop web conferencing...
Trusted User Boundary Services Pattern:
This boundary pattern addresses the controls required for a trusted client to locally (that is, physical connection to an NIH managed network within NIH...
Web Collaboration Solution Pattern:
The Web Collaboration Solution pattern shows how Web conferencing and shared virtual workspace technologies provide formal, structured synchronous and...
Web Conferencing Solution Pattern:
The Web Conferencing Solution Pattern shows how web conferencing technologies provide formal, structured synchronous collaboration instead of formal face-to-face...
Web Content Management Service Pattern:
Web Content Management Systems (WCMS) consist of applications used to create, manage, store and deploy content on the Web, including text, graphics, video...
Web Information Access Pattern:
This solution provides access to Web information resources via a desktop Web browser. An NIH user can access NIH intranet, portal, and Internet websites...
Web Services Pattern:
Web services are a software concept and infrastructure for program-to-program communication and application component delivery. The Web services concept...
Wireless Guest User Pattern:
The logical design pattern for wireless guest user shows how a wireless guest user can access the Internet or NIH resources through the wireless gateway....
Wireless LAN Pattern:
Wireless LAN (WLAN) is a LAN communication technology in which radio, microwave or infrared links replace the physical media (i.e., wires and cables)....
Workflow/Business Process Management (BPM) Service Pattern:
This pattern shows how business process management (BPM) tools can be used to implement business processes through the orchestration of activities between...

Go to top Go to top