copyConfig Script for Node Manager

20-20 Oracle Fusion Middleware Administrators Guide

20.4 Customizing Move Plans When Moving Components

When you move Oracle Fusion Middleware components, you run the extractMovePlan script to create a move plan for the component that you are moving. The extractMovePlan script extracts configuration information from the archive into a move plan. It also extracts any needed configuration plans. Before you apply the archive to the target, you must edit the move plan to reflect the values of the target environment. The following shows an excerpt of a move plan for Java components: ?xml version=1.0 encoding=UTF-8 standalone=yes? movePlan movableComponent componentTypeJ2EEDomaincomponentType moveDescriptor configProperty nameStartup Modename valuePRODUCTIONvalue itemMetadata dataTypeSTRINGdataType scopeREAD_WRITEscope itemMetadata configProperty configGroup typeSERVER_CONFIGtype configProperty id=Server1 configProperty nameServer Namename valueAdminServervalue itemMetadata dataTypeSTRINGdataType scopeREAD_ONLYscope itemMetadata configProperty configProperty nameListen Addressname valueexample.comvalue itemMetadata -movePlanLoc -mpl The absolute path of the modified move plan in the target environment. Mandatory -logDirLoc -ldl The location of an existing directory. A new log file is created in the directory. The default is the system Temp location. Optional -silent None Specifies whether the operation operates silently. That is, it does not prompt for confirmation. The default is that the operation prompts for confirmation. To continue, you must type yes, which is not case sensitive. Typing anything other than yes causes the script to return an error. To specify that it does not prompt for confirmation, specify this option with the value of true. Optional Table 20–9 Cont. Options for the pasteConfig Script for Node Manager Options Shortcut Description Mandatory or Optional Using the Movement Scripts 20-21 dataTypeSTRINGdataType scopeREAD_WRITEscope itemMetadata configProperty You can modify properties with the scope of READ_WRITE. Do not modify the properties with the scope of READ_ONLY.

20.4.1 Locating configGroup Elements

Most move plans contain multiple configGroup elements. When a property is associated with a particular configGroup element, the tables listing the properties group the properties by configGroup element. For example Table 20–11 , which shows the properties for the move plan for Java components, shows multiple configGroup elements, such as SERVER_CONFIG and MACHINE_CONFIG. The following example shows a portion of the move plan for Java components, with portions of the SERVER_CONFIG and MACHINE_CONFIG configGroup elements: ?xml version=1.0 encoding=UTF-8 standalone=yes? movePlan movableComponent componentTypeJ2EEDomaincomponentType moveDescriptor StartupModePRODUCTIONStartupMode configGroup typeSERVER_CONFIGtype configProperty id=Server1 configProperty nameServer Namename valueAdminServervalue itemMetadata dataTypeSTRINGdataType scopeREAD_ONLYscope itemMetadata configProperty . . . configGroup configGroup typeMACHINE_CONFIGtype configProperty id=Machine1 configProperty nameMachine Namename valueLocalMachinevalue itemMetadata dataTypeSTRINGdataType scopeREAD_WRITEscope itemMetadata configProperty configProperty nameNode Manager Listen Addressname valueexample.comvalue itemMetadata dataTypeSTRINGdataType scopeREAD_WRITEscope itemMetadata configProperty .