Home > Articles > Software Development & Management

  • Print
  • + Share This
This chapter is from the book

Deployment Models

There are a number of ways to deploy OIS in your environment. However, most implementations of OIS will fit into a small set of deployment models. The following sections will list the most common models for deploying OIS, explain where each model is best suited, and present the relative advantages and disadvantages of each.

Simple Deployment

The simple deployment model is the simplest and most basic deployment model for OIS. This model has all the OIS components installed on one server and can use either an existing SQL server or it might also have SQL running on the OIS server. Figure 3.5 shows a diagram of a simple OIS deployment.

Figure 3.5

Figure 3.5 Simple deployment model

This model is best suited for a proof of concept, or a limited pilot, and you can use it in a testing environment. However, the simple deployment model is not recommended for a production environment, as it does not provide any fault tolerance for the OIS components. In this model, you normally install all the OIS components on a single server and use an existing SQL instance to host the OIS datastore. If the datastore is also installed on the OIS server, the entire system is at risk if there is a failure.

Here are advantages of this model:

  • Simplest model to install and configure
  • Can run every component on a single server or virtual machine (VM)
  • Limits licensing required

Here are the disadvantages:

  • Does not provide policy failover
  • All automation stops when server is offline
  • Becomes a single point of failure especially if SQL is installed on the same server

Resilient Deployment

The resilient deployment model is most commonly used. This model is suitable from small businesses to large enterprises. The resilience is provided by having two or more Action Servers and clustering SQL Server. In this model the OIS components, the datastore, and automation targets are all on a centralized high-speed network.

For the purposes of this book, a centralized high-speed network is one in which average communication takes place in less than 50ms, and there is little or no data loss. Figure 3.6 shows a diagram of a resilient deployment model.

Figure 3.6

Figure 3.6 Resilient deployment model

This model is well suited for any implementation where the OIS components, datastore, and automation targets are all a centralized high-speed network.

Here are advantages of this model:

  • Provides policy failover by having multiple Action Servers
  • Provides resilient SQL through SQL clustering
  • Provides a separate server to run the Action Server Watchdog service and provides alerting if an Action Server should fail
  • Offers greater flexibility with additional Action Servers

Here are disadvantages:

  • Additional resource demands because of extra Action Servers
  • Additional resource demands from SQL clustering
  • Additional management burden

Cross-Network Deployment

The cross-network deployment model is one in which Action Servers can reach across the network to perform automation on targets. This model is suitable for mid-size businesses or enterprises where remote sites have targets that require automation and are connected by a high-speed remote network, but these remote sites are ones in which it would be impractical or impossible to deploy an Action Server. Resilience is provided by having two or more Action Servers and by clustering SQL. In this model, the OIS components and the datastore are all on a centralized high-speed network and the automation targets are on high-speed remote networks.

For the purposes of this book, a high-speed remote network is one in which average communication takes places in less than 200ms, and there is little or no data loss. Figure 3.7 shows a diagram of a cross-network deployment model.

Figure 3.7

Figure 3.7 Cross-network deployment model

This model is suited for any implementation where the OIS components and datastore are on a centralized high-speed network and where automation targets are on high-speed remote networks. Because not all objects will work over a remote network (see the "Caution" note in this section), this model might not be possible in every environment where it is desired.

Here are advantages of this model:

  • Provides policy failover by having multiple Action Servers
  • Allows Action Servers to reach into other networks to perform automation, especially when the Action Server cannot be placed in the remote network
  • Provides resilient SQL through SQL clustering
  • Provides a separate server to run the Action Server Watchdog service and provides alerting if an Action Server should fail
  • Offers greater flexibility with additional Action Servers

Here are disadvantages:

  • Additional resource demands because of extra Action Servers.
  • Additional resource demands from SQL clustering.
  • Not all policy objects can tolerate this model.
  • Requires additional configuration of firewalls to allow traffic from any of the objects used to pass between sites.
  • Additional management burden.

Cross-Network Action Servers

The cross-network action server model is one in which Action Servers are placed on a remote network to perform automation on targets there. This model is suitable for mid-size businesses or enterprises where remote sites have targets that require automation and they are connected by a high-speed remote network; these remote sites are ones in which it is possible deploy an Action Server. Resilience is provided by having two or more Action Servers and by clustering SQL. In this model, the Management Server, Action Server Watchdog, and the datastore are all on a centralized high-speed network, and the Action Servers are on high-speed remote networks with the automation targets. Figure 3.8 shows a diagram of a cross-network action server model.

Figure 3.8

Figure 3.8 Deployment with Action Servers across networks

This model is suited for any implementation where the Management Server, Action Server Watchdog, and datastore are on a centralized high-speed network and where the Action Servers can be placed on the same high-speed remote network where the automation targets are located. This model requires that the remote network latency be less than 200ms. There must be little or no data loss; otherwise, this model will fail. Latency speeds in the 10-30ms range are recommended.

Here are advantages of this model:

  • Provides policy failover by having multiple Action Servers
  • Allows Action Servers to reside on remote networks to perform automation, assuming the network performance allows this
  • Provides resilient SQL through SQL clustering
  • Provides a separate server to run the Action Server Watchdog service and provides alerting if an Action Server should fail
  • Can be used in some environments where the cross-network deployment model cannot

Here are disadvantages:

  • Additional resource demands because of extra Action Servers
  • Additional resource demands from SQL clustering
  • Action Servers will tolerate only excellent network conditions in this model; without excellent conditions they will lose connectivity to the datastore
  • Requires additional configuration of firewalls to allow SQL traffic between the sites
  • Additional management burden

Multisite Manual Policy Sync

In some environments, the network performance will not be suitable to separate Action Servers from the datastore. If this is the case, it will be necessary to have one installation of the OIS components, including the datastore, at each location that requires automation. OIS installations are always standalone, and they will not communicate natively or share any data between installations (even when on the same network).

A multisite manual policy sync model is one where two or more installations of OIS are in use and there is a requirement or desire to use the policies on all installations. Because these installations will not be able to communicate with one another natively, policies that need to be shared must be exported manually and imported at the target OIS installation. This model provides a method to transfer policies but not policy data. Figure 3.9 shows a diagram of multisite manual policy synchronization.

Figure 3.9

Figure 3.9 Manual policy sync model

This model is best suited for environments where network conditions require several installations of OIS and these installations need to transfer policies with one another. Using a manual process to transfer policies between is not a desirable solution given the effort involved, but if more than one installation is required, there is no other way to transfer the policies.

Here are advantages of this model:

  • Provides a method for using the same policies on remote OIS installations
  • Can provide uniform automation to several remote sites
  • Has all the advantages of a resilient model
  • Offers flexibility in what policies are loaded to which installation

Here are disadvantages:

  • No policy or state data is shared between installations.
  • Requires manual effort to import or export policies.
  • Installations have potential to become out of sync with one another.

Multisite Invoke via Web Services

In some environments, the network performance will not be suitable for Action Servers to be separate from the datastore. In this case, it will be necessary to have one installation of the OIS components, including the datastore, at each location that requires automation. OIS installations are always standalone and will not communicate natively.

A multisite invoke via Web Services model is one where the OIS installations communicate with one another over Web Services during custom policy execution. By installing the OOC, taking advantage of the Web Services, and building custom policies to use these components, you can have two standalone instances of OIS trade data or call actions on one another. Figure 3.10 shows a diagram of a multisite model using Web Services invocation.

Figure 3.10

Figure 3.10 Multisite invoke via Web Services

This model is best suited for environments where data needs to be shared between OIS installations or where one OIS installation provides a critical service to others (such as trouble ticket creation).

Here are advantages of this model:

  • Allows policies to interact with remote installations and networks
  • Allows OIS data to be shared between remote installations
  • Has all the advantages of a resilient model
  • Allows any networked OIS instance to trigger a specific function on another OIS instance
  • Offers flexibility in having differing policies at different locations
  • Allows policy execution across untrusted environments by providing credentials at the connection point using the Invoke Web Services object

Here are disadvantages:

  • Requires special development of all policies to accept or transfer data
  • Requires the Operator Console be installed on target OIS systems
  • At risk for failure if network connection is lost

Multisite Hybrid Solution

The multisite hybrid solution is a combination of both the multisite manual sync and the invoked Web Services model. It provides a method to use the same policies in separate installations while also allowing those installations to communicate with one another at runtime and share data. Figure 3.11 shows a diagram of a multi-site hybrid solution.

Figure 3.11

Figure 3.11 Multisite hybrid solution

This model is best suited for environments where data needs to be shared between OIS installations or where one OIS installation provides a critical service to others (such as trouble ticket creation) while also providing common policies to multiple installations.

Here are advantages of this model:

  • Provides a method for using the same policies on remote OIS installations
  • Can provide uniform automation to several remote sites
  • Has all the advantages of a resilient model
  • Allows policies to interact with remote installations and networks
  • Allows OIS data to be shared between remote installations
  • Offers flexibility in what policies are loaded to which installation

Here are disadvantages:

  • Requires special development of all policies to accept or transfer data
  • Requires the OOC be installed on target OIS systems
  • Requires manual effort to import or export
  • At risk for failure if network connection is lost
  • Installations have potential to become out of sync with one another

Multisite Isolated Deployment

If your environment's network performance is not suitable to separate your Action Servers from the datastore or security limitations make this a necessity, but you still need automation on remote sites, you will use an isolated deployment. In this situation, you will need to use a multisite isolated deployment model. This model is simply several unrelated installations that share no information or policy imports. Figure 3.12 shows a diagram of an isolated multisite OIS deployment model.

Figure 3.12

Figure 3.12 Isolated multisite OIS model

This model is used only when there is no desire or no way to share data or policies between installations. This model is rarely used.

Here are advantages of this model:

  • Each installation is highly available
  • Provides resilient SQL through SQL clustering
  • Has all the advantages of a resilient model
  • Provides a separate server to run the Action Server Watchdog service and provides alerting if an Action Server should fail

Here are disadvantages:

  • No data is shared between installations
  • All policies are designed and implemented separately
  • Additional maintenance burden
  • No policies are shared between installations
  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020