The Build Process: Common Ground for Developers and Administrators
Whether it's simply copying and pasting files to a Domino production server and manually setting the ACLs, or creating a complete system with quality gates and automated approvals, somehow we manage to get our Notes applications out into the world.
Usually, the focus is primarily on the development group’s build and deployment requirements, since the code starts with them. Then we try to figure out how to get the code onto a production server. However, it is just as important--if not more so--to focus primarily on the Domino administrators requirements, as 1) they are ultimately responsible for the server, and 2) most support calls go to admins first. In most organizations, the Domino Administrator is not a full-time position, but these individuals are responsible for managing their Domino servers. So, would it surprise you to hear that many issues developers face are also concerns for administrators?
(read more)
Usually, the focus is primarily on the development group’s build and deployment requirements, since the code starts with them. Then we try to figure out how to get the code onto a production server. However, it is just as important--if not more so--to focus primarily on the Domino administrators requirements, as 1) they are ultimately responsible for the server, and 2) most support calls go to admins first. In most organizations, the Domino Administrator is not a full-time position, but these individuals are responsible for managing their Domino servers. So, would it surprise you to hear that many issues developers face are also concerns for administrators?
(read more)
Compliance issues aside (although I do see this as important), there are fundamental steps that can be automated in order to reduce the time and effort administrators have to spend tracking down issues that can absolutely be avoided. These steps include, but are not limited to:
In the meantime, I'd love to hear what you would like to see what kinds of steps you'd like to have automated in your applications before they hit the production server.
- Signing databases and individual agents with the appropriate IDs
- Ensuring that the servers your agents are supposed to be running on are set properly
- Ensuring all LotusScript is compiled
- Allowing the appropriate ACL access to databases and templates
- Tracking templates and versions, so you know what versions are running and where they are stored
In the meantime, I'd love to hear what you would like to see what kinds of steps you'd like to have automated in your applications before they hit the production server.
Category Application Development Best Practices Build Process Production
| Permalink |
|
|
|
|
|
