Install Weblogic 10.3/11g

Silent Mode of Installation - 


Note - Please note you need to have Java installed as pre-requisite in case if you are running 64-Installer.

32-bit Installer -
./wls1036_linux32.bin -mode=silent -silent_xml=silent.xml -log=wls_install.log -log_priority=debug


silent.xml

<?xml version="1.0" encoding="UTF-8"?>
<!-- Silent installer option -mode=silent -silent_xml=C:\myfiles\silent.xml -->
<!-- Specify values for each data-value name as follows:

     BEAHOME            Complete pathname to the Middleware Home directory that
                        will contain this installation.

     WLS_INSTALL_DIR    Complete pathname to the product installation
                        directory in which to install WebLogic Server.

     COMPONENT_PATHS    Components and subcomponents to be installed.
                        To install multiple components, separate the components
                        with a bar (|).
                        To install subcomponents, specify a
                        component/subcomponent combination. For example,
                        to install Core Application Server, use
                        "WebLogic Server/Core Application Server".

     INSTALL_NODE_MANAGER_SERVICE  Install Node Manager as a Windows
                                   service. The default is "no".
                                   Requires Administrator privileges.

     NODEMGR_PORT       Node Manager listen port number. If none specified,
                        installer uses default port 5556.
                        INSTALL_NODE_MANAGER_SERVICE must be set to "yes".

     INSTALL_SHORTCUT_IN_ALL_USERS_FOLDER
                        The Windows Start menu folder in which you want the
                        Start menu shortcuts created.
                        The user performing the installation must have
                        Administrator privileges to install the shortcuts
                        in the All Users folder.
                        Possible values:

true/yes  The shortcuts are created in

                                  the All Users folder (default)

                        false/no  The shortcuts are created in

                                  the local user's folder

     BEA_BUNDLED_JVMS

                        Option to select BEA bundled JVMS (for e.g. either

                        jrockit_160_05 or jdk160_05 for Windows and Linux

                        platforms). The default value is all BEA bundled JVMs

                        for selected platform.

     LOCAL_JVMS

                        Option to select supported JVM, which is already

                        installed. Note: The presence of either(BEA_BUNDLED_JVMS

                        or LOCAL_JVMS) or both of these tokens negates any

                        default selection and only sets the values assigned for

                        these tokens as user selection. The value of the token

                        can be a pipe ('|') separated JavaHomes.

-->

<!-- <?xml version="1.0" encoding="UTF-8"?> -->

   <bea-installer>

     <input-fields>

       <data-value name="BEAHOME" value="/opt/thirdparty/middleware/oracle" />

       <data-value name="WLS_INSTALL_DIR" value="/opt/thirdparty/middleware/oracle/wls11g" />

       <data-value name="COMPONENT_PATHS"

        value="WebLogic Server/Core Application Server|WebLogic Server/Administration Console|WebLogic Server/Configuration Wizard and Upgrade Framework|WebLogic Server/Web 2.0 HTTP Pub-Sub Server|WebLogic Server/WebLogic JDBC Drivers|WebLogic Server/Third Party JDBC Drivers|WebLogic Server/WebLogic Server Clients|WebLogic Server/WebLogic Web Server Plugins|WebLogic Server/UDDI and Xquery Support|WebLogic Server/Server Examples|Oracle Coherence/Coherence Product Files" />

       <data-value name="INSTALL_NODE_MANAGER_SERVICE" value="yes" />

       <data-value name="NODEMGR_PORT" value="5559" />

       <data-value name="INSTALL_SHORTCUT_IN_ALL_USERS_FOLDER" value="yes"/>

true/yes  The shortcuts are created in

                                  the All Users folder (default)

                        false/no  The shortcuts are created in

                                  the local user's folder

     BEA_BUNDLED_JVMS

                        Option to select BEA bundled JVMS (for e.g. either

                        jrockit_160_05 or jdk160_05 for Windows and Linux

                        platforms). The default value is all BEA bundled JVMs

                        for selected platform.

     LOCAL_JVMS

                        Option to select supported JVM, which is already

                        installed. Note: The presence of either(BEA_BUNDLED_JVMS

                        or LOCAL_JVMS) or both of these tokens negates any

                        default selection and only sets the values assigned for

                        these tokens as user selection. The value of the token

                        can be a pipe ('|') separated JavaHomes.

-->

<!-- <?xml version="1.0" encoding="UTF-8"?> -->

   <bea-installer>

     <input-fields>

       <data-value name="BEAHOME" value="/opt/thirdparty/middleware/oracle" />

       <data-value name="WLS_INSTALL_DIR" value="/opt/thirdparty/middleware/oracle/wls11g" />

       <data-value name="COMPONENT_PATHS"

        value="WebLogic Server/Core Application Server|WebLogic Server/Administration Console|WebLogic Server/Configuration Wizard and Upgrade Framework|WebLogic Server/Web 2.0 HTTP Pub-Sub Server|WebLogic Server/WebLogic JDBC Drivers|WebLogic Server/Third Party JDBC Drivers|WebLogic Server/WebLogic Server Clients|WebLogic Server/WebLogic Web Server Plugins|WebLogic Server/UDDI and Xquery Support|WebLogic Server/Server Examples|Oracle Coherence/Coherence Product Files" />

       <data-value name="INSTALL_NODE_MANAGER_SERVICE" value="yes" />

       <data-value name="NODEMGR_PORT" value="5559" />

       <data-value name="INSTALL_SHORTCUT_IN_ALL_USERS_FOLDER" value="yes"/>

To run the Upgrade installer in silent mode:

The process for upgrading an installation in silent mode is similar to the process for a full installation in silent mode, except that thesilent.xml file is much simpler. Please note the following issues when performing an upgrade in silent mode:

• If you created a silent.xml file when you initially installed WebLogic Server, you should store it in a safe location or make a backup copy of it so that you do not accidentally overwrite it with the silent.xml file you are creating for your upgrade installation. Alternatively, you can name your upgrade file using a different file name, for example silent_upgrade.xml.
• Incorrect entries in silent.xml can cause installation failures. To help you determine the cause of a failure, Oracle recommends that you create a log file when you start the installation. See Generating a Verbose Installation Log.
• When using an Upgrade installer to upgrade an existing WebLogic Server installation on Linux or UNIX operating systems, you must run the Upgrade installer using the same user ID as was used to perform the initial WebLogic Server installation.
• If you are upgrading an existing WebLogic Server 10.3.0, 10.3.1, 10.3.2, or 10.3.3 installation that includes Workshop for WebLogic, you must uninstall the Workshop components before upgrading your software. You must use either GUI mode or console mode to remove the Workshop components. See Uninstalling the Software, for more information.
  If you do not remove Workshop prior to running the Upgrade installer, you can remove it after the upgrade only by reverting to the previous installation and running the WebLogic uninstall program to remove the WebLogic components. WebLogic Server 10.3.6 does not support removal of Workshop components.

Just in case, If we want to install any additional components which were missing in the main/first installation.. here is a way to upgrade.

NOTE - Please take a back up of registry.xml and registry.dat file also as these files are going to get updated when you run upgrade installer -

1. Create a silent.xml file (or silent_upgrade.xml file) to specify the Middleware home directory that contains the WebLogic Server installation you want to upgrade. See the sample in Sample silent.xml File for Upgrade Installation.
2. Save the XML file in the directory in which the Upgrade installer is stored.
3. Start the Upgrade installer as described in one of the following sections:

Make sure that the -silent_xml option points to the XML file you created for the upgrade installation.

4. After the installation completes, if you are using the JRockit SDK, Oracle recommends that you upgrade your domains to use the latest production version. See Configuring Domains to Use the Latest Version of JRockit.

For Example -

./wls1036_linux32.bin -mode=silent -silent_xml=silent_upgrade1.xml -log=wls_upgrade1.log -log_priority=debug

<!-- <?xml version="1.0" encoding="UTF-8"?> -->
   <bea-installer>
     <input-fields>
       <data-value name="BEAHOME" value="/opt/thirdparty/middleware/oracle" />
       <data-value name="WLS_INSTALL_DIR" value="/opt/thirdparty/middleware/oracle/wls11g" />
       <data-value name="COMPONENT_PATHS"
        value="WebLogic Server/Evaluation Database|Oracle Coherence/Coherence Examples" />
    <!--
    <data-value name="LOCAL_JVMS" value="D:\jrockit_160_05|D:\jdk160_11"/>
    -->
   </input-fields>
</bea-installer>