copyConfig Script for System Components

Using the Movement Scripts 20-19 You must run the pasteConfig script for each Node Manager in the source environment. The syntax is: pasteConfig -javaHome path_of_jdk -archiveLoc archive_location -targetNMHomeLoc trgt_Node_Manager_Home_path -targetMWHomeLoc trgt_Middleware_Home_path -movePlanLoc move_plan_path [-logDirLoc log_dir_path] [-silent {true | false}] The following example shows how to apply the copy of Node Manager to Node Manager home located in scratchOracleMiddleware1wlserver_ 10.3commonnodemanager: pasteConfig -javaHome USER_HOMEjrockit_160_17_R28.0.0-679 -archiveLoc tmpnm.jar -targetNMHomeLoc scratchOracleMiddleware1wlserver_ 10.3commonnodemanager -targetMWHomeLoc scratchOracleMiddleware1 -movePlanLoc scratchoraclet2pplansmoveplan.xml -silent true Table 20–9 describes the options for the pasteConfig script for Node Manager. Note: All the domains that are to be managed by Node Manager should be moved before applying the copy of Node Manager to the target environment. In addition, the Administration Server must be running. Even if the source Node Manager connection between the Administration Server and Node Manager is configured with SSL, they will both change to plain socket connection type after the copy of Node Manager is applied to the target environment. Table 20–9 Options for the pasteConfig Script for Node Manager Options Shortcut Description Mandatory or Optional -javaHome None The absolute path of the Java Developers Kit. If the operating system is SunOS, HP-UX, or Linux 64 bit, pass the -d64 option to the scripts in the command line. To set the runtime property, you can specify the -d64 option in the T2P_JAVA_OPTIONS environment variable. For example: setenv T2P_JAVA_OPTIONS -d64 -Djava.io.tmpdir=homet2ptemp Mandatory -archiveLoc -al The absolute path of the archive location. Use this option to specify the location of the archive file created by the copyConfig script. Mandatory -targetNMHomeLoc -tnh The absolute path of the target Node Manager. Mandatory -targetMWHomeLoc -tmw The absolute path of the target Middleware home in which the copy of Node Manager is to be applied. Mandatory 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