Las Vegas

Yazar: enes koc Kategori: Genel

Uzun bir aradan sonra yazdığım bir yazı olduğu için eğlenceli bir görsel ekleyeyim dedim.

İşle ilgili bir konferans dolayısıyla Las Vegas’taydım. Hastasıyız dedeeeee dedirten Hangover filminin soundtrack’ ı olan right round eşliğinde görüntüleri …  Yüklemesi biraz uzun sürebilir.

“What happens in Vegas stays in Vegas”

 

Yorum (comment) (0)


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

Solution:

Change the owner/group for the files to the user that is mentioned in the Process

execution properties of the WebSphere Application Server environment, for the subdirectory org.eclipse.osgi in the directory:

/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/configuration

In this example the owner/group should be “mqm”:

$ ls -l                                                                  
drwxr-xr-x    3 mqm      mqm       4096 Oct 20 00:18  org.eclipse.core.runtime
drwxr-xr-x    3 mqm      mqm        256 Oct 20 00:18  org.eclipse.osgi
drwxr-xr-x    3 mqm      mqm        256 Oct 20 00:18  org.eclipse.update

 

 

Yorum (comment) (0)


If you see below eroor while installing websphere 6 or 7 , this error is related to the “noexec” file system property sometimes.

There is insufficient free disk space on the system:
/opt/IBM/WebSphere/AppServer:
Required: 500 MB Available: 0 MB
/tmp:
Required: 100 MB Available: 0 MB

To resolve the problem:

change “/etc/fstab” :

before

 “none        /tmp      tmpfs      size=250m,rw,noexec,nosuid,noatime 0 0”

after

 “none        /tmp      tmpfs      size=250m,rw,nosuid,noatime 0 0”

run “mount -o remount /tmp” command to active the changes

Yorum (comment) (0)


Göz İzleme Methodu

Yazar: enes koc Kategori: Net

Daha önceki yazıda F-Pattern ile ilgiliydi. Userspots firması bu konuya baya eğilmişve şuan birçok firmadan referansa sahip.

Eğer göz izleme tekniği ile ilgiliyseniz  linkteki çalışmayı okuyun derim.

Yorum (comment) (0)


SALT Araştırma

Yazar: enes koc Kategori: Arzıweb

Projesinde yeraldığım SALT Araştırma açıldı.

SALT Galata ve Beyoğlu ‘nun fiziki ve dijital doküman arşivini biraraya getiren SALT Araştırma’nın web sitesine göz atmanızı tavsiye ederim.

 

Yorum (comment) (0)


Yandex

Yazar: enes koc Kategori: Arzıweb

Google ın tahtı sallanırmı bilinmez ama bir Rus firması olan  Yandex arama motoru birçok özelliğini Türk kullanıcılarına sundu. Özellikler Yandex haritalar bölümü  panoramik görüntüler ve trafik durumu gösterimi ile dikkat çekiyor.

 

 

Yorum (comment) (0)


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.

 

Yorum (comment) (0)


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) »

Yorum (comment) (0)


Afrika yardım

Yazar: enes koc Kategori: Genel

Birleşmiş milletler yetkilileri yıl sonuna kadar ihtiyaç duyulan yardım miktarının 500 milyon Dolar’a kadar çıkabileceğine dikkat çekiyor. Afrika boynuzu son 60 yılın en kurak dönemini yaşıyor. Uluslararası kuruluşlar özellikle 500 bin kadar çocuğun hayati tehlike altında olduğunu vurguluyor.

 

Yorum (comment) (0)


 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

Yorum (comment) (0)