This procedure describes how to create a custom heartbeat plug-in and add it to a default or custom heartbeat.
Before You Begin
If you are creating a custom heartbeat plug-in for a custom heartbeat, ensure that the custom heartbeat already exists.
You must be assigned the Geo Management rights profile to complete this procedure. For more information, see Securing Geographic Edition Software in Oracle Solaris Cluster 4.3 Geographic Edition Installation and Configuration Guide.
# geohb add-plugin custom-plug-in-name heartbeat-name [-p property-setting [-p…]]
Specifies the name of a default or custom heartbeat on the local cluster.
Caution - The presence of a custom heartbeat prevents the default heartbeat from being used during partnership creation. If you want to use the default heartbeat for your partnership, you must delete the custom heartbeat before you create the partnership with the geops create command.
Specifies the name of the custom heartbeat plug-in you are creating.
Specifies a heartbeat plug-in property that is assigned a value by using a name=statement pair. Multiple properties might be set at one time by using multiple statements.
Specify the path to your custom heartbeat plug-in by using the Query_cmd property.
For more information about the properties you can set, see Standard Geographic Edition Properties.
For more information about the geohb command, refer to the geohb(1M) man page.
# geoadm status
The following example adds the custom heartbeat plug-in, command1, and adds it to the default heartbeat, hb_cluster-paris~cluster-newyork.
# geohb add-plugin command1 hb_cluster-paris~cluster-newyork -p Query_cmd=/usr/bin/hbExample 11 Creating a Custom Heartbeat Plug-in For a Custom Heartbeat
This example creates the custom plug-in command1 and adds it to the paris-to-newyork custom heartbeat.
# geohb add-plugin command1 paris-to-newyork -p Query_cmd=/usr/bin/hb/