Unable to apply activespace hotfix without bringing down all metaspaces on machine.
book
Article ID: KB0086548
calendar_today
Updated On:
Products
Versions
TIBCO ActiveSpaces
-
Not Applicable
-
Description
Resolution: Description: =========== We have multiple metaspaces that uses the same physical machine. We wanted to apply hotfixes on this machine while doing application deployment for one the applications(metaspace). But since as-agents for other metaspace were still running, we could not apply hotfix. Also we could not bring down the metaspace for other application as we did not have approvals. We might run into the same issue going ahead. We wanted to check if there are ways around this
Environment: =========== ActiveSpaces 2.0.* ,ActiveSpaces 2.1.* All operating systems
Resolution: =========== Install a different TIBCO home for each metaspace or project. Do not set any TIBCO home in the user profile. While running the AS-agent through a script you can set the AS library dynamically to the desired TIBCO Home.
Remove AS_HOME,LD_LIBRARY_PATH from user profile, define manually for each terminal.
setenv-ms1 =============================== export AS_HOME=<as_home_for_ms1> export LD_LIBRARY_PATH=$AS_HOME/lib set PATH=$AS_HOME/bin/;$PATH
setenv-ms2 =============================== export AS_HOME=<as_home_for_ms2> export LD_LIBRARY_PATH=$AS_HOME/lib set PATH=$AS_HOME/bin/;$PATH
setenv-ms3 =============================== export AS_HOME=<as_home_for_ms3> export LD_LIBRARY_PATH=$AS_HOME/lib set PATH=$AS_HOME/bin/;$PATH
While starting your metaspace, from each terminal,you would need to run the respective setenv shell.
Terminal-1 . setenv-ms1 <startup-script>
Terminal-2 . setenv-ms2 <startup-script>
Terminal-3 . setenv-ms3 <startup-script>
Issue/Introduction
Unable to apply activespace hotfix without bringing down all metaspaces on machine.