Weblogic 11g Installation Using Jar File

Pre-requisites for installing Weblogic 11g through .jar file. 

1. Install Java 1.6.2 or higher version

      Installing the Weblogic Server:

            UNIX:

            JAVA_HOME/bin/java -jar wls1036_generic.jar

           Windows:

           JAVA_HOME\bin\java -jar wls1036_generic.jar

                                                       Figure 1

After you start the Oracle WebLogic Server Installer, the Welcome screen is displayed.
Click Next.

                                                         Figure 2

On the Choose Middleware Home Directory screen, appears select Create a new Middleware Home
Click Next.

Figure 3

On the Register for Security Updates screen, select whether or not you want to receive the latest product and security updates. If you choose not to receive updates, you are asked to verify your selection before continuing.
Click Next.

Figure 4

On the Choose Install Type screen, select Typical and click Next.

Figure 5

On the JDK Selection screen, select a valid JDK and click Next.

Figure 6

On the Choose Product Installation Directories screen, verify the location for the WebLogic Server Installation and click Next.

Figure 7

We are installing Oracle WebLogic Server on a Windows system, the Choose Shortcut Location screen appears. Specify a location where you want Windows to create a shortcut to Oracle products and click Next

Figure 8

Click Next on the Installation Summary screen.

Figure 9

On the Installation Complete screen, de-select Run Quickstart and click Done to exit the Installer.

Figure 10

Go to -> Windows-> StartMenu -> Able to See Weblogic installation Directories.

Figure 11

Installation of Weblogic 11g using .jar file is completed.

How to redirect the Weblogic Servers (Admin and Managed) startup logs. (WLS_REDIRECT_LOG)

First we need to update startWebLogic.sh file in /domain/bin Folder.

[root@10 bin]# pwd

/mnt/Oracle/Middleware/user_projects/domains/base_domain/bin

[root@10 bin]# view startWebLogic.sh

Add the below highlighted line only in startWebLogic.sh file and save the file and try to restart the Weblogic Admin Server or Managed Weblogic Server.

WLS_REDIRECT_LOG=${DOMAIN_HOME}/servers/${SERVER_NAME}/logs/${SERVER_NAME}_`date +"%F-%H-%M-%S"`.out

-------------------------------------------------------------------------------

  

Out Put example:

[root@10 bin]# ./startWebLogic.sh &

[3] 7178

[root@10 bin]#

.

JAVA Memory arguments: -Xms512m -Xmx512m

.

WLS Start Mode=Production

.

CLASSPATH=/mnt/Oracle/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/mnt/Oracle/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/mnt/Oracle/Middleware/jrockit_160_29_D1.2.0-10/lib/tools.jar:/mnt/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/mnt/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/mnt/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/mnt/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/mnt/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/mnt/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/mnt/Oracle/Middleware/wlserver_10.3/common/derby/lib/derbyclient.jar:/mnt/Oracle/Middleware/wlserver_10.3/server/lib/xqrl.jar

.

Oracle JRockit(R) (build R28.2.0-79-146777-1.6.0_29-20111005-1807-linux-ia32, compiled mode)

Redirecting output from WLS window to /mnt/Oracle/Middleware/user_projects/domains/base_domain/servers/AdminServer/logs/AdminServer_2012-08-02-18-34-42.out

tail -f /mnt/Oradmsd/Oracle/Middleware/user_projects/domains/base_domain/servers/AdminServer/logs/AdminServer_2012-08-02-18-34-42.out

Apache Upgradation

Upgrading From 2.2 to 2.4

This document describes changes in server behavior that might require you to change your configuration or how you use the server in order to continue using 2.4 as you are currently using 2.2. To take advantage of new features in 2.4, see the New Features document.

This document describes only the changes from 2.2 to 2.4. If you are upgrading from version 2.0, you should also consult the 2.0 to 2.2 upgrading document.

§         Compile-Time Configuration Changes

§        Run-Time Configuration Changes

§        Misc Changes

§        Third Party Modules

§       Common problems when upgrading

Compile-Time Configuration Changes

The compilation process is very similar to the one used in version 2.2. Your old configure command line (as found in build/config.nice in the installed server directory) can be used in most cases. There are some changes in the default settings. Some details of changes:

·         These modules have been removed: mod_authn_default, mod_authz_default, mod_mem_cache. If you were using mod_mem_cache in 2.2, look at mod_cache_disk in 2.4.

·         All load balancing implementations have been moved to individual, self-contained mod_proxy submodules, e.g. mod_lbmethod_bybusyness. You might need to build and load any of these that your configuration uses.

·         Platform support has been removed for BeOS, TPF, and even older platforms such as A/UX, Next, and Tandem. These were believed to be broken anyway.

·         configure: dynamic modules (DSO) are built by default

·         configure: By default, only a basic set of modules is loaded. The other LoadModule directives are commented out.

·         configure: the "most" module set gets built by default

·         configure: the "reallyall" module set adds developer modules to the "all" set

Run-Time Configuration Changes

There have been significant changes in authorization configuration, and other minor configuration changes, that could require changes to your 2.2 configuration files before using them for 2.4.

Authorization

Any configuration file that uses authorization will likely need changes.

You should review the Authentication, Authorization and Access Control Howto, especially the section Beyond just authorization which explains the new mechanisms for controlling the order in which the authorization directives are applied.

Directives that control how authorization modules respond when they don't match the authenticated user have been removed: This includes AuthzLDAPAuthoritative, AuthzDBDAuthoritative, AuthzDBMAuthoritative, AuthzGroupFileAuthoritative, AuthzUserAuthoritative, and AuthzOwnerAuthoritative. These directives have been replaced by the more expressive RequireAny, RequireNone, and RequireAll.

Access control

In 2.2, access control based on client hostname, IP address, and other characteristics of client requests was done using the directives Order, Allow, Deny, and Satisfy.

In 2.4, such access control is done in the same way as other authorization checks, using the new module mod_authz_host. The old access control idioms should be replaced by the new authentication mechanisms, although for compatibility with old configurations, the new module mod_access_compat is provided.

Here are some examples of old and new ways to do the same access control.

In this example, all requests are denied.

2.2 configuration:

Order deny,allow

Deny from all

2.4 configuration:

Require all denied

In this example, all requests are allowed.

2.2 configuration:

Order allow,deny

Allow from all

2.4 configuration:

Require all granted

In the following example, all hosts in the example.org domain are allowed access; all other hosts are denied access.

2.2 configuration:

Order Deny,Allow

Deny from all

Allow from example.org

2.4 configuration:

Require host example.org

Other configuration changes

Some other small adjustments may be necessary for particular configurations as discussed below.

·         MaxRequestsPerChild has been renamed to MaxConnectionsPerChild, describes more accurately what it does. The old name is still supported.

·         MaxClients has been renamed to MaxRequestWorkers, which describes more accurately what it does. For async MPMs, like event, the maximum number of clients is not equivalent than the number of worker threads. The old name is still supported.

·         The DefaultType directive no longer has any effect, other than to emit a warning if it's used with any value other than none. You need to use other configuration settings to replace it in 2.4.

·         EnableSendfile now defaults to Off.

·         FileETag now defaults to "MTime Size" (without INode).

·         mod_log_config: ${cookie}C matches whole cookie names. Previously any substring would match.

·         mod_dav_fs: The format of the DavLockDB file has changed for systems with inodes. The old DavLockDB file must be deleted on upgrade.

·         KeepAlive only accepts values of On or Off. Previously, any value other than "Off" or "0" was treated as "On".

·         Directives AcceptMutex, LockFile, RewriteLock, SSLMutex, SSLStaplingMutex, and WatchdogMutexPath have been replaced with a single Mutex directive. You will need to evaluate any use of these removed directives in your 2.2 configuration to determine if they can just be deleted or will need to be replaced using Mutex.

·         mod_cache: CacheIgnoreURLSessionIdentifiers now does an exact match against the query string instead of a partial match. If your configuration was using partial strings, e.g. using sessionid to match /someapplication/image.gif;jsessionid=123456789, then you will need to change to the full string jsessionid.

·         mod_ldap: LDAPTrustedClientCert is now consistently a per-directory setting only. If you use this directive, review your configuration to make sure it is present in all the necessary directory contexts.

·         mod_filter: FilterProvider syntax has changed and now uses a boolean expression to determine if a filter is applied.

·         mod_include:

§  The #if expr element now uses the new expression parser. The old syntax can be restored with the new directive SSILegacyExprParser.

§  An SSI* config directive in directory scope no longer causes all other per-directory SSI* directives to be reset to their default values.

·         mod_charset_lite: The DebugLevel option has been removed in favour of per-module LogLevel configuration.

·         mod_ext_filter: The DebugLevel option has been removed in favour of per-module LogLevel configuration.

·         mod_ssl: CRL based revocation checking now needs to be explicitly configured through SSLCARevocationCheck.

·         mod_substitute: The maximum line length is now limited to 1MB.

·         mod_reqtimeout: If the module is loaded, it will now set some default timeouts.

Misc Changes

·         mod_autoindex: will now extract titles and display descriptions for .xhtml files, which were previously ignored.

·         mod_ssl: The default format of the *_DN variables has changed. The old format can still be used with the new LegacyDNStringFormat argument to SSLOptions. The SSLv2 protocol is no longer supported. SSLProxyCheckPeerCN and SSLProxyCheckPeerExpire now default to On, causing proxy requests to HTTPS hosts with bad or outdated certificates to fail with a 502 status code (Bad gateway)

·         htpasswd now uses MD5 hash by default on all platforms.

·         The NameVirtualHost directive no longer has any effect, other than to emit a warning. Any address/port combination appearing in multiple virtual hosts is implicitly treated as a name-based virtual host.

·         mod_deflate will now skip compression if it knows that the size overhead added by the compression is larger than the data to be compressed.

·         Multi-language error documents from 2.2.x may not work unless they are adjusted to the new syntax of mod_include's #if expr= element or the directive SSILegacyExprParser is enabled for the directory containing the error documents.

·         The functionality provided by mod_authn_alias in previous versions (i.e., the AuthnProviderAlias directive) has been moved into mod_authn_core.

Third Party Modules

All modules must be recompiled for 2.4 before being loaded.

Many third-party modules designed for version 2.2 will otherwise work unchanged with the Apache HTTP Server version 2.4. Some will require changes; see the API update overview.

Common problems when upgrading

·         Startup errors:

§  Invalid command 'User', perhaps misspelled or defined by a module not included in the server configuration - load module mod_unixd

§  Invalid command 'Require', perhaps misspelled or defined by a module not included in the server configuration, orInvalid command 'Order', perhaps misspelled or defined by a module not included in the server configuration- load module mod_access_compat, or update configuration to 2.4 authorization directives.

§  Ignoring deprecated use of DefaultType in line NN of /path/to/httpd.conf - remove DefaultType and replace with other configuration settings.

·         Errors serving requests:

§  configuration error: couldn't check user: /path - load module mod_authn_core

Reference: http://httpd.apache.org

Commands to Check Weblogic Server Status

Admin Server Status

From Domain Home execute the below command

C:\Oracle\Middleware\user_projects\domains\base_domain

Java –cp C:\ Oracle\Middleware\wlserver_10.3\server\lib\weblogic.jar  weblogic.Admin  -adminurl t3:\\localhost:7001 –username weblogic –password –weblogic123 GETSTATE

You will get output as “new_Managed_1”: RUNNING

Managed Server Status

From Domain Home execute the below command

C:\Oracle\Middleware\user_projects\domains\base_domain

Java –cp C:\ Oracle\Middleware\wlserver_10.3\server\lib\weblogic.jar  weblogic.Admin  -adminurl t3:\\localhost:7001 –username weblogic –password –weblogic123 GETSTATE  new_Managed_1

You will get output as “new_Managed_1”: RUNNING

Cluster Status

From Domain Home execute the below command

C:\Oracle\Middleware\user_projects\domains\base_domain

Java utils:MULTICASTTEST  -N clustername –A clusteraddress –p clusterport –T10 –S 2

Apache Upgrade (2.2 to 2.4)

Apache Upgrading to 2.4.2 on Solaris servers

CONTENTS:

    1)    Introduction to Apache

2)    Scope

3)    Basics related to Apache and Pre-checks/ Important points

4)    Installation steps of Apache

5)    Glossary

     6)    References

Introduction to Apache Web Server:

Apache web server is an open source HTTP web server that provides secure and efficient HTTP services in sync with current HTTP standards. There will be frequent releases in the Apache HTTP server project and this makes other related software developments to depend on these releases. The document mainly describes on how to install/upgrade Apache 2.4.2 on Solaris Operating System if it has previous versions of Apache.

Basics related to Apache and Pre-checks/Important points:

1)    To check if Apache web server is running on the Solaris machine, run the following command.

$ps –ef | grep httpd

2)    Several important folders of Apache are listed as follows with their description.

·         cgi-bin : is the place where the cgi scripts are placed (like the Perl or Python scripts)

·         htdocs : is the place where we place the html/php files that are to be  located. logs: is folder that contains 3 files with important information along with the logs

·         conf: contains the configuration files such as httpd.conf that are most important for running of Apache web server. The conf files provide facility to change several options that serve as input parameters to apache engine.

·         bin:  contains utility scripts and executables like apachectl and httpd.

·         lib: contains the library modules.

3)    The apache web server can be started using the command

/opt/apache/bin/apachectl start

          and can be stopped/restarted using the commands

/opt/apache/bin/apachectl stop

/opt/apache/bin/apachectl restart

Both the above commands are given assuming that apache is installed at the location /opt/apache.

4)    It is strongly recommended to back up the httpd.conf file of the current website before doing any modifications/upgradations to the same.

5)    Although Apache can be installed at any location like /etc/apache and /usr/local/apache etc, it is recommended to install at the path where it is previously installed because the  scripts/html pages related to the website are located in that path and it sometimes become very difficult to move all those scripts and folders to the new location if the install destination path is changed to a new location other than the current location. Obviously, the new installation/up-gradations will only modify the files with same names to new files and the other entire tree structure not related to apache stay as they are before. If the install location is changed all the scripts need to be changed to the new location which is tough task along with the changes in the scripts to suite to the new location. It is obvious that the new installations/up-gradations will only modify the files with same names to new files and the other entire tree structure/remaining files not related to apache stay as they are before.

6)    The httpd is Apache HTTP daemon. The commands that are useful while dealing with Apache httpd are as given below.

·         /opt/apache/bin/httpd –v returns the version of httpd and exits

·         /opt/apache/bin/httpd –V returns the version and build parameters of httpd.

·         /opt/apache/bin/httpd –l outputs the list of modules compiled into the server

·         /opt/apache/bin/httpd –S shows the setting parsed from the httpd.conf file.

Refer to manual page for more options. Apache is assumed to be installed at /opt/apache.

  7)    There should be C compiler already installed on the Solaris servers. Else please install a C compiler. If it is already installed, the path where the C compiler is present should be set in path variable.

The Installation steps of Apache 2.4.2 on Solaris servers at /opt/apache:

The following steps should be followed for installing Apache. Here it is assumed that older version of apache is already installed at /opt/apache.

1)    Download the required Apache version 2.4.2 from http://httpd.apache.org/ .

2)    FTP to the solaris server that requires the Apache upgrade and put the installable in a temporary folder (say /tmp/apache).

3)    Uncompress and extract the Apache installable scripts to a folder using the ‘gunzip <filename>’ and ‘tar –xvf <filename>’ commands.

4)    Go to existing /opt/apache/conf folder and copy the httpd.conf and other conf files to the above mentioned temporary folder.

5)    Take a complete back up of the /opt/apache folder in the /opt as apache_bakup.tar using the command

tar –cvf “apache_bakup.tar” /opt/apache

6)    Now, compile the extracted apache installation scripts. The options used in the compilation will affect the functioning of the apache web server. Go to the temporary folder into which apache is extracted and run the following commands.

./configure --prefix=/opt/apache  --enable-module=so

         

This configures the installation to be done at the path /opt/apache and to enable to use modules of type ‘so’. Use the --enable-module=NAME and --disable-module=NAME options to enable or disable a particular already distributed module from the Apache src/Configuration.tmpl file.

7)    Then run the following commands for building and installing the compiled and configured packages.

$make

$make install

8)    Check if the old httpd.conf file is present at the path /opt/apache/conf. Else copy the httpd.conf file that is backed up in the temporary folder to this folder.

9)    Try starting the Apache Web server using the following command.

$/opt/apache/bin/apachectl start

10) The services should start saying that the “Apache web services started successfully”.

11) If the apache start shows some error saying that “Unable to Load Module…… ” , the environment variables related to the module should be set using the scripts related to the module and should be investigated. ‘LoadModule’ directive in httpd.conf is used in loading modules of some other software or agents whenever apache services are started.

12) Restart the apache services by the command $/opt/apache/bin/apachectl start.