Websphere,Weblogic, JAVA,UNIX,LINUX, Solaris.

Edge of Enterprise Integration

2013-02-28T11:34:00.000-08:00

Dear Readers,

Now the IBM B2B Webinar - is ready to view DataPower Redbook please go through below link you will find useful information about Websphere DataPower B2B appliance.

Secure, Optimize and Govern B2B Services on DataPower An IBM sponsored Event

ATTEND AND RECEIVE

420 Page eBook:
IBM WebSphere DataPower B2B Appliance XB60 Revealed

EXPERT SPEAKER


	Richarch KinardSenior Product Manager WebSphere DataPower Appliances

Login URL:
https://www.idevnews.com/registration/?event_id=251&code=Login

Problem in IBM Websphere Process server 7.0 "Out of Memory error"

2011-04-19T14:06:00.000-07:00

Last week I have seen a strange Out of Memory error in websphere process server 7.0.
More info about error:
When calling wsadmin tasks from built ws_ant under the product_install_root_bin directory of WPS 7 it through Out of memory error.

Attention to users who is using ant based application deployment solutions:
Please be aware that WPS7 has problem when you use ant for application deployments ,Hence plan or use alternative solutions for time being like administrative console or wsadmin scripting client (WAS_HOME/bin/wsadmin.sh or .bat) to deploy your applications. But good news for Websphere portal users hence its just works fine with Websphere Portal 7
Will keep you updated info as soon as I get the solution.

What is Service Data Object (SDO)

2011-03-21T23:00:00.000-07:00

Service Data Object (SDO) provides a framework for data application development that simplifies the J2EE data programming model.

The use of the SDO API to work with a business object.

You can use SDO APIs to do the following tasks:

Create a business object at runtime
Set the value for the simple-typed attribute of a business object
Set the value for the complex-typed attribute of a business object
Set the value for an attribute that is an array of a complex type
Retrieve the values for attributes of various types in the business object

WebSphere Portal and Lotus Web Content Management 6.1.x Performance Tuning Guide

2010-11-12T02:19:00.000-08:00

This guide provides a basis for parameter and application tuning for IBM® WebSphere® Portal for Multiplatforms Version 6.1.X. Remember that both tuning and capacity are affected by many factors, including the workload scenario and the performance measurement environment. For tuning, the objective of this paper is not to recommend that you use the values we used when measuring our scenarios, but to make you aware of those parameters used in our configuration. When tuning your individual systems, it is important to begin with a baseline, monitor the performance metrics to determine if any parameters should be changed and, when a change is made, monitor the performance metrics to determine the effectiveness of the change.
This updated version of the tuning guide for WebSphere Portal 6.1/6.1.0.X. This update includes newly added tuning sections for z/OS, Solaris, Oracle and much more.
Performance tuning overview
Tuning a WebSphere Portal environment involves tuning and configuring the various systems and components of the environment. This chapter discusses some general concepts and details the specifics of the configuration used in our measurement environments. These specifics entail:
Configuring the application server and the resources defined for that application server
Tuning the database(s) and database server
Tuning the directory server and its database
Tuning the web server and/or proxy server
Tuning the operating system and network
Tuning the WebSphere Portal services
When tuning your individual systems, it is important to begin with a baseline, monitor the performance metrics to determine if any parameters should be changed and, when a change is made, monitor the performance metrics to determine the effectiveness of the change.
In addition to the tuning changes we made in our measurement environments, there are some additional tuning options available which can improve performance in certain circumstances; these will be discussed in a separate section.

Please click here for PDF

WebSphere Portal startup problem

2010-11-12T02:02:00.000-08:00

How to Troubleshoot a WebSphere Portal startup problem

This guide will teach you how to troubleshoot a WebSphere Portal startup failure. For the purposes of this guide, a startup failure is defined as being unable to render Portal in the web browser after starting the WebSphere_Portal server even though the server is 'open for e-business'.

When accessing WebSphere Portal in a browser, it is important to keep in mind that you are simply accessing the wps.ear application within the WebSphere_Portal server.
Even though you may see the 'open for e-business' message for the WebSphere_Portal server, this does not guarantee that the wps.ear application itself started successfully.

We will explore three common scenarios:

1. '404 Initialization of one or more services failed' in browser
2. '404 Page Not Found' in browser
3. 'A WebGroup/Virtual Host to handle /wps/portal has not been defined.' or 'Error 404: No target servlet configured for uri: /wps/portal ' in browser

To begin troubleshooting these failures, you will only need the SystemOut.log. This log is located by default in the following directories for Portal v6.0 and v6.1:

Portal v6.0: /log
Portal v6.1: /logs/WebSphere_Portal/

Scenario 1: '404 Initialization of one or more services failed'

If you see this message in your web browser, this is a definitive sign that the wps.ear application failed to start correctly. This can occur for numerous reasons and is often difficult to determine where to start investigating. The following steps should help you determine which errors are relevant:

1. Open the SystemOut.log for the WebSphere_Portal server
2. Find the last startup attempt of this server. Each startup is headed by the following block of text (details within this block of text, such as WAS version, OS version, classpaths, will vary):

Start Display Current Environment
.......
* End Display Current Environment *

HINT: To quickly find the last startup, search for the last occurrence of the string 'Start Display Current Environment'

HINT: This same block of text always appears at the top of the SystemOut.log, despite whether or not it's at the beginning of a startup. The very next line after the above block of text will be:

TRAS0017I: The startup trace state is *=info

If you do not see this line, check the most recent backed up SystemOut.log file and repeat until you find the last startup attempt.

3. Find the following line during this startup attempt:

WSVR0200I: Starting application: wps

4. Find the following line during this startup attempt:

WSVR0221I: Application started: wps

5. Note all error messages that occur between these two lines. These are the ONLY error messages you need to be concerned with. Every other error message that you may see outside of these two lines are irrelevant.

6. See if you can find any “Caused By:” statements in the error messages. These are the most important errors and are the root cause of the issue.

7. wps.ear can fail to start for a variety of reasons so it is not possible to document here every possible issue for a startup failure. If the error message is not obvious, search the WebSphere Portal Support site for any error codes you find to see if there are any known documented issues or apars.

http://www-01.ibm.com/software/genservers/portal/support/

For example, suppose you see messages like this:

[9/10/08 16:16:22:081 CDT] 00000017 VaultServiceI E com.ibm.wps.services.credentialvault.VaultServiceImpl checkSystemDNInitialized EJPSK0028E: Invalid system user DN 'systemcred.dn' property value. Ensure that the DN value is valid in the vault service properties file.
com.ibm.portal.puma.MemberNotFoundException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,o=defaultWIMFileBasedRealm
.
.
.
Caused by: com.ibm.websphere.wim.exception.EntityNotFoundException: CWWIM4001E The 'uid=wpsadmin,o=defaultWIMFileBasedRealm' entity was not found.
at com.ibm.ws.wim.adapter.file.was.FileData.getByDN(FileData.java:929)
at com.ibm.ws.wim.adapter.file.was.FileAdapter.get(FileAdapter.java:798)

You would search for the error codes:

CWWIM4001E EJPSK0028E EJPSG0002E

Scenario 2: 'Page Not Found'

If you see this message in the browser, this typically means one of the following:

- The WebSphere_Portal server is not started
- You are using the wrong port number
- You are using the wrong hostname

For this scenario, we will assume that the server is actually started. The correct values for the port and hostname , from a WAS perspective, are controlled by the Virtual Host configuration in WAS. You can retrieve this information from the SystemOut.log by following these steps:

1. Open the SystemOut.log for the WebSphere_Portal server.
2. Find the last startup attempt of this server. Each startup is headed by the following block of text (details within this block of text, such as WAS version, OS version, classpaths, will vary):

Start Display Current Environment
.......
* End Display Current Environment *

HINT: To quickly find the last startup, search for the last occurrence of the string 'Start Display Current Environment'

HINT: This same block of text always appears at the top of the SystemOut.log, despite whether or not it's at the beginning of a startup. The very next line after the above block of text will be:

TRAS0017I: The startup trace state is *=info

If you do not see this line, check the most recent backed up SystemOut.log file and repeat until you find the last startup attempt.

3. Find where the wps application is started:

WSVR0221I: Application started: wps

4. A few lines before this line, you should see a line similar to this:

SRVE0250I: Web Module WebSphere Portal Server has been bound to default_host[*:10000,*:80,*:10002,*:10038,*:10035].

This line shows you which virtual host wps is mapped to, along with which ports and hostnames are valid. In this example, you see *. This means that any hostname that is valid for the operating system will work here. In some cases you might see a specific hostname:

SRVE0250I: Web Module WebSphere Portal Server has been bound to default_host[hostname:10000,hostname:80,hostname:10002,hostname:10038,hostname:10035].

This means that in order to access this application, you must explicitly use this hostname.

5. Find in the log where the server is open for e-business:

WSVR0001I: Server WebSphere_Portal open for e-business

6. A few lines before this line, you will see several ports being initialized. Check which port is being initialized for WCInboundDefault:

TCPC0001I: TCP Channel TCP_2 is listening on host * (IPv4) port 10038.
CHFW0019I: The Transport Channel Service has started chain WCInboundDefault.

This port must be listed as one of the ports from step 4. This is the port you must use to access wps.

7. Ensure that you are using the correct hostname from step 4 (if *, this can be any valid hostname for the OS) and the correct port from step 6.

http://hostname:port/wps/portal

Scenario 3: 'A WebGroup/Virtual Host to handle /wps/portal has not been defined.' or 'Error 404: No target servlet configured for uri: /wps/portal'

If you see this exception, this means one of the following:

– wps.ear has been uninstalled
– wps.ear is no longer mapped to the WebSphere_Portal server or the Cluster
– The context root for wps.ear is no longer /wps/portal

Follow these steps to determine if something has happened to wps.ear:

1. Open the SystemOut.log
2. Find the last startup attempt of this server. Each startup is headed by the following block of text (details within this block of text, such as WAS version, OS version, classpaths, will vary):

Start Display Current Environment
.......
* End Display Current Environment *

HINT: To quickly find the last startup, search for the last occurrence of the string 'Start Display Current Environment'

HINT: This same block of text always appears at the top of the SystemOut.log, despite whether or not it's at the beginning of a startup. The very next line after the above block of text will be:

TRAS0017I: The startup trace state is *=info

If you do not see this line, check the most recent backed up SystemOut.log file and repeat until you find the last startup attempt.

3. Find the following line during this startup attempt:

WSVR0200I: Starting application: wps

NOTE: If you do not see this line, this is a clear indication that wps has either been uninstalled or is no longer mapped to your server. To check this, do the following:
• Login to server1 or the DMGR
• Navigate to Applications -> Enterprise Applications
• Search for wps
• If do not find it, it has been uninstalled. If you do find it, click the link for it.
• For WAS v6.0.x, click 'Map modules to servers'
For WAS v6.1.x, click 'Manage Modules'
• Ensure that WebSphere_Portal if standalone or the ClusterName if clustered is mapped correctly for this application

4. Assuming you find the line in step 3, double check the context root. Several lines after this line, you should see a line like this:

SRVE0242I: [wps] [/wps] [portal]: Initialization successful.

This is your context root. In this example, it is:

/wps/portal

This can vary. For example:

SRVE0242I: [wps] [/contextRoot] [portal]: Initialization successful.

In this case, it is: /contextRoot/portal

This is what you should be typing to access Portal.

A new era in Business process Management

2010-05-10T07:43:00.000-07:00

What is IBM WebSphere Business Modeler software

IBM WebSphere Business Modeler software is the tool for documenting and understanding existing processes. It can help you visualize, document and model business processes for understanding and process execution, enabling you to rework older business processes into more agile ones or create new processes from scratch. The software enables users to make informed decisions about deployment with advanced analysis and simulation capabilities based on modeled and actual data. Business analysts can visualize and identify bottlenecks to better optimize processes. This robust modeling tool can then turn these process models into executable business processes for automation.

What is IBM WebSphere Dynamic Process Edition software
To realize the full potential of business processes, organizations with diverse,constantly evolving IT environments need comprehensive BPM capabilities, including modeling and simulation, rapid deployment and real-time business process monitoring and analysis. IBM WebSphere Dynamic Process Edition includes all of these capabilities and organizes SOA and BPM infrastructure into shareable, reusable intelligent business services, for a fully realized SOA vision of architectural agility and reuse.

What is IBM WebSphere Industry Content Pack assets
IBM WebSphere Industry Content Packs provide prebuilt assets to speed and enhance BPM solution delivery from modeling to deployment to monitoring including maps and models, service schemas and interfaces, key performance indicators (KPIs), business glossaries and end-to-end solution examples. Based on industry standards, they can help to reduce risk and increase consistency and reuse across the different lines of business within an enterprise and are available for banking, healthcare, insurance, industrial product life-cycle manageme
and telecommunications. The industry content packs are a core part of the IBM Industry Frameworks, which combine the power of award-winning IBM software with industry-specific assets and best practices specifically configured to meet an industry’s specific challenges and needs.

What is IBM WebSphere Transformation Extender software
IBM WebSphere Transformation Extender software increases the speed and reliability with which SOA applications and services can be extended beyond organizational walls to partners, suppliers and customers. For industry-specific data solutions, enterprises can leverage predefined WebSphere Transformation Extender Industry Packs, including healthcare, financial services, insurance and electronic data interchange (EDI). Complex industry transformations can be deployed quickly, with relative ease, helping to increase transaction volume while providing additional flexibility and fostering adaptability to industry changes. WebSphere Transformation Extender software helps remove risk from projects where regulatory bodies or industry service providers require strict conformance to mandatory and advisory guidelines.

What is IBM WebSphere Business Monitor software
When business leaders can link operational metrics to business strategy, their decision-making ability improves. WebSphere Business Monitor software provides real-time insight into business processes, presented in easy-to-read role-based business dashboards. Users can integrate existing business activity monitoring capabilities into WebSphere Business Monitor dashboards, along with other BPM, enterprise resource planning (ERP) and legacy applications, for more holistic process management. And the software offers an embedded metrics library of more than 800 open standard KPIs.

Troubleshooting IBM HTTP Server

2010-05-03T00:53:00.000-07:00

Troubleshooting IBM HTTP Server.

Viewing error messages for a server that fails to start

If you encounter an error starting a HTTP server, you can view the error message in the server logs.

About :

If the target Web server fails to start, a message might appear on the WebSphere Application Server administrative console that indicates that the Web server cannot be started and to view the error messages in the server logs for further details. The types of errors that can result are:

•errors due to caching problems
•errors due to configuration problems
•errors due to SSL handshake failures
•errors due to SSL initialization problems
•errors due to I/O failures
•errors due to Secure Sockets Layer (SSL) stash utility problems

Cache messages
This topic contains error messages that might result due to caching problems and provides a solution to help you troubleshoot the problem.
The following messages are displayed due to caching problems:
• Message: SSL0600E: Unable to connect to session ID cache
o Reason: The server cannot connect to the Session ID caching daemon.
o Solution: Verify that the daemon successfully started.
• Message: SSL0601E: Session ID cache daemon process exited with exit code ; restarting
o Reason: If the value of is 0, the session ID cache daemon (sidd) received the SIGTERM signal. Other exit codes are not expected. Sidd automatically restarted.
o Solution: If the value of is 0 and IBM® HTTP Server did not stop or restart, verify that locally installed CGI scripts, scheduled operating system tasks, or other monitoring software cannot send SIGTERM to sidd.
• Message: SSL0602E: Session ID cache daemon process exited with terminating signal ; restarting
o Reason: The session ID cache daemon (sidd) received a signal other than SIGTERM was received by the session ID cache daemon (sidd), which caused it to exit. Sidd automatically restarted.
o Solution: If the value of is 0 and IBM HTTP Server did not stop or restart, verify that locally installed CGI scripts, scheduled operating system tasks, or other monitoring software cannot send the signal to sidd.
• Message: SSL0603E: Session ID cache daemon process exited with exit code; not restarting; check sidd configuration or enable sidd error log with SSLCacheErrorLog
o Reason: The session ID cache daemon (sidd) did not initialize. The following possible exit code values might be displayed:
Value Reason
2 Log files could not be opened. The SSLCacheTraceLog or the SSLCacheErrorLog directive is not valid.
3 The AF_UNIX socket cannot be initialized. Use the SSLCachePortFilename directive to specify a different socket for the session ID cache daemon.
4 Sidd cannot switch to the configured user and group. Verify the values for the user and group directives.
o Solution: Provide a valid value for the directives and restart IBM HTTP Server.

Configuration messages
This topic contains error messages that might result due to configuration problems and provides solutions to help you troubleshoot these problems.
The following messages appear due to configuration problems:
• Message: SSL0300E: Unable to allocate terminal node.
• Message: SSL0301E: Unable to allocate string value in node.
• Message: SSL0302E: Unable to allocate non terminal node.
• Message: SSL0303E: Syntax Error in SSLClientAuthGroup directive.
• Message: SSL0304E: Syntax Error in SSLClientAuthRequire directive.
• Message: SSL0307E: Invalid token preceding NOT or !
• Message: SSL0308E: A group is specified in SSLClientAuthRequire but no groups are specified.
• Message: SSL0309E: The group is specified in SSLClientAuthRequire is not defined.
• Message: SSL0310I: Access denied to object due to invalid SSL version , expected .
• Message: SSL0311E: Unable to get cipher in checkBanCipher.
• Message: SSL0312I: Cipher is in ban list and client is forbidden to access object.
• Message: SSL0313E: Fell through to default return in checkCipherBan.
• Message: SSL0314E: Cipher is NULL in checkRequireCipher.
• Message: SSL0315E: Cipher used is not in the list of required ciphers to access this object.
• Message: SSL0316E: Fell through to default return in checkCipherRequire.
• Message: SSL0317E: Unable to allocate memory for fake basic authentication username.
• Message: SSL0318E: Limit exceeded for specified cipher specs, only 64 total allowed.
o Reason: The number of ciphers configured using the SSLCipherSpec directive exceeds the maximum allowed of 64.
o Solution: Check for duplicate SSLCipherSpec directives.
• Message: SSL0319E: Cipher Spec is not supported by this GSK library.
o Reason: The cipher is not a valid cipher for use with the installed SSL libraries.
o Solution: Check that a valid cipher value was entered with the SSLCipherSpec directive.
• Message: SSL0320I: Using Version 2|3 Cipher: .
o Reason: This is an informational message listing the ciphers used for connections to this virtual host.
o Solution: None.
• Message: SSL0321E: Invalid cipher spec .
o Reason: The cipher is not a valid cipher.
o Solution: Check the documentation for a list of valid cipher specs.
• Message: SSL0322E: Cipher Spec is not valid.
o Reason: The cipher is not a valid cipher.
o Solution: Check the documentation for a list of valid cipher specs.
• Message: SSL0323E: Cipher Spec has already been added.
o Reason: A duplicate SSLCipherSpec directive has been encountered.
o Solution: This instance of the directive is ignored and should be removed from the configuration file.
• Message: SSL0324E: Unable to allocate storage for cipher specs.
o Reason: The server could not allocate memory needed to complete the operation.
o Solution: Take action to free up some additional memory. Try reducing the number of threads or processes running, or increasing virtual memory.
• Message: SSL0325E: Cipher Spec has already been added to the v2|v3 ban|require list.
o Reason: A duplicate cipher was specified on the SSLCipherBan directive.
o Solution: This instance of the directive is ignored and should be removed from the configuration file.
• Message: SSL0326E: Invalid cipher spec set for SSLCipherBan|SSLCipherRequire.
o Reason: The cipher is not a valid cipher.
o Solution: Check the documentation for a list of valid cipher specs.
• Message: SSL0327E: Invalid value for sslv2timeout|sslv3timeout, using default value of nn seconds.
o Reason: The timeout value specified is not in the valid range.
o Solution: Check the documentation for the proper range of values.
• Message: SSL0328W: Invalid argument for SSLClientAuth: . CRL can not be turned on unless Client Authentication is on.
• Message: SSL0329W: Invalid argument for SSLClientAuth: . If a second argument is entered it must be CRL. CRL cannot be turned on unless client authentication is on.
• Message: SSL0330W: Invalid argument for SSLClientAuth: . If a second value is entered it must be crl.
• Message: SSL0331W: Invalid argument for SSLClientAuth: . The first value must be 0, 1, 2 none, optional, or required.
• Message: SSL0332E: Not enough arguments specified for SSLClientAuthGroup.
• Message: SSL0333E: No parse tree created for .
o Reason: An error occurred processing the SSLClientAuthRequire directive.
o Solution: Check for other error messages. Enable tracing of Client Authentication by adding the directive SSLClientAuthRequireTraceOn to the configuration file.
• Message: SSL0334E: Function ap_make_table failed processing label .
• Message: SSL0337E: OCSP is not supported with this level of GSKit
o Reason: OCSP support requires GSKit 7.0.4.14 or higher
o Solution: Upgrade the level of GSKit on the system to 7.0.4.14 or higher

Handshake messages
This topic contains error messages that might result due to SSL handshake failures and provides solutions to help you troubleshoot these problems.
The following messages display due to handshake failures:
• Message: SSL0200E: Handshake Failed,

. 

o Reason: The handshake failed when the SSL library returned an unknown error. 

o Solution: Report this problem to Service.

• Message: SSL0201E: Handshake Failed, Internal error - Bad handle. 

o Reason: An internal error has occurred. 

o Solution: Report this problem to Service. 

• Message: SSL0202E: Handshake Failed, The GSK library unloaded. 

o Reason: A call to the GSKit function failed because the dynamic link library unloaded (Windows® operating systems only). 

o Solution: Shut down the server and restart. 

• Message: SSL0203E: Handshake Failed, GSK internal error. 

o Reason: The communication between client and the server failed due to an error in the GSKit library. 

o Solution: Retry connection from the client. If the error continues, report the problem to Service. 

• Message: SSL0204E: Handshake Failed, Internal memory allocation failure. 

o Reason: The server could not allocate memory needed to complete the operation. 

o Solution: Take action to free up some additional memory. Try reducing the number of threads or processes running, or increasing virtual memory.

• Message: SSL0205E: Handshake Failed, GSK handle is in an invalid state for operation. 

o Reason: The SSL state for the connection is invalid. 

o Solution: Retry connection from the client. If the error continues, report the problem to Service.

• Message: SSL0206E: Handshake Failed, Key-file label not found 

o Reason: The label specified for the SSLServerCert directive was not found in the key database (KDB) file specified for the KeyFile directive. 

o Solution: Specify a value for the SSLServerCert directive that corresponds to a personal certificate available in the KDB file specified for the KeyFile directive

• Message: SSL0207E: Handshake Failed, Certificate is not available. 

o Reason: The client did not send a certificate. 

o Solution: Set client authentication to optional if a client certificate is not required. Contact the client to determine why it is not sending an acceptable certificate. 

• Message: SSL0208E: Handshake Failed, Certificate validation error. 

o Reason: The received certificate failed one of the validation checks. 

o Solution: Use another certificate. Contact Service to determine why the certificate failed validation.

• Message: SSL0209E: Handshake Failed, ERROR processing cryptography. 

o Reason: A cryptography error occurred. 

o Solution: None. If the problem continues, report it to Service. 

• Message: SSL0210E: Handshake Failed, ERROR validating ASN fields in certificate. 

o Reason: The server was not able to validate one of the ASN fields in the certificate. 

o Solution: Try another certificate.

• Message: SSL0211E: Handshake Failed, ERROR connecting to LDAP server. 

o Reason: The Web server failed to connect to the CRL LDAP server. 

o Solution: Verify that the values entered for the SSLCRLHostname and SSLCRLPort directives are correct. If access to the CRL LDAP server requires authentication, is the SSLCRLUserID directive coded and was the password added to the stash file pointed to by the SSLStashfile directive. 

• Message: SSL0212E: Handshake Failed, Internal unknown error. 

o Report problem to Service. Reason: An unknown error has occurred in the SSL library. 

o Solution: Report the problem to Service. 

• Message: SSL0213E: Handshake Failed, Open failed due to cipher error. 

o Reason: An unknown error has occurred in the SSL library. 

o Solution: Report the problem to Service. 

• Message: SSL0214E: Handshake Failed, I/O error reading key file. 

o Reason: The server could not read the key database file. 

o Solution: Check file access permissions and verify the Web server user ID is allowed access. 

• Message: SSL0215E: Handshake Failed, Key file has an invalid internal format. Recreate key file. 

o Reason: Key file has an invalid format. 

o Solution: Recreate key file.

• Message: SSL0216E: Handshake Failed, Key file has two entries with the same key. Use IKEYMAN to remove the duplicate key. 

o Reason: Two identical keys exist in key file. 

o Solution: Use IKEYMAN to remove duplicate key.

• Message: SSL0217E: Handshake Failed, Key file has two entries with the same label. Use IKEYMAN to remove the duplicate label. 

o Reason: A second certificate with the same label was placed in the key database file. 

o Solution: Use IKEYMAN to remove duplicate label. 

• Message: SSL0218E: Handshake failed, Either the key file has become corrupted or the password is incorrect. 

o Reason: The key file password is used as an integrity check and the test failed. Either the key database file is corrupted, or the password is incorrect. 

o Solution: Use IKEYMAN to stash the key database file password again. If that fails, recreate the key database. 

• Message: SSL0219E: SSL Handshake Failed, Either the default key in the keyfile has an expired certificate or the keyfile password expired. Use iKeyman to renew or remove certificates that are expired or to set a new keyfile password. 

o Reason: Either the default key in the keyfile has an expired certificate or the keyfile password expired.

o Solution: Use iKeyman to renew or remove certificates that are expired or to set a new keyfile password.

• Message: SSL0220E: Handshake Failed, There was an error loading one of the GSKdynamic link libraries. Be sure GSK was installed correctly. 

o Reason: Opening the SSL environment resulted in an error because one of the GSKdynamic link libraries could not load. 

o Solution: Contact Support to make sure the GSKit is installed correctly.

• Message: SSL0221E: Handshake Failed, Either the certificate has expired or the system clock is incorrect. 

o Reason: Either the certificate expired or the system clock is incorrect.

o Solution: Use the key management utility (iKeyman) to recreate or renew your server certificate or change the system date to a valid date.

• Message: SSL0222W: Handshake failed, no ciphers specified. 

o Reason: SSLV2 and SSLV3 are disabled. 

o Solution: None. Report this problem to Service.

• Message: SSL0223E: Handshake Failed, No certificate. 

o Reason: The client did not send a certificate. 

You can also see this message when your keyfile does not have a default certificate specified and you have not specified an SSLServerCert directive. It will pass initialization but fail at connection (handshake) time.

o Solution: Set client authentication to optional if a client certificate is not required. Contact the client to determine why it is not sending a certificate. 

• Message: SSL0224E: Handshake failed, Invalid or improperly formatted certificate. 

o Reason: The client did not specify a valid certificate. 

o Solution: Client problem. 

• Message: SSL0225E: Handshake Failed, Unsupported certificate type. 

o Reason: The certificate type received from the client is not supported by this version of IBM® HTTP Server SSL. 

o Solution: The client must use a different certificate type. 

• Message: SSL0226I: Handshake Failed, I/O error during handshake. 

o Reason: The communication between the client and the server failed. This is a common error when the client closes the connection before the handshake has completed. 

o Solution: Retry the connection from the client.

• Message: SSL0227E: Handshake Failed, Specified label could not be found in the key file. 

o Reason: Specified key label is not present in key file. 

o Solution: Check that the SSLServerCert directive is correct, if coded, and that the label is valid for one of the keys in the key database.

• Message: SSL0228E: Handshake Failed, Invalid password for key file. 

o Reason: The password retrieved from the stash file could not open the key database file. 

o Solution: Use IKEYMAN to open the key database file and recreate the password stash file. This problem can also result from a corrupted key database file. Creating a new key database file may resolve the problem. 

• Message: SSL0229E: Handshake Failed, Invalid key length for export. 

o Reason: In a restricted cryptography environment, the key size is too long to be supported. 

o Solution: Select a certificate with a shorter key.

• Message: SSL0230I: Handshake Failed, An incorrectly formatted SSL message was received. 

• Message: SSL0231W: Handshake Failed, Could not verify MAC. 

o Reason: The communication between the client and the server failed. 

o Solution: Retry the connection from the client. 

• Message: SSL0232W: Handshake Failed, Unsupported SSL protocol or unsupported certificate type. 

o Reason: The communication between the client and the server failed because the client is trying to use a protocol or certificate which the IBM HTTP Server does not support. 

o Solution: Retry the connection from the client using an SSL Version 2 or 3, or TLS 1 protocol. Try another certificate. 

• Message: SSL0233W: Handshake Failed, Invalid certificate signature. 

• Message: SSL0234W: Handshake Failed, The certificate sent by the peer expired or is invalid. 

o Reason: The partner did not specify a valid certificate. The server is acting as a reverse proxy to an SSL URL and the _server_ cert could not be validated.

o Solution: Partner problem. If this occurs during an SSL Proxy connection, the remote SSL server sent a bad certificate to IBM HTTP Server. Check the certificate and certificate authority chain at the other end of the SSL connection. For more information, see Securing with SSL communications.

• Message: SSL0235W: Handshake Failed, Invalid peer. 

• Message: SSL0236W: Handshake Failed, Permission denied. 

• Message: SSL0237W: Handshake Failed, The self-signed certificate is not valid. 

• Message: SSL0238E: Handshake Failed, Internal error - read failed. 

o Reason: The read failed. 

o Solution: None. Report this error to Service. 

• Message: SSL0239E: Handshake Failed, Internal error - write failed. 

o Reason: The write failed. 

o Solution: None. Report this error to Service. 

• Message: SSL0240I: Handshake Failed, Socket has been closed. 

o Reason: The client closed the socket before the protocol completed. 

o Solution: Retry connection between client and server. 

• Message: SSL0241E: Handshake Failed, Invalid SSLV2 Cipher Spec. 

o Reason: The SSL Version 2 cipher specifications passed into the handshake were invalid. 

o Solution: Change the specified Version 2 cipher specs. 

• Message: SSL0242E: Handshake Failed, Invalid SSLV3 Cipher Spec. 

o Reason: The SSL Version 3 cipher specifications passed into the handshake were invalid. 

o Solution: Change the specified Version 3 cipher specs.

• Message: SSL0243E: Handshake Failed, Invalid security type. 

o Reason: There was an internal error in the SSL library. 

o Solution: Retry the connection from the client. If the error continues, report the problem to Service. 

• Message: SSL0245E: Handshake Failed, Internal error - SSL Handle creation failure. 

o Reason: There was an internal error in the security libraries. 

o Solution: None. Report this problem to Service. 

• Message: SSL0246E: Handshake Failed, Internal error - GSK initialization has failed. 

o Reason: An error in the security library has caused SSL initialization to fail. 

o Solution: None. Report this problem to Service. 

• Message: SSL0247E: Handshake Failed, LDAP server not available. 

o Reason: Unable to access the specified LDAP directory when validating a certificate. 

o Solution: Check that the SSLCRLHostname and SSLCRLPort directives are correct. Make sure the LDAP server is available.

• Message: SSL0248E: Handshake Failed, The specified key did not contain a private key. 

o Reason: The key does not contain a private key.

o Solution: Create a new key. If this was an imported key, include the private key when doing the export.

• Message: SSL0249E: Handshake Failed, A failed attempt was made to load the specified PKCS#11 shared library. 

o Reason: An error occurred while loading the PKCS#11 shared library. 

o Solution: Verify that the PKCS#11 shared library specified in the SSLPKCSDriver directive is valid.

• Message: SSL0250E: Handshake Failed, The PKCS#11 driver failed to find the token label specified by the caller. 

o Reason: The specified token was not found on the PKCS#11 device. 

o Solution: Check that the token label specified on the SSLServerCert directive is valid for your device.

• Message: SSL0251E: Handshake Failed, A PKCS#11 token is not present for the slot. 

o Reason: The PKCS#11 device has not been initialized correctly. 

o Solution: Specify a valid slot for the PKCS#11 token or initialize the device.

• Message: SSL0252E: Handshake Failed, The password/pin to access the PKCS#11 token is either not present, or invalid. 

o Reason: Specified user password and pin for PKCS#11 token is not present or invalid. 

o Solution: Check that the correct password was stashed using the SSLStash utility and that the SSLStashfile directive is correct.

• Message: SSL0253E: Handshake Failed, The SSL header received was not a properly SSLV2 formatted header. 

o Reason: The data received during the handshake does not conform to the SSLV2 protocol. 

o Solution: Retry connection between client and server. Verify that the client is using HTTPS.

• Message: SSL0254E: Internal error - I/O failed, buffer size invalid. 

o Reason: The buffer size in the call to the I/O function is zero or negative. 

o Solution: None. Report this problem to Service.

• Message: SSL0255E: Handshake Failed, Operation would block. 

o Reason: The I/O failed because the socket is in non-blocking mode. 

o Solution: None. Report this problem to Service.

• Message: SSL0256E: Internal error - SSLV3 is required for reset_cipher, and the connection uses SSLV2. 

o Reason: A reset_cipher function was attempted on an SSLV2 connection. 

o Solution: None. Report this problem to Service. 

• Message: SSL0257E: Internal error - An invalid ID was specified for the gsk_secure_soc_misc function call. 

o Reason: An invalid value was passed to the gsk_secure_soc_misc function. 

o Solution: None. Report this problem to Service.

• Message: SSL0258E: Handshake Failed, The function call, , has an invalid ID. 

o Reason: An invalid function ID was passed to the specified function. 

o Solution: None. Report this problem to Service.

• Message: SSL0259E: Handshake Failed, Internal error - The attribute has a negative length in: . 

o Reason: The length value passed to the function is negative, which is invalid. 

o Solution: None. Report this problem to Service. 

• Message: SSL0260E: Handshake Failed, The enumeration value is invalid for the specified enumeration type in: . 

o Reason: The function call contains an invalid function ID. 

o Solution: None. Report this problem to Service.

• Message: SSL0261E: Handshake Failed, The SID cache is invalid: . 

o Reason: The function call contains an invalid parameter list for replacing the SID cache routines. 

o Solution: None. Report this problem to Service. 

• Message: SSL0262E: Handshake Failed, The attribute has an invalid numeric value: . 

o Reason: The function call contains an invalid value for the attribute being set. 

o Solution: None. Report this problem to Service.

• Message: SSL0263W: SSL Connection attempted when SSL did not initialize. 

o Reason: A connection was received on an SSL-enabled virtual host but it could not be completed because there was an error during SSL initialization. 

o Solution: Check for an error message during startup and correct that problem. 

• Message: SSL0264E: Failure obtaining Cert data for label . 

o Reason: A GSKit error prevented the server certificate information from being retrieved. 

o Solution: Check for a previous error message with additional information. 

• Message: SSL0265W: Client did not supply a certificate. 

o Reason: A client who connected failed to send a client certificate and the server is configured to require a certificate. 

o Solution: Nothing on the server side.

• Message: SSL0266E: Handshake failed. 

o Reason: Could not establish SSL proxy connection. 

o Solution: IBM HTTP Server could not establish a proxy connection to a remote server using SSL.

• Message: SSL0267E: SSL Handshake failed. 

o Reason: Timeout on network operation during handshake.

o Solution: Check client connectivity, adjust TimeOuts.

• Message: SSL0270I: SSL Handshake Failed, Timeout (dd seconds) occurred before any data received. 

o Reason: A connection was received on an SSL port, but no data was received from the client before the timeout expired. 

o Solution: If the timeout (set by the Timeout directive) has been reduced from the default value, verify that it is reasonable. If the message occurs intermittently, it is probably normal, due to things like users cancelling page loads and browser or system crashes. If the message occurs in bursts, it might indicate a denial of service attack in progress.

• Message: SSL0271I: SSL Handshake Failed, client closed connection without sending any data. 

o Reason: A connection was received on an SSL port, but the client closed the connection without beginning the handshake. 

o Solution: If the timeout (set by the Timeout directive) has been reduced from the default value, verify that it is reasonable. If the message occurs intermittently, it is probably normal, due to things like users cancelling page loads and browser or system crashes. If the message occurs in bursts, it might indicate a denial of service attack in progress.

• Message: SSL0272I: SSL Handshake Failed, I/O error before any data received. 

o Reason: A connection was received on an SSL port, but a network error broke the connection before any data was received from the client. 

o Solution: If the message occurs intermittently, it is probably normal, due to things like users cancelling page loads and browser or system crashes. If the message occurs in bursts, it might indicate a denial of service attack in progress.

• Message: SSL0273I: Non-SSL request received on connection configured for SSL 

o Reason: A connection was received on an SSL port, but the data received was not SSL, and looked like a normal non-SSL request.

o Solution: Verify that the port in question is intended to be configured for SSL. Look for bad links to the page in question that should use https:, but instead use http:.





SSL initialization messages

This topic contains error messages that might result due to SSL initialization problems and provides solutions to help you troubleshoot these problems.

The following messages display as a result of initialization problems: 

• Message: SSL0100E: GSK could not initialize,  

o Reason: Initialization failed when the SSL library returned an unknown error. 

o Solution: None. Report this problem to Service. 

• Message: SSL0101E: GSK could not initialize, Neither the password nor the stash file name was specified. Could not open key file. 

o Reason: The stash file for the key database could not be found or is corrupted. 

o Solution: Use IKEYMAN to open the key database file and recreate the password stash file. 

• Message: SSL0102E: GSK could not initialize, Could not open key file. 

o Reason: The server could not open the key database file. 

o Solution: Check that the Keyfile directive is correct and that the file permissions allow the Web server user ID to access the file. 

• Message: SSL0103E: Internal error - GSK could not initialize, Unable to generate a temporary key pair. 

o Reason: GSK could not initialize; Unable to generate a temporary key pair.

o Solution: Report this problem to Service. 

• Message: SSL0104E: GSK could not initialize, Invalid password for key file. 

o Reason: The password retrieved from the stash file could not open the key database file. 

o Solution: Use IKEYMAN to open the key database file and recreate the password stash file. This problem could also result from a corrupted key database file. Creating a new key database file may resolve the problem. 

• Message: SSL0105E: GSK could not initialize, Invalid label. 

o Reason: Specified key label is not present in key file.

o Solution: Check that the SSLServerCert directive is correct, if coded, and that the label is valid for one of the keys in the key database. 

• Message: SSL0106E: Initialization error, Internal error - Bad handle 

o Reason: An internal error has occurred. 

o Solution: Report this problem to Service.

• Message: SSL0107E: Initialization error, The GSK library unloaded. 

o Reason: A call to the GSKit function failed because the dynamic link library unloaded (Windows® only). 

o Solution: Shut down the server and restart. 

• Message: SSL0108E: Initialization error, GSK internal error. 

o Reason: The communication between client and the server failed due to an error in the GSKit library. 

o Solution: Retry connection from the client. If the error continues, report the problem to Service. 

• Message: SSL0109E: GSK could not initialize, Internal memory allocation failure. 

o Reason: The server could not allocate memory needed to complete the operation. 

o Solution: Take action to free up some additional memory. Try reducing the number of threads or processes running, or increasing virtual memory. 

• Message :SSL0110E: Initialization error, GSK handle is in an invalid state for operation. 

o Reason: The SSL state for the connection is invalid. 

o Solution: Retry connection from the client. If the error continues, report the problem to Service. 

• Message: SSL0111E: Initialization error, Key file label not found. 

o Reason: Certificate or key label specified was not valid.

o Solution: Verify that the certificate name specified with the SSLServerCert directive is correct or, if no SSLServerCert directive was coded, that a default certificate exists in the key database.

• Message: SSL0112E: Initialization error, Certificate is not available. 

o Reason: The client did not send a certificate.

o Solution: Set Client Authentication to optional if a client certificate is not required. Contact the client to determine why it is not sending an acceptable certificate. 

• Message: SSL0113E: Initialization error, Certificate validation error. 

o Reason: The received certificate failed one of the validation checks.

o Solution: Use another certificate. Contact Service to determine why the certificate failed validation. 

• Message: SSL0114E: Initialization error, Error processing cryptography. 

o Reason: A cryptography error occurred. 

o Solution: None. If the problem continues, report it to Service.

• Message: SSL0115E: Initialization error, Error validating ASN fields in certificate. 

o Reason: The server was not able to validate one of the ASN fields in the certificate.

o Solution: Try another certificate.

• Message: SSL0116E: Initialization error, Error connecting to LDAP server. 

o Reason: The Web server failed to connect to the CRL LDAP server.

o Solution: Verify that the values entered for the SSLCRLHostname and SSLCRLPort directives are correct. If access to the CRL LDAP server requires authentication, is the SSLCRLUserID directive coded and was the password added to the stash file pointed to by the SSLStashfile directive. 

• Message: SSL0117E: Initialization error, Internal unknown error. Report problem to service. 

o Reason: Initialization error, Internal unknown error. Report problem to service.

o Solution: Initialization error, Internal unknown error. Report problem to service.

• Message: SSL0118E: Initialization error, Open failed due to cipher error. 

o Reason: Report problem to service. 

o Solution: Report problem to service.

• Message: SSL0119E: Initialization error, I/O error reading keyfile. 

o Reason: I/O error trying to read SSL keyfile. 

o Solution: Check the file permissions for keyfile.

• Message: SSL0120E: Initialization error, Keyfile has and invalid internal format. Recreate keyfile. 

o Reason: Initialization error, the keyfile has an invalid internal format. Recreate the keyfile. 

o Solution: Verify the keyfile is not corrupted.

• Message: SSL0121E: Initialization error, Keyfile has two entries with the same key. Use Ikeyman to remove the duplicate key. 

o Reason: The keyfile has two entries with the same key. Use Ikeyman to remove the duplicate key. 

o Solution: Use Ikeyman to remove the duplicate key.

• Message: SSL0122E: Initialization error, Keyfile has two entries with the same label. Use Ikeyman to remove the duplicate label. 

o Reason: The keyfile has two entries with the same label. Use Ikeyman to remove the duplicate label. 

o Solution: Use Ikeyman to remove the duplicate label.

• Message: SSL0123E: Initialization error, The keyfile password is used as an integrity check. Either the keyfile has become corrupted or the password is incorrect. 

o Reason: The keyfile password is used as an integrity check. Either the keyfile has become corrupted or the password is incorrect. 

o Solution: Use Ikeyman to verify that the keyfile is valid, check permissions on the stash file, verify passwords.

• Message: SSL0124E: SSL Handshake Failed, Either the default key in the keyfile has an expired certificate or the keyfile password expired. Use iKeyman to renew or remove certificates that are expired or to set a new keyfile password. 

o Reason: Either the default key in the keyfile has an expired certificate or the keyfile password expired.

o Solution: Use iKeyman to renew or remove certificates that are expired or to set a new keyfile password.

• Message: SSL0125E: Initialization error, There was an error loading one of the GSK dynamic link libraries. Be sure GSK is installed correctly. 

o Reason: There was an error loading one of the GSK dynamic link libraries. Be sure GSK is installed correctly. 

o Solution: Verify GSK is installed and appropriate level for release of IBM® HTTP Server.

• Message: SSL0126E: Handshake Failed, Either the certificate has expired or the system clock is incorrect. 

o Reason: Either the certificate expired or the system clock is incorrect.

o Solution: Use the key management utility (iKeyman) to recreate or renew your server certificate or change the system date to a valid date.

• Message: SSL0127E: Initialization error, No ciphers specified. 

o Reason: Initialization error, no ciphers specified. 

o Solution: Report problem to service.

• Message: SSL0128E: Initialization error, Either the certificate expired or the system clock is incorrect. 

o Reason: Initialization error, no certificate. 

o Solution: Report problem to service.

• Message: SSL0129E: Initialization error, The received certificate was formatted incorrectly. 

o Reason: The received certificate is formatted incorrectly. 

o Solution: Use Ikeyman to validate certificates used for connection.

• Message: SSL0130E: Initialization error, Unsupported certificate type. 

o Reason: Unsupported certificate type. 

o Solution: Check certificates that are used for this connection in Ikeyman.

• Message: SSL0131I: Initialization error, I/O error during handshake. 

o Reason: I/O error during handshake. 

o Solution: Check network connectivity.

• Message: SSL0132E: Initialization error, Invalid key length for export. 

o Reason: Invalid key length for export. 

o Solution: Report problem to service.

• Message: SSL0133W: Initialization error, An incorrectly formatted SSL message was received. 

o Reason: An incorrectly formatted SSL message was received. 

o Solution: Check client settings.

• Message: SSL0134W: Initialization error, Could not verify MAC. 

o Reason: Could not verify MAC. 

o Solution: Report problem to service.

• Message: SSL0135W: Initialization error, Unsupported SSL protocol or unsupported certificate type. 

o Reason: Unsupported SSL protocol or unsupported certificate type. 

o Solution: Check server ciphers and certificate settings.

• Message: SSL0136W: Initialization error, Invalid certificate signature. 

o Reason: Invalid certificate signature. 

o Solution: Check certificate in Ikeyman. 

• Message: SSL0137W: Initialization error, Invalid certificate sent by partner. 

o Reason: Invalid certificate sent by partner. 

o Solution: If this occurs during an SSL Proxy connection, the remote SSL server sent a bad certificate to IBM HTTP Server. Check the certificate and certificate authority chain at the other end of the SSL connection.

• Message: SSL0138W: Initialization error, Invalid peer. 

o Reason: Invalid peer. 

o Solution: Report problem to service.

• Message: SSL0139W: Initialization error, Permission denied. Distributed Platforms 

o Reason: Permission denied.

o Solution: Report problem to service.

z/os

o Reason: If a System Authorization Facility (SAF) SSL keyring is in use, the current user ID is not authorized to read the keyring.

o Solution: See the information about access to SAF keyrings in Performing required z/OS system configurations 

• Message: SSL0140W: Initialization error, The self-signed certificate is not valid. 

o Reason: The self-signed certificate is not valid. 

o Solution: Check the certificate in Ikeyman. 

• Message: SSL0141E: Initialization error, Internal error - read failed. 

o Reason: Internal error - read failed. 

o Solution: Report to service.

• Message: SSL0142E: Initialization error, Internal error - write failed. 

o Reason: Internal error - write failed. 

o Solution: Report to service.

• Message: SSL0143I: Initialization error, Socket has been closed. 

o Reason: Socket has been closed unexpectedly. 

o Solution: Check the client and network. Report problem to service.

• Message: SSL0144E: Initialization error, Invalid SSLV2 Cipher Spec. 

o Reason: Invalid SSLV2 cipher spec. 

o Solution: Check the SSLCipherSpec directive.

• Message: SSL0145E: Initialization error, Invalid SSLV3 Cipher Spec. 

o Reason: Invalid SSLV3 Cipher Spec. 

o Solution: Check the SSLCipherSpec directive.

• Message: SSL0146E: Initialization error, Invalid security type. 

o Reason: Invalid security type. 

o Solution: Report to service.

• Message: SSL0147E: Initialization error, Invalid security type combination. 

o Reason: Invalid security type combination. 

o Solution: Report to service.

• Message: SSL0148E: Initialization error, Internal error - SSL Handle creation failure. 

o Reason: Internal error - SSL handle creation failure. 

o Solution: Report to service.

• Message: SSL0149E: Initialization error, Internal error - GSK initialization has failed. 

o Reason: Internal error - GSK initialization has failed. 

o Solution: Report to service.

• Message: SSL0150E: Initialization error, LDAP server not available. 

o Reason: LDAP server not available. 

o Solution: Check CRL directives.

• Message: SSL0151E: Initialization error, The specified key did not contain a private key. 

o Reason: The specified key did not contain a private key. 

o Solution: Check the certificate in use in Ikeyman.

• Message: SSL0152E: Initialization error, A failed attempt was made to load the specified PKCS#11 shared library. 

o Reason: A failed attempt was made to load the specified PKCS#11 shared library. 

o Solution: Check SSLPKCSDriver directive and file system.

• Message: SSL0153E: Initialization error, The PKCS#11 driver failed to find the token specified by the caller. 

o Reason: The PKCS#11 driver failed to find the token specified by the caller. 

• Message: SSL0154E: Initialization error, A PKCS#11 token is not present for the slot. 

o Reason: A PKCS#11 token is not present for the slot. 

o Solution: Verify PKCS#11 directives.

• Message: SSL0155E: Initialization error, The password/pin to access the PKCS#11 token is invalid. 

o Reason: The password and pin to access the PKCS#11 token is invalid. 

• Message: SSL0156E: Initialization error, The SSL header received was not a properly SSLV2 formatted header. 

o Reason: The SSL header received was not a properly SSLV2 formatted header. 

• Message: SSL0157E: Initialization error, The function call, %s, has an invalid ID. 

o Reason: The function call, %s, has an invalid ID. 

o Solution: Report problem to service.

• Message: SSL0158E: Initialization error, Internal error - The attribute has a negative length: %s. 

o Reason: Internal error - The attribute has a negative length. 

o Solution: Report problem to service.

• Message: SSL0159E: Initialization error, The enumeration value is invalid for the specified enumeration type: %s. 

o Reason: The enumeration value is invalid for the specified enumeration type: %s. 

o Solution: Report problem to service.

• Message: SSL0160E: Initialization error, The SID cache is invalid: %s. 

o Reason: The SID cache is invalid.

o Solution: Report problem to service. 

• Message: SSL0161E: Initialization error, The attribute has an invalid numeric value: %s. 

o Reason: The attribute has an invalid numeric value: %s.

o Solution: Check SSL directives.

• Message: SSL0162W: Setting the LD_LIBRARY_PATH or LIBPATH for GSK failed. 

o Reason: Could not update the environment for GSK libraries. 

o Solution: Report problem to service.

• Message: SSL0163W: Setting the LIBPATH for GSK failed, could not append /usr/opt/ibm/gskkm/lib. 

o Reason: Could not append to LD_LIBRARY_PATH or LIBPATH for GSK failed. 

o Solution: Report problem to service.

• Message: SSL0164W: Error accessing Registry, RegOpenKeyEx/RegQueryValueEx returned [%d]. 

o Reason: Error accessing registry. 

o Solution: Check GSK installation and windows registry.

• Message: SSL0165W: Storage allocation failed. 

o Reason: Storage allocation failed. 

o Solution: Check memory usage, report problem to service.

• Message: SSL0166E: Failure attempting to load GSK library. 

o Reason: Failure while attempting to load GSK library. 

o Solution: Check the GSK installation.

• Message: SSL0167E: GSK function address undefined. 

o Reason: GSK function address is undefined. 

o Solution: Check the GSK installation and level.

• Message: SSL0168E: SSL initialization for server: %s, port: %u failed due to a configuration error. 

o Reason: Iinitialization for server: %s, port: %u failed due to a configuration error. 

o Solution: Check the SSL configuration.

• Message: SSL0169E: Keyfile does not exist: %s. 

o Reason: Keyfile does not exist. 

o Solution: Check to ensure the path that is provided to the KeyFile directive exists, and is readable by the user that IBM HTTP Server is running as.

• Message: SSL0170E: GSK could not initialize, no keyfile specified. 

o Reason: Keyfile is not specified. 

o Solution: Specify Keyfile directive.

• Message: SSL0171E: CRL cannot be specified as an option for the SSLClientAuth directive on HPUX because the IBM HTTP Server does not support CRL on HPUX. 

o Reason: CRL cannot be specified as an option for the SSLClientAuth directive on HPUX because IBM HTTP Server does not support CRL on HPUX. 

o Solution: Remove CRL directives.

• Message: SSL0172E: If CRL is turned on, you must specify an LDAP hostname for the SSLCRLHostname directive. 

o Reason: If CRL is turned on, you must specify an LDAP hostname for the SSLCRLHostname directive. 

o Solution: Specify SSLCRLHostname.

• Message: SSL0173E: Failure obtaining supported cipher specs from the GSK library. 

o Reason: Failure obtaining supported cipher specs from the GSK library. 

o Solution: Check the GSK installation, report problem to service.

• Message: SSL0174I: No CRL password found in the stash file: %s. 

o Reason: No CRL password is found in the stash file: %s. 

o Solution: Check the stash file permissions, regenerate stash file.

• Message: SSL0174I: No CRYPTO password found in the stash file: %s. 

o Reason: No CRYPTO password is found in the stash file: %s. 

o Solution: Check stash file permissions, regenerate stash file.

• Message: SSL0175E: fopen failed for stash file: %s. 

o Reason: fopen failed for stash file. 

o Solution: Check stash file permissions, regenerate stash file. 

• Message: SSL0176E: fread failed for the stash file: %s. 

o Reason: fread failed for the stash file.

o Solution: Make sure the stash file is readable by user IBM HTTP Server is running as.

• Message: SSL0179E: Unknown return code from stash_recover(), %d. 

o Reason: Unknown return code from stash_recover(), %d. 

o Solution: Check the stash file.

• Message: SSL0181E: Unable to fork for startup of session ID cache. 

o Reason: Unable to fork for startup of session ID cache.

o Solution: Check the location of sidd daemon, file permissions.

• Message: SSL0182E: Error creating file mapped memory for SSL passwords. 

o Reason: Error creating file mapped memory for SSL passwords. 

o Solution: Report problem to service.

• Message: SSL0183E: Exceeded map memory limits. 

o Reason: Exceeded map memory limits. 

o Solution: Report problem to service.

• Message: SSL0184E: Could not find a password for the resource: %s. 

o Reason: SSL0184E: Could not find a password for the resource: %s. 

o Solution: Report problem to service, disable password prompting.

• Message: SSL0185E: ssl_getpwd() failed, unable to obtain memory. 

o Reason: ssl_getpwd() failed, unable to obtain memory. 

o Solution: Report problem to service, disable password prompting.

• Message: SSL0186E: Linked list mismatch. 

o Reason: SSL0186E: Linked list mismatch. 

o Solution: Report problem to service, disable password prompting.

• Message: SSL0186E: ssl_getpwd() failed, password exceeded maximum size of 4095. 

o Reason: ssl_getpwd() failed, password exceeded the maximum size of 4095. 

o Solution: The password must be smaller than 4K.

• Message: SSL0187E: It is invalid to enable password prompting for the SSLServerCert directive without specifying a Crypto Card Token. 

o Reason: It is invalid to enable password prompting for the SSLServerCert directive without specifying a crypto card token. 

o Solution: Specify a crypto card token or disable password prompting for the SSLServerCert directive.

• Message: SSL0188E: SSL initialization for server: %s, port: %u failed. SSL timeouts cannot be set in a virtualhost when the SSLCacheDisable directive has not been specified globally. 

o Reason: When the SSL session cache is being used, only the global timeout settings apply because they are managed by the external session cache daemon. See information about the SSLCacheDisable and SSLCacheEnable directives in the information center topic entitled SSL directives.

o Solution: If separate SSL timeouts are required, disable use of the session ID cache (SSLCacheDisable), otherwise make sure the SSLV3Timeout and SSLV2Timeout directives are only set in the global scope.



SSL initialization messages

This topic contains error messages that might result due to SSL initialization problems and provides solutions to help you troubleshoot these problems.

The following messages display as a result of initialization problems: 

• Message: SSL0100E: GSK could not initialize,  

o Reason: Initialization failed when the SSL library returned an unknown error. 

o Solution: None. Report this problem to Service. 

• Message: SSL0101E: GSK could not initialize, Neither the password nor the stash file name was specified. Could not open key file. 

o Reason: The stash file for the key database could not be found or is corrupted. 

o Solution: Use IKEYMAN to open the key database file and recreate the password stash file. 

• Message: SSL0102E: GSK could not initialize, Could not open key file. 

o Reason: The server could not open the key database file. 

o Solution: Check that the Keyfile directive is correct and that the file permissions allow the Web server user ID to access the file. 

• Message: SSL0103E: Internal error - GSK could not initialize, Unable to generate a temporary key pair. 

o Reason: GSK could not initialize; Unable to generate a temporary key pair.

o Solution: Report this problem to Service. 

• Message: SSL0104E: GSK could not initialize, Invalid password for key file. 

o Reason: The password retrieved from the stash file could not open the key database file. 

o Solution: Use IKEYMAN to open the key database file and recreate the password stash file. This problem could also result from a corrupted key database file. Creating a new key database file may resolve the problem. 

• Message: SSL0105E: GSK could not initialize, Invalid label. 

o Reason: Specified key label is not present in key file.

o Solution: Check that the SSLServerCert directive is correct, if coded, and that the label is valid for one of the keys in the key database. 

• Message: SSL0106E: Initialization error, Internal error - Bad handle 

o Reason: An internal error has occurred. 

o Solution: Report this problem to Service.

• Message: SSL0107E: Initialization error, The GSK library unloaded. 

o Reason: A call to the GSKit function failed because the dynamic link library unloaded (Windows® only). 

o Solution: Shut down the server and restart. 

• Message: SSL0108E: Initialization error, GSK internal error. 

o Reason: The communication between client and the server failed due to an error in the GSKit library. 

o Solution: Retry connection from the client. If the error continues, report the problem to Service. 

• Message: SSL0109E: GSK could not initialize, Internal memory allocation failure. 

o Reason: The server could not allocate memory needed to complete the operation. 

o Solution: Take action to free up some additional memory. Try reducing the number of threads or processes running, or increasing virtual memory. 

• Message :SSL0110E: Initialization error, GSK handle is in an invalid state for operation. 

o Reason: The SSL state for the connection is invalid. 

o Solution: Retry connection from the client. If the error continues, report the problem to Service. 

• Message: SSL0111E: Initialization error, Key file label not found. 

o Reason: Certificate or key label specified was not valid.

o Solution: Verify that the certificate name specified with the SSLServerCert directive is correct or, if no SSLServerCert directive was coded, that a default certificate exists in the key database.

• Message: SSL0112E: Initialization error, Certificate is not available. 

o Reason: The client did not send a certificate.

o Solution: Set Client Authentication to optional if a client certificate is not required. Contact the client to determine why it is not sending an acceptable certificate. 

• Message: SSL0113E: Initialization error, Certificate validation error. 

o Reason: The received certificate failed one of the validation checks.

o Solution: Use another certificate. Contact Service to determine why the certificate failed validation. 

• Message: SSL0114E: Initialization error, Error processing cryptography. 

o Reason: A cryptography error occurred. 

o Solution: None. If the problem continues, report it to Service.

• Message: SSL0115E: Initialization error, Error validating ASN fields in certificate. 

o Reason: The server was not able to validate one of the ASN fields in the certificate.

o Solution: Try another certificate.

• Message: SSL0116E: Initialization error, Error connecting to LDAP server. 

o Reason: The Web server failed to connect to the CRL LDAP server.

o Solution: Verify that the values entered for the SSLCRLHostname and SSLCRLPort directives are correct. If access to the CRL LDAP server requires authentication, is the SSLCRLUserID directive coded and was the password added to the stash file pointed to by the SSLStashfile directive. 

• Message: SSL0117E: Initialization error, Internal unknown error. Report problem to service. 

o Reason: Initialization error, Internal unknown error. Report problem to service.

o Solution: Initialization error, Internal unknown error. Report problem to service.

• Message: SSL0118E: Initialization error, Open failed due to cipher error. 

o Reason: Report problem to service. 

o Solution: Report problem to service.

• Message: SSL0119E: Initialization error, I/O error reading keyfile. 

o Reason: I/O error trying to read SSL keyfile. 

o Solution: Check the file permissions for keyfile.

• Message: SSL0120E: Initialization error, Keyfile has and invalid internal format. Recreate keyfile. 

o Reason: Initialization error, the keyfile has an invalid internal format. Recreate the keyfile. 

o Solution: Verify the keyfile is not corrupted.

• Message: SSL0121E: Initialization error, Keyfile has two entries with the same key. Use Ikeyman to remove the duplicate key. 

o Reason: The keyfile has two entries with the same key. Use Ikeyman to remove the duplicate key. 

o Solution: Use Ikeyman to remove the duplicate key.

• Message: SSL0122E: Initialization error, Keyfile has two entries with the same label. Use Ikeyman to remove the duplicate label. 

o Reason: The keyfile has two entries with the same label. Use Ikeyman to remove the duplicate label. 

o Solution: Use Ikeyman to remove the duplicate label.

• Message: SSL0123E: Initialization error, The keyfile password is used as an integrity check. Either the keyfile has become corrupted or the password is incorrect. 

o Reason: The keyfile password is used as an integrity check. Either the keyfile has become corrupted or the password is incorrect. 

o Solution: Use Ikeyman to verify that the keyfile is valid, check permissions on the stash file, verify passwords.

• Message: SSL0124E: SSL Handshake Failed, Either the default key in the keyfile has an expired certificate or the keyfile password expired. Use iKeyman to renew or remove certificates that are expired or to set a new keyfile password. 

o Reason: Either the default key in the keyfile has an expired certificate or the keyfile password expired.

o Solution: Use iKeyman to renew or remove certificates that are expired or to set a new keyfile password.

• Message: SSL0125E: Initialization error, There was an error loading one of the GSK dynamic link libraries. Be sure GSK is installed correctly. 

o Reason: There was an error loading one of the GSK dynamic link libraries. Be sure GSK is installed correctly. 

o Solution: Verify GSK is installed and appropriate level for release of IBM® HTTP Server.

• Message: SSL0126E: Handshake Failed, Either the certificate has expired or the system clock is incorrect. 

o Reason: Either the certificate expired or the system clock is incorrect.

o Solution: Use the key management utility (iKeyman) to recreate or renew your server certificate or change the system date to a valid date.

• Message: SSL0127E: Initialization error, No ciphers specified. 

o Reason: Initialization error, no ciphers specified. 

o Solution: Report problem to service.

• Message: SSL0128E: Initialization error, Either the certificate expired or the system clock is incorrect. 

o Reason: Initialization error, no certificate. 

o Solution: Report problem to service.

• Message: SSL0129E: Initialization error, The received certificate was formatted incorrectly. 

o Reason: The received certificate is formatted incorrectly. 

o Solution: Use Ikeyman to validate certificates used for connection.

• Message: SSL0130E: Initialization error, Unsupported certificate type. 

o Reason: Unsupported certificate type. 

o Solution: Check certificates that are used for this connection in Ikeyman.

• Message: SSL0131I: Initialization error, I/O error during handshake. 

o Reason: I/O error during handshake. 

o Solution: Check network connectivity.

• Message: SSL0132E: Initialization error, Invalid key length for export. 

o Reason: Invalid key length for export. 

o Solution: Report problem to service.

• Message: SSL0133W: Initialization error, An incorrectly formatted SSL message was received. 

o Reason: An incorrectly formatted SSL message was received. 

o Solution: Check client settings.

• Message: SSL0134W: Initialization error, Could not verify MAC. 

o Reason: Could not verify MAC. 

o Solution: Report problem to service.

• Message: SSL0135W: Initialization error, Unsupported SSL protocol or unsupported certificate type. 

o Reason: Unsupported SSL protocol or unsupported certificate type. 

o Solution: Check server ciphers and certificate settings.

• Message: SSL0136W: Initialization error, Invalid certificate signature. 

o Reason: Invalid certificate signature. 

o Solution: Check certificate in Ikeyman. 

• Message: SSL0137W: Initialization error, Invalid certificate sent by partner. 

o Reason: Invalid certificate sent by partner. 

o Solution: If this occurs during an SSL Proxy connection, the remote SSL server sent a bad certificate to IBM HTTP Server. Check the certificate and certificate authority chain at the other end of the SSL connection.

• Message: SSL0138W: Initialization error, Invalid peer. 

o Reason: Invalid peer. 

o Solution: Report problem to service.

• Message: SSL0139W: Initialization error, Permission denied. 

o Reason: Permission denied.

o Solution: Report problem to service.



o Reason: If a System Authorization Facility (SAF) SSL keyring is in use, the current user ID is not authorized to read the keyring.

o Solution: See the information about access to SAF keyrings in Performing required z/OS system configurations 

• Message: SSL0140W: Initialization error, The self-signed certificate is not valid. 

o Reason: The self-signed certificate is not valid. 

o Solution: Check the certificate in Ikeyman. 

• Message: SSL0141E: Initialization error, Internal error - read failed. 

o Reason: Internal error - read failed. 

o Solution: Report to service.

• Message: SSL0142E: Initialization error, Internal error - write failed. 

o Reason: Internal error - write failed. 

o Solution: Report to service.

• Message: SSL0143I: Initialization error, Socket has been closed. 

o Reason: Socket has been closed unexpectedly. 

o Solution: Check the client and network. Report problem to service.

• Message: SSL0144E: Initialization error, Invalid SSLV2 Cipher Spec. 

o Reason: Invalid SSLV2 cipher spec. 

o Solution: Check the SSLCipherSpec directive.

• Message: SSL0145E: Initialization error, Invalid SSLV3 Cipher Spec. 

o Reason: Invalid SSLV3 Cipher Spec. 

o Solution: Check the SSLCipherSpec directive.

• Message: SSL0146E: Initialization error, Invalid security type. 

o Reason: Invalid security type. 

o Solution: Report to service.

• Message: SSL0147E: Initialization error, Invalid security type combination. 

o Reason: Invalid security type combination. 

o Solution: Report to service.

• Message: SSL0148E: Initialization error, Internal error - SSL Handle creation failure. 

o Reason: Internal error - SSL handle creation failure. 

o Solution: Report to service.

• Message: SSL0149E: Initialization error, Internal error - GSK initialization has failed. 

o Reason: Internal error - GSK initialization has failed. 

o Solution: Report to service.

• Message: SSL0150E: Initialization error, LDAP server not available. 

o Reason: LDAP server not available. 

o Solution: Check CRL directives.

• Message: SSL0151E: Initialization error, The specified key did not contain a private key. 

o Reason: The specified key did not contain a private key. 

o Solution: Check the certificate in use in Ikeyman.

• Message: SSL0152E: Initialization error, A failed attempt was made to load the specified PKCS#11 shared library. 

o Reason: A failed attempt was made to load the specified PKCS#11 shared library. 

o Solution: Check SSLPKCSDriver directive and file system.

• Message: SSL0153E: Initialization error, The PKCS#11 driver failed to find the token specified by the caller. 

o Reason: The PKCS#11 driver failed to find the token specified by the caller. 

• Message: SSL0154E: Initialization error, A PKCS#11 token is not present for the slot. 

o Reason: A PKCS#11 token is not present for the slot. 

o Solution: Verify PKCS#11 directives.

• Message: SSL0155E: Initialization error, The password/pin to access the PKCS#11 token is invalid. 

o Reason: The password and pin to access the PKCS#11 token is invalid. 

• Message: SSL0156E: Initialization error, The SSL header received was not a properly SSLV2 formatted header. 

o Reason: The SSL header received was not a properly SSLV2 formatted header. 

• Message: SSL0157E: Initialization error, The function call, %s, has an invalid ID. 

o Reason: The function call, %s, has an invalid ID. 

o Solution: Report problem to service.

• Message: SSL0158E: Initialization error, Internal error - The attribute has a negative length: %s. 

o Reason: Internal error - The attribute has a negative length. 

o Solution: Report problem to service.

• Message: SSL0159E: Initialization error, The enumeration value is invalid for the specified enumeration type: %s. 

o Reason: The enumeration value is invalid for the specified enumeration type: %s. 

o Solution: Report problem to service.

• Message: SSL0160E: Initialization error, The SID cache is invalid: %s. 

o Reason: The SID cache is invalid.

o Solution: Report problem to service. 

• Message: SSL0161E: Initialization error, The attribute has an invalid numeric value: %s. 

o Reason: The attribute has an invalid numeric value: %s.

o Solution: Check SSL directives.

• Message: SSL0162W: Setting the LD_LIBRARY_PATH or LIBPATH for GSK failed. 

o Reason: Could not update the environment for GSK libraries. 

o Solution: Report problem to service.

• Message: SSL0163W: Setting the LIBPATH for GSK failed, could not append /usr/opt/ibm/gskkm/lib. 

o Reason: Could not append to LD_LIBRARY_PATH or LIBPATH for GSK failed. 

o Solution: Report problem to service.

• Message: SSL0164W: Error accessing Registry, RegOpenKeyEx/RegQueryValueEx returned [%d]. 

o Reason: Error accessing registry. 

o Solution: Check GSK installation and windows registry.

• Message: SSL0165W: Storage allocation failed. 

o Reason: Storage allocation failed. 

o Solution: Check memory usage, report problem to service.

• Message: SSL0166E: Failure attempting to load GSK library. 

o Reason: Failure while attempting to load GSK library. 

o Solution: Check the GSK installation.

• Message: SSL0167E: GSK function address undefined. 

o Reason: GSK function address is undefined. 

o Solution: Check the GSK installation and level.

• Message: SSL0168E: SSL initialization for server: %s, port: %u failed due to a configuration error. 

o Reason: Iinitialization for server: %s, port: %u failed due to a configuration error. 

o Solution: Check the SSL configuration.

• Message: SSL0169E: Keyfile does not exist: %s. 

o Reason: Keyfile does not exist. 

o Solution: Check to ensure the path that is provided to the KeyFile directive exists, and is readable by the user that IBM HTTP Server is running as.

• Message: SSL0170E: GSK could not initialize, no keyfile specified. 

o Reason: Keyfile is not specified. 

o Solution: Specify Keyfile directive.

• Message: SSL0171E: CRL cannot be specified as an option for the SSLClientAuth directive on HPUX because the IBM HTTP Server does not support CRL on HPUX. 

o Reason: CRL cannot be specified as an option for the SSLClientAuth directive on HPUX because IBM HTTP Server does not support CRL on HPUX. 

o Solution: Remove CRL directives.

• Message: SSL0172E: If CRL is turned on, you must specify an LDAP hostname for the SSLCRLHostname directive. 

o Reason: If CRL is turned on, you must specify an LDAP hostname for the SSLCRLHostname directive. 

o Solution: Specify SSLCRLHostname.

• Message: SSL0173E: Failure obtaining supported cipher specs from the GSK library. 

o Reason: Failure obtaining supported cipher specs from the GSK library. 

o Solution: Check the GSK installation, report problem to service.

• Message: SSL0174I: No CRL password found in the stash file: %s. 

o Reason: No CRL password is found in the stash file: %s. 

o Solution: Check the stash file permissions, regenerate stash file.

• Message: SSL0174I: No CRYPTO password found in the stash file: %s. 

o Reason: No CRYPTO password is found in the stash file: %s. 

o Solution: Check stash file permissions, regenerate stash file.

• Message: SSL0175E: fopen failed for stash file: %s. 

o Reason: fopen failed for stash file. 

o Solution: Check stash file permissions, regenerate stash file. 

• Message: SSL0176E: fread failed for the stash file: %s. 

o Reason: fread failed for the stash file.

o Solution: Make sure the stash file is readable by user IBM HTTP Server is running as.

• Message: SSL0179E: Unknown return code from stash_recover(), %d. 

o Reason: Unknown return code from stash_recover(), %d. 

o Solution: Check the stash file.

• Message: SSL0181E: Unable to fork for startup of session ID cache. 

o Reason: Unable to fork for startup of session ID cache.

o Solution: Check the location of sidd daemon, file permissions.

• Message: SSL0182E: Error creating file mapped memory for SSL passwords. 

o Reason: Error creating file mapped memory for SSL passwords. 

o Solution: Report problem to service.

• Message: SSL0183E: Exceeded map memory limits. 

o Reason: Exceeded map memory limits. 

o Solution: Report problem to service.

• Message: SSL0184E: Could not find a password for the resource: %s. 

o Reason: SSL0184E: Could not find a password for the resource: %s. 

o Solution: Report problem to service, disable password prompting.

• Message: SSL0185E: ssl_getpwd() failed, unable to obtain memory. 

o Reason: ssl_getpwd() failed, unable to obtain memory. 

o Solution: Report problem to service, disable password prompting.

• Message: SSL0186E: Linked list mismatch. 

o Reason: SSL0186E: Linked list mismatch. 

o Solution: Report problem to service, disable password prompting.

• Message: SSL0186E: ssl_getpwd() failed, password exceeded maximum size of 4095. 

o Reason: ssl_getpwd() failed, password exceeded the maximum size of 4095. 

o Solution: The password must be smaller than 4K.

• Message: SSL0187E: It is invalid to enable password prompting for the SSLServerCert directive without specifying a Crypto Card Token. 

o Reason: It is invalid to enable password prompting for the SSLServerCert directive without specifying a crypto card token. 

o Solution: Specify a crypto card token or disable password prompting for the SSLServerCert directive.

• Message: SSL0188E: SSL initialization for server: %s, port: %u failed. SSL timeouts cannot be set in a virtualhost when the SSLCacheDisable directive has not been specified globally. 

o Reason: When the SSL session cache is being used, only the global timeout settings apply because they are managed by the external session cache daemon. See information about the SSLCacheDisable and SSLCacheEnable directives in the information center topic entitled SSL directives.

o Solution: If separate SSL timeouts are required, disable use of the session ID cache (SSLCacheDisable), otherwise make sure the SSLV3Timeout and SSLV2Timeout directives are only set in the global scope.

SSL stash utility messages

This topic contains error messages that might result due to Secure Sockets Layer (SSL) stash utility problems and provides solutions to help you troubleshoot these problems.

The following messages appear due to SSL Stash utility errors: 

• Message: SSL0700S: Invalid function  

o Reason: An invalid parameter was entered. The valid values are crl or crypto. 

o Solution: Rerun the command with the proper function. 

• Message: SSL0701S: The password was not entered. 

o Reason: The password was not entered on the command line. 

o Solution: Rerun the command with the password added. 

• Message: SSL0702S: Password exceeds the allowed length of 512. 

o Reason: The password that was entered is longer than the allowed maximum of 512 characters. 

o Solution: Use a shorter password.



IBM HTTP Server basic administration of server
2010-05-03T00:06:00.000-07:00
This topic describes how to start and stop the IBM® HTTP Server administration server on distributed platforms.



null





For this task 



Start the IBM HTTP Server administration server as follows. You must be logged in as a root user, or If you installed as non root user for IHS then you must SU - to same user which is owned by IHS.

If it is Windows then you should be administrator.



Procedure 

Windows : 



From the Start menu



Click Start > Programs > IBM HTTP Server > Start Administration Server. 

A message box displays that indicates the server has started.



If the IBM HTTP Server administration server does not start, complete the following steps:

1.Open the Control Panel.

2.Click Services.

3.Double-click IBM HTTP Server Administration Server to start the server.

Confirm that IBM HTTP Server administration server started successfully by checking the admin_error.log file for a "start successful" message. If you use the developer installation option, then the IBM HTTP Server administration server does not install as a service. You have to run the httpd.exe file from a command line with the -f option. From the default directory, type:

httpd -f  conf\admin.conf









ALL UNIX (AIX, HP-UX, Linux, Solaris):



The adminctl command starts and stops the IBM HTTP Server administration server. You can find the adminctl command in the bin subdirectory, within the IBM HTTP Server installation directory. If that directory is not in your PATH, the full path should be given on the command line. Start or stop the IBM HTTP Server administration server using the default admin.conf configuration file as follows:



null



1.Run the adminctl start command to start the server or run the adminctl stop command to stop the server.



Issue the commands from the default directories, based on your operating system:



AIX : /usr/IBM/HTTPServer/bin/adminctl start|stop 



HP-UX, Linux, Solaris : /opt/IBM/HTTPServer/bin/adminctl start|stop 



null





For example, The adminctl command is not in your PATH, the IBM HTTP Server installation directory is /usr/IBM/HTTPServer, and the default configuration file is used as follows:



/usr/IBM/HTTPServer/bin/adminctl start

/usr/IBM/HTTPServer/bin/adminctl stop



Important: The admin.conf configuration file supports single-byte characters (SBCS) only.

2.Confirm that IBM HTTP Server administration server started successfully by checking the admin_error.log.



Note: Some times IBM HTTP server process will be found Hung (defunct process) in UNIX environments resulting server will not respond or function even though server’s status is running. 



Possible Cause’s: More child process for single instance / reached the maximum open files limit / more memory or CPU usage / reached the maximum user limit..Etc..!



Resolution: How to kill in the above situation. 



Kill – (Process ID) , Kill -9 (Process ID) for force fully kill. 



If you want to number of defunct process or chilled process which is causing problem. 



for i in `ps -ef|grep master Process id of http server|grep -v grep |awk '{print $2}'`; do echo $i;kill -9 $i; done


Thinking in Patterns, Problem-Solving Techniques using Java
2010-04-29T08:12:00.000-07:00
nullThe pattern concept

“Design patterns help you learn from others' successes instead of your





own failures[2].”

Probably the most important step forward in object-oriented design is the “design patterns”



null





movement, chronicled in Design Patterns (ibid)[3]. That book shows 23 different solutions to

particular classes of problems. In this book, the basic concepts of design patterns will be

introduced along with examples. This should whet your appetite to read Design Patterns by

Gamma, et. al., a source of what has now become an essential, almost mandatory, vocabulary

for OOP programmers.

The latter part of this book contains an example of the design evolution process, starting with

an initial solution and moving through the logic and process of evolving the solution to more

appropriate designs. The program shown (a trash sorting simulation) has evolved over time,

and you can look at that evolution as a prototype for the way your own design can start as an

adequate solution to a particular problem and evolve into a flexible approach to a class of

problems.

What is a pattern?

Initially, you can think of a pattern as an especially clever and insightful way of solving a

particular class of problems. That is, it looks like a lot of people have worked out all the angles

of a problem and have come up with the most general, flexible solution for it. The problem

could be one you have seen and solved before, but your solution probably didn’t have the kind

of completeness you’ll see embodied in a pattern.

Although they’re called “design patterns,” they really aren’t tied to the realm of design. A

pattern seems to stand apart from the traditional way of thinking about analysis, design, and

implementation. Instead, a pattern embodies a complete idea within a program, and thus it

can sometimes appear at the analysis phase or high-level design phase. This is interesting

because a pattern has a direct implementation in code and so you might not expect it to show

up before low-level design or implementation (and in fact you might not realize that you need

a particular pattern until you get to those phases).

The basic concept of a pattern can also be seen as the basic concept of program design: adding

a layer of abstraction. Whenever you abstract something you’re isolating particular details,

and one of the most compelling motivations behind this is to separate things that change

from things that stay the same. 





null







Another way to put this is that once you find some part of

your program that’s likely to change for one reason or another, you’ll want to keep those

changes from propagating other changes throughout your code. Not only does this make the

code much cheaper to maintain, but it also turns out that it is usually simpler to understand

(which results in lowered costs).

Often, the most difficult part of developing an elegant and cheap-to-maintain design is in

discovering what I call “the vector of change.” (Here, “vector” refers to the maximum gradient



and not a container class.)









 This means finding the most important thing that changes in your

system, or put another way, discovering where your greatest cost is. Once you discover the

vector of change, you have the focal point around which to structure your design.

So the goal of design patterns is to isolate changes in your code. If you look at it this way,

you’ve been seeing some design patterns already in this book. For example, inheritance can be

thought of as a design pattern (albeit one implemented by the compiler). It allows you to

express differences in behavior (that’s the thing that changes) in objects that all have the

same interface (that’s what stays the same). Composition can also be considered a pattern,

since it allows you to change—dynamically or statically—the objects that implement your

class, and thus the way that class works.

You’ve also already seen another pattern that appears in Design Patterns: the iterator (Java

1.0 and 1.1 capriciously calls it the Enumeration; Java 2 containers use “iterator”). This

hides the particular implementation of the container as you’re stepping through and selecting

the elements one by one. The iterator allows you to write generic code that performs an

operation on all of the elements in a sequence without regard to the way that sequence is

built. Thus your generic code can be used with any container that can produce an iterator.



Pattern taxonomy



One of the events that’s occurred with the rise of design patterns is what could be thought of

as the “pollution” of the term – people have begun to use the term to mean just about

anything synonymous with “good.” After some pondering, I’ve come up with a sort of

hierarchy describing a succession of different types of categories:

1. Idiom: how we write code in a particular language to do this particular type of thing.

This could be something as common as the way that you code the process of stepping

through an array in C (and not running off the end).

2. Specific Design: the solution that we came up with to solve this particular problem.

This might be a clever design, but it makes no attempt to be general.

3. Standard Design: a way to solve this kind of problem. A design that has become

more general, typically through reuse.

4. Design Pattern: how to solve an entire class of similar problem. This usually only

appears after applying a standard design a number of times, and then seeing a

common pattern throughout these applications.

I feel this helps put things in perspective, and to show where something might fit. However, it

doesn’t say that one is better than another. It doesn’t make sense to try to take every problem

solution and generalize it to a design pattern – it’s not a good use of your time, and you can’t

force the discovery of patterns that way; they tend to be subtle and appear over time.

One could also argue for the inclusion of Analysis Pattern and Architectural Pattern in this

taxonomy.

Design principles

(Update from slides to here)

When I put out a call for ideas in my newsletter[4], a number of suggestions came back which

turned out to be very useful, but different than the above classification, and I realized that a

list of design principles is at least as important as design structures, but for a different reason:

these allow you to ask questions about your proposed design, to apply tests for quality.

• Principle of least astonishment (don’t be astonishing).

• Make common things easy, and rare things possible

• Consistency. One thing has become very clear to me, especially because of Python:

the more random rules you pile onto the programmer, rules that have nothing to do

with solving the problem at hand, the slower the programmer can produce. And this

does not appear to be a linear factor, but an exponential one.

• Law of Demeter: a.k.a. “Don’t talk to strangers.” An object should only reference

itself, its attributes, and the arguments of its methods.

• Subtraction: a design is finished when you cannot take anything else away.

• Simplicity before generality[5]. (A variation of Occam’s Razor, which says “the

simplest solution is the best”). A common problem we find in frameworks is that they

are designed to be general purpose without reference to actual systems. This leads to a

dizzying array of options that are often unused, misused or just not useful. However,

most developers work on specific systems, and the quest for generality does not

always serve them well. The best route to generality is through understanding welldefined

specific examples. So, this principle acts as the tie breaker between otherwise

equally viable design alternatives. Of course, it is entirely possible that the simpler

solution is the more general one.

• Reflexivity (my suggested term). One abstraction per class, one class per

abstraction. Might also be called Isomorphism.

• Independence or Orthogonality. Express independent ideas independently. This

complements Separation, Encapsulation and Variation, and is part of the Low-

Coupling-High-Cohesion message.

• Once and once only: Avoid duplication of logic and structure where the duplication

is not accidental, ie where both pieces of code express the same intent for the same

reason.

In the process of brainstorming this idea, I hope to come up with a small handful of

fundamental ideas that can be held in your head while you analyze a problem. However, other

ideas that come from this list may end up being useful as a checklist while walking through

and analyzing your design.

Classifying patterns

The Design Patterns book discusses 23 different patterns, classified under three purposes (all

of which revolve around the particular aspect that can vary). The three purposes are:

1. Creational: how an object can be created. This often involves isolating the details of

object creation so your code isn’t dependent on what types of objects there are and thus

doesn’t have to be changed when you add a new type of object. The aforementioned

Singleton is classified as a creational pattern, and later in this book you’ll see examples

of Factory Method and Prototype.

2. Structural: designing objects to satisfy particular project constraints. These work

with the way objects are connected with other objects to ensure that changes in the

system don’t require changes to those connections.

3. Behavioral: objects that handle particular types of actions within a program. These

encapsulate processes that you want to perform, such as interpreting a language,

fulfilling a request, moving through a sequence (as in an iterator), or implementing an

algorithm. This book contains examples of the Observer and the Visitor patterns.

The Design Patterns book has a section on each of its 23 patterns along with one or more

examples for each, typically in C++ (rather restricted C++, at that) but sometimes in

Smalltalk. (You’ll find that this doesn’t matter too much since you can easily translate the

concepts from either language into Java.) This book will revisit many of the patterns shown in

Design Patterns but with a Java orientation, since the language changes the expression and

understanding of the patterns. However, the GoF examples will not be repeated here, since I

believe that it’s possible to produce more illuminating examples given some effort. The goal is

to provide you with a decent feel for what patterns are about and why they are so important.

After years of looking at these things, it began to occur to me that the patterns themselves use

basic principles of organization, other than (and more fundamental than) those described in

Design Patterns. These principles are based on the structure of the implementations, which is

where I have seen great similarities between patterns (more than those expressed in Design

Patterns). Although we generally try to avoid implementation in favor of interface, for awhile

I thought that it was easier to understand the patterns in terms of these structural principles,

and tried reorganizing the book around the patterns based on their structure instead of the

categories presented in Design Patterns.

However, a later insight made me realize that it’s more useful to organize the patterns in

terms of the problems they solve. I believe this is a subtle but important distinction from the

way Metsker organizes the patterns by intent in Design Patterns Java Workshop (Addison-

Wesley 2002), because I hope that you will then be able to recognize your problem and search

for a solution, if the patterns are organized this way.

In the process of doing all this “book refactoring” I realized that if I changed it once, I would

probably change it again (there’s definitely a design maxim in there), so I removed all

references to chapter numbers in order to facilitate this change (the little-known “numberless

chapter” pattern ☺).

The development challenge

Issues of development, the UML process, Extreme Programming.

Is evaluation valuable? The Capability Immaturity Model:

Wiki Page: http://c2.com/cgi-bin/wiki?CapabilityImMaturityModel

Article: http://www.embedded.com/98/9807br.htm

Pair programming research:

http://collaboration.csc.ncsu.edu/laurie/



Unit testing

In an earlier version of this book I decided that unit testing was essential (for all of my books)

and that JUnit was too verbose and clunky to consider. At that time I wrote my own unit

testing framework using Java reflection to simplify the syntax necessary to achieve unit

testing. For the third edition of Thinking in Java, we developed another unit testing

framework for that book which would test the output of examples.

In the meantime, JUnit has changed to add a syntax remarkably similar to the one that I used

in an earlier version of this book. I don’t know how much influence I may have had on that

change, but I’m simply happy that it has happened, because I no longer feel the need to

support my own system (which you can still find ) and can simply

recommend the defacto standard.

I have introduced and described the style of JUnit coding that I consider a “best

practice” (primarily because of simplicity), in Thinking in Java, 3rd edition, chapter 15. That

section provides an adequate introduction to any of the unit testing you will see associated

with this book (however, the unit testing code will not normally be included in the text of this

book). When you download the code for this book, you will find (4/9/2003: Eventually, not

yet) unit tests along with the code examples whenever possible



Location of test code



Public: in test subdirectory; different package (don’t include in jar).

Package access: same package, subdirectory path underneath library code (don’t include in

jar)

Private access: (white box testing). Nested class, strip out, or Junit addons.







null



Simplifying Idioms

Before getting into more complex techniques, it’s helpful to look at some basic ways to keep

code simple and straightforward.

Messenger

The most trivial of these is the messenger, which simply packages information into an object

to be passed around, instead of passing all the pieces around separately. Note that without the

messenger, the code for translate() would be much more confusing to read:

//: simplifying:MessengerDemo.java

package simplifying;

import junit.framework.*;

class Point { // A messenger

public int x, y, z; // Since it's just a carrier

public Point(int x, int y, int z) {

this.x = x;

this.y = y;

this.z = z;

}

public Point(Point p) { // Copy-constructor

this.x = p.x;

this.y = p.y;

this.z = p.z;

}

public String toString() {

return "x: " + x + " y: " + y + " z: " + z;

}

}

class Vector {

public int magnitude, direction;

public Vector(int magnitude, int direction) {

this.magnitude = magnitude;

this.direction = direction;

}

}

class Space {

public static Point translate(Point p, Vector v) {

p = new Point(p); // Don't modify the original

// Perform calculation using v. Dummy calculation:

p.x = p.x + 1;

p.y = p.y + 1;

p.z = p.z + 1;

return p;

}

}



public class MessengerDemo extends TestCase {

public void test() {

Point p1 = new Point(1, 2, 3);

Point p2 = Space.translate(p1, new Vector(11, 47));

String result = "p1: " + p1 + " p2: " + p2;

System.out.println(result);

assertEquals(result,

"p1: x: 1 y: 2 z: 3 p2: x: 2 y: 3 z: 4");

}

public static void main(String[] args) {

junit.textui.TestRunner.run(MessengerDemo.class);

}

} ///:~

Since the goal of a messenger is only to carry data, that data is made public for easy access.

However, you may also have reasons to make the fields private.



Collecting Parameter

Messenger’s big brother is the collecting parameter, whose job is to capture information from

the method to which it is passed. Generally, this is used when the collecting parameter is

passed to multiple methods, so it’s like a bee collecting pollen.

A container makes an especially useful collecting parameter, since it is already set up to

dynamically add objects:

//: simplifying:CollectingParameterDemo.java

package simplifying;

import java.util.*;

import junit.framework.*;

class CollectingParameter extends ArrayList {}

class Filler {

public void f(CollectingParameter cp) {

cp.add("accumulating");

}

public void g(CollectingParameter cp) {

cp.add("items");

}

public void h(CollectingParameter cp) {

cp.add("as we go");

}

}

public class CollectingParameterDemo extends TestCase {

public void test() {

Filler filler = new Filler();

CollectingParameter cp = new CollectingParameter();

filler.f(cp);

filler.g(cp);

filler.h(cp);

String result = "" + cp;

System.out.println(cp);

assertEquals(result,"[accumulating, items, as we go]");

}

public static void main(String[] args) {

junit.textui.TestRunner.run(

CollectingParameterDemo.class);

}

} ///:~



The collecting parameter must have some way to set or insert values. Note that by this

definition, a messenger could be used as a collecting parameter. The key is that a collecting

parameter is passed about and modified by the methods it is passed to.



Object quantity



The two patterns described here are solely used to control the quantity of

objects.

Singleton could actually be thought of as a special case of Object Pool, but the applications of

the Object Pool tend to be uniqe enough from Singleton that it’s worth treating the two

separately.


Dell PowerEdge M910 Blade-Server
2010-04-29T07:15:00.000-07:00
null



PowerEdge M910



Der PowerEdge M910, ein Blade-Server in voller Höhe mit vier Sockeln, ist ideal für Virtualisierungs-Workloads oder Kernanwendungen. Er steht für hervorragende Leistung, Zuverlässigkeit und Skalierbarkeit bei einem Formfaktor mit extrem hoher Dichte.



Leistungsfähig: bis zu vier Intel Xeon Prozessoren der 7500 Serie

Skalierbar: bis zu 512 GB DDR3-RAM

Kompakt: Blade-Formfaktor in voller Höhe ermöglicht bis zu acht Blades je Gehäuse mit 10 HE 



Leistungsfähig, skalierbar und kompakt



Der PowerEdgeTM  M910 wurde für die Anforderungen nahezu aller IT-Umgebungen entwickelt. Mit den leistungsstarken Intel Xeon Prozessoren der 7500 Serie und erweiterten Funktionen zur Systemverwaltung ist der M910 ideal für die anspruchsvollen Anwendungen vieler Rechenzentren.

Dank der Dell FlexMem Bridge Technologie kann der M910 bei Konfigurationen mit zwei oder vier Sockeln nahtlos von 4 GB auf 512 GB DDR3-RAM skaliert werden. Mit dieser zum Patent angemeldeten Technologie kann Dell eine einzigartige Plattform bereitstellen, die mit Ihren Anforderungen wächst.

Durch die Bereitstellung dieser Funktionen in einem Blade-Server ermöglicht es Dell Ihrem Unternehmen, die Leistungsfähigkeit bei einem außergewöhnlich energieeffizienten und leicht zu verwaltenden Formfaktor erheblich zu steigern. Mit acht 4-Sockel-Servern bei 10 Höheneinheiten (HE) im Rack stellt der M910 mehr als die dreifache Dichte zur Verfügung, die traditionelle Rack-Server mit vier Höheneinheiten und vier Sockeln bieten können.





Der PowerEdge M910 nutzt die redundante Stromversorgungs-, Kühlungs- und Netzwerkinfrastruktur des Dell M1000e Blade-Gehäuses. Der PowerEdge M910 verfügt über zusätzliche Funktionen, die höchsten Schutz gegen potenzielle Ausfallzeiten bieten: er unterstützt z. B. drei vollständig redundante Architekturen pro Blade und bietet einen für zwei Datenträger geeigneten, redundanten Hypervisor.



Der PowerEdge M910 verfügt auch über Intel Xeon Prozessoren der 7500 Serie, die Hardwarefehler automatisch überwachen, melden und beheben, um die Datenintegrität und geschäftskritische Services aufrechtzuerhalten.



Wie alle Dell PowerEdge Server wird der M910 im Werk mit unserem "One-Touch"-Verfahren hergestellt. Durch dieses Verfahren wird sichergestellt, dass nur eine Person für alle Fertigungsschritte eines Servers verantwortlich ist. Dies führt zu einer noch besseren Qualitätskontrolle. Außerdem wird jeder vollständig konfigurierte Dell Server (mehrfach) auf ein Höchstmaß an Zuverlässigkeit getestet, bevor er das Werk verlässt.



Vereinfachte Systemverwaltung



Die nächste Generation des Dell OpenManageTM  Softwarepakets bietet erweiterte Funktionen und standardbasierte Befehle, die in die bestehenden Systeme zur effektiven Steuerung integriert werden können.



null



Die Dell Management Console auf Basis von Altiris von Symantec bietet eine zentrale Ansicht und eine gemeinsame Datenquelle für die gesamte Infrastruktur. Die Dell Management Console basiert auf der SymantecTM  Management Plattform (vormals Altiris®  Notification Server), einer problemlos erweiterbaren, modularen Basis, die eine grundlegende Hardwareverwaltung oder erweiterte Funktionen wie Bestands- und Sicherheitsmanagement zur Verfügung stellt. Die Dell Management Console reduziert manuelle Arbeitsschritte, sodass Zeit und Geld gespart werden und stattdessen in strategische Funktionen der Technologie investiert werden kann.



Der Lebenszyklus-Controller ist der "Motor" der im Server integrierten erweiterten Systemverwaltungsfunktionen. Der Lebenszyklus-Controller vereinfacht typische Administratortätigkeiten, indem er umfassende Verwaltungsfunktionen, wie Systemimplementierung, System-Updates, Hardwarekonfiguration und -diagnose, über die intuitive Benutzeroberfläche Unified Server Configurator (USC) in einer Pre-OS-Umgebung bereitstellt. Es ist daher nicht mehr notwendig, eine Vielzahl unterschiedlicher CD-/DVD-Medien zu verwenden und diese zu verwalten.



Der Dell Unified Server Configurator (USC) bietet einen einzigen Zugriffspunkt für eine sichere, effiziente und benutzerfreundliche Infrastrukturverwaltung. Aufgrund der Einbettung und Integration in das System können ein schneller, konsistenter Zugriff, eine großartige Flexibilität und erweiterte Funktionen geboten werden. Mit der integrierten Treiber-Installation, den Firmware-Updates, der Hardware-Konfiguration und den Diagnosen bietet das USC-Tool die Bereitstellung eines Betriebssystems aus einer Hand.


The old mainframe
2010-04-29T06:44:00.000-07:00
The mainframe was born some 50 plus years ago when the government needed a machine to support advanced research. Since that time it has taken its rightful place in the world’s financial transactions, transportation management, health care and industry management. Most of that code was written in COBOL and VSAM and ran on systems from CICS and IMS to DB2. Today it still fulfills those venerated roles but it has evolved into the most powerful, flexible, reliable server in the industry, running new workloads from Java to Linux. This is the machine that supports tens of thousands of users working with hundreds of terabytes of data, with response times still in sub-seconds. This is not your father’s mainframe.
Why then do many IT professionals, and as a result industry leaders, believe that migrating these trusted applications and data from a mainframe to rooms of distributed commodity servers can provide the same levels of service, security and reliability that the mainframe still excels at today? The truth is these folks don’t really know what a mainframe is, much less what makes it so powerful. Let’s take a short tour through this new mainframe, the System z10, and see what separates it from the rest. And the best way to review these differences is to look at one of those “mainframe is dead” white papers, in the form of “The Story about the IBM Mainframe Makeover” that HP has posted on their web site2.


Modern Mainframe, z/OS 10.
2010-04-29T06:32:00.000-07:00
IBM has been building and shipping mainframe computers for over 40 years. Every generation of the mainframe gets better, faster, more efficient, and carries more and more of the data load for business and industry all over the world. In the early 90’s there were no mainframes in India or China either for that matter. Now there are a growing number of mainframes in China running the major banks and financial institutions in that emerging country.
Mainframe installations and skills are growing in India, not only running financial markets but also in place to support millions of lines of programming code that are being developed for the rest of the mainframes circling the globe.1 And yet, year after year since the first “minicomputers” were developed and shipped by Digital Equipment, Data General, and others, we have continuously heard about the mainframe being replaced by smaller, cheaper, easier to deploy technology of every kind.
Admittedly the mainframe has not assumed the role of personal computer, mobile appliance, small departmental server, nor supercomputing grid, but in fact most of the world funds clearing and transfers are still routed through mainframe connections. It has been estimated that the mainframe manages some 70% of the world’s critical data. And today, with new departmental workloads in Java, C and C++, the mainframe is assuming many of these roles with Linux on System z.
So why is it then that year after year, someone writes a paper, article or book about the demise of this most capable machine? How can rational technologists believe that there is any technology in the market today that can do what the mainframe has done, and continues to do? What would make someone believe that a hundred Intel processors, ganged together in a loosely connected environment, could replace the capabilities that the mainframe has provided all these decades? The only answer that comes to mind is that those who espouse the demise of the mainframe don’t understand either the problem, or the solution.


JBoss Enterprise Application Platform ( FAQ's )
2010-04-19T06:44:00.000-07:00
What is JBoss Enterprise Application Platform ?

JBoss Enterprise Application Platform is the industryleading
platform for next-generation enterprise Java
applications. It provides a stable, open source foundation
for highly transactional Java applications and services.
And it's integrated, simplified, and delivered by Red Hat,
the leader in enterprise open source software.

What does it do?

By combining market-leading technologies into a single,
simple, and flexible solution, JBoss Enterprise Application
Platform makes it easy to develop, deploy, and manage
Java Enterprise Edition (EE) applications. It includes leading
open source technologies for building, deploying, and
hosting enterprise Java applications in dynamic environments.
JBoss Enterprise Application Platform provides
a stable and consistent enterprise Java foundation that
supports a variety of popular programming models and
deployment options, spanning traditional application
deployments to on- and off-premise cloud deployments.

Why should I care?

JBoss Enterprise Application Platform balances innovation
with enterprise-class stability. By integrating and certifying
the most popular Java application server on the
market with next-generation application frameworks, it
removes complexities from enterprise Java development
and deployment. JBoss Enterprise Application platform
includes high-availability features and comprehensive
administrative tooling to support, manage, and scale out
mission-critical enterprise Java applications. By including
all of the technologies needed for enterprise Java deployments
in a single subscription, JBoss Enterprise Application
Platform provides a stable platform that simplifies the
development and management of next-generation Java
applications and services. Red Hat customers take advantage
of affordable JBoss Enterprise Application Platform
subscriptions to help extend their companies' middleware
budgets and improve their total costs of ownership.
and available through flexible and affordable subscriptions,
JBoss Enterprise Application Platform includes everything
you need to build and manage rich and highly transactional
enterprise Java applications.

Benefits ?

Choice without compromise. Support the variety of popular
programming choices and deployment styles on a single,
flexible Java application platform—without compromising
on operational stability. Enterprise services for clustering,
caching, web services, security, messaging, and transactions
can be easily configured and customized across a
selection of supported programming styles (POJOs, Java
EE, Spring) and frameworks to support all of the common
types of enterprise Java applications from a single runtime
platform.

Innovation with stability. Benefit from the latest open
source innovations that have been tested and certified
for enterprise-class stability on a combination of leading
operating systems, chip architectures, and databases.
With a long-term product support lifecycle and backed
with an extensive partner ecosystem of certified independent
software vendors (ISVs), JBoss Enterprise Application
Platform provides a stable and supportable platform for
any mission-critical Java application.

Build applications faster. Take advantage of rich web
technologies and popular developer productivity frameworks
that work together from the start. Remove library
configuration complexities and conflicts. Simplify enterprise
Java development with a flexible and easy-touse
application platform. JBoss Enterprise Application
Platform, combined with JBoss Developer Studio, provides
a fully integrated development environment that helps
improve developer productivity throughout the entire
application development lifecycle.

Standard and flexible. Develop and deploy on an enterprise
Java platform that implements industry standards
in a flexible and open way. Delivered as a 100% pure
Java open source solution, JBoss Enterprise Application
Platform provides you with absolute transparency to see
exactly what's happening in your enterprise application
server. Customize configurations, tune applications, and opment and deployment platforms are in operationally in sync.

Enhanced application security. Targeted at meeting rigorous
industry security requirements, such as Common
Criteria, JBoss Enterprise Application Platform implements
all of the required Java security standards and more. In
addition to being backed by Red Hat's security response
process, JBoss Enterprise Application Platform includes
features for password masking, instance-based access control,
security negotiation, audit, and integration support
with common single sign-on solutions to help IT organizations
maintain a safe and secure middleware environment.

Simplify application management and configuration. With
JBoss Enterprise Application Platform's administration console,
spend less time configuring and managing application
and application server settings. Through its rich embedded
user interface, developers and administrators can easily
adjust configuration settings, execute controls, and drill
into application performance metrics. For enterprise-wide
management, leverage JBoss Operations Network to control,
administer, and proactively manage all of your development,
testing, and deployment environments.


What are the JBoss Enterprise Application Platform 5 Components ?

JBoss Enterprise Application Platform is a Java Enterprise
Edition (EE) application server platform. It includes default
configurations for both development and production
use and is performance-tuned from the start for highly
transactional applications in mission-critical environments.
Delivered as a single integrated distribution, JBoss
Enterprise Application Platform includes enterprise versions
of:
JBoss Application Server, the most • widely used Java
application server on the market. In addition to being
a certified Java EE 5 platform, it also provides support
for a variety of popular programming and component
models, like POJOs and Spring. Featuring a set of highly
flexible and configurable enterprise services for caching,
clustering, messaging, transactions, and security,
as well as support for a comprehensive web services

development environment for all JBoss platforms,
JBoss Developer Studio includes both tooling and an
integrated version of the certified application platform
runtime.
• JBoss Operations Network. Red Hat's comprehensive
middleware management solution gives IT operations
a single, centralized easy to use graphical management
and administration tool for all types of Java application
workloads. With JBoss Operations Network, companies
can inventory resources from operating systems
to applications; control and audit application configurations;
standardize deployments; and manage, monitor,
and tune applications for improved visibility, performance,
and availability.

What are the Platform's and Standards Support ?

JBoss Enterprise Application Platform 5
Minimum system requirements
• JDK 1.6
• 512 MB RAM
• 100 MB hard disk space
• 400 MHz CPU
Supported JDKs
• Sun JDK 1.6
• OpenJDK 1.6
• IBM JDK 1.6
Supported operating systems
JBoss Enterprise Application Platform is 100% pure Java.
It is supported on any operating system, including Red Hat
Enterprise Linux, Windows, and UNIX, as long as a supported
JDK is used.
Supported databases
JBoss Enterprise Application Platform is supported with
any JDBC compliant database. Each release is certified
with IBM DB2, Oracle, Microsoft, MySQL, PostgreSQL,
and Sybase databases.
Additional standards
• Java Transaction Service (JTS) 1.0
• CORBA 2.3.1
• JDBC 3.0
• SPNEGO / Kerberos

Supported standards

JBoss Enterprise Application Platform supports the following
standards:
Java Enterprise E • dition 5, including:
• Java Servlet 2.5, JavaServer Faces (JSF) 1.2
• JavaServer Pages (JSP) 2.1
• Java Transaction API (JTA) 1.1
• Enterprise Java Beans (EJB) 2.1, 3.0
• Java Messaging Service (JMS) 1.1
• Java Persistence API (JPA) 1.0
• Web Services Metadata for the Java Platform 2.0
(JSR 181)
• Java API for XML Web Services (JAX-WS) 2.1
• Java Architecture for XML Binding (JAXB) 2.0
• Java API for RESTful Web Services (JAX-RS) 1.0
• Web services standards
• Simple Object Access Protocol (SOAP) 1.2
• SOAP Message Transmission Optimization
Mechanism (MTOM)
• XML-Binary Optimized Packaging (XOP)
• Web Services Description Language (WSDL) 1.1, 2.0
• WS-I Basic Profile 1.1
• WS-Addressing 1.0
• WS-Security 1.1
• UDDI 2.0
• Java API for XML Web Services Addressing (JAXWSA)
1.0
• WS-Atomic Transactions 1.1
• Fast Infoset
• WS-Business Activity 1.1
• WS-Coordination 1.1
• WS-Security Policy 1.3
• WS-I Attachments Profile 1.0

Subscriptions of 32 CPUs or greater include additional
value-added features, including JBoss Operations Network
and Developer support. For subscriptions totaling fewer
than 32 CPUs, JBoss Operations Network and Developer
support subscriptions may be purchased separately.

What are the additional solutions for Java applications

Round out your JBoss Enterprise Application Platform subscription
with solutions for lighter enterprise Java applications
and productivity tools targeted at both developers
and middleware administrators:
• JBoss Enterprise Web Server. For simple web applications
and the lightest Java workloads, JBoss Enterprise
Web Server provides a stable, long-term, enterprise
product support lifecycle for Apache Web Server,
Apache Tomcat, and all of the common connectors
used in between.
• JBoss Developer Studio. Red Hat's innovative Eclipsebased
developer tool that provides a single integrated

What are the JBoss Enterprise Application Platform 5
Features

Enterprise-class performance & scalability. Take advantage
of integrated clustering and high-availability features
for superior application performance. With built-in features
for failover, caching, intelligent load balancing, and distributed
deployment, JBoss Enterprise Application Platform
is a proven foundation for highly scalable Java applications
in mission-critical environments.

Second-generation, service-based architecture.
JBoss Enterprise Application Platform is built on top
of the innovative JBoss Microcontainer architecture to
provide improved class-loading, performance, lifecycle
management, and flexibility across a wide variety of programming
and component models including Java EE,
POJOs, OSGi, and Spring. The Microcontainer lets you
separate enterprise services from the core application
server runtime engine to deliver a highly configurable
and flexible Java application platform without compromising
operational stability.

Integrated frameworks. JBoss Enterprise Application
Platform features industry-leading frameworks for building
rich Internet applications and integrating all of the technologies
required to build common types of Java applications,
from simple web apps to highly transactional Java
EE applications and everything in between. Stable, enterprise-
grade versions of each framework are integrated,
certified, and kept up to date as part the JBoss Enterprise
Application Platform product lifecycle, ensuring both develstack, JBoss Application Server supports all types
of enterprise Java applications.
Hibernate, the leading object/relational mapping and
persistence (ORM) framework. 

Hibernate directly addresses enterprise Java complexities by providing
the ability to easily map an object model’s data representation
to a relational data model and corresponding
database schema. Hibernate also provides data query
and retrieval facilities that significantly reduce development
time and help eliminate the need for manual,
hand-crafted data processing using SQL and JDBC.

• Seam, a powerful application framework that simplifies
building next-generation web applications. Seam
supports a streamlined programming model and helps
overcome common framework integration issues.
Seam helps unify technologies such as Asynchronous
JavaScript and XML (AJAX), Java Server Faces (JSF),
Enterprise Java Beans (EJB 3), Java Portlets and business
process management (BPM) through a standardized
approach.

• JBoss Web Framework Kit includes popular web frameworks
for quickly and easily building light and rich Java
applications. By combining leading rich application
frameworks—Google Web Toolkit and RichFaces—with
popular Java frameworks—Spring and Apache Struts—
JBoss Web Framework Kit provides an enterprise with
a certified way to adopt popular open source frameworks
on JBoss Enterprise Middleware.


AIX 6.1 - Workload Partitions (WPARs)
2009-10-12T03:11:00.000-07:00
AIX 6.1 - Workload Partitions (WPARs)

Virtualization unquestionably saves a lot of money on power and cooling. The more partitions you can carve on your existing systems, the better utilization you will have. WPAR, a new innovation of AIX 6.1, allow for operating systems virtualization, outside of traditional hypervisor-based logical partitioning. In essence, it allows you to carve up multiple workload environments inside of one host and OS kernel. So you can now have one single instance of AIX 6.1 and using WPARs you can have four different test environments working within that instance, appearing like separate operating system instances. Prior to WPARs, you would need to carve out separate logical partitions (LPARs) within the physical server.

This new feature of AIX 6.1 has the effect of reducing the amount of physical devices necessary to support your logical environments. Though one can conceivably get by with the bare minimum of physical devices for a logical partition, the WPAR is clearly the most efficient means that you can use when creating a new environment. This is purely an AIX innovation, unrelated to the POWER6. Furthermore, Live Application Mobility, another AIX 6.1 innovation, allows you to relocate running WPARs from one LPAR to another. IBM is the first vendor that allows for this feature without having to shut down the application or partition. This helps promote energy savings by allowing datacenter operators to move around workloads in such a way as to allow physical servers to sleep during non-peak periods. This feature is available on Power5™ servers and even Power4™ as well!


Human Resources organization is optimized
2009-10-08T02:32:00.000-07:00
How do you make sure your Human Resources organization is optimized for effectiveness, efficiency, and business alignment? How do you best organize, manage, staff, and invest in HR to drive the greatest business impact? 

You are invited to participate in Bersin & Associates' major research study to help you answer these questions in detail: The High-Impact HR Organization. This research study is a comprehensive look at trends and best-practices in the organization, management, and operations of Human Resources. 

Goals of this study: 

HR executives and professionals need ways to deliver ever-greater levels of service, support, and talent management solutions to their organizations. Today's business climate - with its rapidly changing workforce, economic challenges, regulatory requirements, and evolving technologies – demands that HR re-evaluate its role, structure, and delivery strategy to drive employee and business value. 

This in-depth research will look at best-practices in HR organization, structure, roles, technology, service-delivery, program strategy, and resource allocation. The goal is to provide you a proven set of modern solutions you can use to improve the impact of HR. 
As a participant in this research, you will be able to contribute, learn, and benchmark your organization against these best practices. All research participants will receive a detailed overview of study findings and will be invited to a special webinar presenting the results 
In appreciation for your time, you will also receive a copy of our recently published 2009 Career Factbook for HR and Learning Professionals. This 130 page report provides a comprehensive view of career paths, competencies, compensation, education, motivation, and the challenges of HR and L&D professionals.

Please click here to participate. This survey will take you approximately 20 minutes to complete. If you have any questions about this research, please contact Bersin & Associates at info@bersin.com.  For more background on this research, please visit http://www.bersin.com/hihr. 

Thank you for your participation.


Preparing to host applications.
2009-07-13T01:48:00.000-07:00
Websphere Application Server Network Deployment, Version 6.1
Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

Preparing to host applications
Rather than use the default application server provided with the product, you can configure a new server and set of resources.
About this task 
The default application server and a set of default resources are available to help you begin quickly. You can choose instead to configure a new server and set of resources. Here is what you need to do in order to set up a runtime environment to support applications.
Procedure 
1. Configure an application server.
2. Create a virtual host.
3. Configure a Web container.
4. Configure an EJB container.
5. Create resources for data access.
6. Create a JDBC provider and data source.
7. Create a URL and URL provider.
8. Create a JavaMail session.
9. Create resources for session support.
10. Configure a Session Manager.


WebSphere Message Broker V6.1 - Fix Pack 6.1.0.4
2009-06-13T17:21:00.000-07:00
Downloadable files

Abstract
This is Fix Pack 6.1.0.4 for WebSphere Message Broker Version 6.1

Download Description
Fix Pack 6.1.0.4 is the fourth maintenance for WebSphere Message Broker Version 6.1. It is available for the following platforms:

AIX 
HP-UX
HP-UX Itanium
Linux
Linux on zSeries
Linux (Power)
Linux on Intel x86
Sun Solaris
Solaris x86-64
Windows 2003 and Windows XP
z/OS

Note that this Fix Pack is for the broker product only. Updates for the toolkit are available from the product Toolkit links on the following 
URL : http://www-1.ibm.com/support/docview.wss?uid=swg27006041
 
 
Prerequisites
Install the Fix Pack on top of IBM WebSphere Message Broker Version 6.1.

The link below gives the supported environments for IBM WebSphere Message Broker V6.1 and it's components.
 
URL                  LANGUAGE          SIZE(Bytes)
System Requirements  English           9999
 
 
 
Installation Instructions
Instructions for applying maintenance are given in the product Infocenter, under the heading "Installing". You can view the Infocenter Online or via your Message Brokers Toolkit, or download the PDF file "Managing your Installation" from the Library link below.
These instructions must be amended by any changes documented in the latest product readme file and any changes documented in the Release Notes, below.
 
URL                                 LANGUAGE SIZE(Bytes)
Problems Fixed                           English 9999
WebSphere Message Broker Library         English 9999
Readme                                   English 9999
Release Notes                            English 9999

 
Download package

 
What is Fix Central (FC)?

Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
AIX 11/06/2009 Language Independent 471955609 FC

HP-UX 11/06/2009 Language Independent 502067148 FC

HP Itanium 11/06/2009 Language Independent 412594521 FC

Solaris SPARC 11/06/2009 Language Independent 377896150 FC

Solaris X86-64 11/06/2009 Language Independent 313041059 FC

Linux x86 11/06/2009 Language Independent 291632615     FC

Linux s390x (zSeries) 11/06/2009 Language Independent 286513941 FC

Linux PPC 11/06/2009 Language Independent 295896193 FC

Linux x86-64 11/06/2009 Language Independent 394557011 FC

Windows 11/06/2009 Language Independent 251496632 FC

z/OS 11/06/2009 Language Independent 203107328 FC


 
 Problems (APARS) fixed    
 
IC54662, IC54505, IC54555, PK57973, PK57974, PK57975, PK57976, PK54892, PK59269, IC56211, PK64389, PK64390, PK64391, PK64397, PK65847, IC53957, IC53997, IC54097, IC54202, IC54484, IC54524, IC54633, IC54698, IC54737, IC54749, IC54755, IC54784, IC54958, IC54963, IC54985, IC55034, IC55146, IC55254, IC55257, IC55271, IC55298, IC55311, IC55424, IC55507, IC55521, IC55578, IC55608, IC55613, IC55689, IC55997, IC56013, IC56113, IC56190, IC56236, IY89266, IY94881, IY97796, IZ02427, IZ02657, IZ04441, IZ05008, IZ06546, IZ06738, IZ06984, IZ07456, IZ08644, IZ08787, IZ09066, IZ10043, IZ12481, IZ13223, IZ13831, IZ13992, IZ14327, IZ14470, IZ15182, IZ15371, IZ15987, IZ16570, IZ17454, IZ17623, IZ19550, PK53829, PK55676, PK59124, PK59650, PK61664, PK63922, IC57836, PK71665, PK71666, PK71669, PK71705, IC54769, IC55028, IC55033, IC55502, IC55513, IC55514, IC55871, IC55987, IC56239, IC56296, IC56349, IC56457, IC56497, IC56525, IC56531, IC56566, IC56710, IC56790, IC56793, IC56802, IC56847, IC56853, IC56898, IC56912, IC56916, IC56918, IC57012, IC57021, IC57022, IC57057, IC57105, IC57159, IC57319, IC57327, IC57335, IC57375, IC57451, IC57469, IC57476, IC57534, IC57572, IC57573, IC57587, IC57599, IC57602, IC57689, IC57705, IC57834, IC57886, IC57946, IC58134, IC58202, IC58205, IC58260, IC58261, IC58286, IC58542, IC58785, IC59016, IZ15874, IZ18000, IZ18492, IZ18912, IZ20361, IZ20680, IZ20708, IZ21068, IZ22174, IZ22782, IZ22999, IZ23135, IZ23315, IZ25616, IZ26492, IZ27860, IZ27873, IZ33255, PK63949, PK67146, PK69088, PK70138, PK70374, PK72103, PK73298, IC54781, IC55513, IC57088, IC57219, IC57560, IC57650, IC58217, IC58247, IC58363, IC58455, IC58467, IC58607, IC58621, IC58716, IC58786, IC58866, IC58890, IC58935, IC58943, IC58946, IC58951, IC58961, IC59034, IC59051, IC59058, IC59090, IC59107, IC59116, IC59128, IC59142, IC59164, IC59190, IC59197, IC59201, IC59217, IC59229, IC59250, IC59260, IC59303, IC59320, IC59398, IC59402, IC59417, IC59467, IC59618, IC59641, IC59642, IC59644, IC59672, IC59673, IC59717, IC59818, IC59851, IC59897, IC59899, IC59900, IC59901, IC59933, IC60078, IC60103, IC60118, IC60152, IC60154, IC60237, IC60238, IC60247, IC60311, IC60316, IC60332, IC60333, IC60394, IC60397, IC60401, IC60428, IC60449, IC60454, IC60916, IZ22756, IZ28848, IZ30043, IZ31895, IZ32333, IZ33918, IZ34287, IZ35449, IZ35623, IZ35853, IZ36932, IZ37666, IZ38636, IZ38978, IZ39246, IZ39312, IZ39419, IZ40853, IZ40999, IZ41957, IZ42616, IZ42696, IZ43211, IZ43892, IZ44450, IZ44920, IZ46862, PK72883, PK73212, PK74382, PK74968, PK76235, PK77862, PK81096, PK81355, PK81837, PK81907, PK81924, PK82423, PK82443, PK82545, PK83041, PK83232, PK84635, PK85152  
  


Copyright and trademark information
 
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.


Get group discounts at IBM's Rational Software Conference 2009
2009-06-13T04:01:00.001-07:00

                                            
                                                                                       Sign  up as a group and get real discounts.                
                                               
                                The IBM Rational Software Conference 2009, is  all about real results in times of real challenges. So it doesn't come as a  surprise that we're offering you real discounts to this event. Group discounts  are                    just one of them.                
                                               
                                You could refer a friend  and get them                    Rs. 200 off on  their registration fee. What's in it  for you? If they enter your 
 name as the  referring friend, then you get Rs. 500 off                    at 
                   next year's conference.*                
                                               
                                So go ahead, get real and sign up.                
                                               
                                To register for the conference, call 
                   Navin: +91 97310 88442   or   Lubna: +91 97413 00554                
                                                     
         
               
                         
                        
                IBM, the IBM logo, ibm.com, Rational and its products are trademarks of International Business Machines, registered in many jurisdictions worldwide. © Copyright IBM Corporation 2009. All Rights Reserved. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at ibm.com/legal/copytrade.shtml         
     
        
 
 
 


Writitng Verbose GC to a Specified Log –Xverbosegclog, How do you get verbose GC output to another log besides native_stderr?
2009-05-26T05:50:00.000-07:00
Verbose GC data is captured by default in the native_stderr.log for IBM AIX®, Microsoft Windows® and Linux® and native_stdout.log for SUN Solaris and HP -UX.

WebSphere Application Server 7.0
-Xverbosegclog[:[,,]]
Causes -verbose:gc output to be written to the specified file. If the file cannot be found, -verbose:gc tries to create the file, and then continues as normal if it is successful. If it cannot create the file (for example, if an invalid filename is passed into the command), it will redirect the output to stderr. 
If you specify  and  the -verbose:gc output is redirected to  files, each containing  GC cycles. 
The dump agent tokens can be used in the filename. See Dump agent tokens for more information. If you do not specify , verbosegc.%Y%m%d.%H%M%S.%pid.txt is used. 

Dump agent tokens
Use tokens to add context to dump file names and to pass command-line arguments to the tool agent.
The tokens available are listed in the table below:
Token Description
%Y Year (4 digits)
%y Year (2 digits)
%m Month (2 digits)
%d Day of the month (2 digits)
%H Hour (2 digits)
%M Minute (2 digits)
%S Second (2 digits)
%pid Process id
%uid User name
%seq Dump counter
%tick msec counter
%home Java™ home directory
%last Last dump
%job Job name (z/OS® only)
&DS Dump Section. 

An incrementing sequence number used for splitting TDUMP files to be less than 2 GB in size. (z/OS 64-bit version 1.10 or newer only)

1. In the administrative console, click Servers > Server Types > WebSphere application servers > server_name. Then, under Server Infrastructure, click Java™ and process management > Process definition. 
2. Select Java Virtual Machine . 
3. Specify values for the JVM settings as needed and click OK. 
4. Click Save on the console task bar. 
5. Restart the application server.

WebSphere Application Server 6.1

-Xverbosegclog:[,,]
Causes -verbose:gc output to be written to the specified file. If the file cannot be found, -verbose:gc tries to create the file, and then continues as normal if it is successful. If it cannot create the file (for example, if an invalid filename is passed into the command), it will redirect the output to stderr. 
If you specify  and  the -verbose:gc output is redirected to  files, each containing  GC cycles. 
1. In the administrative console, click Servers > Application Servers >server. Then, under Server Infrastructure, click > Java and Process Management > Process Definition . 
2. Select Java Virtual Machine. 
3. Specify values for the JVM settings as needed and click OK. 
4. Click Save on the console task bar. 
5. Restart the application server.

WebSphere Application Server 6.0 and 5.1

-Xverbosegclog:
Causes verboseGC output to be written to the specified file. If the file cannot be found, verboseGC tries to create the file, and then continues as normal if it is successful. If it cannot create the file (for example, if an invalid filename is passed into the command), it will redirect the output to stderr. Use .%p to append the process id to the file name. 

-Xverbosegclog: 
1. Filename must contain a "#" (hash symbol), which is substituted with a generation identifier, starting at X and Y are integers. This option works similarly to -Xverbosegclog:, but, in addition, the verboseGC output is redirected to X files, each containing verboseGC output from Y GC cycles. 

**Example: -Xverbosegclog:/opt/WebSphere/logs/gc#.log,50,100
The above setting would create 50 log files named gc.log with 100 GC cycles each.
2. In the administrative console, click Servers > Application Servers >server. Then, under Server Infrastructure, click > Java and Process Management > Process Definition . 
3. Select Java Virtual Machine. 
4. Specify values for the JVM settings as needed and click OK. 
5. Click Save on the console task bar. 
6. Restart the application server.


What is Secure Sockets Layer (SSL) Overview
2009-04-06T03:11:00.000-07:00
Secure Sockets Layer (SSL) Overview 
Privacy and security are concepts that are more critical than ever in today’s electronic business
environment.
Every business professional needs to be concerned about security over open communication
networks, such as the Internet. It is not enough to have a secure Web site; you also need to have
secure communication between Web sites, communication that cannot be monitored by outside
parties. Both you and your users need to be confident that you have a secure environment in
which to conduct your business.
That kind of secure communication requires encryption, and encryption is what the Secure
Sockets Layer (SSL) provides: security for the connection over which you can communicate.
SSL was developed jointly by Netscape Communications and RSA Data Security. Many
companies worldwide have adopted SSL as their communication protocol of choice. In fact,
many financial transactions on the Internet, including online banking, are now conducted using
SSL.
Because digital certificates are an important component of SSL.

What is Digital certificate
Digital certificates allow unique identification of an entity; they are, in essence, electronic ID
cards issued by trusted parties. Digital certificates allow a user to verify to whom a certificate is
issued as well as the issuer of the certificate.
Digital certificates are the vehicle that SSL uses for public-key cryptography. Public-key
cryptography uses two different cryptographic keys: a private key and a public key. Public-key
cryptography is also known as asymmetric cryptography, because you can encrypt information
with one key and decrypt it with the complement key from a given public-private key pair.
Public-private key pairs are simply long strings of data that act as keys to a user's encryption
scheme. The user keeps the private key in a secure place (for example, encrypted on a computer's
hard drive) and provides the public key to anyone with whom the user wants to communicate.
The private key is used to digitally sign all secure communications sent from the user; the public
key is used by the recipient to verify the sender's signature.
Public-key cryptography is built on trust; the recipient of a public key needs to have confidence
that the key really belongs to the sender and not to an impostor. Digital certificates provide that
confidence.
A digital certificate serves two purposes: it establishes the owner’s identity, and it makes the
owner's public key available. A digital certificate is issued by a trusted authority—a certificate
authority (CA)—and it is issued only for a limited time. When its expiration date passes, the
digital certificate must be replaced.
Format of digital certificates
The digital certificate contains specific pieces of information about the identity of the certificate
owner and about the certificate authority:
_ Owner's distinguished name. A distinguished name is the combination of the owner's
common name and its context (position) in the directory tree. In the simple directory tree
shown in Figure 1, for example, LaurenA is the owner's common name, and the context
is OU=Engnring.O=XYZCorp; therefore, the distinguished name is:
.CN=LaurenA.OU=Engnring.O=XYZCorp


_ Owner's public key.
_ Date the digital certificate was issued.
_ Date the digital certificate expires.
_ Issuer's distinguished name. This is the distinguished name of the CA.
_ Issuer's digital signature.


What is CA SiteMinder®Web Access Manager
2009-04-05T20:07:00.000-07:00
CA SITEMINDER® WEB ACCESS MANAGER (CA SITEMINDER WAM) PROVIDES A CENTRALIZED
SECURITY MANAGEMENT FOUNDATION THAT ENABLES THE SECURE USE OF THE WEB TO DELIVER
APPLICATIONS AND DATA TO CUSTOMERS, PARTNERS AND EMPLOYEES.
Overview

Your customers, partners and employees fully expect anytime, anywhere access to your critical applications, information and services. The proliferation of intranets, B2B extranets and e-commerce
Websites presents opportunities to increase revenues, manage costs and deepen relationships with users. But opening your organization via the Web also presents significant security, management and compliance challenges.

Benefits

CA SiteMinder WAM lets you manage and deploy secure web applications to:
• Increase new business opportunities
• Manage costs
• Improve security to mitigate risk
• Ease compliance

The CA Advantage

CA SiteMinder WAM delivers unparalleled reliability, availability, scalability and manageability.
The de facto gold standard for enterprise-class web access management, CA SiteMinder WAM is also a key part of the CA Identity & Access Management (CA IAM) solution, which automates the administration of user identities and ensures only properly authorized users can access critical IT resources from the Web to the mainframe. This in turn is part of CA’s vision for Enterprise IT Management (EITM).

CA SiteMinder WAM Centralizes Web Access Management and Security Policy

For all the promise of the Web to increase revenues, manage costs and deepen relationships
with users, it also raises a new class of security, management and compliance challenges. As
your IT organization deploys applications with web front-ends and looks to build and manage
websites and portals to meet the information and access needs of potentially millions of users
both inside and outside your enterprise, a fundamental question looms: How do you let business
in while keeping risk out?
The answer is CA SiteMinder Web Access Manager. With advanced security management
capabilities and enterprise-class site administration, CA SiteMinder WAM provides the centralized
security management your organization needs to authenticate users and control access to web
applications and portals. Across Internet and intranet applications, it enables the secure delivery
of essential information and applications to your employees, partners, suppliers and customers.
It also scales to meet your growing business needs with flexible administration tools that can
support either centralized or distributed administration.
Use CA SiteMinder WAM to build and manage secure websites that offer a rich user experience,
simplified administration, enterprise-class security and 24 × 7 availability.

Key Capabilities
SINGLE SIGN-ON (SSO) CA SiteMinder WAM eliminates the challenge of multiple user logins
by enabling single sign-on for seamless access across multiple diverse web applications,
portals and security domains. Seamless access to enterprise applications such as SAP, Siebel,
PeopleSoft and Oracle is also supported through the SSO capability of CA SiteMinder WAM.
Integration with CA Single-Sign-On (CA SSO), the enterprise SSO component of the CA Identity &
Access Management solution, enables users to authenticate only once and have access both to
web applications protected by CA SiteMinder WAM and non-web applications with access
controlled by CA SSO.

STRONG AUTHENTICATION MANAGEMENT CA SiteMinder WAM provides a unified authentication
strategy to ensure the right level of security across Internet and intranet applications. This
ensures that high value applications are protected by stronger authentication methods while
lower value applications may be protected by simpler user name/password approaches.
CA SiteMinder WAM provides access management support for many authentication systems —
including passwords, tokens, X.509 certificates, smartcards, custom forms, biometrics — and
combinations of authentication methods.
In addition, CA SiteMinder WAM enables authorization policies to incorporate authentication
context. For example, when two authentication methods are in use by a particular organization
(for example username/password and one-time password tokens) and the user authenticates
with the one-time password, the user can be granted increased application entitlements.

CENTRALIZED, POLICY-BASED AUTHORIZATION, AUDIT, AND REPORTING CA SiteMinder
WAM centralizes the access management for customers, partners and employees across an
enterprise’s web applications. This eliminates the need for redundant, application-specific
security logic and provides a lower cost approach for ensuring an enterprise’s ability to meet
compliance requirements. CA SiteMinder WAM policies are rules or rule groups that allow
or deny access to a resource. Access can be restricted by user attributes, roles, groups and
dynamic groups and determined based on location and time. Authorization can be conducted
at the file, page or object level. In addition, controlled “impersonation” — where one
authorized user, such as a customer service representative, can access what another user
can access — is also defined by policies. An embedded policy analysis engine, reporting
system, and out of the box reports support an organization’s evolving needs for compliance
and governance reporting.

Dynamic Authorization triggers security policies that evaluate data in real time from a variety
of local or external sources, including Web services and databases, to determine access
authorization or denial. Finer-grained authorization is achieved through contextual evaluation.
For example, limit access to a specific application (a certain banking service) to customers who
meet specific criteria (a minimum account balance). Authorization policies can also be applied
in conjunction with external systems, such as risk-based security systems.
ENTERPRISE MANAGEABILITY CA SiteMinder WAM provides enterprise-class system management
tools, which gives security personnel the ability to monitor, manage and maintain multiple
environments more efficiently, including the management of development, test and production
environments. These management tools include:
• Unattended installs
• Operational monitoring
• Rolling upgrades
• Centralized web agent management
• Application management abstraction
• Delegated and segregated management
• Web-based administrative UI
• Security policy migration
• Security zones
• Scripting interface capabilities
SCALABILITY AND RELIABILITY CA SiteMinder WAM can be scaled to meet enterprise-class
security requirements both in terms of the number of users and number of protected resources,
ensuring its ability to handle growth, including growth from acquisitions or partnerships.
Use CA SiteMinder WAM to deploy critical business applications to multimillion user populations
and be confident that its performance has been verified through independent testing to provide
significantly higher transaction rates, reliability and manageability than alternative solutions.

Reliability, availability and scalability are supported by features including:
• Dynamic load balancing
• Two-level caching
• Policy Server clustering and cluster-to-cluster failover
• Policy Store and user store replication
• Support for 4- and 8-way SMP servers
IDENTITY FEDERATION CA SiteMinder WAM also provides an architecturally integrated,
separately-licensed capability that enables browser-based federation whereby users can securely
traverse from home sites (identity provider) to websites hosted by partners and customers (service
provider). CA SiteMinder WAM customers can play the role of either website in a federation.
The federation functionality, called CA Federation Manager, provides a flexible and robust
platform for identity federation, enabling organizations to realize the benefits of connecting
distributed business applications across domains without sacrificing security. CA Federation
Manager supports a comprehensive set of federation standards, including the Security
Assertion Markup Language (SAML) and WS-Federation/Microsoft ADFS. It enables complete,
bidirectional federation from a single Web security system with maximum interoperability
among partnering enterprises. In addition CA SiteMinder WAM can be extended to provide
security for Web services through the addition of CA SOA Security Manager.


HOW CA SITEMINDER WEB ACCESS MANAGER WORKS



The process for securely accessing   
web applications:
1 User attempts to access a protected
resource.
2 User is challenged for credentials and
presents them to the CA SiteMinder
web agent or to the Secure Proxy
Server.
3 The user’s credentials are passed to
the Policy Server.
4 The user is authenticated against the
appropriate user store.
5 The Policy Server evaluates the user’s
entitlements and grants access.
6 User profile and entitlement information
is passed to the application.
7 The user gets access to the secured
application, which delivers customized content.

CA SiteMinder WAM Supports Online Business, Enhances User
Satisfaction, Mitigates Costs and Increases IT Control and Security
The Web is open for business around-the-clock, and CA SiteMinder WAM reliably and
effectively enables your online presence to be secure, available and accessible to the right
users. Recognized for having the most advanced security management capabilities and
enterprise-class site administration, CA SiteMinder WAM can scale to support millions of
users and thousands of protected resources.
CA SiteMinder WAM allows you to meet the challenge of deploying resources via the Web
while maintaining high performance and high availability. It controls who is able to access
which applications and under what conditions, improves users’ online experiences and
simplifies security administration. By enforcing policies and monitoring and reporting online
activities and user privileges, CA SiteMinder WAM also eases regulatory compliance.
ENSURE THE RIGHT USERS HAVE THE RIGHT ACCESS With CA SiteMinder WAM, the secure
management of identities across diverse web systems means the system controls access by
leveraging the user’s context to the business (partner, consultant, customer, etc.) and their
rights to each application. CA SiteMinder WAM enables users to connect to the information
and applications they need to do their jobs, place an order or otherwise transact business.
INCREASE SECURITY TO MITIGATE RISKS CA SiteMinder WAM reduces the risk of unauthorized
access to critical resources and sensitive information, protecting the content of an entire web
portal or set of applications. Centralized security enforcement and FIPS certified cryptographic
algorithms means that there are no holes left open in a CA SiteMinder WAM secured web
environment.
PROVIDE USERS WITH A POSITIVE ONLINE EXPERIENCE CA SiteMinder WAM lets a user sign on
once to access web applications, engaging them in a unified, personalized online experience
rather than frustrating them with multiple logins.
INCREASE BUSINESS OPPORTUNITIES CA SiteMinder WAM lets you securely deploy web
applications to multiple different user communities, enabling increased business opportunities
that can enhance revenue. Extend CA SiteMinder WAM with identity federation and your
organization can improve collaboration with partners, further enhancing relationships to
increase revenue, manage cost and mitigate risk
MANAGE COSTS CA SiteMinder WAM mitigates IT administration costs. It also reduces the
security burden on users and thus the burden on the help desk caused by lost or forgotten
credentials. It also reduces redundant security-related application development and
maintenance costs.
EASE REGULATORY COMPLIANCE Central policy management, enforcement, reporting and
auditing support your ability to comply with IT impacting regulations.






The CA Advantage
CA SiteMinder WAM is part of the complete and proven CA IAM solution that helps you protect
your IT assets across all platforms and environments. As such, it contributes to your ability to
optimize the performance, reliability and efficiency of your overall IT environment. The next step
is to tightly integrate the control and management of distinct functions such as operations, storage
and life cycle and service management, along with IT security.
This higher level of management control is CA’s vision for EITM — a dynamic and secure approach
that integrates and automates the management of applications, databases, networks, security,
storage and systems across departments and disciplines to maximize the full potential of each.
CA’s comprehensive portfolio of modular IT management solutions helps the enterprise unify,
simplify and secure IT to better manage risk, costs and service, and ensure that IT meets the
business needs of the enterprise.

Next Steps
To fully leverage the reach and power of the Web, investigate the breadth and depth of
CA SiteMinder Web Access Manager. As the most comprehensive, scalable and reliable
Web Access Management solution on the market, it supports your organization’s ability to
increase new business opportunities, manage costs, improve security to mitigate risk and
ease compliance.


Unix, Linux administration interview questions
2009-03-27T05:07:00.000-07:00
What is LILO?

LILO stands for Linux boot loader. It will load the MBR, master boot record, into the memory, and tell the system which partition and hard drive to boot from.

What is the main advantage of creating links to a file instead of copies of the file?

The main advantage is not really that it saves disk space (though it does that too) but, rather, that a change of permissions on the file is applied to all the link access points. The link will show permissions of lrwxrwxrwx but that is for the link itself and not the access to the file to which the link points. Thus if you want to change the permissions for a command, such as su, you only have to do it on the original. With copies you have to find all of the copies and change permission on each of the copies.

Write a command to find all of the files which have been accessed within the last 30 days.

find / -type f -atime -30 > December.files
This command will find all the files under root, which is ‘/’, with file type is file. ‘-atime -30′ will give all the files accessed less than 30 days ago. And the output will put into a file call December.files.

What is the most graceful way to get to run level single user mode?

The most graceful way is to use the command init s.
If you want to shut everything down before going to single user mode then do init 0 first and from the ok prompt do a boot -s.

What does the following command line produce? Explain each aspect of this line.

$ (date ; ps -ef | awk ‘{print $1}’ | sort | uniq | wc -l ) >> Activity.log 
First let’s dissect the line: The date gives the date and time as the first command of the line, this is followed by the a list of all running processes in long form with UIDs listed first, this is the ps -ef. These are fed into the awk which filters out all but the UIDs; these UIDs are piped into sort for no discernible reason and then onto uniq (now we see the reason for the sort - uniq only works on sorted data - if the list is A, B, A, then A, B, A will be the output of uniq, but if it’s A, A, B then A, B is the output) which produces only one copy of each UID. 
These UIDs are fed into wc -l which counts the lines - in this case the number of distinct UIDs running processes on the system. Finally the results of these two commands, the date and the wc -l, are appended to the file "Activity.log". Now to answer the question as to what this command line produces. This writes the date and time into the file Activity.log together with the number of distinct users who have processes running on the system at that time. If the file already exists, then these items are appended to the file, otherwise the file is created.


IKEYCMD ( IKEYMAN ) Command Line Interface (gsk7cmd)
2009-03-26T04:23:00.000-07:00
Environment Set Up for IKEYCMD Command Line Interface
To run IKEYMAN , set up environment variables to use the IKEYCMD command line interface
as follows:
1. Set your PATH to where your Java or JRE executable resides:
EXPORT PATH=/opt/IBMJava/bin:$PATH

2. Set the following CLASSPATH environment variable:
EXPORT CLASSPATH=/usr/local/ibm/gsk/classes/cfwk.zip:/usr/local/ibm/gsk/classes/gsk4cls.jar:$CLASSPATH

Once completed, IKEYCMD should run from any directory. To run an IKEYCMD command,
use the following syntax:
java com.ibm.gsk.ikeyman.ikeycmd (command)

You can substitute JRE for Java, depending on whether you are using a JRE or JDK.
Example:
jre com.ibm.gsk.ikeyman.ikeycmd (command)

IKEYCMD Command Line Syntax
The syntax of the Java CLI is: java [-Dikeycmd.properties= com.ibm.gsk.ikeyman.ikeycmd (object) (action)[options]

where:
-Dikeycmd.properties Specifies the name of an optional properties file to use for this Java
invocation. A default properties file, ikeycmd.properties, is provided as a sample file that can be modified and used by any Java application.

Object is one of the following:

-keydb    Actions taken on the key database (either a CMS key database file, a WebDB keyring file, or SSLight class)
-cert   Actions taken on a certificate
-certreq   Actions taken on a certificate request
-help   Display help for the IKEYCMD invocations
-version   Display version information for IKEYCMD

Action is the specific action to be taken on the object, and options are the options, both required
and optional, specified for the object and action pair.

Note: The object and action keywords are positional and must be specified in the selected
order. However, options are not positional and can be specified in any order, provided
that they are specified as an option and operand pair.

User Interface Task Reference
IKEYCMD command line interface tasks are summarized in the following table.

IKEYMAN and IKEYCMD task

Create a new key database and specify the
database password

Create a new key pair and certificate request
Create a self-signed certificate
Export a key to another database or PKCS12 file
Import a key from another database or PKCS12
file
List certificate authorities (CAs) and certificate
requests
Open a key database

Receive a CA-signed certificate into a key
database
Show the default key in a key database

Store the root certificate of a CA
Store the encrypted database password in a stash
file


Free Trial - IBM WebSphere Message Broker, WebSphere Message Broker V6.1
2009-03-19T23:38:00.000-07:00
WebSphere Message Broker V6.1, an Enterprise Service Bus (ESB) built for universal connectivity and transformation in heterogeneous IT environments. WebSphere Message Broker distributes information and data generated by business events in real time to people, applications, and devices throughout your extended enterprise and beyond.

Provides a smart approach to SOA, extending the reach of your business beyond your firewall by supporting a broad range of multiple transport protocols and data formats
Integrates multiple applications, networks, and device types using a platform-independent based enterprise service bus that lets you conduct business reliably and securely
Increases business agility and flexibility, extending easily to a Federated ESB model, while reducing development costs by separating integration logic from applications
Improves the flow of information around the business, moving away from hard-coded point-to-point links to more flexible distribution mechanisms such as publish/subscribe and multi-cast
Uses a simple programming model for connectivity and mediation, including a robust set of pre-built mediation function and ways to customize mediations
Exploits the industry-leading WebSphere MQ messaging infrastructure, and supports transformation options with graphical mapping, Java, ESQL, XSL, and WebSphere Transformation Extender
Delivers extensive administration and systems management facilities for developed solutions
Features and benefits of WebSphere Message Broker

IBM WebSphere® Message Broker V6.1 supports the following key capabilities and benefits:
Platform-Independent Based Enterprise Service Bus
Distribute any type of information across and between multiple diverse systems and applications, providing delivery of the right information in the right format at the right time
Reduce point-to-point interconnections and simplify application programming through separation of integration logic from the applications and from process logic
Powerful publish-and-subscribe matching engine routes information in real time based on topic and content to any endpoint
Validate and transform messages in-flight between any combination of different message formats, including Web Services, other XML and non-XML formats
Route messages based on (evaluated) business rules to match information content and business processes
Improve business agility by dynamically reconfiguring information distribution patterns without reprogramming end-point applications
Powerful runtime security model to address security concerns.
Integrated JCA based WebSphere Adapters as built-in nodes
Strengthens security and accelerates Web Services Security processing with DataPower SOA Appliance
Integration and enhancement of WebSphere Service Registry and Repository support to virtualize services for greater reuse
Enhance SOA support with advanced Web Services
Mediates (provides routing, transformation and logging) between Web Service requesters and providers
Mediates between Web Services and other integration models as both a service requester and a service provider
Delivers support for Web Services Security and Web Services Addressing, and compliance for Basic Profile
Works with the latest implementations of standards such as WSDL (Web Services Definition Language), SOAP (Simple Object Access Protocol), SOAP with attachments, any JMS (Java™ Message Service) HTTP(s) (Hypertext Transport Protocol), MTOM/XOP, and MQ
Enhanced support for provider and consumer scenarios
Toolkit support for WSDL drag and drop for skeleton flow creation and configuration
Full message set round-tripping for WSDL imports and exports.
New Web services parser creates more consumable message tree.
Integration without bounds with connectivity and transformation capabilities
Integrated WebSphere MQ transports - for Enterprise, Mobile, Real-Time, Multicast and Telemetry end points - extend the reach, scope and scale of the enterprise integration bus, out to mobile and handheld devices, along with embedded devices such as sensors or actuators.
Enable the secure and seamless interaction of enterprise applications with thousands of users within the Intranet and across the Internet
Provide native JMS interoperability, acting as a bridge between any combinations of different JMS providers.
Out-of-the-box nodes to simplify management and improve performance for key enterprise resource planning (ERP) integration scenarios (for example, SAP, Siebel, and PeopleSoft) through WebSphere Adapters packaged as native message-processing nodes
Native support for large file processing, including FTP, to simplify processing of large, repeating complex file records without using excessive storage
New Email Output node
Integration with WebSphere Transformation Extender, including the launcher, enabling WebSphere Transformation Extended maps to run natively in WebSphere Message Broker
Improved Consumability, Productivity and Systems Management
Provides a quick start with a single-click installation; install the product and run a sample in less than an hour
Simple packaging allowing for easy identification of appropriate install assets
Single install DVD for Windows and Linux desktops
ISMP installer for all platforms, SMP/.E for z/Os systems
Comprehensive "samples gallery" for all new and existing functions
Enterprise-wide identity, authentication, and authorization with Tivoli and Lightweight Directory Access Protocol (LDAP) servers to enforce service policy at the user level for greater security
Administration of both WebSphere MQ and WebSphere Message Broker networks in one console with the Eclipse-based Message Broker Explorer
Roll back with a single click
Extend your infrastructure with broader platform support and performance
Extend an existing WebSphere MQ and WebSphere Event Broker infrastructure
Available on IBM z/OS®, IBM AIX®, Linux (zSeries®, Intel, Power), Solaris (x86-64 and SPARC), HP/UX(PA-RISC, Itanium) and Microsoft® Windows® Server
Full range of industry standard databases includting support for DB2, SQL Server, Oracle, Sybase and Informix
Accounting and statistics reports support usage based charges and real-time graphical performance analysis for internal business charging
Enhanced SAP IDOC support
Improved binary data modeling within text messages.
64-bit capability on Linux and UNIX, Java Database Connectivity (JDBC) XA support, and Java 5 on all platforms
Ultra High Performance XML parser, including schema validation
Compacted memory footprint
Enhanced Developer Productivity
Eclipse based Message Broker Toolkit compatible with Rational Application Developer V6 and available on Windows and Linux
Data transformation options to match the data format and the developer skill set
Reduced toolkit size with enhanced look and feel improvements including productivity aids.
Standards based metadata including XML Schema and Web Services Definition Language
Java Debug Protocol (JDP) enabled withing toolkit
Graphical message metadata and mapping definition
Visual trace capability to display message path through flow in real time in Eclipse
New message viewer to graphically identify source and/or target message element locations
Simplified development with a configuration-drive approach for all new nodes
Eclipse based Type Designer and Map Designer integrated with the toolkit
Download a free trial version of WebSphere Message Broker V6.1



History of IBM Websphere Application Server (WAS), What is WAS.
2009-03-07T21:32:00.000-08:00
IBM WebSphere Application Server (WAS)
a software application server, is the flagship product within IBM's Websphere brand. WAS is built using open standards such as Java EE, XML, and Web Services. It works with a number of Web servers including Apache HTTP Server, Netscape Enterprise Server, Microsoft Internet Information Services (IIS), IBM HTTP Server for i5/OS, IBM HTTP Server for z/OS, and IBM HTTP Server for AIX/Linux/Microsoft Windows/Solaris.
WAS Versions
Version 1 of IBM WebSphere Application Server (WAS).
IBM has shipped several versions and editions of WAS. In the first beta versions, WAS was called Servlet Express.
What started it all in June, 1998. Really only a Java Servlet engine at that point.
Version 2 of IBM WebSphere Application Server (WAS).
In this version IBM adds JavaBean and CORBA support. Now supports Linux. Comes in two editions: Standard Edition (SE) and Advanced Edition (AE).
Version 3 of IBM WebSphere Application Server (WAS).
This version of WAS was compatible with a JDK 1.2, J2EE 1.0 version. IBM provided many enhancements to the basic J2EE 1.0 spec. Support for OS/400 (now i5/OS) and OS/390 (now z/OS) was added, although the z/OS version maintained a substantially separate codebase until v5.x. Version 3 is distributed in three editions: Standard Edition (SE), Advanced Edition (AE), and Enterprise Edition (EE).
Version 3.5 of IBM WebSphere Application Server (WAS).
This version was shipped in following editions:
· SE (Standard Edition)
· AE (Advanced Edition)
· EE (Enterprise Edition)
Version 4 of IBM WebSphere Application Server (WAS).
This was a J2EE 1.2 certified application server. It inherited the database-based configuration model from V3.x for all but the single-server edition, which already used an XML datastore.
· AE (Advanced Edition)
· AEs (Advanced Edition single). Single-server edition that was not able to run in a cluster configuration.
· AEd (Developer Edition). Functionally equivalent to AEs, but intended only for non-production development use.
· EE (Enterprise Edition) 

Version 5 of IBM WebSphere Application Server (WAS).
The version released on 19 November 2002. This was a J2EE 1.3 certified application server. It was a major rewrite of the V3/V4 codebase and was the first time WebSphere Application Server was coded from a common codebase. Now WAS across all deployment platforms, from Intel x86 to the mainframe, are substantially the same code. The database-based configuration repository was replaced with a replication XML file-based configuration repository. A service called the Deployment Manager had the master copy of the cell configuration, and nodes had the file(s) they needed copied from this master server whenever they changed. V5 also included a miniature version of MQ 5.3 called the embedded Java Message Service (JMS) server.
· Express Edition replaces the Standard Edition. Express now becomes the term to indicate SME-oriented offerings from IBM, across all its software brands.
· Base
· Network Deployment. This version supports deployment of a cell configuration with cluster and J2EE failover support. It now also includes Edge Components, previously known as Edge Server. This provides a proxy server, load balancing, and content-based routing.
· Enterprise Edition. This version added a workflow engine, called the Process Choreographer, for the first time but predates the BPEL standard. It also added the first fully supported application threading model called WebSphere Asynchronous Beans.
· WebSphere Application Server for z/OS. This version is essentially the same as the Network Deployment product but is optimized to take full advantage of z/OS features, such as Workload Manager, to leverage the key technologies that make the mainframe indispensable for mission-critical, scalable, and secure workloads. 
Version 5.1 of IBM WebSphere Application Server (WAS).
Released 1 April 2004.
· The main change from V5.0 was a JDK upgrade to 1.4.2 and use of the Jython language for wsadmin scripting support instead of only supporting Java Tcl.
· Express
· Base
· Network Deployment
· WebSphere Application Server for z/OS
Version 5.1 for z/OS is the first to support zAAP engines.
· WebSphere Business Integration Server Foundation V5.1
This is the follow on product to WebSphere Application Server Enterprise Edition V5.0. The workflow engine was updated to support BPEL rather than the proprietary FDML format used in V5.0. The product was also repriced and available on all IBM platforms from the Intel environments to the mainframe.
· WebSphere eXtended Deployment (XD)
For more information please reference the #WebSphere eXtended Deployment section below. 

Version 6 of IBM WebSphere Application Server (WAS).
· This version was released on December 31, 2004. It is a Java EE 1.4 compliant application server. Security enhancements include support for JACC 1.0 and WS-Security 1.0.
· Support for Java Standard Edition 1.4
· Community Edition (free, support for fee)
Code based on Apache Geronimo project
· Express (list price US$2,000 per CPU, licensed to use up to two CPUs)
Many programming model extensions previously found in WebSphere Application Server V5.0 Enterprise Edition were moved out of enterprise and into Express and Base. These APIs included application profile, startup beans, the scheduler, and async beans.
The JMS engine, now called "WebSphere Platform Messaging," was rewritten in 100% Java and its functionality greatly enhanced. (WebSphere MQ is still supported as the JMS provider and is interoperable with WebSphere Platform Messaging.)
· Base (list price US$10,000 per CPU)
· Network Deployment (list price US$16,000 per CPU)
The clustering was rewritten to use the high availability manager. This manages all singletons in the WebSphere environment and can provide hot recovery for those singletons.
WebSphere was modified so that a shared file system can be used to store transaction logs and this meant that any cluster member with that shared file system mounted can hot recover in-doubt XA transactions with no external HA software.
The Deployment Manager's role was eliminated from all clustering runtime operations. It's only required for centralized JMX admin and config changes.
Now supports running mixed version cells (V5 to V6) in production.
· WebSphere Application Server for z/OS
Provides the same core functionality as Network Deployment, since it shares a common programming model, but still contains the platform advantages such as:
· z/OS Workload Manager for prioritized management of mixed workloads
· Resource Recovery Services (added transactional integrity for complex, critical transactions)
· Support for security mainframe products such a RACF
· Advanced vertical scaling for application server by featuring a unique control region (integrated control area) server region (where workloads are completed) separation which enables the control region to open and close server regions as needed by the volume of incoming requests
· Parallel Sysplex support for full participation in the Sysplex, enabling advanced failover support and a geographically dispersed environment that seamlessly acts as one with a centralized logging and management facility
· eXtended Deployment (listprice: $16000 USD / cpu)
WAS XD as it is known increases the functionality of the application server in two main areas - Manageability and Performance. It also allows makes possible new configurations, such as dynamic virtualization between pools of application servers.
Under the performance header the ObjectGrid component was added, which is a standalone distributed cache that can be used with any application server (any version with a 1.4 JDK) or with any J2SE 1.4 runtime, including zLinux and z/OS support.
With Version 6, some of the functionality previously found in WebSphere Business Integration Server Foundation (WBISF) moved into the new IBM WebSphere Process Server. Other function moved into the other editions (Express and above).
Version 6.1 of IBM WebSphere Application Server (WAS).
This version was released on June 30, 2006. It is a Java EE 1.4 compliant application server and includes the following function:
·        Support for Java Standard Edition 1.5
·        Support for running JSR 168 Portlets in the application server
·        Session Initiation Protocol (SIP) Servlets
·        Enhancements to the WebSphere Install Factory
·        IBM Support Assistant
·        IBM JSF Widget Library
·        Simplified Administration
·        Improved Certificate and Key Management
·        Security Enhancements
·        Administration of IBM HTTP Server from WebSphere Admin Console
·        Support for Web Services Resource Framework and WS-BusinessActivity (WS-BA)
·        Support for JSR160 JMX Remote Connections (From IBM Agents Only)
·        Administrative Console Jython Command Assistance
·        Enhanced scripting. This version started the deprecation process for the Jacl syntax.[1]
·        64-bit servants and a new Apache-based IBM HTTP Server for z/OS
Support for the EJB 3.0 technology and support for some webservices standards were provided by the EJB feature pack and the webservices feature packs, respectively. These function in these feature packs has been folded into the main product in version 7. Functions in the webservices feature pack include:
·        Asynchronous programming model (Limited functional support)
·        Multiple Payload structures
·        StAX (Streaming API for XML)
·        WS-RM (Limited functional support)
·        WS-Addressing (Limited functional support)
·        JAX-B support
·        Policy Set (Limited functional support)
·        Secured thin client (Limited functional support)
·        SOAP (protocol) Message Transmission Optimization Mechanism (MTOM)
·        Supports CGI and CORBA 

Version 7 of IBM WebSphere Application Server (WAS).
·        This version was released on September 9, 2008. It is a Java EE 5 compliant application server.
Following are the flagship features of WebSphere Application Server Version 7:
·        Flexible Management
Flexible Management facilitate administration of a large number of WebSphere Application Server base edition and Network Deployment topologies that might be geographically distributed.
·        Business-Level Application
Business-Level Application is used for managing application artifacts independent of packaging or programming models.
·        Property Based Configuration
Property Based Configuration feature simplifies the experience of automating administration, administrator can update the WebSphere Application Server Version 7 configuration using simple property file.
WebSphere Extended Deployment
WebSphere Application Server V6 Extended Deployment Edition (WebSphere XD) was released in 2006 as an add-on for WebSphere 6. XD provides advanced features for both administrators who manage multiple Java EE-based applications and developers building advanced applications that require asymmetric clustering techniques. It also has a number of technologies to significantly increase the performance of running applications, including an in-memory database cache and a highly advanced load balancer called the on demand router.
Administrator benefits
Many businesses run multiple server farms but wish to consolidate them into a single smaller server farm. This is because most server farms are underutilizied or over provisioned. The boxes are typically running at 10% load which is quite costly and is not flexible. For example, one server farm goes hot and maxes out while the farm in the next room is still basically idle at 10%. XD allows administrators to define a single cluster (a node group) then monitor the workload and dynamically decide which boxes in the node group should host which application in order to meet these goals. If application A has a current response time of 1.5 seconds, XD will move resources away from applications B and C to increase the power dedicated to A and decrease its response time. XD can also predict that A will likely exceed its response time in 10 minutes based on a trend and react in anticipation of the event. This greatly simplifies the life of an administrator and allows the machines to be more efficiently used than a conventional multiple, independent farm of farms approach. XD also offers options to generate various email alerts when conditions are exceeded. It can also restart servers when they appear to have a memory leak, or after X requests.
Developer benefits
WebSphere Partition Facility
Traditional Java EE applications work well for a large class of applications. The class can be broadly categorized as applications that run in a stateless symmetric cluster in front of a database:
·        All the cluster members can perform any task at any time.
·        The application is stateless.
·        The application is modal, such that it only performs work synchronously in response to a client request which can be received using http://IIOP or JMS.
There are other applications that do not work well in such an environment, for example, an electronic trading system in a bank. Such applications typically use performance enhancing techniques such as partitioning, multi-threading, and write-through caching. These are applications that can exploit asymmetric clustering. An asymmetric cluster is essentially the opposite of a symmetric cluster:
·        Applications can declare named partitions at any point while they are running, partitions are highly available, mobile within the cluster, and usually only run on a single cluster member at a time.
·        Incoming work for a partition is routed to the cluster member hosting the partition.
·        The application is amodal. Partitions have a lifecycle of their own and can start background threads or alarms as well as respond to incoming events whether they are IIOP/HTTP or JMS/foreign messages.
WebSphere XD offers a new set of APIs called the WebSphere Partition Facility (WPF). These APIs allow applications that require an asymmetric cluster to be deployed on a Java EE server.
ObjectGrid
The ObjectGrid is the first piece of the IBM distributed caching framework. V6 of XD shipped with support for local Java object caching as well as peer-to-peer caching with asynchronous data push/invalidation. It is designed as a small footprint, to install customer extensible framework for caching objects. All aspects of the core framework have plugin points. This allows customers to add function as well as allow IBM to extend it in future product levels. It is designed to run independent of WebSphere. This does not mean it won't integrate with WebSphere 6.0 XD -- it will. But it will also work on older versions of the application server, Tomcat servers, and competitive application servers. In a very limited sense, memcached performs some of the same functions as ObjectGrid[2]
ObjectGrid is intended to compete against the other distributed cache products on the market. It currently requires only a 1.4 level JDK from any vendor. Version 2 of the ObjectGrid is currently under development for shipping in XD 6.0.1. It will add significant function to the component as well as widen JDK level support. The intent is to allow customers to build large grids of JVMs into which they can connect applications and store objects at various qualities of service. The grid is being designed to scale to thousands of JVMs and hold a large quantity of data.
Compute Grid
Also known as WebSphere Batch, WebSphere XD also offers a Java Batch processing system called Compute Grid. This was first introduced in XD version 6.1. Compute Grid is deployed as an additional feature of a WebSphere Network environment. It provides a number of features that help you create, execute and manage batch jobs. The features include: an XML-based job control language (xJCL), batch programming model, job scheduler, and batch container.
Security
The WebSphere Application Server security model is based on the services provided in the operating system and the Java EE security model. WebSphere Application Server provides implementations of user authentication and authorization mechanisms providing support for various user registries:
·        Local operating system user registry
·        LDAP user registry
·        Federated user registry (as of version 6.1)
·        Custom user registry
The authentication mechanisms supported by WebSphere are [3]
·        Lightweight Third Party Authentication (LTPA)