Khaliq's Knoweldge Zone: 2010

How to increase the passcode lock time from 15 minutes to 1 or 4 hours:
a. Jailbreak phone.
b. SSH into the phone as [ root ]
c. Edit the following file [ "/var/Managed Preferences/mobile/com.apple.springboard.plist" ] Just double click on the file to edit.
d. Make the following change, setting of the key "maxGracePeriod" integer from 15 to 480. Also change the "maxInactivity" integer also from 15 to 480. Even though 480 is 4 hours, when you go back to preferences, your passcode lock will have (additionally) the 1 hour and 4 hours options.
<key>PolicyInformation</key>
<dict>
<key>SBAutoLockTime</key>
<integer>900</integer>
<key>SBDeviceLockGracePeriod</key>
<integer>900</integer>
<key>forcePIN</key>
<string>0</string>
<key>manualFetchingWhenRoaming</key>
<string>0</string>
<key>maxGracePeriod</key>
<integer>480</integer>
<key>maxInactivity</key>
<integer>480</integer>
</dict>
Make sure and "save" the changes. and exit from the SSH program.
e. Now go into passcode lock "Require Passcode" to 1 or 4 hours.

Installing MRG Complete Suit Using the following command

yum groupinstall "MRG Messaging"
yum groupinstall "MRG Grid"
yum groupinstall "MRG Realtime"
yum groupinstall "MRG Management"
or in one go
yum groupinstall "MRG Grid/Realtime/Messaging/MRG Management"

Checking If Installation has happened properly

Checking if MRG Messaging is installed properly you should see a list of files if not then installation has not happened.
rpm -ql rhm

Checking if MRG Grid is installed properly you should see a list of files if not then installation has not happened.
rpm -ql cumin

Checking if MRG Realtime is installed properly you should see a list of files if not then installation has not happened.
rpm -ql cumin

Checking if MRG Management is installed properly you should see a list of files if not then installation has not happened.
rpm -ql cumin

Starting the Messaging Broker
$ /usr/sbin/qpidd -t
****Command Output****
[date] [time] info Loaded Module: libbdbstore.so.0
[date] [time] info Locked data directory: /var/lib/qpidd
[date] [time] info Management enabled
[date] [time] info Listening on port 5672

By default, the broker is installed in /usr/sbin/. If this is not on your path, you will need to type the whole path to start the broker:
$ /usr/sbin/qpidd -t
****Command Output****
[date] [time] info Loaded Module: libbdbstore.so.0
[date] [time] info Locked data directory: /var/lib/qpidd
[date] [time] info Management enabled
[date] [time] info Listening on port 5672
The -t or --trace option enables debug tracing, printing messages to the terminal.

To stop the broker, type CTRL+C at the shell prompt
****Command Output****
[date] [time] notice Shutting down.
[date] [time] info Unlocked data directory: /var/lib/qpidd
For production use, MRG Messaging is usually run as a service. To start the broker as a service, run the following command as the root user:
# service qpidd start
****Command Output****
Starting qpidd daemon:     [ OK ]
You can check on the status of the service using the service status command and stop the broker with service stop.
# service qpidd status
****Command Output****
qpidd (pid PID) is running...

# service qpidd stop
****Command Output****
Stopping qpidd daemon:     [ OK ]

Starting Messaging Grid

It is advised that you review the local configuration file before starting MRG Grid. By default, this file is located at ~condor/condor_config.local. However, some installations might put this file in a different location.Check the exact location of the local configuration file by running the following command from the shell prompt:
****Command Output****
$ condor_config_val LOCAL_CONFIG_FILE
/var/lib/condor/condor_config.local

The default configuration sets up a Personal Condor. This is a specific configuration suited for individual users who do not have their own pool of machines. To find out more about Personal Condor, see the Condor Manual.

To allow other machines to join your pool additional configuration must be done. Specifically, you will need to customize the HOSTALLOW_WRITE option. Open the ~condor/condor_config.local file in your preferred text editor and locate the section titled Host/IP Access Levels.

The value for this option should be set to allow machines to join your pool and submit jobs. Any machine that you give write access to using the HOSTALLOW_WRITE option should also be given read access using the HOSTALLOW_READ option.
HOSTALLOW_WRITE = *.your.domain.com

MRG Grid is usually run as a service. To start MRG Grid run the following command:
# service condor start

Starting Messaging Management Console

Before you run the MRG Management Console for the first time, you will need to configure the postgresql database server and prepare the Cumin database.
The MRG Management Console requires the condor-qmf-plugins package so that it can be used with MRG Grid. If it will not be used with MRG Grid, this step can be skipped. The condor-qmf-plugins package can be installed using the yum command:
# yum install condor-qmf-plugins
The configuration file for the postgresql database is in /var/lib/pgsql/data/pg_hba.conf. You will need to check whether or not this file exists on your system. If it does not exist, run the following command as root to create it:
# service postgresql start
Starting postgresql service:              [ OK ]

# service postgresql stop
Stopping postgresql service:              [ OK ]
Once you have ensured that the /var/lib/pgsql/data/pg_hba.conf file exists, change to the postgres user:
$ su - postgres
Open the file in your preferred text editor, and locate the configuration settings at the end of the file. You will need to add the following line before the other similar lines:
host    cumin       cumin       127.0.0.1/32          trust

Your configuration settings should now look like this:
...[output truncated]...
# TYPE DATABASE    USER        CIDR-ADDRESS          METHOD

host    cumin       cumin       127.0.0.1/32          trust

# "local" is for Unix domain socket connections only
local   all         all                               reject

# IPv4 local connections:
host    all         all         127.0.0.1/32          reject

# IPv6 local connections:
host    all         all         ::1/128               reject
Ensure you are running as the root user, and restart the postgresql service to pick up the configuration changes:
# service postgresql status
postmaster is stopped

# service postgresql start
Starting postgresql service:                  [ OK ]
Initialize the Cumin database and schema:
# cumin-database-init
Executed 102 statements from file '/var/lib/cumin/sql/schema.sql'
Executed 6 statements from file '/var/lib/cumin/sql/indexes.sql'

A username and password is required to log on to the MRG Management Console. Run the cumin-admin add-user command as the root user to add a new user:
# cumin-admin add-user testuser
Set password: *****
Retype password: *****
User 'testuser' is added

Install Sesame
Sesame is a messaging package that is used to assist the MRG Management Console connect to MRG Grid.
Sesame is part of the MRG Messaging yum package group and should be automatically installed. You can check if it is installed on your system by running the following command:
$ rpm -q sesame
To install the Sesame package individually on Red Hat Enterprise Linux 5 use yum:
# yum install sesame
On Red Hat Enterprise Linux 4 use up2date:
# up2date sesame
In order to send system information, Sesame needs to be configured. Open the /etc/sesame/sesame.conf in your preferred text editor and locate the host parameter. Adjust the value of this parameter to the address of the broker to send QMF data to:
host=example.com
You can also adjust the port parameter, although the default settings should be adequate for nmost configurations.
If authentication is enabled on the broker, the uid and pwd parameters will also need to be adjusted accordingly.
Enable Sesame for the default run levels using chkconfig:
$ chkconfig sesame on
Start the Sesame service:
$ service sesame start
o test that Sesame is connected and publishing system information, use qpid-tool to connect to your broker and query for objects of type sysimage:
$ qpid-tool example.com
Management Tool for QPID
qpid: list
Management Object Types:
ObjectType                  Active Deleted
=============================================
com.redhat.sesame:sysimage 1       0
qpid: list sysimage
Objects of type com.redhat.sesame:sysimage
ID   Created   Destroyed Index
================================================================
101 16:00:13 -          40fda910-dade-40b3-9ff0-df5e787b3339
qpid:

Finally Starting the MRG Management Console

The MRG Management Console is a web-based tool. You can use any internet browser to access the tool, with or without an internet connection.
By default, the web console is bound to localhost, which allows only local connections to be made.If you just want to test MRG on local system you dont have to proceed any further just access the console at http://localhost:45672/. To make the MRG Management Console accessible from other hosts on the network, add the IP address of the host to the configuration file. You can do this by editing the /etc/cumin/cumin.conf file directly, or by using a command line option.
To edit the configuration file directly, open /etc/cumin/cumin.conf with your preferred text editor and add the following line with the host IP address:
addr: 192.168.0.20
To set the host IP address using a command line option, run the following command as the cumin user:
# su cumin

$ cumin --addr 192.168.0.20
For security over a network Secure Socket Layer (SSL) support can be enabled, either by editing the /etc/cumin/cumin.conf file directly, or by using a command line option.
To edit the configuration file directly, open /etc/cumin/cumin.conf with your preferred text editor and add the following line:
ssl: yes
To enable SSL encryption using a command line option, run the following command as the cumin user:
# su cumin

$ cumin --ssl yes
By default, the MRG Management Console is installed with a self-signed certificate. This is useful for testing a deployment, but it is not secure. You can install a new certificate and key and save them at /etc/cumin/cumin.crt and /etc/cumin/cumin.key.
When Cumin is restarted with the --ssl option, it will use the new certificate files.
You may also want to adjust how often the MRG Messaging broker sends updated information to the MRG Management Console. The default value is 10 seconds. If you are attempting to reduce the load on the broker or your network, you may want to increase the interval for fewer updates. If you want higher-resolution statistics, you may want to decrease the interval time to 5 seconds for more frequent updates. This can be done using the mgmt-pub-interval option with MRG Messaging.

# /usr/sbin/qpidd --mgmt-pub-interval 30
To start Cumin as a service, become the root user and use the service start command at/sbin/service

# /sbin/service cumin start
Starting Cumin daemon:               [ OK ]
You can also use the service commands to stop and restart Cumin, and check on the status:
# /sbin/service cumin status
cumin (pid PID) is running...

# /sbin/service cumin restart
Stopping Cumin daemon:               [ OK ]
Starting Cumin daemon:               [ OK ]

# /sbin/service cumin stop
Stopping Cumin daemon:               [ OK ]

To start Cumin as an unprivileged user, you will need to identify an unprivileged port for it to run on. You can do this with the --port option.
$ cumin --port 8080
Open your internet browser and navigate to the MRG Management Console page. If you started Cumin as root, use http://localhost:45672/.

In Next Blog I would describe usage of Management Console and Writing samples in java which sends messages to MRG