There are three playback modes that give users varying levels of automation with the SAS Deployment Wizard:. In quiet mode, there is no user interface in which you provide installation inputs. Note: On Windows, you might also want to specify restart options. To run the SAS Deployment Wizard, you must be a user who is known to the target machine and who will be available for the long term to perform future maintenance. When running in quiet mode, the SAS Deployment Wizard's default action is to look for its response file by default in the current user's home directory.
To specify a response file that does not use the default name, use the -responsefile absolute-pathname option. For Windows machines, in the event that the machine must be rebooted, use the restart options to avoid having to manually log back on to the machine. For example, you might type a command similar to this:.
If certain Microsoft system components that are required by SAS 9. If you are playing back a response file in quiet mode, you should use the following options in order to log back on to the machine automatically and continue the SAS Deployment Wizard session:.
In rare circumstances, it is possible those values will remain in your Windows registry after their use, thus posing a potential security risk. For more information about this functionality, including any risks, please refer to Microsoft's documentation about security and automatic logons on their Web site.
You should weigh the risks of convenience for automatic logon after restart against the security policies in place at your site. You can fully automate the SAS installation quiet mode , or you can pick and choose certain parts of the installation to automate partial prompt mode.
When you run the SAS Deployment Wizard in partial prompt mode, the user sees only those wizard pages for which there are no response file values. There might be situations where it is permissible to automate most of the installation inputs but necessary to prompt for certain sensitive pieces of information.
For example, storing user account credentials--even in an encrypted form--might violate a site's corporate security policy. It would require the user to interact with the SAS Deployment Wizard for those pages where user account credentials are entered. When running in partial prompt mode, the SAS Deployment Wizard's default action is to look for its response file by default in the current user's home directory. For more information, see Verifying the Playback Install. There are three levels of automation from which you can choose when running the SAS Deployment Wizard in playback mode: quiet, partial prompt, and full prompt.
Full prompt mode is the least automated of the three modes. When running in full prompt mode, the SAS Deployment Wizard requires user confirmation for all of its pages. However, in full prompt mode, the user is prompted with default values that are stored in the response file. When running in full prompt mode, the SAS Deployment Wizard expects you to specify a path and filename to a valid response file.
For example, on Windows type the following command:. IBM Installation Manager enables you to modify the language and feature selections of an installed product package. The Uninstall option in IBM Installation Manager enables you to uninstall packages from a single installation location.
You can uninstall all installed packages from every package group. After you copy product packages, you define the repository location in the Preferences window of Installation Manager. You can install, update, modify and uninstall product packages using a silent install.
When you complete the silent install, you can use an existing response file or record a new one using Installation Manager. For more information and instructions for recording a response file, see Working in silent mode in the Installation Manager documentation. Customer Support. Home Installing Learn how to install the product.
Installing Learn how to install the product. Enter the username of the My Oracle Support account to download the updates during the installation. Enter the password of the My Oracle Support account to download the updates during the installation. Ensure that the middleware location has write permission. Note that the middleware location is essentially the one and only Oracle home in 13 c release.
Note: Ensure that the number of characters in the middleware home path does not exceed 70 characters for Unix platforms and 25 characters for Microsoft Windows platforms. The host name must resolve to the local host because the host name is used for the local Oracle WebLogic Server as well as the Oracle Management Service. Do not provide a remote host or a load balancer virtual host in this field. Do not enter an IP address. Do not use underscores in the name.
Short names are allowed, but you will see a warning, so Oracle recommends that you enter a fully qualified domain name instead. If you do not mention the host name, the installation wizard will proceed further, honoring the host name it automatically detects for that host. Enter the absolute path to the agent base directory, a location outside the Oracle Middleware home where the Management Agent can be installed. Ensure that this location is empty and has write permission.
Also ensure that it is always maintained outside the Oracle Middleware home. Note: Only for Microsoft Windows Ensure that the number of characters in the agent base directory path does not exceed 25 characters. By default, weblogic is the name assigned to the default user account that is created for the Oracle WebLogic Domain.
If you want to accept the default name, then skip this variable. However, if you want to have a custom name, then enter the name of your choice. Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value. By default, nodemanager is the name assigned to the default user account that is created for the node manager. Enter a password for this node manager user account. Enter the absolute path to a location outside the middleware home leading up to the directory name.
Even if you do not configure it at the time of installation, your installation will succeed, and you can always configure it later from the Enterprise Manager Cloud Control Console. Oracle recommends toconfigure it at the time of installation therefore it's automatically configured by the installer which saves time and effort. Ensure that the location you enter is a shared location on the OMS host. This helps when you install additional OMS instances that can use the same shared Software Library location.
Enter the fully qualified name of the host where the existing database resides. Ensure that the host name does not have underscores. If you have already created a database instance with a preconfigured Management Repository using the database templates offered by Oracle, then provide details about that database instance. If you are connecting to an Oracle RAC Database, and if the nodes have virtual host names, then enter the virtual host name of one of its nodes.
The connection to the database is established with a connect string that is formed using only this virtual host name, and the installation ends successfully. However, if you want to update the connect string with other nodes of the cluster, then after the installation, run the following command:.
If you are providing the details of a pluggable database PDB , then use the full service name instead of the alias. For example, pdb. If you are providing the details of a lone-pluggable database Lone-PDB , then use the full service name. Set one of the following values to indicate the number of targets you plan to monitor, the number of Management Agents you plan to have, and the number of concurrent user sessions you plan to have. LARGE, to monitor 10, or more targets, with or more Management Agents, and with about 25 to 50 concurrent user sessions.
The prerequisite checks are run regardless of the selection you make, but the values to be set for the various parameters checked depend on the selection you make.
You can also modify the deployment size after the installation. For more information on deployment sizes, the prerequisite checks that are run, the database parameters that are set, and how you can modify the deployment size after installation, refer to What is a Deployment Size for Enterprise Manager Cloud Control in an Advanced Configuration? If the database you are connecting to is a database instance created with a preconfigured Management Repository using the database templates offered by Oracle, then make sure the deployment size you set here matches with the deployment size you selected on the Database Templates screen of Oracle Database Configuration Assistant DBCA while creating the database instance.
If you want to select a deployment size different from the deployment size you had selected while creating the database instance using DBCA, then do one of the following:. Create another database instance with a template for the desired deployment size, then return to this response file and set the same deployment size to this parameter.
0コメント