You can use -Xloratio parameter For WebSphere Application Server V6.0, V5.1 and V5.0 (Java 1.4.2) .If your WAS version is WebSphere Application Server V7.0, V6.1 (Java V1.6, V1.5) ,There is no need to explicitly set the size. The value can be manually limited with using the -Xloainitial and -Xloamaximum, however it is not recommended.

The detailed technote :

Yorum (comment) (1)

If you are getting an error something like this:
“SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: /jsp/custinfo/CustomerInfoView.jsp. Exception thrown : javax.servlet.ServletException: Duplicate component ID ‘viewns_7_63MG8B1A00CNB0IILUHGC33082_:form1:_id18’ found in view.”

This error related with JSF :
WebSphere Application Server’s JSF implementation generates new
client IDs for some JSF components on a post back. These new
IDs can collide with the cached client IDs when the order of
the components change, or a new component requests an ID that
did not do so in the previous request.

Work around to fix this issue:

To prevent collision with existing client IDs, the property must be set to
“true” in the web.xml file. true

Yorum (comment) (0)

1- Create a group (ihsgrp) and a user (ihsadm) for the IHS (IBM Http Server)

2- Change owner for IHS
chown –R ihsadm:ihsgrp /opt/IBMIHS61

3- Edit the httpd.conf file so that the web server runs with the user ihsadm and the group ihsgrp
User ihsadmin
Group ihsgrp

4- Edit visudo to add belowed line for linux:
wasadm ALL=NOPASSWD: /opt/IBMIHS60/bin/apachectl -k start -f /opt/IBMIHS60/conf/httpd.conf, /opt/IBMIHS60/bin/apachectl -k stop -f /opt/IBMIHS60/conf/httpd.conf

5- Create file in IHS/bind directory and add this command:
/usr/bin/sudo /opt/IBMIHS61/bin/apachectl “$@”

6- Change owner for so wasadm user can execute
chown wasadm:wasgrp

7- Change startCommand and stopCommand parameter values:
Go webserver properties page of the admin console
Web servers > TWSWKI0101TR > Process Definition

startCommand : ${WEB_INSTALL_ROOT}/bin/
stopCommand : ${WEB_INSTALL_ROOT}/bin/

Yorum (comment) (0)

If you want to change your node names you can follow this steps:

1- Stop nodes except deployment manager

2 – Execute following command at /bin directory:

./ dmgr01 16003 node1 -username wpsbind -password wpsbind -logfile ( dmgr_host dmgr_port node_name ) changenode.txt

3- Execute following command at /ConfigEngine directory:

/ rename-node-in-cell-registry -DWasPassword=wpsbind -DpreviousNodeName=node1 (./ rename-node-in-cell-registry -DWasPassword=password -DpreviousNodeName=oldNodeName )

4- Edit deployment.xml files with new nodename under /config/application/ at dmgr machine

Yorum (comment) (0)

FOR  6.0.x

1- locate <dmgrprofile>/config/wmm/

2- add properties  in  wmmAttributes.xml  and wmmLDAPServerAttributes.xml files.

Caution:  wmmAttributes.xml uses attribute properties  ,  wmmLDAPServerAttributes.xml uses attributeMap properties.


          <attribute wmmAttributeName=”workingBranch”


        <attributeMap wmmAttributeName=”workingBranch”
Yazının tamamını okuyun (

Yorum (comment) (0)

Following technote’s  suggestion was’nt work corrently on my Portal Servers. So I have prapered new procedure for me .

My configuration:

For Websphere Administrative Console Machine:

1- Stop dmgr ,nodes,instances processes. Change hostname on server

2-Modify   hostnames with new hostname  in  <dmgrprofile>/config/../dmgrnode/serverindex.xml and virtualhost.xml

3- Modify parameter  in on <profileroot>/properties  both servers (dmgr and nodes)

4- Clean  under dmgrprofile and nodeprofiles temp,wstemp folders.

5-  Start dmgr.

6-Sync nodes with synNode command and start nodes.

For Node  Machines:

1- Stop nodes,instances processes. Change hostname on node servers

2-Modify   hostnames with new hostname  in  <dmgrprofile>/config/…/node/serverindex.xml

3- Modify parameter  in on <profileroot>/properties  both servers (dmgr and nodes)

4- Clean  under nodeprofiles temp,wstemp folders.

5-Sync nodes with synNode command and start nodes.

6-Star node

7- Download file at following link . Extract it into your /ConfigeEngine

8- run following script : ./ConfigEngine .sh localize-clone

9- Verify that the /ConfigEngine/properties/ has been updated with the new hostname.

Yorum (comment) (3)

If you have a ldap seach problem with user whose names contain non-ASCII character,such as Turkish or Cyrillic characters like this error:

[1/26/10 18:59:56:592 EET] 000000b6 WMM Trace Log 1 Attributes getAttributes(String name, String[] attrIds) The following exception was logged LDAP DN “cn=ipek sari,ou=xxx,o=xx” is not found.

This is caused during the authentication process, Webspher Portal binds with the DN of the user against the Domino LDAP server version Lotus Domino 8.0.x , using the DN converted to lower case. If the LDAP server is unable to resolve the lower case DN, then the bind fails and the user fails to authenticate.

We have fixed this problem with;

1.) Open the names.nsf in Notes Designer Client
2.) Locate the $LDAPRDNHier view
3.) Right click on the view and select “Design properties”
4.) On the third tab select “Unicode standard sorting” and close the design properties
5.) On the Domino server console run “updall -R -T $LDAPRDNHier names.nsf” to rebuild the view

I would also suggest restarting the Domino server after the change to ensure it is implemented.

Yorum (comment) (0)

If you want jsp files to reload automaticly you can change this value :
goto “was_profile_root/config/cells/cell_name/applications/wps.ear /deployments/wps/wps.war/WEB-INF/ibm-web-ext.xmi” folder. change “reloadingEnabled” to “true” .To active this setting you have to restart portal server.

Yorum (comment) (0)

File related commands

1) find text in the matching files and show the filename with the pattern. The below example shows the list of filenames and the location of the hostname in those files, which will be helpful when changing hostnames for your websphere installation.

find . -name ‘*.xml’ -print | xargs grep ‘hostName’ /dev/null

bash-2.05b# find /usr/IBM/WebSphere/AppServer/profiles/AppSrv01/config/ -name ‘server*.xml’ -print | xargs grep ‘hostName’ /dev/null | more
/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/portalserverCell01/nodes/portalserverNode01/serverindex.xml:<SERVERINDEX:ServerIndex xmi:version=”2.0″ xmlns:xmi=”” xmlns:serverindex=”
.0/serverindex.xmi” xmi:id=”ServerIndex_1″ hostName=”” endPointRefs=”NamedEndPoint_1130375480667 NamedE
ndPoint_1130375480668 NamedEndPoint_1130375480669 NamedEndPoint_1130375480670 NamedEndPoint_1130375480671 NamedEndPoint_113037548067

Yazının tamamını okuyun (

Yorum (comment) (0)

Network related Commands


a) dig (domain information groper) – is a flexible tool for interrogating DNS name servers.
b) nslookup – Queries a name server for a host or domain lookup.
c) host – DNS lookup uility.

The below example shows the information like CNAME , Aliases, ipaddres , etc about

a) dig
bash-2.05b# dig

; <<>> DiG 9.2.4 <<>>
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1088
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 7, ADDITIONAL: 0

Yazının tamamını okuyun (

Yorum (comment) (0)