HOMEBASE SOLUTION COMMISIONING GUIDE
3 Deployment Guidance
3.1 Introduction
Critical to the success of deploying a Homebase solution within a business is
understanding and planning for the deployment process.
The deployment plan should consider and make allowances for:
1. Understanding the Homebase profile repository.
2. The physical location of the servers to be covered by Homebase
3. The Homebase server agent to Homebase server communication protocol
to be used
4. The location of any Homebase Proxy servers
5. The network connectivity required to support the Homebase deployment
topology
6. The configuration of the Homebase servers
7. The configuration of Homebase server communication interfaces
8. The configuration of supporting IT services.
9. Business access to the Homebase servers
Each of these elements will have varying impact of the final solution in the
deployment plan, depending on the choices the business makes. They are
presented in no particular order, but represent a “logical flow” through the
deployment process.
A brief overview of the Homebase deployment choices that is available in a
Technical Blue Book, titled Homebase Deployment Architectures.
3.2 Understanding the Homebase profile repository
All profiles received, validated and accepted by a Homebase server are stored
in a hierarchical repository. The determination of where a received profile is
situated in the repository is based on information held with the license key of
any Homebase Server agent.
The hierarchy is structured as follows:
[country] – [company] – [location] – [site]
For example, for a profile that is taken from a server located at the Indigo
Stone head office at Witney in the United Kingdom the following would be a
typical hierarchy entry:
[uk] – [indigostone] – [witney] – [headoffice]
All servers transmitting profiles from this site would be situated under the head
office entry of the hierarchy.
© INDIGO STONE INTERNATIONAL LIMITED 4
