Running Greenplum Command Center 2.x in Parallel With 3.x

Continue Running an Installed GPCC 2.x Version
Install GPCC 2.x in Addition to GPCC 3.x
Managing Concurrent GPCC 2.x and 3.x Versions

To use features of GPCC 2.x not available in 3.x, you can run a GPCC 2.x instance on a separate port on the master host and manage it independently from GPCC 3.x.

Continue Running an Installed GPCC 2.x Version

After you install GPCC 3.x:

Run gpcmdr --status to identify an available port that is not in use by a GPCC 3.x instance.
Change the symbolic link in your installation directory to the 2.x version:
```
$ ln -sfn /usr/local/greenplum-cc-web-2.x.x /usr/local/greenplum-cc-web
```
Edit $GPPERFMONHOME/instances/<instance_name>/conf/lighttpd.conf.
- Change the server.port parameter so it does not conflict with the 3.x port. For example:
```
server.port = 28090
```
- Change the seven occurrences of greenplum-cc-web to the absolute path of the 2.x installation directory. For example:
```
server.document-root = "/usr/local/greenplum-cc-web/./instances/demo/web"
```
becomes
```
server.document-root = "/usr/local/greenplum-cc-web-2.5.0/instances/demo/web"
```
Start the GPCC 2.x instance:
```
$ gpcmdr --start <instance_name>
```
Change the symbolic link in your installation directory to point to your current 3.x version:
```
$ ln -sfn /usr/local/greenplum-cc-web-3.0.0 /usr/local/greenplum-cc-web
```

Install GPCC 2.x in Addition to GPCC 3.x

After you install GPCC 3.x:

Run gpcmdr --status to identify an available port not in use by a GPCC 3.x instance.
Download the GPCC 2.5.0 installer from Pivotal Network.
Unzip and run the installer:
```
$ unzip greenplum-cc-web-2.5.0-RHEL5-x86_64.zip 
$ bash greenplum-ccweb-2.5.0-RHEL5-x86_64.bin
```
This will change the symlink at /usr/local/greenplum-cc-web to the GPCC 2.5.0 installation directory.

Note: Do not run gpccinstall, just the downloaded installer binary.
Create a GPCC 2.x instance:
```
$ gpcmdr --setup
```
Specify a port that is not used by any existing GPCC 3.x instances.
Edit $GPPERFMONHOME/instances/<instance_name>/conf/lighttpd.conf.
- Change the seven references to the greenplum-cc-web symbolic link to the absolute path of the GPCC 2.x installation directory. For example:
```
 server.document-root = "/usr/local/greenplum-cc-web/./instances/demo/web"
```
becomes
```
 server.document-root = "/usr/local/greenplum-cc-web-2.5.0/instances/demo/web"
```
Start the GPCC 2.x instance:
```
 $ gpcmdr --start <instance_name>
```
At the prompt “Do you want to start the beta server?” enter N.
Change the symbolic link in your installation directory to point to your current GPCC 3.x version:
```
  $ ln -sfn /usr/local/greenplum-cc-web-3.0.0 /usr/local/greenplum-cc-web
```

Managing Concurrent GPCC 2.x and 3.x Versions

The gpcmdr utility manages the instances for the version of GPCC in the current gpcc_path.sh. Assuming your .bashrc or other source file contains source $GPPERFMONHOME/gpcc_path.sh, to switch between versions, just modify the symbolic link greenplum-cc-web (in the /usr/local directory, by default) to point to the appropriate version.

To manage 2.x instances:

$ ln -sfn /usr/local/greenplum-cc-web-2.x.x /usr/local/greenplum-cc-web

To manage 3.x instances:

$ ln -sfn /usr/local/greenplum-cc-web-3.x.x /usr/local/greenplum-cc-web