First Installation Preparation
The official documentation should be used for a proper preparation (
Documentation ). This is a quick checklist to improve that preparation. Each point can be a lot of work in the preparation, but it does pay off when topics are well prepared.
Identify where to store workproducts (plan docs, architecture etc)
- Identify how to communicate (tools, meetings)
- Identify how to communicate the frequent changes on workproducts (shared disk, wiki)
- Create 1 dynamic plan
- Share the plan among all stakeholders
- Update the plan frequently
- Identify risks and list them in the plan
- Assume things won't work in line with
Make an architecture image to clarify what should be installed where (
- Identify components (clients, servers, code-repositories, license servers)
- Are there any company preferred platforms (e.g. Linux for servers)
- Arrange domain names for servers ( e.g. proxy-prod.rit.company.com, rtcp-prod.rit.company.com )
- Think of what-if scenario's (backup scenario's, failing components)
- Advisable is to have a test-test-environment and a test-production environment for these components.
- Check firewalls
Identify and allocate minimum amount of people
- Identify and allocate internal leader who is in charge
- Identify and allocate internal manager who can be supportive to deliver 'additional push'. Discuss the risks with him.
- Identify and allocate employees who have access to machines and are allowed to install
- Identify and allocate employees who have authority to do DB-admin tasks
- Identify and allocate the employee who represents the users.
- Reserve (virtual/cloud) Machines
- Check minimum specification for each product (validate if OS is supported!)
- Linux: Is a GUI available?
- Userid's / Passwords
- Do we have the right userid's passwords (e.g. with admin privileges)
- Can we access the code-server from the machines
- Download Applications from Passport Advantage
- Unzip them into separate folders to proof correct downloads
- Get appropriate licenses
- Check firewalls between license servers and users of licenses
- Verify correct installation of licenses on the server
- Internet access
- Do we have internet (www) access. Very handy if things fails to search for error and solutions. Creating PMRs.
- Get IBM Support
- Identify how you can communicate with IBM Support (PMRs). Especially who is allowed to create PMRs!
While preparing, create your own check list/action list. Update with your own experience and specifics (e.g. contact details).
This is not an upgrade scenario! It can be used as input for the preparation of an upgrade scenario.