How to configure hawk with as_session

How to configure hawk with as_session

book

Article ID: KB0082055

calendar_today

Updated On:

Products Versions
TIBCO Hawk -
Not Applicable -

Description

Description:
The article described the steps about how to configure hawkagent/hma/hawk console application with as_session. 

Issue/Introduction

How to configure hawk with as_session

Environment

Product: TIBCO HawkVersion:OS: All Supported Operating Systems--------------------

Resolution

1. Edit cfg file, comment rv_session and ems_transport. Uncomment as_session, You can use the default value for all of them "-as_session "" tibpgm://8989/"
2. While using as_session as the transport, hawkagent behave as as-server, hawkhma/the other hawk micro-agent/hawk console application behave as as-client.
3. Hawkagent is seeder, hawkhma/the other hawk micro-agent/hawk console application is leech.

The roles base on hawk code implementation. It is hard-coded by design. It can not be customize.

4. Hawk domain name do become the metaspace name. 

5. While you using the as_session start hawk application, the first started node would be manager, the following nodes would be member.

You may use as-admin to view that:

 

java -jar <absolutely_path>/as-admin.jar

as-admin>connect 'metaspace_name' discovery 'tibpgm://8989/'

as-admin>show spaces

as-admin>show space 'space_name'

You will see the details of all members.

6. Discovery url format:

  tcp://interface:port;interface2:port2;interface3:port3

  tibpgm://dport/interface;multicast/key1=value1;key2=value2;key3=value3

  tibrv://service/network/daemon

7. ActiveSpace  jar version should be exactly the same among the as members.Eg:

[hawkas@docker4infra bin]$ ./tibhawkagent

Mon Jun 01 15:19:13 CST 2015 Starting Hawk Agent...

Config file used by Agent : /home/hawkas/TIBCO_HOME/tibco/cfgmgmt/hawk/bin/hawkagent.cfg

[2015-06-01T15:19:16][15537][139790700295968][INFO][transport] ip_address=192.168.69.26 port=50002

[2015-06-01T15:19:17][15537][139790472271616][INFO][default.$gmp] -------------------------------

[2015-06-01T15:19:17][15537][139790472271616][INFO][default.$gmp] configuring new manager

[2015-06-01T15:19:17][15537][139790472271616][INFO][default.$gmp] new manager = c0a8451a-c350 (c0a8451a-c350-555e40a7-7f, 192.168.69.26:50000)

[2015-06-01T15:19:17][15537][139790472271616][INFO][default.$gmp] self node = c0a8451a-c352 (c0a8451a-c352-556c0774-300, 192.168.69.26:50002)

[2015-06-01T15:19:17][15537][139790472271616][INFO][default.$gmp] -------------------------------

[2015-06-01T15:19:17][15537][139790358849280][INFO][default.$members] member joined: 192.168.69.26:50000

[2015-06-01T15:19:17][15537][139790358849280][INFO][default.$members] member joined: 192.168.69.26:50001

[2015-06-01T15:19:17][15537][139790358849280][INFO][default.$members] member joined: 192.168.69.26:50003

[2015-06-01T15:19:17][15537][139790358849280][INFO][default.$members] member joined: 192.168.69.26:50004

[2015-06-01T15:19:17][15537][139790358849280][INFO][default.$members] member joined: 192.168.69.51:50000

[2015-06-01T15:19:17][15537][139790358849280][INFO][default.$members] member joined: 192.168.69.26:50002

[2015-06-01T15:19:17][15537][139790700295968][INFO][default.metaspace] Connected metaspace name=[default], listen=[tcp://192.168.69.26:50002], discovery=[tibpgm://8989/], member name=[c0a8451a-c352] version=2.1.2.107

Additional Information

http://10.106.148.71/sr/005/584168.htm