more info:
The Cassatt Service Configuration Utility is used to configure
BEA WL domains for deployment within WAM for WebLogic. Those parameters,
including basic service information, dependencies on other services,
service and node monitored values, service monitors, and deployment
constraints, are used to add the service to Cassatt Active Response and to modify
the appropriate WebLogic files to support their management by
WAM for WebLogic.
Choices are listed in parentheses (a, b, c).
Default values are listed in brackets [y].
Cassatt Controller Authentication
Enter the Cassatt Active Response administrator login user name [admin]:
Enter the Cassatt Active Response administrator login password:
Basic Service Information
Enter a name for the service:
Enter a version for the service:
Enter the name of the service image []:
Enter the version of the service image []:
Using service type wl92
estimated golden size (kb):
Choice Filesystem mount point Free(kb)
------ ------------------------------ --------- --------------
1 /file_system_mount_point space_free [cassatt base]
Enter choice for filesystem (q for quit):
Enter the name of the WebLogic admin tier []:
admin OS type is Linux
Enter the absolute path to the WebLogic domain location on the admin tier [/home//bea/user_projects/domains/helloworldDomain]:
Would you like to use a pre-existing domain? [n]
Enter the absolute path to the WebLogic installation (e.g. WL_HOME) on the admin tier []:
Enter the absolute path to the Java installation (e.g. JAVAHOME) on the admin tieer []:
Enter the user name to run Weblogic admin server: [root]
Enter the name of the WebLogic managed server tier []: Managed Server Tier
server OS type is Linux
Enter the absolute path to the WebLogic installation (e.g. WL_HOME) on the manageed server tier Managed Server Tier [/home/bea/bea92/weblogic92]:
Enter the absolute path to the Java installation (e.g. JAVAHOME) on the managed sserver tier Managed Server Tier [/home/bea/bea92/jrockit90_150_04]:
Enter the user name to run Weblogic managed server: [root]
Enter the port used by the WebLogic node manager []:
Enter the WebLogic port to be used for this service []:
Do you want to update the IP addresses and port numbers in the configuration? [n]]
Enter the minimum number of nodes for this service [0]:
Enter the maximum number of nodes for this service [5]:
Enter the service shutdown mode (NORMAL, FORCE, KILL) [NORMAL]:
Service Dependencies
Service Dependencies allow relationships to be established between
services. If this service depends on another service to function
properly, specify that dependency here.
Do you want to specify any service dependencies for this service? [n]:
Monitoring
Do you have a Cassatt Active Response Passkey defined for this service? [n]
Enter a new Cassatt Active Response Passkey name:
Passkey weblogic already exists.
Do you have a Cassatt Active Response Passkey defined for this service? [n]
Enter the Cassatt Active Response Passkey :
Service Monitored Values
Service monitored values are performance measurements provided by
BEA WebLogic (e.g., PendingRequests) that you can use to build service
level agreements (SLAs). You must specify any service monitored values
you will use in an SLA for this service.
Default service monitored values:
WL92Jmx:ExecuteThreadIdleCount, WL92Jmx:ExecuteThreadTotalCount, WL92Jmx:StandbyThreadCount
Do you want to delete any of the service monitored values? [n]:
Do you want to add an additional service monitored value? [n]:
Node Monitored Values
Node monitored values are the SNMP-provided monitors for a node
(e.g. SNMP:Load15Average) that are used when creating Deployment Constraints.
Default node monitored values:
SNMP:Load5Average, SNMP:RealMemoryFree
Do you want to delete any of the node monitored values? [n]:
Do you want to add an additional node monitored value? [n]:
Enter the amount of time to wait for the service to start (seconds), after which WAM will begin monitoring the service [120]:
Enter the amount of time to wait for the service level to adjust after deploying a new service instance before determining whether to deploy an additional servicce instance (seconds) [240]:
Service Level Agreements
Service Level Agreements (SLAs) are limits at which increases in
utilization necessitate new instances of a service and decreases allow
termination of a service. SLAs use calculations based on service
monitored values.
WebLogic domain default SLAs:
Name: BusyThreadPercentage
Expression: (WL92Jmx:ExecuteThreadTotalCount-(WL92Jmx:ExecuteThreadIdleCount+WL92Jmx:StandbyThreadCount))*100/WL92Jmx:ExecuteThreadTotalCount
Minimum Threshold: 35.0
Maximum Threshold: 75.0
Collection Period (seconds): 120
Calculation frequency (seconds): 30
Do you want to change any of the service monitors? [n]:
Do you want to delete any of the service monitors? [n]:
Do you want to add an additional service monitor? [n]:
Deployment Constraints
Deployment constraints use Node Monitored Values to ensure that a node
has the available resources needed for a domain to operate on that node.
WebLogic domain default deployment constraints:
Name: LoadAverage
Expression: SNMP:Load5Average
Minimum Threshold: --
Maximum Threshold: 4.0
Collection Period (seconds): 120
Calculation frequency (seconds): 30
Name: FreeMemory
Expression: SNMP:RealMemoryFree/(1024*1024)
Minimum Threshold: 0.5
Maximum Threshold: --
Collection Period (seconds): 120
Calculation frequency (seconds): 30
Do you want to change any of the deployment constraints? [n]:
Do you want to delete any of the deployment constraints? [n]:
Do you want to add an additional deployment constraint? [n]:
The domain password file (boot.properties) already exists - do you want to replacce it? [n]
Attempting to start admin server and node managers