Managing TUXEDO When Running Under Multiple Environments(e.g. Development Through Production Test)
(Doc ID 764608.1)
Last updated on OCTOBER 31, 2018
Applies to:Oracle Tuxedo - Version 6.5 and later
Information in this document applies to any platform.
***Checked for relevance on 09-July-2013***
Product and Version:
All Tuxedo Versions
There is often the need for Tuxedo to be run under multiple environments - particularly during the initial phases of application development, testing and implementation. As an example, consider a case where a customer has several test environments, say:
- integration testing
- acceptance testing
Under such a setup, application software (server executables) would be rolled from one environment to the next as the application development phases progress. Each environment would use different versions of the server and client executables, may run a slightly different version of the environment, even different versions of Tuxedo (e.g. developer VS run-time), possibly a different configuration, each may even run on different machines and with differing abilities of the user to alter their own environment e.g. not allowed under training or production but allowed for development. Executables may be maintained by a particular group (e.g. software control group) whose job is simply to compile and place the various version of the executables for use by the other groups involved in testing or administration of the test areas.
Independently developers or administrators would be responsible for one or more of the environments which are ultimately used by the different test groups; that being either themselves (for the developers areas) or the particular test group. For each of these various areas, unique userids could be maintained which ensure the independence of each test system - unique userid and groupid (uid and gid), individual configurations, environment variables setup and administration being maintained for each. Generally this set-up may also apply to having several independent environments for individual developers or groups.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document