Step by step Apache Installation & Configuaration

Apache Installation & Configuaration

Installation made simple Steps which you can follow them

Step1: Download the any stable version of httpd for your operating environemnt (Now I am intersted in Solaris) suitable binaries given as tar/zip file (Ex: httpd-2.2.11.tar) and Extract it

tar -xvf httpd-2.2.11.tar

Step2: Go to httpd-2.2.11 directory and execute the confiure command to configure the apache in one folder (Ex: apache2)

cd httpd-2.2.11
./configure --prefix=$Home/apache2

Step3: We need to execute the below commands to build I mean compile the binaries

make
make install

Step4: take the backup of httpd.conf file

cd apache2/conf
cp httpd.conf httpd.conf_original

Step5: Edit the httpd.conf configuration file

vi httpd.conf
ServerRoot "$Home/apache2"
(ServerRoot is the path to the server's configuration, error and log files.It is possible to change this path, provided all the necessary files are copiedto the new location accordingly)
Listen IPAddress:Port (Ex: Listen 4.192.50.25:9999)
LoadModule weblogic_module modules/mod_wl_22.so
User wlusername
#main content of wl application details to update in httpd.conf file
Open tag of IfModule
#keep the info in open tag of IfModule ---mod_weblogic.c
WebLogicCluster hostname:9902,hostnamevir1:9902
MatchExpression *.jsp
close tag of IfModule
Open tag of Location
#keep /application root folder name in Lacation
SetHandler weblogic-handler
DynamicServerList ON
HungServerRecoverSecs 600
ConnectTimeoutSecs 40
WLCookieName JSESSIONID
DebugConfigInfo OFF
Debug ON
WLLogFile /$Home/apache2/logs/web1.log
ConnectRetrySecs 2
Idempotent ON
FileCaching ON
WLProxySSL OFF
SecureProxy OFF
Debug OFF
Close tag of Location

ServerAdmin sarangapani.matoori@gmail.com
ServerName 4.192.50.25 (we can use dns name , if we don't have it then we can use the ip)

Step6:copy the mod_wl_22.so module file from $Home/wl923/bea/weblogic92/server/plugin/solaris/sparc to $Home/apache2/modules
cp $Home/wl923/bea/weblogic92/server/plugin/solaris/sparc/mod_wl_22.so $Home/apache2/modules/

Step7:check the status of apche configuaration is ok
cd $Home/apache2/bin
apachectl -t
Step8: Now the starting your newly installed Apache webserver
apchectl -k start or httpd -k start

Step9: Access the application with the apache port
http://hostip:port(which%20is%20kept%20in%20httpd.conf/ file)/ProjectName/jsp/Logon.jsp
Step10: Stop the Apache
apchectl -k stop or httpd -k stop

Can't find string terminator "END" anywhere before EOF error in perl

Can't find string terminator "END" anywhere before EOF

How to Create getters and setters

Create getters and setters

To create getter and setter methods for a field, select the field's declaration and invoke Source > Generate Getter and Setter.

How to copy the value of a user-defined field in Test Plan to a user-defined field in Test Lab

This VBScript Workflow example will populate a test lab test instance user-defined field (TC_USER_01), with the value of a test plan user-defined field (TS_USER_01) of the corresponding test.

Sub TestSetTests_MoveTo
  TestSet_MoveTo
  TestSetTest_Fields("TC_USER_01").IsReadOnly = True
End Sub

Sub TestSet_MoveTo
    On Error Resume Next

    Dim td
    Dim testSetF
    Dim testSet1
    Dim testSetTestF
    Dim tstestL
    Dim tsTest
    Dim tFactory
    Dim tItem
    Set td = TDConnection
    Set testSetF = td.testsetFactory
    Set tFactory = td.TestFactory
    Set testSet1 = testSetF.Item(TestSet_Fields.Field("CY_CYCLE_ID").Value)
    Set testSetTestF = testSet1.TSTestFactory
    Set tstestL = testSetTestF.NewList("")

    For Each tsTest in tstestL
        'check if the UDF of the test instance is empty
        If Len(tsTest.Field("TC_USER_01")) = 0 Then
            Set tItem = tFactory.Item(tsTest.Field("TC_TEST_ID"))
            tsTest.Field("TC_USER_01") = tItem.Field("TS_USER_01")
            tsTest.Post
       End If
    Next

    On Error GoTo 0
End Sub

SEVERE: Servlet.service() for servlet cgi threw exception

This summary is not available. Please click here to view the post.

Weblogic Logs Rotation setup step by step

Each WebLogic Server instance writes all messages from its subsystems and applications to a server log file that is located on the local host computer. By default, the server log file is located in the logsdirectory below the server instance root directory; for example, DOMAIN_NAME\servers\SERVER_NAME\logs\SERVER_NAME.log, where DOMAIN_NAME is the name of the directory in which you located the domain and SERVER_NAME is the name of the server.


In addition to writing messages to the server log file, each server instance forwards a subset of its messages to a domain-wide log file.The domain log file provides a central location from which to view the overall status of the domain. The domain log resides in the Administration Server logs directory. The default name and location for the domain log file is DOMAIN_NAME\servers\ADMIN_SERVER_NAME\logs\DOMAIN_NAME.log, where DOMAIN_NAME is the name of the directory in which you located the domain and ADMIN_SERVER_NAME is the name of the Administration Server.




You can rotate log files - 


By size ( default)
By Time

By default, when you start a WebLogic Server instance in development mode, the server automatically renames (rotates) its local server log file as SERVER_NAME.log.n. For the remainder of the server session, log messages accumulate in SERVER_NAME.log until the file grows to a size of 500 kilobytes.

Each time the server log file reaches this size, the server renames the log file and creates a new SERVER_NAME.log to store new messages. By default, the rotated log files are numbered in order of creationfilenamennnnn, where filename is the name configured for the log file. You can configure a server instance to include a time and date stamp in the file name of rotated log files; for example, server-name-%yyyy%-%mm%-%dd%-%hh%-%mm%.log.

By default, when you start a server instance in production mode, the server rotates its server log file whenever the file grows to 5000 kilobytes in size. It does not rotate the local server log file when you start the server.

You can change these default settings for log file rotation. 


For example
you can change the file size at which the server rotates the log file or 
you can configure a server to rotate log files based on a time interval. 
You can also specify the maximum number of rotated files that can accumulate. After the number   of log files reaches this number, subsequent file rotations delete the oldest log file and create a new log file with the latest suffix.


To change log size for rotation or by time -




Login to Administration Console
click on the server
On right hand side click on logging tab
under default selected general tab

Or select By time option under rotation type drop box and enter time in begin rotation time at the you want your server rotate log file

To update for access logs

Login to Administration Console

click on the server

On right hand side click on logging tab

Select HTTP tab and follow the same above instructions.

java.io.IOException: CreateProcess: perl

This summary is not available. Please click here to view the post.