Installing Remedy – new non-root Remedy Installation
I am getting ready to do a big new install again and I’ve been getting ready for a while.
Don’t get me wrong – installing a COTS product should never be hard – but at times the environment can be trying. Specifically I am installing the following:
- ARS 7.1
- AR Email Engine 7.1
- SLM 7.x
- Incident Management 7.x
- Assorted necessary support components (Assignment Engine, Etc).
In this particular customer environment I will have several challenges – they are as follows:
- The environment consists of three systems: Dev, Cat, and Prod
- The Remedy Action Request Server will reside on several servers (virtual and physical) in each of these configurations
- The operating system for all AR Servers will be Solaris
- The ARS server installs will be non-root on SAN and NAS – SAN for Prod, NAS for everything else
- The HTTP Server for the mid-tiers will be IBM HTTP Server
- The JSP/App Server will be IBM Websphere
- The report server will be Windows with BOXI
- Port Mapper is of course NOT being used.
- All server connections will be secured and the major boxes will be in a secure enclave.
Last time I did this I wasn’t blogging. I’ll post any problems I run into – last time we had several major problems – I am hoping BMC has them all worked out by now.
