Şile Volume 1

Yazar: enes koc Kategori: Şile


Şile – Sahil Günlüğü
Yükleyen Kelebegin_Gunlugu. – İlginç seyahat videolarını izleyin ve yeni yerleri keşfedin.

Yorum (comment) (0)


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
com.ibm.ws.jsf.storeDynamicClientIds property must be set to
“true” in the web.xml file.

com.ibm.ws.jsf.storeDynamicClientIds true

Yorum (comment) (0)


Search folder in jar file example:
find folder -name ‘*.jar’ -o -name ‘*.war’ -o -name ‘*.ear’ -type f | xargs -i bash -c “java path -tvf {}| tr / . | grep searched data && echo {}”

find /opt/WebSphere60/PortalServer/ -name ‘*.jar’ -o -name ‘*.war’ -o -name ‘*.ear’ -type f | xargs -i bash -c “/opt/WebSphere60/AppServer/java/bin/jar -tvf {}| tr / . | grep EDataObjectHbtrImpl$EDataObjectExternalizable && echo {}”

Search a word in gzip files without extract example :
zcat compressed folder | grep -i searched data | wc -l
zcat SystemOut.log.gz | grep -i Enes | wc -l

Yorum (comment) (0)


Konumlar önemlidir. Ama onu bilgelik ile kazanmamışsan saltanatın kısa sürer.
Ünvanlar kıymetlidir. Ama ilişkiler daha kıymetlidir.
İçeriksiz tarza kanmam. Ama tarzsız içeriği de dikkate almam.
Sistemlere yatırım yaptık. Ama sen onun arkasına saklan diye değil.
Cehennemin yolları iyi niyet taşlarıyla değil, sıradanlık taşlarıyla örülmüştür.
Kontrol zaruridir. Ama insanları değil, sadece durumları kontrol edebilirsin.
Mükemmel, iyinin düşmanı değildir. İyi, vasatın en sadık dostudur.
Kurallar düzenin şartıdır. Ama kurallara saplanıp kalmamak ilk kuralımızdır.
Otoriteni kabul ederim. Ama kalbimde buna hak kazanmışsan.
Tabii ki önemlisin. Ama özür dilerim, dünyanın merkezinde değilsin.
Mükemmel değilim ama özür dilemeyi bilirim.
İş tanımlarına karşı değilim. Ama kendini aşmaya niyetin varsa.
Hepimiz eşitiz. Ama bazılarımız daha eşit.
Katılmıyor musun? Bu meseleyi Tanrı’yla hallet, benimle değil.
Ben insaf ederim. Ama müşteri etmez.
Hoşgörüsüzlüğe bile hoşgörü gösterebilirim. Ama sen de gayret göster biraz.
Yeteneğine hayranım. Ama deneyimimi yabana atarsan kapılar kapanır.
Yükselmek güzel bir duygu. Ama yücelmek çok daha müthiş bir duygu.
Anlaşılmak mı istiyorsun? O zaman önce anlamaya çalış.
Stratejistler önemlidir. Ama kreatifler daha önemlidir. Üzgünüm.
Evet, ortam kaotik. Ama köşe kapmaca oynamaktan daha keyifli değil mi?
Bana sorun da getirebilirsin, çözüm de. Ama fikir getirirsen berhudar olurum.
Ödüllere inanırım. Ama çıtayı indiren değil, yükselten ödüllere değer veririm.
Yanlış biliyorsun. Patron seni yönetmez, sen patronunu yönetirsin.
Kediler de eğitilir. Ama biraz sabır lütfen.
Kapris çekerim. Ama sadece buna değiyorsan.
Eleştiriye açığım. Hele özeleştiri yapmayı bilen birinden gelirse.
Rasyonel kararlar verebiliriz. Duyguları işin içine karıştırdığımız sürece.
Yanlış benzetme. Bu bir maraton değil. Maratonların finiş çizgisi vardır.

Yorum (comment) (1)


Julio Iglesias ‘ın meşhur Gozar la Vida’sı ile Brussels-Brugge-Paris-Luxembourg-Koln-Amsterdam-Volendam-Lahey-Delft-Rotterdam dongusunun görüntüleri. (Görüntüleri metacafe ye yüklemiştir. Fakat erişim engeli olduğundan haberim yoktu.Bu yasaklar ülkesinde video upload edecek site bulmakda güç. Neyseki vimeo hala açık.)

My Belelux tour from enes koc on Vimeo.

Yorum (comment) (1)


Again home

Yazar: enes koc Kategori: Genel

Home-Brussels-Brugge-Paris-Luxembourg-Koln-Amsterdam-Volendam-Lahey-Delft-Rotterdam-Home.This is my last week circle.I’m really so tired.If you want any information about this cities please just type me.

Yorum (comment) (1)


An excerpt from Portal Wiki Site about Site Management:
Site Management features provided by WebSphere Portal v6.1 make managing multiple
portal deployments easier. Portal administrators can use Site Management and the
Resource Manager portlet to develop and test a portal page on a test server, then copy the
page to a target server for review and later promotion to a live page. Once you publish the
page to a target server where only a selected group of users can preview and do additional
test before promoting the page to all users and groups with the appropriate access rights.
After the page is modified , republished and re-promoted, the previous promoted page
becomes a version page. The demote function makes the page no longer visible in the
target server if a rollback is needed.
The following example illustrates how to use Site Management to perform a portal
transfer.
Enabling remote access to your servers
The portal site management publish feature requires at least two portal systems: a source
system, where you create new pages that you need to publish, and a target system, where
you make the new pages visible to portal users. You can also use one server with two or
more virtual portals for your source and target systems. The Resource Manager portlet
can display the contents of the systems. By default, the portal server is pre-configured to
allow remote access.
If you have a portal cluster, you need to run the enable-http-basic-auth-taisitemgmt
task before you start managing your site. A WebSphere Application Server
Trust Association Interceptor (TAI) is used to authorize access to the servers.
Note: Individual virtual portals on a single portal server do not require the enablehttp-
basic-auth-tai-sitemgmt task to be run more than once.
In this River Bend project, the development server is a standalone portal server, both
staging and production environments are vertical portal clusters with two portal instances
installed on the same physical Windows 2003 server. In order to manage the sites, the
task enable-http-basic-auth-tai-sitemgmt needs to be run on the staging
and production servers for each portal instance, details of running this task are described

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

Yorum (comment) (2)


Since Websphere Portal 6.1 we can use friendly URL on my pages. Page Properties portlet provides an additional field which specifies the URL suffix which will be appended to portal URL:

The service is disabled by default. To enable it:

  • log in to WebSphere Application Server console
  • navigate to Resources -> Resource Environment -> Resource Environment Providers
  • click WP ConfigService on the  providers list
  • click Custom properties under Additional properties section
  • add new property called friendly.enabled and set it to true
  • save changes
  • restart server
  • You can confirm that my friendly URL works when you navigate to the following URL:

    http://myserver:10040/wps/myportal/mypage

    Another confusing thing related to friendly URLs is that a path must reflect pages hierarchy. The above example works only when My Page is placed below Content Root. In order to place the page under Home, a friendly URL for Home label must be also created (for example: home) and then the path to My Page would be:

    http://myserver:10040/wps/myportal/home/mypage

    Note: I guess there is a bug . If you use friendly URL label name’s first chracter with uppercase like “Home”   for Home page  You can getting endless loop error when calling page.

    Yorum (comment) (1)


    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 run.sh file in IHS/bind directory and add this command:
    /usr/bin/sudo /opt/IBMIHS61/bin/apachectl “$@”

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

    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/run.sh
    stopCommand : ${WEB_INSTALL_ROOT}/bin/run.sh

    Yorum (comment) (0)


    1- Change owner for Websphere Application root directory with spcified user and group.
    chown -R was1:wasgroup /opt/WebSphere/AppServer

    2- Change file permissions as the root user
    chmod -R g+wr AppServer
    Note: When you use the chown command to change the owner of JSPs that are already complied and reside in the temp directory, the CPU does not have to continuously recompile these JSP. If you do not issue this command, you should delete the application temp directory to lower CPU usage.

    3- Specify user and group values for the Runas User and Runas Group setiings for a server
    Go Process execution page of the administrative console

    You must define properties in the following table. Click Servers > Application Servers > server1 > Process Definition > Process Execution and change all of the following values:Property Value
    Run As User wasadm
    Run As Group wasgrp

    Yorum (comment) (0)