Friday, April 25, 2014

Use SAR to Monitor CPU Utilization

SAR (System Activity Reporting) is a common *nix utiliy that can be used to track cpu utilization, memory utilization etc.
 
A common scenario is the need capture cpu statistics during some kind of load testing and then later report on those.  To capture cpu statistics with SAR you can do the following:
 
  1. Logon to the host in question and make sure that sar is installed (run sar from the command line).
  2. To capture statistics every 2 seconds to a file called "mystats.sar" in your home directory, you would execute the following command: sar -o ~/mystats.sar -u 2 0 >/dev/null 2>&1.  Note that this will keep gathering statistics until you kill it using ctrl-c.
  3. To run that same command in the background add an "&" to the end.  You can also "nohup" it so that it keeps running after you logoff - but don't forget to turn it off.  If you background it, then you can find it by typing in "jobs" and it will show you all processes you have put in the background.  You can then kill it with "kill %<jobnum>".  Or you can put it in the foreground "fg %<jobnum>" and then kill it with ctrl-c.
  4. Now you have a file that contains sar statistics, you can retrieve the contents of the file using something like: sar -f ~/mystats.sar.  If you want to just take a timeslice from the file, then you can use the -s hh:mm:ss and -e hh:mm:ss parameters.
See the sar manual page (man sar) for more details.
On Production, SAR are being generated under this directory: /var/log/sa/

Wednesday, April 16, 2014

No edit privilege on a newly imported toolkit

Problem Statement

No edit privilege on a newly imported toolkit. Even though I have listed myself to have read-write permission, I'm not able to edit any artifact in the toolkit. The toolkit was imported recently into the process-center.

Solution

For any toolkit imported into the a process-center, from another process-center, the option "Allow users to update toolkit" is disabled by default. This check-box can be found in the "Manage" tab for the toolkit. This option is only available to the "Admins" of the toolkit. Check that option and restart your process-designer, you will be able to modify toolkit artifacts now.

Tuesday, April 8, 2014

Configuring Apache Load balancer URL

Problem Statement :

You have a clustered environment with 2 or more nodes or you have an Apache layer between the user and your application servers. The users access your application interfaces through the Apache layer, which is responsible for load-balancing, SSO, etc. But when you load the portal or admin console you find that some resources are directly referenced from the application server nodes instead of going through Apache.

Resolution :

Put the following into a file (101CustomLoadBalancer.xml) and place it at

/app/websphere/<DMGR_PROFILE>/config/cells/<CELL>/nodes/<NODE>/servers/<APP_TARGET_JVM>/process-<center/server>/config

<properties>
    <authoring-environment merge="mergeChildren">
        <images-prefix merge="replace">https://<APACHE URL>/teamworks</images-prefix>
        <portal-prefix merge="replace">https://<APACHE URL>/portal</portal-prefix>
        <servlet-prefix merge="replace">https://<APACHE URL>/teamworks</servlet-prefix>
        <webapi-prefix merge="replace">https://<APACHE URL>/webapi</webapi-prefix>
        <repository-prefix merge="replace">https://<APACHE URL>/ProcessCenter</repository-prefix>
        <process-help-wiki-url-view merge="replace">https://<APACHE URL>/processhelp/en/%TITLE%?teamworksTitle=%TEAMWORKS_TITLE%</process-help-wiki-url-view>
        <process-help-wiki-url-edit merge="replace">https://<APACHE URL>/processhelp/en/Special:Edit?topic=%TITLE%&amp;teamworksTitle=%TEAMWORKS_TITLE%</process-help-wiki-url-edit>
    </authoring-environment>
    <common merge="mergeChildren">
        <portal-prefix merge="replace">https://<APACHE URL>/portal</portal-prefix>
        <process-admin-prefix merge="replace">https://<APACHE URL>/ProcessAdmin</process-admin-prefix>
        <!-- Disable for Process Center -->
        <teamworks-webapp-prefix merge="replace">https://<APACHE URL>/teamworks</teamworks-webapp-prefix>
        <coach-designer-xsl-url merge="replace">https://<APACHE URL>/teamworks/coachdesigner/transform/CoachDesigner.xsl</coach-designer-xsl-url>
       
        <webservices merge="mergeChildren">
            <base-url merge="replace">https://<APACHE URL>/teamworks/webservices</base-url>
        </webservices>
        <xml-serialization merge="mergeChildren">
            <default-namespace-uri merge="replace">https://<APACHE URL>/schema/</default-namespace-uri>
        </xml-serialization>
    </common>
    <server merge="mergeChildren">
        <repository-server-url merge="replace">https://<APACHE URL>/ProcessCenter</repository-server-url>
        <email merge="mergeChildren">
            <mail-template merge="mergeChildren">
                <client-link merge="replace">https://<APACHE URL>/teamworks</client-link>
            </mail-template>
        </email>
    </server>
</properties>