do not hard code cql port when initializing session
Add itests for AlertManager

As part of this commit, AlertManager #purgeAlerts method was also deleted as well as associated JPA named queries
AlertDefinitionManager was also fixed as it did not clean correctly the database after tests
[BZ 928971] - Set the correct classloader for the dynamically created
resource proxy classes.
Restore QUERY_NATIVE_TRUNCATE_SQL in Alert objects to preserve API
For Group Availability graph change WARN status to MIXED to better convey the meaning of the status.
[BZ 948080] Add AutoRefresh capability to graphs other than portlet graphs. Refactored Auto refresh capability to be more generic so that it could be used for more than just portlets.
make stack size passed to C* JVM configurable

Cassandra sets the JVM stack size to 180k in cassandra-env.sh which causes a
segfault on OpenJDK 6. This commit parameterizes the value passed to the -Xss
option in cassandra-env.sh and also makes it configurable in the metrics
simulator. There is now a stackSize property similar to the heapSize property.
It defaults to 180k.

This commit also updates the simulator to shut down the cluster when the
simulation run finishes.
set the stack size property of DeploymentOptions to effect stack size change
do not block indefinitely when checking cluster initialization
[BZ 924942] - Add portlet key to New charts on dashboard so the same resource, metric can be displayed on multiple dashboards.
Various updates to data migration runner to support simple command line invocation.

Updated the runner to use property layering:
1) Have a default set of properties
2) Override properties with values from a config file if provided
3) Override properties with command line arguments if provided

Added debug mode logs and made programmatic log4j configuration
Stop compiling projects in verbose mode
Fix NPE condition when autorefreshing a dashboard portlet graph before it has been configured (it has been added but not configured).
Fix issue with Resource Group Charts and refactor class hierarchy to make it flatter by eliminating AbstractMetricD3GraphView and ResourceGroupMetricD3GraphView.
Rename ResourceMetricD3Graph to MetricD3Graph to better reflect its new, more general, responsibilities.
Bug 846451, 949048, 949062
* Users with just Resource Group access cannot access alerts on their Groups
* Failure adding member to group with alert definition
*  Removing member from group with group alert definition removes all instances of the alert definition

Bug 846451
Change AlertDefinition.resourceGroup to AlertDefinition.group.  This brings
the name into the convention we use everywhere else, and that the GriteriaGenerator
expects for group FK relations.
- Update all relevant queries and AlertDefinitionCriteria
- For back compat, keep existing setter/getter and deprecate. Refactor all
  internal code to use the new setter/getter.

Bugs 949048, 949062
The handling of group member add/remove was berry berry broken. Various changes:
- Prevent the passing of Hibernate proxies across sessions when adding group
  alert defs to new members.
- Fix logic around removing group alert defs when removing group members.
- Add new filterGroupAlertDefinitionGroupId and filterReadOnly to AlertDefinitionCriteria
- Rename alertDefManager.createAlertDefinition to alertDefManager.createAlertDefinitionInNewTransaction to
  make it very clear what happens when you make this SLSB call. This is the
  convention.
- Add some more integration tests and fix up some stuff in AlertDefinitionManagerBeanTest
- We had two SLSB methods named removeGroupAlertDefinitions. Rename the proper one
  to removeGroupMemberAlertDefinitions and completely fix it as it did the
  wrong thing (likely due to the wrong name).
- Deprecate a portal-war only Local SLSB method.
Bug 949082
RFE: Allow alert ack/delete from recent alerts portlet and reporting view

Based on contribution from mark Addy (thanks!)
Change the "Delete" and "Acknowledge" alert buttons in the AlertHistoryView
to use "ResourceAuthorizedTableAction" rather than  "AbstractTableAction".
This generates additional calls to the backend to check permissions on
row selections (for non-admins). But, it should likely not be noticeable.

I made one small optimization in ResourceAuthorizedTableAction.  If
constructed with a requiredPermission=null it will ignore the authz check.
Using that we can make it perform like a standard table action. So, if in
fact the user is an admin or otherwise has write access then it should
act as before.  I took away the isEnabled() overrides in the original
patch in favor of this approach.  The overrides had a small issue because
they did not consider "enablement". Meaning the buttons would be active
(for admins) even if nothing was selected.
[BZ 949103] - On inventory detail summary metrics charts N+2 clicks of Set button stops firing.
Enable partial Oracle support. Add command line option documentation. And add better parsing for boolean options.
Add documentation and re-order methods to follow flow.