It is possible to do this, with two changes that must occur:

• First make sure that you have two different port numbers for your installations. The same rules apply; the Port number must be between 1024 and 65535 and each must be a unique number. During installation, the installer attempts to detect if you already have an existing installation running, and will refuse to allow you to use the same port number. However, if the first installation is shutdown it will not be detected, so you need to make sure to use a different port number. You can find the port number of an installation by looking in $OSP_HOME/bin/etc/ospenv.sh, it's the value of OSP_PORT.
• Second is the licensing issue. The thing to do here is to only run one osp flexlm daemon at a time. To do this, start whichever version is your main release (we'll assume v2.5.0), start v2.5.0 as normal. In your v2.4.x Installation, when you start your Shared Services, do the following:

$OSP_HOME/bin/runOSServices.sh nolicense start

The "nolicense" option will cause the startup to look for an already running osp daemon, which will be the one from your v2.5.0 installation.

NOTE: The v2.5.0 version of the runOSServices.sh no longer uses the "nolicense" option.

This typically happens in the following cases:

1. During installation, the host name was incorrectly specified and various files were generated with the incorrect host name of the server installation.
2. After an installation has been used for various reasons, you want to run the server installation on another host.
3. You are making client installations that cannot resolve the host name and you want to replace the host name with an IP address that can be resolved on the client installations.

Either reinstall OpenSpirit or follow the instructions below to edit your server side installation. If you haven't started the shared services by running "$OSP_HOME/bin/runOSServices.sh start", then this is much simpler and only some of the steps need to be executed.

If OpenSpirit version is v3.x.x, then, you should modify the host via the OpenSpirit Desktop's Installation Admin Tool.

If OpenSpirit version is v2.7.0 - v2.9.4

• Check the $OSP_HOME/classes/License.properties and be sure it has the right port@host if you are running the FlexLM license daemon on a different host.
• Modify the OSP_HOST in the $OSP_HOME/bin/etc/ospenv.sh and ospenv.csh files to replace one occurrence in each file of the old host name with the new host name.
• Modify the openspirit.orb.host line in the $OSP_HOME/classes/ospenv.properties file with the new host name.

If you have already run "$OSP_HOME/bin/runOSServices.sh start"(even if they have been run just once) and your OpenSpirit version is v2.6.3 or lower

• Have all OpenSpirit users stop their servers and clients, then stop all services using "$OSP_HOME/bin/runOSServices.sh stop".
• Run $OSP_HOME/bin/cops.sh to delete *all* the persistent objects, including the EpCoordinateService and EpUnitOfMeasureService objects. WARNING: This will remove all your users' sessions and their associated unsaved data, so warn them first!
• Do all of the file modifications listed above.
• Restart the OpenSpirit services by running "$OSP_HOME/bin/runOSServices.sh start".
• NOTE: if you have any Windows installations which were based on the re-hosted server installation, you will now need to modify each of the Windows installations as well. You can either remove and re-install the Windows installation (probably the simplest option) or make these changes to each Windows installation:
  • Modify the system environment variable OSP_HOST value to the new server installation host name.
  •  Modify the %OSP_HOME%classesLicense.properties file to have the correct port@host.
  • If the new OpenSpirit server installation has a different OSP_HOME than the original server installation, you will also need to modify the %OSP_HOME%classesOpenSpirit.properties file, changing the "openspirit.installation.master.home" value to the new OpenSpirit server installation location.
  • The Windows machine will need rebooting to pick up the environment variable change. 

NOTE: If you are relocating $OSP_HOME, you MUST also make the following changes OpenSpirit. In rare cases you may need to relocate the Oracle database instance in which the OpenSpirit table space resides.

For example, you installed OpenSpirit in /home/prod/OpenSpirit and want to move it to /apps/OpenSpirit. You also have to modify:

• $OSP_HOME/external/OpenFusion/classes/openfusion.properties (v2.5.x only)
• $OSP_HOME/classes/OpenSpirit.properties
• $OSP_HOME/bin/etc/ospenv.sh
• $OSP_HOME/bin/etc/ospenv.csh
• $OSP_HOME/classes/ospenv.properties

Each of these files must be modified in order to show what your new $OSP_HOME is.

We do not recommend that you do an OpenSpirit installation as root. The root userid is a special account that should not own an installation and the processes that run from that installation.

If you did an install as root and now want to change the ownership of the installation to another user, you need to do the following as root:

• Have all OpenSpirit users stop their servers and clients, then stop all services using "$OSP_HOME/bin/runOSServices.sh stop".
• Change ownership of the files from the top level to the userid that will now own the OpenSpirit installation. Note that you do not need to change the file permissions. After installation you should leave them as they were.
• Update the following Oracle table in the OpenSpirit table space.
  • First, set up a proper Oracle environment; this will allow you to access the Oracle instance where the OpenSpirit table space was installed. Also, make sure you know the account that has access to that table. If you need help finding this information please contact support@openspirit.com.
    • Update OSP_USER_ALIAS set alias_login='' where alias_login='root'
    • Update OSP_USER set master_login='' where master_login='root'; 4.
• If you plan on starting up the OpenSpirit shared services at boot time, then you will also want to modify $OSP_HOME/bin/etc/OpenSpirit_init.d because this will still refer to the root userid.

If you are sure that you no longer need any of the data in your desired table space, it is possible to clean out the table space so that it may be used for a new OpenSpirit installation.

You can download the script:

ADSClean.sh 

Modify site-specific values at the top of the script, and then run it to clean out all the data from your OpenSpirit tablespace

Warning: This will cause all of the data and tables to be removed from the table space, so use this script with great caution. Be sure that you are aware of what you're doing and that you are providing a table space that was previously used for OpenSpirit. This is not intended to clean out any table space, just one that was previously created for specific use with OpenSpirit.

We use a third party installer called InstallAnywhere, which is generally very robust. However, if problems do occur, they generally fall into one of two categories:

Installer says that there isn't enough disk space for an installation, but you are positive that you do have enough space

InstallAnywhere attempts to determine if a disk partition is large enough, but this check can sometimes fail (it generally gets confused on certain types of automounted partitions).

You can turn this check off by setting the environment variable CHECK_DISK_SPACE to OFF before running the installer.

On UNIX in csh/tcsh, set the variable this way:

% setenv CHECK_DISK_SPACE OFF (or ON, as needed)

On UNIX in sh/ksh/bash set the variable, as follows:

$ CHECK_DISK_SPACE=OFF (or ON, as needed) $ export CHECK_DISK_SPACE

Now run the installer within the shell that you set the environment variable was set to.

Installer unpacks itself in /tmp, which can sometimes be too small

Before running the installer, set the environment variable IATEMPDIR to an alternative temporary directory.

This generally occurs on Unix systems that do not have large /tmp directories. The installer always checks if this value is set, and will use it if it is. If it is not set, the default (temp or /tmp) will be used.

As a reminder, all installers require roughly 3 times the amount of space required by the unpacked files. Therefore, a 100Mb installer would need 300Mb of space in /tmp to install.

If you are still having problems with the Unix installer, set the environment variable LAX_DEBUG to true; this will generate debug output that can be sent to support@openspirit.com for analysis.

To migrate the OpenSpirit Tablespace, you need to:

• Make sure everyone is out of OpenSpirit, and stop the shared services: $OSP_HOME/bin/runOSServices.sh stop
• In the new Oracle instance, create a new OpenSpirit Oracle tablespace and account with the same exact username and password as used in the old instance.

This is the account you use when logging into the ospconfig tool. It can also be found in the $OSP_HOME/classes/OpenSpirit.properties under the property openspirit.ads.ObjectPersistence.Userid file and looks like openspirit.ads.ObjectPersistence.Userid=OpenSpirit260. In this case the Oracle user should be OpenSpirit260.

A script for creating the Oracle tablespace and account is available on the OpenSpirit web site http://www.openspirit.com/support/ADSCreateTableSpace.sh. You can use this script to create the new tablespace and account, or you can do it “manually”. The script shows how the Oracle account needs to be created. Please note that the account’s default tablespace must be set to the tablespace that will contain the OpenSpirit tables. Also note that the account must be granted CONNECT and RESOURCE permissions.

Next, migrate the tables from the old tablespace to the new tablespace. Edit the $OSP_HOME/classes/OpenSpirit.properties file to include the new Oracle information. Change the following items to reflect your new Oracle set-up:

openspirit.ads.ObjectPersistence.dbHost
openspirit.ads.ObjectPersistence.dbInstanceName
openspirit.ads.ObjectPersistence.dbPort
openspirit.ads.ObjectPersistence.dbURL

openspirit.ads.ProjectSet.dbHost
openspirit.ads.ProjectSet.dbInstanceName
openspirit.ads.ProjectSet.dbPort
openspirit.ads.ProjectSet.dbURL

openspirit.ads.ReferenceValueService.dbHost
openspirit.ads.ReferenceValueService.dbInstanceName
openspirit.ads.ReferenceValueService.dbPort
openspirit.ads.ReferenceValueService.dbURL

openspirit.ads.UserAliasService.dbHost
openspirit.ads.UserAliasService.dbInstanceName
openspirit.ads.UserAliasService.dbPort
openspirit.ads.UserAliasService.dbURL

openspirit.ads.config.dbHost
openspirit.ads.config.dbInstanceName
openspirit.ads.config .dbPort
openspirit.ads.config.dbURL

As an example, if the new host is on a machine 10.10.10.30, Oracle SID is “gf”, port is 1542, the values would be:
...dbHost=10.10.10.30
...dbInstanceName=gf
...dbPort=1542
...dbURL=jdbc:oracle:thin:@10.10.10.30:1542