In the same way Agile development methodologies have lead to significant improvements in software engineering process, Situate™ Deployer applies principles and best practices to software deployment and configuration -- filling the Agile gap all the way to the customer.
Situate™ Deployer, embodies our tried-and-true process for application life cycle management, consisting of deployment, configuration management, activation and automation. By leveraging best practices, Situate delivers consistent, reproducible, error-free, runtime environments that require fewer support resources and incur less downtime. With Situate™, releases can be more frequent, allowing you to deliver the lastest functionality faster and with confidence.
In a recent use case at a major financial insituation, the principles and practices behind Situate™ were shown to significantly reduce the number of employees required to manage the release of a significant trading system. Don't throw people at a problem; leverage technology.
The deployment of a major system is often an "all hand on deck" situation, keeping everyone on call or in the office all weekend, but it doesn't have to be. Situate™ promises one button deployments, enabling a small team to effectively and confidently manage the release.
Because deployment becomes quick and reliable, upcoming releases can be pushed out more frequently, allowing you to deliver brand-new features to the business sooner.
An outage can cost you more than just the loss of business. Outages can damage your business' reputation and expose it to regulatory fines and infractions. Situate™ reduces risk.
Situate™ helps maintain auditory and regulatory requirements such as SOX. Situate™ employs a flexible security model that enables you to manage access to critical resources as well as business and operational processes. Every access or change to any resource or asset is audited and tracked.
Best practices in information security are also enforced. Situate™ only uses secure communication channels for everything it does, ensuring proprietary, trade secret and confidential data are treated appropriately.
Approved users can execute pre-defined workflows that act upon software environments. This helps minimize the number of users who require access to elevated rights to manage the application and its infrastructure.
Situate™ divides the deployment process into three separate pieces: Assemble, Deploy and Initiate. For simplicity and easy of implementation, each phase is implemented using an out-of-the-box workflow.
We know your business in unique. Principles and best practices are nice, but they are just guidelines. That's why Situate™ is built on top of our workflow engine. Using graphical tools, you can completely rewire the behavior of each phase or just tweak it here and there to optimize it for your situation and/or align it with the business process you already have in place. And, because Situate™ employs an open, plug-in architecture, third party, legacy and other components can be quickly integrated.
There are two parts to a deployment: the Strategy and the Layout. The strategy is to an application system as a blueprint is to a building. It defines each of the components, how they interact and what composes them (such as build artifacts and 3rd party dependencies).
The strategy abstracts the things in common between environments and defines application properties that change between environments.
As part of designing the strategy, configuration files are replaced with templates. When a release is assembled, these templates are "processed" by our powerful template engine, creating the proper configuration artifact customized to the environment.
Dependencies among components can also be modeled. Once deployed to an environment, dependency information will be used to genrate starup and shutdown procedures.
An environment is a runtime collection of components specificly arranged and provisioned upon real computational assets.
Templates are expanded using environment-specific parameters to create configuration dependencies for applications and middleware.
Because Situate™ understands the dependencies among components, it generates statup and shutdown producedures for the whole system as well as any piece that can be independently restarted. For certain application servers that support load ballancing, Situate™ can perform a "rolling bounce" -- restarting the system without ever having a total outage.
A project is a set of application components that follow the same development lifecycle. In other words, they are all built and relased as one unit.
Situate™ manages multiple projects, each having separate security models to allow each devlopment team the ability to manage security in a way that best makes sense for them, while still enforcing company-wide policy.
A release is an instance of a project. Once the initial release is designed, subsequent releases are created by "copying forward" the last release and applying necessary changes. One important part of the Situate™ process is that the deployment process and its configuration becomes integrated into the development and Q/A process. Just like software is pushed to Q/A for testing, so is deployment and configuration. In this way, errors and problems get fixed just like software bugs so by the time you reach production, your ability to deploy and configure are well tested.
Situate's manifest editor allows you to specify each of the pieces that make up your component.
Situate™ unifies or federates many different kinds of file systems together into one. Build artifacts and various other documents that make up your release can be pulled from any managed asset, directly from popular source control systems (such as Subversion), and/or various binary repositories.
Situate supports the ability to deploy files to jar files. For example, a .jar file can first be deployed, then a configuration item can be deployed into that jar
Sometimes data to be deployed is not built artifacts but rather created in the process of deployment. These are generated files.
Whether you have just a few or hundreds of environments, Situate makes them easy to manage. Consistent configuration is enforced through successive Q/A and test environments on its way to production. In this way, configuration errors are eliminated prior to production.
Regardless of whether you are scaling your infrastructure horizontally or vertically, Situate simplifies growth. It is easy to create environments -- development, Q/A, production or disaster recovery.
Situate provides an overarching view of all the software and their versions deployed in all your environments.
Situate is designed to be integrated and can be extended in several ways.
Get a 14 day trial edition of Situate™ and Connect to the X now and experience the world of Automation 2.0!