64-bit Support in Web Server 7

Retaining all versions of Converged Load Balancer XML File

CLB xml file in sailfin gets regenerated each time with new version number when clb xml changes (<name>.xml.v<number> Eg. clb.xml.v39). When a new version is generated the old clb xml file is deleted. If you need to retain the old files for debugging purposes you need to add a java system property clbreconfig.debug to true under java-config. It can be done using Admin GUI/CLI (asadmin script).

The following is the java system property added under java-config of server-config element

<java-config classpath-prefix="${com.sun.aas.installRoot}/lib/comms-appserv-rt.jar" classpath-suffix="" debug-enabled="false" debug-options="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009" env-classpath-ignored="true" java-home="${com.sun.aas.javaRoot}" javac-options="-g" rmic-options="-iiop -poa -alwaysgenerate -keepgenerated -g" system-classpath="">
<jvm-options>-XX:MaxPermSize=192m</jvm-options>
<jvm-options>-Djavax.management.builder.initial=com.sun.enterprise.ee.admin.AppServerMBeanServerBuilder</jvm-options>

<jvm-options>-Djava.endorsed.dirs=${com.sun.aas.installRoot}/lib/endorsed</jvm-options>
<jvm-options>-Djava.security.policy=${com.sun.aas.instanceRoot}/config/server.policy</jvm-options>
<jvm-options>-Djava.security.auth.login.config=${com.sun.aas.instanceRoot}/config/login.conf</jvm-options>
<jvm-options>-Dsun.rmi.dgc.server.gcInterval=3600000</jvm-options>
<jvm-options>-Dsun.rmi.dgc.client.gcInterval=3600000</jvm-options>
<jvm-options>-Dclbreconfig.debug=true</jvm-options>
<jvm-options>-Xmx512m</jvm-options>
<jvm-options>-client</jvm-options>

Similarly to retain the clb xml under instances you need to do the same under instance config.

Posted at 02:43AM Jan 29, 2009 by srinik in Sun  |  Comments[0]

SIP Access Logging in Sailfin

SIP Access logging is disabled by default in Sailfin. The following steps need to be done to enable SIP access logging. (Example mentioned below is for enabling sip access logging in DAS)

1. Start the DAS.

2. Use the following Administration CLI command to enable the SIP access logging.

    # asadmin set server-config.sip-service.property.accessLoggingEnabled = true

    server-config need to be replaced by config for which you need to enable the access logging.

    The above command will create the access log file sip_access_log under the directory
    <sailfin_install_dir>/domains/<domain_name>/logs/sipacess.

3. To get the default access log format

    # asadmin get server-config.sip-service.access-log.format

    The default access log format is "%client.name% %auth-user-name% %datetime% %request% %status% %response.length%". 
 
    The following sip headers are supported

            client.name
            auth-user-name
            datetime
            request
            status
            response.length
            max.forwards
            from
            cseq
            contact
            to
            content.type
            via
            call.id


    To enable all headers, run the following command

    # asadmin set server-config.sip-service.access-log.format="%client.name% %auth-user-name% %datetime% %request% %status%
       %response.length% %max.forwards% %from% %cseq% %contact% %to% %content.type% %via% %call.id%"

        NOTE: Need to escape the format string, else asadmin will fail

4. Now send the SIP request to DAS, you can see the requests logged in the sip access log. Following is the sample access log on sending a
    request with all headers enabled.

    "NULL-CLIENT-NAME" "129.158.228.116" "23/Oct/2008:13:13:06 +0530" "INVITE sip:bar@129.158.228.116:5060"  247 "SIP/2.0/UDP
    129.158.228.116:5080;branch=z9hG4bK7a45cc230bb906944221f6fc5606c11f"
    "249a31b3f8c16af039fbdb937d78e43b@129.158.228.116" ""Mr.    Bar"<sip:bar@java.net>" ""Mr. Foo"
     <sip:foo@sun.com>;tag=70560" "1 INVITE" "70" ""Mr. Foo" <sip:foo@129.158.228.116:5080;transport=udp>" "application/sdp"

5. The above can also be done using Administration GUI.

    i) In the common tasks tree click on Configurations.

    ii) Click on server-config

    iii) Click on sip-service

    iv) Add property accessLoggingEnabled and set it to true.

    v) Click on the Access Log Tab, set the access log format.

    Repeat step 4 and you can see the requests logged in the sip access log.

Posted at 01:50AM Jan 29, 2009 by srinik in Sun  |  Comments[0]

Web Server 7 Technology Preview Download

Sun Java System Web Server 7 Technology Preview 1 is a full product install of Sun Java System Web Server (hence forth Web Server 7). Web Server 7 is the first major feature update to Web Server since the release of Web Server 6.1. It can be downloaded from the location
http://www.sun.com/download/products.xml?id=446518d5

Posted at 02:56AM May 22, 2006 by srinik in Sun  |  Comments[0]

Silent Installation in Web Server 7

The Sun Java System Web Server 7 provides a easy way of installation called Silent Installation. It does not require any interaction with the user and it uses a installer configuration file called statefile for install information. It makes the installation process simple and fast.[Read More]

Posted at 11:53PM May 18, 2006 by srinik in Sun  |  Comments[0]

64-bit Support in Web Server 7

Web Server 7 provides the option for installing a 64-bit version of the Web Server on Solaris SPARC and Solaris AMD64. [Read More]

Posted at 11:51PM May 18, 2006 by srinik in Sun  |  Comments[0]