Bug 778409 (SOA-893)

Summary: Enterprise console - need to document that SOA-P users need to change rhq.agent.plugins.service-discovery.period-secs value for ESBs to be auto-discovered quickly
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Len DiMaggio <ldimaggi>
Component: Documentation, Monitoring and ManagementAssignee: tcunning
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.3 IR5   
Target Milestone: ---   
Target Release: 4.3 GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-893
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
rhq-jbossesb-plugin-2.1.0-SNAPSHOT.jar (Sept 23, supplied by Tom) http://jon01.qa.atl2.redhat.com:8042/dist/qa/jon-agent-2.1.0-6450.zip http://jon01.qa.atl2.redhat.com:8042/dist/qa/jon-server-2.1.0-6450.zip SOA-P 4.3 IR5
Last Closed: 2009-01-16 15:52:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Len DiMaggio 2008-09-29 19:18:53 UTC 
Affects: Documentation (Ref Guide, User Guide, etc.), Release Notes
Date of First Response: 2008-09-30 04:17:59
project_key: SOA

See:  https://jira.jboss.org/jira/browse/JBNADM-3511?focusedCommentId=12431636#action_12431636

To avoid having to perform a manual discovery of newly deployed ESB's, users should un-comment and modify the default value (24 hours) to a shorter time

In agent config file:


conf/agent-configuration.xml,

               <!--
               _______________________________________________________________
               rhq.agent.plugins.service-discovery.period-secs

               Defines how often a service discovery scan is run. This type
               of scan is used to find new services that have been added or
               removed from existing platforms and servers.
               The value is specified in seconds.
               -->
               <!--
               <entry key="rhq.agent.plugins.service-discovery.period-secs" value="86400"/>
               -->
Comment 2 Len DiMaggio 2008-09-29 19:21:50 UTC 
Link: Added: This issue depends JBNADM-3511
Comment 3 Len DiMaggio 2008-09-29 20:32:15 UTC 
Note:

This is only an issue for users who deploy ESB archives by manually copying the archive .esb files to the target server's /deploy directory.

Deploying an .esb archive file through the server > serverJBossSOA SOA_4.3.0.IR5 default (1099) > JBoss ESB Statistics  -> Inventory option results in the archive being discovered immediately.
Comment 4 Jaroslaw Kijanowski 2008-09-30 08:17:59 UTC 
Docs should also mention that: "The agent *won't* re-read this file by default. You need to specify the -c argument and point it at your config file."
Comment 5 Mark Little 2008-10-01 09:12:54 UTC 
Affects: Added: [Documentation (Ref Guide, User Guide, etc.), Release Notes]
Comment 6 Burr Sutter 2008-10-02 20:15:11 UTC 
24 hours?  And a special switch on the command line?

This is falling in the "too hard for average humans to use" category.

There should be some big warning some place on this topic.  It is common for a new ESB developer who deploy & undeploy dozens of .esb archives and services.  Also, how do I get the command line trick working when the agent should be running as a service in Windows? Something else that needs obvious docs.
Comment 7 Mark Little 2008-10-04 09:56:17 UTC 
Link: Added: This issue is related to SOA-899
Comment 8 tcunning 2008-10-10 05:59:04 UTC 
This has been documented in the ESB JON plugin document in SOA-P.
Comment 9 Len DiMaggio 2008-11-14 19:05:00 UTC 
Link: Added: This issue related JBNADM-3555
Comment 10 Len DiMaggio 2009-01-16 15:52:35 UTC 
Verified in 4.3 GA version of Admin Guide - section "6.3. JON for SOA"