Weblogic installation in linux

Oracle Weblogic Server

Once planning for the weblogic server hardware and OS is done we can proceed with installation.
The following types of WebLogic Server installers are available:

• OS-specific package installer: This type of installer is a self-extracting executable binary of the installation that includes the JDK’s JRockit and Hotspot for the selected platform. The installer may be either an .exe file or a .bin file, depending on the selected platform.
• Generic package installer: This type of installer is a .jar file. It does not include the JRockit and Hotspot. You can use this type of installer on machines where Java is already installed. For AIX, you need the IBM JDK. These kinds of JDKs are also not pre-packaged by Oracle.
• Upgrade installer: Upgrade installers allow you to upgrade an existing WebLogic Server installation to the current patch release. For example, if you have WebLogic Server 10.3.0, 10.3.1, or 10.3.2 installed, you can use an upgrade installer to upgrade your installation to WebLogic Server 10.3.3. If a patch upgrade is available for your current WebLogic Server installation, you can download an upgrade installer from My Oracle Support.
• Zip installer: It is mainly for developers.

Installation modes to choose:

– GUI mode: This requires a graphical environment.you have to have X-term client installed to avail this.In this case, you will have to forward the DISPLAY to your own PC.
– Console mode: It is the same as the GUI mode but does not need a graphical environment. Installation is done through a text-based console.
– Silent mode: You use this mode for scripted, automated installations.(my favorite when you have to install in 100’s of servers)

Oracle Weblogic GUI-based installation:

Binary Installers:

In this case, make it executable and run it:

chmod +x wls1033_linux32.bin

./ wls1033_linux32.bin

Generic Installers:

Generic jar file:

PATH=$JAVA_HOME/bin:$PATH
export PATH

java –jar wls1033_generic.jar

For your 64-bit environment:
java –d64 –jar wls1033_generic.jar

This will result in a pop-up splash screen from the Oracle Installer
Oracle Installer

weblogic 11g welcome screen

weblogic 11g welcome screen

now you have to choose where to place the Middleware home for Oracle weblogic few homes example are below

/app/oracle/product/Middleware
/opt/oracle/Middleware
/u01/app/oracle/product/Middleware

Do not include spaces in your pathnames, because the CLASSPATH might not be resolved because of a line break.Be aware of using capitals; Linux is case-sensitive.Size your filesystems to be big enough; it gives you some space for increasing the capacity.

middleware home

middleware home

The directory will be created, but be aware that none of them exist and that you have enough permissions to write in it.

Choose install type

Choose install type – Oracle Weblogic

Choose the Custom option to see which options are available. In future, for silent installations you can script the components for your environment needs.

Choose Products and components

Choose Products and components – Oracle Weblogic 11g

In the Choose Products and Components section, you see a list of components that you can select. Some are mandatory, such as the Core Application Server, others are optional, such as WebLogic SCA or Oracle Coherence. Depending on the applications you will run the top of your WebLogic Server, you will have to select or deselect components. For instance, Oracle SOA Suite requires WebLogic SCA, and for your Oracle Service Bus you want to implement Oracle Coherence, so think well about the purpose of your WebLogic Server.

Choose JDK - oracle Weblogic Installation

Choose JDK – oracle Weblogic Installation

At WebLogic 10.3.3, there are still two Java environments available, SUN Hotspot and JRockit. Oracle prescribes using SUN Hotspot for Development Mode and JRockit for Production Mode.

you can also choose external JDk by clicking on Browse button and navigating to the Sun JDK installed by you locally.

Product Installation Directories

Product Installation Directories – Oracle Weblogic 11g

At this point, the WebLogic Server home directory for binaries, libraries, and configuration files is set.

Installation summary

overview of the components and installation Oracle weblogic

Above is an overview of the components and installation.

• Core Application Server: This is the complete WebLogic application server.
• Administration Console: The Administration Console application.
• Configuration Wizard and Upgrade Framework: This is the framework used for creating domains and performing upgrades.
• Web 2.0 HTTP Pub-Sub Server: This is the WebLogic’s built-in HTTP Server.
• WebLogic SCA: This is a Spring container for Java applications that use the Service Component Architecture. This is included as an optional library in the WebLogic Server.
• WebLogic JDBC Drivers and third-party JDBC Drivers: These can be used to connect a WebLogic Server environment to an external database.

Installation running

oracle weblogic application server installation

installation complete screen

Oracle weblogic installation complete screen

Installation completed. uncheck Quick Start and click on Done, as we will configure separately.

QuickStart is designed to help first-time users evaluate, learn, and install a demo workshop.

Installation in console mode:

The –mode=console redirects the output in text to your computer screen.

./wls1033_linux32.bin -mode=console
or
java –d64 –jar wls1033_generic.jar -mode=console

Extracting 0%............................................................
........................................100%
< ---------------------------------------------------------- Oracle Installer - WebLogic 10.3.3.0 ------------------------------------------- --------------->
Welcome:
--------
This installer will guide you through the installation of WebLogic
10.3.3.0. Type "Next" or enter to proceed to the next prompt. If you
want to change data entered previously, type "Previous". You may quit
the installer at any time by typing "Exit".
Enter [Exit][Next]>
< ---------------------------------------------------------- Oracle Installer - WebLogic 10.3.3.0 ------------------------------------------- --------------->
Choose Middleware Home Directory:
---------------------------------
->1|* Create a new Middleware Home
2|/u01/app/oracle/product/Middleware

The rest of the installation is the same as the GUI installation

Silent and scripted installation mode:

Silent mode can be used to specify your installation settings, and after you’ve set it you can propagate the same installation settings to multiple machines. During installation in silent mode, the installation program reads the settings for your configuration from an XML file that you create prior to beginning the installation. The installation program does not display any configuration options during the installation process. Silent-mode installation works on both Windows and UNIX systems.

A sample file can be downloaded from oracle here:

http://docs.oracle.com/cd/E14571_01/doc.1111/e14142/silent.htm#BABGGACD
<?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="UFF-8"?>
   <bea-installer>
     <input-fields>
       <data-value name="BEAHOME" value="D:\Oracle\Middleware_Home" />
       <data-value name="WLS_INSTALL_DIR" value="D:\Oracle\Middleware_Home\wlserver_10.3" />
       <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"/>
    <!--
    <data-value name="LOCAL_JVMS" value="D:\jrockit_160_05|D:\jdk160_11"/>
    -->

   </input-fields>
</bea-installer>

You must be aware of choosing the right components. Here’s an overview of the components:

Weblogic products and Components options

Weblogic products and Components options

Running the silent installation:

Go to the directory that contains the installation program. On a Linux 32-bit environment, this will be wls1033_linux32.bin. When you install with the generic jar installer, it will be wls1033_generic.jar.

Launch the installation program by entering the following commands:
chmod a+x wls1033_linux32.bin
./wls1033_linux32.bin -mode=silent -silent_xml=path_to_silent.xml
Or use the generic installer:
java -jar wls1033_generic.jar -mode=silent -silent_xml=path_to_silent.xml

On a 64-bit environment use the –d64 option, such as java –d64 –jar -mode=silent -silent_xml=path_to_silent.xml, which is the full path of the silent.xml file.
Some additional options you can add are –log=path_to_logfile.

If you have installed the JDK package already some where in the system , you will have to give the option:
-jreLoc={location of your JAVA installation}

The installation can end with 3 different exit codes:
• 0: Successful installation.
• 1: Installation failed due to a fatal error.
Could be a missing directory or missing permissions to the file locations,
which you specified in your XML.
• 2: Installation failed due to an internal XML parsing error.
This is normally a typo or a missing quote in your XML files.
** Error during execution, error code = 65280″

The use of the XML template enables you to script your installation with a shell script (on Linux/UNIX) or batch script (on Windows).In this shell script, you can specify the same options you use when doing an installation from the command-line.In this way you will be able to automate installation into large number of machines hassle free.

In case of any ©Copyright or missing credits issue please check CopyRights page for faster resolutions.

2 Responses

Leave a Reply