If you want to cut off the incoming requests that take more than specified time from the server side, unfortunately no way to configure this in WebSphere. There is a property at the plug-in level that might be sufficient. Please see the ‘ServerIOTimeout’ property in the document at link:  http://www-01.ibm.com/support/docview.wss?uid=swg21318463

This would make it so that the plug-in cuts off the connection after 5 seconds. Please keep in mind that this request would still continue in WAS and eventually result in an IOException when it tries to write the response. This will not cause any problems, but it won’t reduce any performance impact if you’re expecting that when reducing the timeout.

If you faced  HMGR0149E error on nodeagent or intance logs, follow below steps:

1. Stop all nodes, servers, dmgrs

2. Start dmgr
3. run command ./syncNode.sh x.xx.xxx.xxx 8879 -username xxx -password xxxxxxx
4. start node and servers.
5. check the log at the same time. no errors now!

If you get WASX7070E error when you use wsadmin command, it means the script takes one of the argument as SOAP_CONNECTOR_ADDRESS.

Once make sure to the SOAP_CONNECTOR_ADDRESS port (dmgr port in ND environment), now take look at  the \AppServer\profiles\AppSrv01\properties\wsadmin.properties and look for value for com.ibm.ws.scripting.port . Both port should be same.

taken error in my environment:

WASX7015E: Exception running command: “AdminConfig.list (‘Server’)”; exception information:
com.ibm.ws.scripting.ScriptingException: WASX7070E: The configuration service is not available.

-Once Installation Manager is installed, the appData Location cannot be changed.

-If directory is lost or corrupt, future updates to the product can be affected

-Products will run fine but cannot be updated or uninstalled

-Recommended to backup this directory when WAS backup is taken

-The default can be changed by installing IM with -dL or -dataLocation option •Example for Graphical Install

− ./userinst -dL /usr/IBM/AppData (non root) − ./install -dL /opt/IBM/AppData (root)

-The user can use different appDataLocation for each product by specifying the – dataLocation (or –dL) option when starting Installation Manager, and then should use the same option on subsequent invocations

-User need to maintain record of data agent used for each install

If you use captcha on your application the default fonts defined on Websphere couldn’t suffice. You can use custom fonts for this.

Default font location on WAS: <WAS install location>/java/jre/lib/fonts

Configured custom fonts:

If you have stale connnection error as below  set min. connection parameter to “0”  in datasource panel.

min connection = 0

Error:

com.ibm.websphere.ce.cm.StaleConnectionException: Broken pipe

You are using Websphere Application Server 7 and also see the following exception in the SystemOut file:

[2/20/12 13:58:48:154 EET] 00000000 JMSRegistrati E   WMSG1603E: An internal error occurred. It was not possible to register the WebSphere MQ JMS client with the application server due to exception org.osgi.framework.BundleException: An error occurred trying to read the bundle

The steps to enable strong encryption are as follow:

1) Go to the developerWorks Java Technology Security page at URL:- http://www.ibm.com/developerworks/java/jdk/security/

2) Click on the “J2SE 5.0” link

3) Scroll down on the resulting page and click on the “IBM SDK Policy files” link.

4) This will take you to the “Unrestricted JCE Policy files” page. If you already have an IBM ID and password, click on the “Sign in” link. Otherwise, click on the “register now” link to create an ID.

5) On the Sign in page, supply your IBM ID and Password.

6) Select “Unrestricted JCE Policy files for SDK for all newer versions 1.4.2+” and click on Continue.

7) Scroll down to the License portion of the resulting page and click on the View license link to see the licensing terms for the download.

8) If the licensing terms are acceptable, check “I agree” and click on the “I confirm” link. If the terms are not acceptable, you will not be able to enable strong encryption and should click “I cancel”.

9) Click on the Download now link to download the unrestricted.zip file.

10) Extract the local_policy.jar and US_export_policy.jar files from the unrestricted.zip archive.

11) Place these two files in the WAS_HOME/java/jre/lib/security directory, replacing the existing files with the same names. For a default installation, the directory would be WAS_HOME/java/jre/lib/security.

There are thee ways for tracking:

• Cookies
• URL Rewriting
• SSL information

COOKIES

Using cookies is the simplest and most common way to track HTTP sessions, because it requires no special programming to track sessions. When session management is enabled and a client makes a request, the HttpSession object is created and a unique session ID is generated for the client and sent to the browser as a cookie. On subsequent requests to the same hostname, the browser continues to send the same session ID back as a cookie and the Session Manager uses the cookie to find the HttpSession associated with the client.
Yazının tamamını okuyun (read more) »

 You cannot re-send an “old” certreq.arm to the CA (for example: Verisign, Thwarte, Entrust, and so on) or re-import/receive the “old” certificate issued by the CA into iKeyman for renewal. Neither one of the preceding methods will work, nor are they supported.

1. Start the iKeyman graphical interface.
2. Open the existing KeyFile (.kdb) that contains the certificate.
3. Click on the “old” certificate in the Personal Certificates section of the KeyFile and then click on the Recreate request button to the right of the screen. This will bring up a window asking you to provide a name for the request. The default of certreq.arm is fine. Save the file to the hard drive (preferably in the same directory as the old request file.)
   Note: Do not delete the “old” certificate.
4. Send the “new” certreq.arm to your CA.
5. After receiving the “renewal” certificate from the CA, click on the Receive button to the right of the screen and browse to the directory where you have stored the “renewal” certificate.
6. Highlight the “renewal” certificate and click Open and then click OK. You should then see the following message:
   

   A renewal certificate was found, Do you want to update the existing certificate?

7. Select Yes.
8. Your “renewal” certificate should be successfully added to your (.kdb) file.
9. Close the iKeyman utility and restart the IBM HTTP Server for the changes to take effect.
   Caution: Some certificate authorities add strings to the users requested Distinguished Name, but will not accept renewal requests that already contain the added strings. One such example is an addition to the OU field of:”OU = Member, VeriSign Trust Network”If the renewal request is rejected due to the presence of the CAs additions in the request, create a new certificate request manually instead of using the “recreate certificate request” function of iKeyman.

taken from IBM support