Mevlana der ki:

Yazar: enes koc Kategori: Şiir

Sonsuz bir karanlığın içinden doğdum.
Işığı gördüm, korktum.
Ağladım.

Zamanla ışıkta yaşamayı öğrendim.
Karanlığı gördüm, korktum.
Gün geldi sonsuz karanlığa uğurladım sevdiklerimi…
Ağladım.

Yaşamayı öğrendim.
Doğumun, hayatın bitmeye başladığı an olduğunu;
aradaki bölümün, ölümden çalınan zamanlar olduğunu
öğrendim.

Zamanı öğrendim.
Yarıştım onunla…
Zamanla yarışılmayacağını,
zamanla barışılacağını, zamanla öğrendim…

İnsanı öğrendim.
Sonra insanların içinde iyiler ve kötüler olduğunu…
Sonra da her insanin içinde
iyilik ve kötülük bulunduğunu öğrendim.
Yazının tamamını okuyun (read more) »

Yorum (comment) (0)


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 com.ibm.ws.wmm.ldap.LdapRepositoryImpl Attributes getAttributes(String name, String[] attrIds) The following exception was logged com.ibm.websphere.wmm.exception.MemberNotFoundException: 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 to view all the Http requests that your application server is handling then you can enable the NCSA log. This might be useful in case of clustered environment to see which server is actually handling particular request or you might be interested in looking at who is accessing the server at what time, load on the server during particular time
Yazının tamamını okuyun (read more) »

Yorum (comment) (0)


Custom Cache Instance

If you want to use say 3-4 different caches in your application or you want to better track your cache instance then you can create your own instance of dynamic cache and configure and use it.

You can create custom cache instance either using administrative console or declaratively using your application.

Administrative Console

YOu can create and configure new cache instance using WAS Administrative console. Inside the Administrative Console go to Resources -> Cache Instance -> Object Cache Instance and create a new cache instance like this

Using cacheinstance.properties

Other method of creating cache is that you can create cacheinstance.properties file like this in your WEB-INF/classes forlder. If your using RAD you can create in root of your source folder, so that it gets copied to WEB-INF/classes folder.


cache.instance.0=/wpcertification/cache/customCache
cache.instance.0.cacheSize=1000
cache.instance.0.enableDiskOffload=true
cache.instance.0.diskOffloadLocation=c:/temp/diskOffload
cache.instance.0.flushToDiskOnStop=true
cache.instance.0.useListenerContext=true
cache.instance.0.enableCacheReplication=false
cache.instance.0.disableDependencyId=false
cache.instance.0.htodCleanupFrequency=60

Inside your code you can access the distributed Map object using this code

distributedMap= (DistributedMap)context.lookup("/wpcertification/cache/customCache");

You can download the CustomDynaCache portlet and install it on your server. After installing it try accessing it couple of times and then check it in the CacheMonitor

Yorum (comment) (1)


How to enable lazy load of portlet applications during Portal startup
Abstract
This technote describes how to enable and disable the startup of administrative and sample portlets during Portal startup to speed up the server start and reduce the Portal memory footprint.
Content
WebSphere Portal 6.1.0.2 introduces a new configuration task to enable and disable the lazy load of administrative and sample Portlet Applications. When enabled the applications are not loaded during startup of the server but when accessed for the first time

Read IBM TechNote

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)


Certificate Management:

SSL Certificates expiration monitoring for WebSphere or any java based application server using java keystore
If you are a WebSphere Administrator or any Application Server (WebLogic, Tomcat) administrator you might already know that managing the ssl certificates in a large complex environments becomes hectic and troublesome because of the different expiration dates of the certificates that websphere uses and also the ssl certificates of the external systems (like SAP , Siebel) that websphere applicaton server might connect to using a secure connection, multiple administrators in an organization renewing it and not keeping tracking of the expiration dates. The problem is , SSL certificate might expire resulting in servers will not initialize and your running servers will stop operating, becomes unresposive if not properly renewed on time. Hence this article will explain how you can monitor the expiration of the ssl certificates using a simple command and proactively monitor the expiration dates, setup your calendar and renew it on time to prevent any downtimes.
Yazının tamamını okuyun (read more) »

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=”http://www.omg.org/XMI” xmlns:serverindex=”http://www.ibm.com/websphere/appserver/schemas/5
.0/serverindex.xmi” xmi:id=”ServerIndex_1″ hostName=”portalserver.example.com” endPointRefs=”NamedEndPoint_1130375480667 NamedE
ndPoint_1130375480668 NamedEndPoint_1130375480669 NamedEndPoint_1130375480670 NamedEndPoint_1130375480671 NamedEndPoint_113037548067

Yazının tamamını okuyun (read more) »

Yorum (comment) (0)


Network related Commands
 

 

1)
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 www.google.com

a) dig
bash-2.05b# dig www.google.com

; <<>> DiG 9.2.4 <<>> www.google.com
;; 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 (read more) »

Yorum (comment) (0)


Disk Usage related Commands to monitor Disk space

1)Disk Usage on all mounts
df -h -T

Filesystem Type Size Used Avail Use% Mounted on
/dev/sda1 ext3 2.9G 785M 2.0G 29% /
/dev/sda7 ext3 57G 9.3G 45G 18% /cust
/dev/sda6 ext3 2.0G 82M 1.8G 5% /lc
none tmpfs 5.7G 0 5.7G 0% /dev/shm
/dev/sda5 ext3 2.0G 33M 1.8G 2% /tmp
/dev/sda3 ext3 2.0G 64M 1.8G 4% /var

2)prints just one line with the total size of the directory, the below example show the size of the /usr/IBM/Websphere WebSphere Portal Server directory.
du -ch | grep total

bash-2.05b# du -ch | grep total
6.3G total

Yorum (comment) (0)