Hide Forgot
Date of First Response: 2008-01-11 16:59:05 project_key: SOA Verify the SOA-P can be (auto-)discovered by JON Verify the EAP part is monitored/administrated by JON
Link: Added: This issue is incorporated by SOA-236
Successfully tested SOA-P beta1 with JON 1.4.33: autodiscovery monitoring/administrating of JBMessaging queues/topics (create new JMS destinations doesn't work, see JBNADM-2523 for more detailed description and workaround) start/stop AS deploy resources via GUI scheduling control actions monitoring/administrating child resources like slsb, sfsb, entity beans, mdb, jgroup channels, data sources, JCA connection pools, hibernate session factories instrumenting embedded tomcat monitoring webapps, response time measurements grouping and controling of 2 SOA-P instances
Please close again once you have assigned a Fix field.
Need to retest with CR2 as this build has the correct version string
Just a basic test: autodiscovery start/stop AS
run a smoke test (import, monitor, control) successfully against CR2