set asg credentials
Sets the credentials used to authenticate the OracleAS Guard connections to OracleAS Guard servers.
Format
set asg credentials <host>[:<port>] <ias_administrative_account>/<password> [for farm] [for topology]
Parameters
host
Name of the host system to which the credentials apply. When OracleAS Guard connects to that host, it will use these credentials.
port
The port number of the OracleAS Guard server in its Oracle home. <ias_administrative_account>/password
If this is an OracleAS 10.1.3 installation, the user name must be oc4jadmin and the password for the oc4jadmin account created during the Oracle Application Server 10.1.3 installation. If this is an OracleAS 10.1.2.0.2 or lower installation, the user name must be the ias_admin account name and the password for the ias_admin account created during the Oracle Application Server installation. This account name must be the same as the account name on at least one of the Oracle Application Server homes. for farm (deprecated)
A keyword, that if present in the command line, directs OracleAS Guard to set the credentials for all of the host systems that belong to the same farm as the local host system.
for topology
A keyword, that if present in the command line, directs OracleAS Guard to set the credentials for all of the host systems that belong to the same topology as the local host system.
Usage Notes
By default, the credentials used in the asgctl connect command are used whenever a OracleAS Guard server needs to connect to another OracleAS Guard server. However, there may be cases where you want to use different credentials for a specific server. This command allows you to use the same credentials for all nodes in a topology. For example, you may want to use a common set of credentials in the standby topology that is different from the credentials used in the primary topology.
If you set the credentials for a topology, these credentials are inherited for the entire topology. If you set the credentials for an individual host on the topology, the credentials (for this host) override the default credentials set for the topology. For topologies that have more than one Infrastructure, such as a collocated Oracle Internet Directory+OracleAS Metadata Repository and a separate Portal OracleAS Metadata Repository, OracleAS Guard requires that you set the credentials for each system on which an Infrastructure resides before performing any important OracleAS Guard operations, such as instantiate, sync, switchover, and failover. This is actually a two step process in which you must first identify all OracleAS Infrastructure databases on the topology using the set the primary database command for each Infrastructure,
then you must set the credentials used to authenticate the OracleAS Guard connections to OracleAS Guard servers on which these Infrastructures reside. The following example illustrates this concept. Assume your production topology and standby topology consists of the following systems with installed Infrastructure and middle tier software applications.
Production topology:
host01 (Identity Management+OracleAS Metadata Repository), host04 (OracleAS Metadata Repository only), host06 (J2EE), host06 (Portal & Wireless)
Standby Topology:
host02 (Identity Management+OracleAS Metadata Repository), host05 (OracleAS Metadata Repository only), host07 (J2EE), host07 (Portal & Wireless)
The following OracleAS Guard set primary database and set asg credentials
commands would be required to properly identify the Infrastructures and authenticate OracleAS Guard connections to OracleAS Guard servers prior to performing an instantiate, sync, switchover, or failover operation. Assuming that the Oracle Identity Management+OracleAS Metadata Repository Infrastructure has a service name of orcl and the separate Portal OracleAS Metadata Repository has a service name of asdb.
ASGCTL> set primary database sys/<password>@orcl.us.oracle.com ASGCTL> set primary database sys/<password>@asdb.us.oracle.com ASGCTL> set asg credentials host01.us.oracle.com ias_admin/<password> ASGCTL> set asg credentials host04.us.oracle.com ias_admin/<password>
Note that for a failover operation, these steps would be carried out on the standby topology and are as follows with a change in the host system names:
ASGCTL> set primary database sys/<password>@orcl.us.oracle.com ASGCTL> set primary database sys/<password>@asdb.us.oracle.com ASGCTL> set asg credentials host02.us.oracle.com ias_admin/<password> ASGCTL> set asg credentials host05.us.oracle.com ias_admin/<password>
The OracleAS Guard client must be connected to a OracleAS Guard server before using this command.
An IP address can be used in place of a host name.
See Section 6.1, "Information Common to OracleAS Guard asgctl Commands" and Section 6.2, "Information Specific to a Small Set of OracleAS Guard Commands" for more information.
Example
The following example sets the OracleAS Guard credentials of host system standbyinfra to all host systems that belong to this topology.
set echo
set echo
Sets command-echoing on or off in a asgctl script.
Format
set echo on | off
Parameters
on | off
Specifying "on" turns on command-echoing in a asgctl script. Specifying "off" turns off command-echoing in a asgctl script.
Usage Notes
This command is useful when running large asgctl scripts. For example, if the asgctl script has error test cases with comments entered before each test case or before each asgctl command, setting echo on displays the comment before each test case or before each asgctl command that is run to give you an explanation of what the test case is or what asgctl command is about to be run.
This command also works with nested scripts.
Example
The following example is a asgctl script that turns on command-echoing, runs a test case, connects to a OracleAS Guard server, displays detailed information about the topology, then turns echo off, disconnects from the OracleAS Guard server, and exits from the OracleAS Guard client.
> ASGCTL @myasgctltestscript.txt
# myasgctltestscript.txt # turn on echo
set echo on
# make sure you are not connected disconnect
# not connected, should get an error message dump topology
# connect to an ASG server
connect asg prodinfra ias_admin/adminpwd
#display detailed info about the topology dump topology
#disconnect disconnect
# turn off echo echo off exit