text:
|Publication number
|Publication type
|Application number
|Publication date
|Apr 24, 2007
|Filing date
|Sep 30, 2002
|Priority date
|Sep 30, 2002
|Fee status
|Also published as
|Publication number
|Stephen Pfeiffer, Julian Droescher, Christiane Kettschau
|Original Assignee
|Sap Aktiengesellschaft
|Export Citation
|BiBTeX, EndNote, RefMan
|Patent Citations (7), Non-Patent Citations (4), Referenced by (36), Classifications (25), Legal Events (4)
|External Links: USPTO, USPTO Assignment, Espacenet
This invention relates to monitoring the performance and status of various components of distributed client-server systems, and more particularly to transporting monitoring information and monitored data within an enterprise into a central monitoring system from sources that are not necessarily running on uniform computing platforms
In an enterprise computing environment, large, complex applications that are used in business-critical situations demand well-integrated monitoring and management for safe and successful operation. Monitoring helps avoid unplanned downtimes, which, for example, can produce costs in the six figures per hour. Tightly integrated monitoring systems for single computer family environments have been available for a number of years, for example in the SAP R/3 System. These monitoring systems are based on a suite of management and monitoring tools designed to monitor system resource usage and detect problems by generating statistics and reporting performance data from a variety of business applications running on common platforms.
Many enterprises increasingly find themselves using multiple distinct computing systems to run different aspects of their businesses. SAP for example created ALE (Application Link Enabling) and other technologies to allow multiple R/3 Systems to interact. Application-level links were created, for example, to allow R/3 Systems running the Sales or HR applications to update financials data across system boundaries.
In response to the vastly increased complexity of managing a landscape of systems that are in interaction with one another, centralized management systems were developed, such as SAP's Computing Center Management System (CCMS), that incorporate a uniform monitoring architecture that allows performance and error data to be collected from diverse applications in individual R/3 Systems and shared by means of R/3 Remote Function Calls (RFCs) between systems. Effectively, a customer could set up a central monitoring system, which saw the monitoring data from multiple R/3 Systems. However, because of its reliance on SAP's proprietary ABAP language and RFC, the view offered by the monitoring architecture was limited to traditional R/3 Systems and their application servers, together with the applications running in those systems.
With ever-greater diversity in the software landscape within single enterprises, as open component-oriented computing and Internet applications have been embraced, the pure one company proprietary approach to that environment has been relegated to the past. Given that some of these diverse components may participate in mission critical functions, it is just as important, however, from the IT department point of view, to monitor their performance as that of systems still running exclusively on the traditional core platforms like R/3.
Efforts to capture and transfer equivalent monitoring data from these diverse new sources so as to maintain the comprehensiveness of the existing centralized monitoring system have so far met with limited success. As at result, the scope of monitoring capable from within the centralized monitoring architecture has become over the years increasingly less adequate.
According to one aspect of the invention in general a data collection interface method for supplying monitoring data from monitored components of a distributed computing system to a central monitoring system involves composing a structured text document, preferably XML compliant, containing monitored data derived from the monitored component according to a uniform data type definition associated with a tree-structured monitoring architecture, and then making the contents of the document available electronically to a central monitoring system for using the monitored data to assess and report the condition of the monitored component. The documents are preferably made available to the monitoring system in one of two ways: posting an HTTP message containing the XML document to the monitoring system from the monitored component or filing and updating the document from time to time in a directory accessible to the monitoring system. In the latter case, the monitoring system preferably periodically polls the document in the file.
The XML document can be one of two kinds, long-form or short-form. The long-form format is used initially to completely specify a monitoring tree for the monitored component. The short-form XML document is sent or stored, depending on the transport mode, from time to time with current data corresponding to particular monitoring tree elements.
In one aspect the interface enables a central monitoring system to cope with input from standard components that form part of a consistent system, such as SAP's R/3 software, and also cope with input data from other nonstandard distributed components by translating the parsed XML documents into the same language used by the standard components.
The preferred XML interface provides this solution by making new use of two broadly established technologies:
The use of HTTP (as well as file transfer by means of a CCMS polling agent) allow in the CCMS XML Instrumentation Interface make it possible for a broad range of SAP non-R/3 components (and R/3 itself) and non-SAP components to communicate with the monitoring architecture without having to implement SAP RFC or incorporating any CCMS Monitoring Architecture Interfaces in programming.
Like HTTP, the capability of generating XML documents is anchored in the infrastructure of a broad range of SAP and non-SAP Web components (there are Java class libraries for XML and most J2EE servers offer native XML services), so the effort to produce an XML document that uses the CCMS XML protocol is not very high.
The XML Instrumentation Interface is made even more attractive by the specific XML protocol it uses, which has been optimized to allow instrumented components to use the full range of monitoring design and customizing options offered by the Monitoring Architecture, while at the same time reducing the complexity and volume of the XML documents that have to be produced.
The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the invention will be apparent from the description and drawings, and from the claims.
Like reference symbols in the various drawings indicate like elements.
The following description relates to a specific XML interface designed for SAP's CCMS Monitoring Architecture. First, as background, the pre-existing monitoring architecture within CCMS is shown in
The monitoring architecture shown in
Data suppliers report their data on one or more monitoring objects (as shown by the arrows in
There are five types of monitoring attributes:
1. Performance attribute Collects and averages reported performance values.
2. Status attribute Reports error message text and alert status.
3. Heartbeat attribute Checks that components of the SAP System are running. It generates an alert when no values have been reported on a monitoring attribute for a long time.
4. Log attribute Represents multiple messages. Effectively, a log attribute provides a means of displaying and evaluating log files and trace files within the monitoring architecture. Log attributes can capture an existing log mechanism, such as the SAP system log, or an application can use it to implement its own log.
5. Text attribute Enables a data supplier to report information that has no alert valuation. The text can be updated as required.
The monitoring architecture represents the individual monitoring objects of the SAP System in a hierarchical tree. Each object in the monitoring tree can be assigned a separate severity and criticality, which affect the alert that is displayed when a critical situation occurs. The tree reflects the current implementation of the SAP Systems that are being monitored, that is, the monitor adapts itself automatically to the current configuration of the systems that it is monitoring.
System administrators need to work with two different views in the monitoring architecture. These are:
1. Open alerts view (see
2. Current system status view (see
For each alert that occurs, the system administrator can call up special analysis methods for the corresponding monitoring attributes in both of these views.
Each view also has three levels of detail:
1. Overview Displays only those MTEs that are essential for monitoring the status of the system. Used for routine monitoring of the system during normal operation.
2. Analysis Adds MTEs that are intended for problem analysis or performance tuning to the display. Switch to this view if you need to examine a problem or want to analyze the system in detail.
3. Expert Adds internal SAP MTEs These MTEs are probably useful only if you are working with an SAP consultant, the SAP hotline, or the EarlyWatch service. Specialized knowledge may be required to interpret data at this level.
Alerts report and log warnings and problems in an SAP System and its environment. Alerts also direct system administrators' attention to critical situations and relieve them of constantly having to review the whole set of information. Alerts must always be processed by a system administrator, otherwise they remain in the alert browser.
The alert status of each node of a monitoring tree is clearly displayed and color coded according to criticality. A red alert indicates a problem or an error, a yellow alert indicates a warning. Green status, or the absence of alerts, indicates that there are currently no problems with the component being monitored.
The importance of a red or yellow alert is ranked according to its severity. Since the monitoring architecture propagates alerts up the monitoring tree, it is necessary to have an attribute for prioritizing alerts that have the same criticality (yellow or red). The severity serves as this attribute. A red alert with a higher severity than another red alert has higher priority. The red alert with the higher severity is therefore propagated up the monitoring tree as the most important alert.
Current System Status View
As shown in
The highlighting color of the line of the display associated with the monitoring object (red, yellow or green) indicates its status, as described above, and is independent of any open alerts that may exist for that MTE. For example, an MTE may be green because everything is currently alright, even though that MTE may have open alerts. Note that the display can be set to refresh automatically so the most current system status is always displayed.
Open Alerts View
As shown in
Monitoring properties are associated with each MTE and are inheritable by propagation through the tree.
Changing Monitors
The monitoring architecture can be easily changed to specify when alerts are triggered, or define and modify methods, their assignment, and their configuration.
Changes can be made to the properties, or settings, of a monitor from every monitoring tree element. Properties are either specific to a monitoring attribute, or they apply to a monitoring attribute group. This avoids having to maintain the same properties for many individual monitoring attributes and then saving them in the database. By editing and saving the relevant attribute group, the properties that apply to this group are assigned to the corresponding monitoring attributes.
Monitoring Properties Variants
The properties in an alert monitor represent a particular policy for managing a system or set of systems. With monitoring properties variants, the monitoring architecture allows for several of these policies to be maintained and distributed from a central maintenance system for decentralized monitoring.
A monitoring properties variant saves any or all of the available customizing settings. For example, to maintain different alert thresholds for response time in test systems and production systems, you could define separate monitoring properties variants for these settings. An alert monitor in a production system could run with the properties variant for production response times, whereas an alert monitor in a test system could run with the test system variant.
Monitoring properties variants can also be assigned to operation modes, with the advantage that properties variant no longer have to be activated manually, but will start when the corresponding operation mode starts.
Default Monitoring Properties Variant
The SAP-DEFAULT monitoring properties variant contains the default values for properties of MTEs in the monitoring architecture. This variant can be used as a template for creating your own properties variants for specific MTEs. The values in the SAP-DEFAULT variant cannot be changed or deleted, although you can copy them and then make changes to the copy. The advantage of the SAP-DEFAULT properties variant is that if you do not specify your own values for a specific MTE, then the SAP-DEFAULT values will apply. In this way, SAP-DEFAULT can be used as a fallback if you accidentally change the values provided by SAP in the SAP System, as well as a reference to the values that SAP recommends you should use.
There is also a properties variant hierarchy in the monitoring architecture. At the bottom of this hierarchy are values in SAP-DEFAULT. At the top of the hierarchy are MTE values that have been changed by customers and stored in an active properties variant. When you create a new monitoring properties variant, you can specify a "parent" properties variant, whose values are used if no value is specified for that MTE class in a customer-defined properties variant. If, in turn, this parent properties variant contains no values for that MTE class, the system uses SAP-DEFAULT values. System administrators can also assign monitoring attributes to methods.
A method can be a report, function module, SAP transaction, or URL that should be executed in response to an alert. For example, if you double-click on the MTE for abnormally terminated jobs, the monitoring architecture automatically starts the job-management transaction, pre-selecting the job reported in the MTE.
The monitor architecture provides the following method types:
Analysis method For exact analysis of error situations without leaving the monitoring architecture
Auto-reaction method For automatic response when an alert is triggered
Data Collection method For gathering information on the SAP System and its environment and registering it with the monitoring architecture.
Methods assigned to MTE classes can also be assigned to monitoring properties variants. This has the advantage that different methods can be executed in different monitoring properties variants, providing greater flexibility for monitoring SAP Systems.
Existing Interface between Data Suppliers and the monitoring architecture.
The existing interface for data suppliers in
XML Interface to the Monitoring Architecture
The new system permits completely independent components to interface in a functionally equivalent way with the monitoring architecture though the use of XML documents as an intermediate step.
Extensible Mark-up Language (XML) is a set of rules for structuring data in a document that can be exchanged over the World Wide Web (the "Web"). XML is a subset of an early mark-up language SGML used for technical documentation. XML's particular aim is to simplify SGML and make it compatible with the Web like HTML. But unlike HTML the tags and attributes within XML can all be user-defined as desired, not just for browsers but for any target program. XML is an open standard developed and maintained by the World Wide Web Consortium (W3C). A copy of the current specification for XML 1.0 can be found at http://www.w3.org/TR/REC-xml, which is a stable HTML document offered by WC3 specifically to be used as reference material or cited as a normative reference from another document. The XML standard is a set of strict rules that specify well-formed XML documents, involving tags, namespaces and attributes, etc. These variable parameters give meaning in the context of the target program to data contained within what is actually a text document, one that, as we shall see below, can be visualized with any word processing system. An XML document's purpose, however, is to be parsed and processed by an XML processor that tests the document for validity and sorts out and conditions the data in the XML document and, for example, feeds it to an associated application.
In order to interface non SAP or "foreign" components with the above-referenced centralized monitoring architecture, XML is exploited as an interface or data transport mechanism for the external data supplier, particularly those that would otherwise be unable to access the traditional standard interface for fully compliant SAP components.
In order to be a valid XML document, according to XML 1.0, the document must contain a document type declaration to define constraints on the logical structure and to support the use of predefined storage units. An XML document is valid if it has an associated document type declaration and if the document complies with the constraints expressed in it. The XML document type declaration contains or points to markup declarations that provide a grammar for a class of documents. This grammar is known as a document type definition, or DTD. The document type declaration can point to an external subset (a special kind of external entity) containing markup declarations, or can contain the markup declarations directly in an internal subset, or can do both. The DTD for a document consists of both subsets taken together. A markup declaration is an element type declaration, an attribute-list declaration, an entity declaration, or a notation declaration.
The system described below specifies the DTD and is fully compliant with the required syntax of XML 1.0 referred to above. Examples are given.
XML interface to the CCMS Monitoring Architecture
All of the instrumentation options provided by the existing ABAP interface to the monitoring architecture in function group SALI are made available through the XML interface:
The interface therefore allows complete flexibility in constructing monitoring trees—hierarchical structures representing monitoring data. The XML interface imposes no restrictions of its own on the type or complexity of information structure you can create with XML documents in the monitoring architecture
Processing of XML Documents: Overview
Monitoring data in XML format can be delivered to the CCMS in two ways:
The data can be delivered as HTTP POST requests addressed to the service /default_host/sap/bc/ccms/monitoring/ at, for example, the central monitoring system in a customer environment. The HTTP POST method allows the reporting component to push data into the monitoring architecture as required.
Alternatively, as shown in
The alternative file method is a polling method. It requires a data collection method in the monitoring architecture that specifies where XML data files are to be found. The monitoring architecture then periodically checks for files that meet the naming specification in the method definition, the file selection method specified (newest file or all files), and which have not yet been processed (files must be newer than the timestamp of the last run of the XML file processing method).
To allow for synchronization between file-writing and file-reading, the data collection method also looks for a file called
No matter which way the XML document arrives in the system, it is processed in the class
Because the SAP System does not support external DTDs, the CCMS monitoring DTD is automatically associated with the document and is used to verify the validity of the message. You can obtain the DTD either from the SAP Service Marketplace under alias monitoring or by sending a GET request with the query string
Errors are reported both in the monitoring architecture (Monitoring context
XML Long-Form and Short-Form
XML monitoring interface documents come in two categories, long-form and short-form, defined by respective DTDs. The short form takes full advantage of an existing monitoring tree with all of the MTEs already leafed out and attributed. This form is used primarily for transport of monitored data, e.g., performance and error data. The long-form permits the monitored component itself to set up its own tree. This is typically done in the beginning and once done, short-form XMLs can be employed to supply the data to the MTEs of the tree.
In the long-form XML document, you can create and report information into a monitoring tree with
The short form of the CCMS XML protocol reports information directly into a single, specific MTE that is identified by its full SAP name. This format reports an item of data into a specific MTE that already exists.
By default, XML MTEs are persistent across system starts in the SAP System that is doing the monitoring. Accordingly, as an XML data reporter, one would ideally create the complete monitoring tree that you need once using the long DTD format, and then subsequently report data into specific MTEs in this monitoring tree using the DTD short form.
The CCMS XML DTD
The DTD requires the following structural features:
The element that identifies the start and end of the document body is
The highest-level operative element is always
If the
The term
If the
Only the
The attributes and elements specific to each type of MTE, such as a context, a summary, or a performance attribute, are contained in a
You can allow most attributes (which generally represent meta-information on MTEs) of XML MTEs to default to standard values. Very few attributes are required.
The constants used as values in attributes are identical to those used in ABAP in the SALI instrumentation interface. You can find constants and their definitions in the ABAP includes RSALEXTI and RSALINTI. Numerical values are converted automatically from character representations of digits.
If you are reporting with XML files: Be sure that elements are not broken up by new lines. An element must be located on a single logical line in the file.
Preparing for the HTTP-Method
In order to pass XML documents to the monitoring architecture by way of HTTP POST requests, the configuration of the CCMS XML service must first be completed. A logon user must also be provided, such as the familiar CCMS service user
To complete the configuration of the service, the CCMS XML communication system must simply be activated. By way of example the following steps are required for the SAP r/e ccms monitoring system to accept XML documents from a data supplier:
After activation, HTTP POST requests should be sendable to the CCMS_XML service without an interactive logon.
Defining CCMS Methods for XML File Polling
While the HTTP POST method allows active reporting of data into the monitoring architecture, the file-polling method uses the passive data collection capabilities of the monitoring architecture. In file polling, the monitoring architecture runs a data collection method at start-up and periodically as required.
For each file specification (directory and file name specification), you must define a CCMS data collection method that specifies the files to collect and the agent to ask for them.
The sample method
Parameter Meaning DIRECTORY fully specified name of the directory in which XML files are to be found FILENAME naming convention for XML files to consider for reporting; this name may end with a wild- card character (*) AGENT— RFC destination of the agent which is to DESTINATION provide access to the XML files; the agent must have READ access to the pathname specified in DIRECTORY and to the files identified by FILENAME FILE_SELECTOR specifies which of the files in the directory are to be processed; possible values are: ALL: All XML documents that are newer than the last data supplier run time stamp and which meet the FILENAME naming convention are processed. NEWEST: Only the newest XML document that is newer than the Last data supplier run time stamp and which meets the FILENAME naming convention is processed. Other files are ignored. The file selector lets you distinguish between cases when perhaps multiple components are writing XML documents and several such files are of interest and cases in which one component repeatedly writes XML documents, of which only the newest is of interest.
An example of how a typical screen view would appear for entering the above data for file polling is shown in
Error Analysis and Self-Monitoring
The XML processing class reports on its activity in the
The XML Log
The XML log reports the start and stop of processing, whether originated through HTTP or file polling. All entries pertaining to a processing run carry a uniform time stamp, so that you can associate the entries that belong to a processing run even in a busy system.
A successful run reports only the start and stop of processing, and if file-polling, also the name(s) of any files that were processed or a message that no files were newer than the file-polling timestamp (Last data supplier run MTE).
To check the entries of the log, select the attribute XML Log in the alert monitoring tree and choose Display details:
Any errors that occur are also reported in the log. The three categories of error are:
1. XML parse errors (errors during a preliminary parsing without using the CCMS DTD). In this type of error, there are formal errors, such as unbalanced tags, in the XML document.
2. XML parse errors with DTD (errors during a final parsing using the CCMS DTD, which is generated internally in the SAP System and then associated with every incoming CCMS XML document). In this case, there has been some violation of the CCMS DTD, such as missing or unexpected elements or elements out of order.
3. SALI errors (errors that occurred during SALI function module calls to create or manipulate MTEs). These errors return the error string produced by the SALI call.
If you report XML documents by means of HTTP POST requests, then all error messages that appear in the log also are returned to your HTTP client as the HTTP response. In addition, the HTTP response contains the XML document as a string in the state in which it was passed to the CCMS XML-processing class.
CCMS_XML_FILE_POLL and HTTP Statistics
These two subtrees report on the XML processing activity:
1. The arrival of an HTTP POST request prompts the creation or updating of the HTTP tree. This reports the time stamp in the monitoring system at which the most recent HTTP run occurred. You can use this timestamp to identify the XML log entries associated with the processing of the POST.
2. For each file-polling method, there is a separate monitoring subtree. Illustrated is the subtree for the sample method
The XMI Logon and Auditing
The CCMS's BAPI interface for reading monitoring data requires the so-called XMI logon. This is an internal CCMS logon without any effect on the user's session. It is used to record actions in the monitoring architecture of callers from outside the SAP System.
The CCMS XML interface also uses the XMI mechanism to log the start and finish of the processing of an XML document and optionally also to log the SALI calls that result from the processing of an XML document. This last tracing or auditing option is of course of interest if you are trouble-shooting a document.
The XMI logon and audit parameters are carried as attributes of the
Reqiured/ Parameter Optional Meaning extcompany required The name of the entity that is reporting the monitoring data. extproduct required The name of the product to which the monitoring data pertains. extcompany and extproduct are used together to identify the entity that is reporting and perform an XMI logon. interface optional The CCMS interface that is being used in the XMI session. At this time, the only valid value in an XML DataSupplierReport document is XAL. XAL is also the default value. version optional The version of the CCMS interface that is being used in the XMI session. At this time, the only valid value in an XML DataSupplier Report document is 1.0. This is also the default value. auditlevel optional This value switches on or off detailed activity tracing in the XMI log, viewable with transaction RZ15. Value 0: Detailed auditing switched off. Only the XMI logon and logoff are recorded in the XMI log. Value 1: Detailed auditing switched on. Calls to the ABAP write interface (SALI interface) that result from the processing of an XML document are recorded in the XMI log. Exception: Calls that write to the self- monitoring sections of the monitoring architecture are not logged. Switching to this audit level can help you to trouble-shoot an XML document. With the audit, you can trace the construction of and reporting of data into a monitoring tree.
Sample XML Messages
The next sections show sample XML documents that create, attach to or report into the most important types of MTEs: performance attributes, status message attributes, and log attributes.
Create a Performance Attribute—Long-Form XML Document
The following sample XML document creates a complete monitoring tree terminating in a performance attribute. The XML document uses many more attributes than are actually necessary, assigning for example an SAP T100 message for documentation and methods for each MTE. Most attributes can be allowed to default.
The result is shown in
<SAP_CCMS:DataSupplierReport extcompany="Test" extproduct="New"> <MTE:Instance type="CONTEXT" class="XML_TEST" owner="XML_TEST" numrange="AL_NR_AUTO" descmsgid="RT" descmsgno="112" co_method="CCMS_XML_FILE_POLL" an_method="cxml_an" au_method="cxml_au"> <MTE:Name>XML_Test_Context</MTE:Name> <CNTXT:ContextParameters cntxt_clnt="000" cntxt_sysw="YES"> </CNTXT:ContextParameters> <MTE:Instance type="OBJECT" class="XML_TEST_OBJECT" owner="XML_TEST" numrange="AL_NR_AUTO" descmsgid="RT" descmsgno="113" co_method="CCMS_XML_FILE_POLL" an_method="oxml_an" au_method="oxml_au"> <MTE:Name>Test_Object</MTE:Name> <MTE:Instance type="PERFORMANCE_ATTRIBUTE" class="XML_TEST_PAttrib" numrange="AL_NR_AUTO" owner="XML_TEST" descmsgid="RT" descmsgno="114" co_method="CCMS_XML_FILE_POLL" an_method="pxml_an" au_method="pxml_au"> <MTE:Name>Test_Perf_Attribute</MTE:Name> <PRF:PerformanceParameters agroup="test_xml" subtype="AL_STD_NO_SUBCLASS" severity="248" alkptype="AL_KEEP_OLDEST" alkpmax="12" g2y="5" y2r="10" r2y="8" y2g="4" p_unit="HIPS" p_decimals="1" p_relval="AL_PERF_RV_SMOOTH_05" p_thrshdir="ABOVE" almsgid="RT" almsgno="001" sec_repeat="240" sec_inact="600" sec_warmup="10"> <PRF:TotalVal>300</PRF:TotalVal> <PRF:NumberVal>1</PRF:NumberVal> <PRF:ReportedBy>XML_TEST</PRF:ReportedBy> </PRF:PerformanceParameters> </MTE:Instance> </MTE:Instance> </MTE:Instance> </SAP_CCMS:DataSupplierReport>
Refresh a Performance Attribute—Short-Form XML Document
A short-form XML document allows you to report a new value for an existing attribute MTE (leaf-level MTE). The short form identifies the MTE by its fully-specified name in the monitoring architecture. It is not necessary to build the full monitoring tree to report into the attribute MTE and you need not repeat the default customizing that was specified when the MTE was first created.
An efficient pattern is to create a complete monitoring tree once or only at relatively long intervals, such as at system starts. This start-up processing requires a 'long-form' XML document. All later reporting of data into an MTE can use the short-form, saving network bandwidth and processing time in the client and in the server.
The effect of the XML document is to report new data into an MTE, refreshing the MTE and potentially triggering an alert. The document looks like this:
<SAP_CCMS:DataSupplierReport extcompany="Test" extproduct="New"> <MTE:Instance type="PERFORMANCE_ATTRIBUTE" class="XML_TEST_PAttrib" owner="XML_TEST"> <MTE:FullName>%26SY\XML_Test_Context\...\Test_Object\Test_Perf_Attribute</MTE: FullName> <PRF:PerformanceParameters> <PRF:TotalVal>300</PRF:TotalVal> <PRF:NumberVal>1</PRF:NumberVal> <PRF:ReportedBy>XML_TEST</PRF:ReportedBy> </PRF:PerformanceParameters> </MTE:Instance> </SAP_CCMS:DataSupplierReport>
Create a Log Attribute—Long-Form XML Document
This document creates a log attribute parallel to the performance attribute created and refreshed with the documents described above.
The result is shown in
Here is the XML document:
<SAP_CCMS:DataSupplierReport extcompany="Test" extproduct="New"> <MTE:Instance type="CONTEXT" class="XML_TEST" owner="XML_TEST" numrange="AL_NR_AUTO" descmsgid="RT" descmsgno="112" co_method="CCMS_XML_FILE_POLL" an_method="cxml_an" au_method="cxml_au"> <MTE:Name>XML_Test_Context</MTE:Name> <CNTXT:ContextParameters cntxt_clnt="000" cntxt_sysw="YES"> </CNTXT:ContextParameters> <MTE:Instance type="OBJECT" class="XML_TEST_OBJECT" owner="XML_TEST" numrange="AL_NR_AUTO" descmsgid="RT" descmsgno="113" co_method="CCMS_XML_FILE_POLL" an_method="oxml_an" au_method="oxml_au"> <MTE:Name>Test_Object</MTE:Name> <MTE:Instance type="LOG_ATTRIBUTE" class="XML_TEST_LAttrib" numrange="AL_NR_AUTO" owner="XML_TEST" descmsgid="RT" descmsgno="204" co_method="CCMS_XML_FILE_POLL" an_method="lxml_an" au_method="lxml_au"> <MTE:Name>Test_Log_Attr1</MTE:Name> <LOG:LogParameters agroup="Test_LAttrGrp1" subtype="AL_STD_MSC_CACHE" severity="75" alkptype="AL_KEEP_OLDEST" alkpmax="12" sec_repeat="240" sec_inact="600" sec_warmup="10" m_maxalmid="22" m_kplinetp="AL_TD_KL_OLDEST" m_kplinemx="212" m_amsgmode="AL_TD_MSC_VAL_MODE_WORST_SINCE" m_msgtimfr="302"> <LOG:M_RaiseSev>89</LOG:M_RaiseSev> <LOG:M_RaiseVal>AL_VAL_YELLOW</LOG:M_RaiseVal> <LOG:AlMsgID>00</LOG:AlMsgID> <LOG:AlMsgNo>398</LOG:AlMsgNo> <LOG:AlMsgVal>AL_VAL_RED</LOG:AlMsgVal> <LOG:AlMsgSev>210</LOG:AlMsgSev> <LOG:M_Client>010</LOG:M_Client> <LOG:M_User>XML_TEST</LOG:M_User> <LOG:MsgArg1>Hello World.</LOG:MsgArg1> <LOG:DefaultMsg>Hello World!</LOG:DefaultMsg> <LOG:ReportedBy>XML_TEST</LOG:ReportedBy> </LOG:LogParameters> </MTE:Instance> </MTE:Instance> </MTE:Instance> </SAP_CCMS:DataSupplierReport>
Creating a Status Message Attribute—Long-Form XML Document
This document creates the monitoring tree leading to a status message attribute, an MTE that captures discrete messages from a reporting component.
The result is shown in
<SAP_CCMS:DataSupplierReport extcompany="Test" extproduct="New"> <MTE:Instance type="CONTEXT" class="XML_TEST" owner="XML_TEST" numrange="AL_NR_AUTO" descmsgid="RT" descmsgno="112" co_method="CCMS_XML_FILE_POLL" an_method="cxml_an" au_method="cxml_au"> <MTE:Name>XML_Test_Context</MTE:Name> <CNTXT:ContextParameters cntxt_clnt="000" cntxt_sysw="YES"> </CNTXT:ContextParameters> <MTE:Instance type="OBJECT" class="XML_TEST_OBJECT" owner="XML_TEST" numrange="AL_NR_AUTO" descmsgid="RT" descmsgno="113" co_method="CCMS_XML_FILE_POLL" an_method="oxml_an" au_method="oxml_au"> <MTE:Name>Test_Object</MTE:Name> <MTE:Instance type="STATUS_ATTRIBUTE" class="XML_TEST_SAttrib" numrange="AL_NR_AUTO" owner="STEPH" descmsgid="RT" descmsgno="204" co_method="CCMS_XML_FILE_POLL" an_method="sxml_an" au_method="sxml_au"> <MTE:Name>Test_SMES_Attr_1</MTE:Name> <SMES:StatusParameters agroup="Test_SAttrGrp1" subtype="AL_STD_SMES_GREEN_ONLY_EXPLIC" severity="75" s_almode="AL_SMSG_ALMODE_VALUE_CHG" s_alshift="AL_SMSG_ALSHIFT_RAY_YAG" alkptype="AL_KEEP_NEWEST" alkpmax="12" sec_repeat="240" sec_inact="600" sec_warmup="10"> <SMES:AlMsgID>00</SMES:AlMsgID> <SMES:AlMsgNo>398</SMES:AlMsgNo> <SMES:MsgArg1>Hello World.</SMES:MsgArg1> <SMES:AlMsgVal>AL_VAL_RED</SMES:AlMsgVal> <SMES:DefaultMsg>Hello World!</SMES:DefaultMsg> <SMES:ReportedBy>XML_TEST</SMES:ReportedBy> </SMES:StatusParameters> </MTE:Instance> </MTE:Instance> </MTE:Instance> </SAP_CCMS:DataSupplierReport>
A Java HTTP Client for Testing
Here is a sample class for testing the transmission of a XML document to the CCMS by means of an HTTP POST request. You must customize the instantiation of the socket class to use the name and HTTP port (set in the instance profile) of your SAP application server. You also need to insert your own XML document in the output string of the POST request. Don't forget to observe the required Java conventions for escaping special characters. Be sure to set the content-length header correctly. A content-length that is longer than the number of characters in the XML DataSupplierReport will, for example, cause the client to hang until the connection times out, since this primitive client does not respond to the SAP request for the remaining data to fulfill the content-length specification.
/* * xml_test_client.java * * Created on 6. Mai 2002, 10:58 */ /** * * @author SAP * @version */ import java.io.*; import java.net.*; public class xml_test_client { public static void main(String args[ ]) { try { Socket clientsocket = new Socket("fully-qualified host name of SAP App Server", <SAP HTTP Port number>); System.out.println("Client: " + clientsocket); /* Send an XML document to the CCMS */ sendpost (clientsocket); /* Request the SAP CCMS DTD for the monitoring architecture */ getpage(clientsocket); } catch (UnknownHostException uhe) { System.out.println("UnknownHostException: " + uhe); } catch (IOException ioe) { System.out.println("IOException: " + ioe); } } public static void sendpost (Socket clientsocket) { try { DataOutputStream outbound = new DataOutputStream( clientsocket.getOutputStream( ) ) ; BufferedReader inbound = new BufferedReader( new InputStreamReader(clientsocket.getInputStream( )) ); outbound.writeBytes("POST /sap/bc/ccms/monitoring/CCMS_XML HTTP/1.0\r\nHost: fully-qualified host name of SAP App Server\r\nContent-Type: text/xml\r\nContent- Length: <nnnn>\r\n\r\n<SAP_CCMS:DataSupplierReport extcompany=\"SAP_CCMS\" extproduct=\"XML_Interface\" interface=\"XAL\" version=\"1.0\"><MTE:Instance type=\"CONTEXT\" class=\"XML_TEST\" owner=\"XML_TEST\" numrange=\"AL_NR_AUTO\" descmsgid=\"RT\" descmsgno=\"112\" co_method=\"cxml_co\" an_method=\"cxml_an\" au_method=\"cxml_au\"><MTE:Name>XML_Test_Context</MTE:Name><CNTXT:ContextParameters cntxt_clnt=\"000\" cntxt_sysw=\"YES\"></CNTXT:ContextParameters><MTE:Instance type=\"OBJECT\" class=\"XML_TEST_OBJECT\" owner=\"XML_TEST\" numrange=\"AL_NR_AUTO\" descmsgid=\"RT\" descmsgno=\"113\" co_method=\"oxml_co\" an_method=\"oxml_an\" au_method=\"oxml_au\"><MTE:Name>Test_Object</MTE:Name><MTE:Instance type=\"PERFORMANCE_ATTRIBUTE\" class=\"XML_TEST_PAttrib\" numrange=\"AL_NR_AUTO\" owner=\"XML_TEST\" descmsgid=\"RT\" descmsgno=\"114\" co_method=\"CCMS_XML_FILE_POLL\" an_method=\"pxml_an\" au_method=\"pxml_au\"><MTE:Name>Test_Perf_Attribute</MTE:Name><PRF:PerformanceParameters agroup=\"test_xml\" subtype=\"AL_STD_NO_SUBCLASS\" severity=\"248\" alkptype=\"AL_KEEP_OLDEST\" alkpmax=\"12\" g2y=\"5\" y2r=\"10\" r2y=\"8\" y2g=\"4\" p_unit=\"HIPS\" p_decimals=\"1\" p_relval=\"AL_PERF_RV_SMOOTH_05\" p_thrshdir=\"ABOVE\" almsgid=\"RT\" almsgno=\"001\" sec_repeat=\"240\" sec_inact=\"600\" sec_warmup=\"10\"><PRF:TotalVal>300</PRF:TotalVal><PRF:NumberVal>1</PRF:NumberVal><PRF: ReportedBy>XML_TEST</PRF:ReportedBy></PRF:PerformanceParameters></MTE:Instance> </MTE:Instance></MTE:Instance></SAP_CCMS:DataSupplierReport>"); String responseLine; while ((responseLine = inbound.readLine( )) != null) { System.out.println(responseLine); } outbound.close( ); inbound.close( ); clientsocket.close( ); } catch (IOException ioe) { System.out.println("IOException: " + ioe); } } public static void getpage(Socket clientsocket) { try { DataOutputStream outbound = new DataOutputStream( clientsocket.getOutputStream( ) ) ; BufferedReader inbound = new BufferedReader( new InputStreamReader(clientsocket.getInputStream( )) ); outbound.writeBytes("GET /sap/bc/ccms/monitoring/CCMS_XML?Name=\"CCMS_INSTRUMENTATION_DTD\" HTTP/1.0\r\n\r\n"); String responseLine; while ((responseLine = inbound.readLine( )) != null) { System.out.println(responseLine); } outbound.close( ); inbound.close( ); clientsocket.close( ); } catch (IOException ioe) { System.out.println("IOException: " + ioe); } } }
The CCMS XML DTD
<?xml version="1.0" encoding="UTF-8"?>
<!- -->
<!-- This DTD defines a document for reporting data into the SAP CCMS
<!-- Monitoring Architecture. It encapsulates the interface defined in
<!-- the ABAP SALI function group in the SAP System. This DTD is automatically
<!-- added to an XML document sent to the Monitoring Architecture.
<!DOCTYPE SAP_CCMS:DataSupplierReport
<!ELEMENT SAP_CCMS:DataSupplierReport (MTE:Instance+, CMS_METHOD:MethodDefinition* )
<!ATTLIST SAP_CCMS:DataSupplierReport
<!-- Instance is an MTE in a monitoring tree. The first Instance must always -->
<!-- be of type context. The monitoring tree must be completely instantiated -->
<!-- from the context downwards. Exception: You can directly address a single -->
<!-- MTE that already exists by using the FullName element. In this case,-->
<!-- the XML document handler uses the unique complete name of the MTE to -->
<!-- obtain its handle and then reports the data into the MTE. Typically, -->
<!-- you will first instantiate a monitoring tree once and then use the -->
<!-- fullname for more compact reporting to the monitoring attributes at
<!-- the leaf-level in the tree.
<!ELEMENT MTE:Instance ((MTE:Name | MTE:FullName), (CNTXT:ContextParameters? |
PRF:PerformanceParameters | SMES:StatusParameters |
LOG:LogParameters | REF:RefParameters | TXT:TextParameters),
<!-- Instance specifies attributes that are common to all MTEs -->
<!ATTLIST MTE: Instance
<!-- Type of MTE -->
type (CONTEXT | SUMMARY | OBJECT | PERFORMANCE_ATTRIBUTE | STATUS_ATTRIBUTE |
<!-- MTE class: parameter MT_CLASS or MTE_CLASS in SALI -->
class CDATA #IMPLIED
<!-- Number range of MTE: AL_NR_AUTO for MTEs that are deleted at system -->
<!-- restart, AL_NR_AUTO for MTEs that persist across system starts -->
numrange (AL_NR_AUTO | AL_NR_AUTO) #IMPLIED
<!-- Owner of a context MTE: owner of a monitoring tree -->
owner CDATA #REQUIRED
<!-- ID of an SAP T100 message that provides F1 help for an MTE -->
descmsgid CDATA #IMPLIED
<!-- Number of an SAP T100 message that provides F1 help for an MTE -->
descmsgno CDATA #IMPLIED
<!-- Name of the data collection method for an MTE, if any -->
co_method CDATA #IMPLIED
<!-- Name of the analysis method for an MTE, if any -->
an_method CDATA #IMPLIED
<!-- Name of the autoreaction method for an MTE, if any -->
au_method CDATA #IMPLIED>
<!-- Name of an MTE: may be up to 40 characters long, not translatable -->
<!ELEMENT MTE:Name (#PCDATA)>
<!-- Fully specified name of an MTE. Used for short-form XML message -->
<!-- to update an existing MTE -->
<!ELEMENT MTE:FullName (#PCDATA)>
<!-- Context attributes: cntxt_clnt - specific client to which context
<!-- refers and which can be used in monitor definitions (views)
<!-- cntxt_sysw - whether a context exists once in a system or once in
<!-- each monitoring segment
<!-- cntxt_segm - Monitoring segment in which a context is to be created
May not be used with the file method.
<!ELEMENT CNTXT:ContextParameters (#PCDATA)>
<!ATTLIST CNTXT:ContextParameters
cntxt_clnt CDATA #IMPLIED
cntxt_sysw (YES | NO) #IMPLIED
cntxt_segm #IMPLIED>
<!-- Elements and attributes for performance attribute MTEs
<!-- Element TotalVal - sum of performance values to be reported
<!-- Element NumberVal - number of values in the TotalVal sum
<!ELEMENT PRF:PerformanceParameters (PRF:TotalVal, PRF:NumberVal, PRF:ReportedBy)>
<!ATTLIST PRF:PerformanceParameters
<!-- agroup: attribute group to which MTE belongs, for customizing (40 char) -->
agroup CDATA #IMPLIED
<!-- subtype: operative subtype of MTE (behavior of performance MTE) -->
subtype (AL_STD_NO_SUBCLASS |
<!-- severity: weighting of alert within value (green, yellow, red) -->
severity CDATA #IMPLIED
<!-- alkptype: Alerts to keep should alerts need to be discarded -->
alkptype (AL_KEEP_NEWEST | AL_KEEP_OLDEST) #IMPLIED
<!-- alkpmax: Number of alerts to hold for an MTE of this class -->
alkpmax CDATA #IMPLIED
<!-- Thresholds for green to yellow and to red and back down
<!-- Alerts are triggered at yellow and red thresholds
g2y CDATA #REQUIRED
y2r CDATA #REQUIRED
r2y CDATA #IMPLIED
y2g CDATA #IMPLIED
<!-- p_unit: Unit to display for performance MTE (up to four characters) -->
p_unit CDATA #IMPLIED
<!-- p_decimals: Number of decimal places to insert in reported value -->
p_decimals CDATA #IMPLIED
<!-- p_relval: Value to compare to thresholds for generating alerts -->
p_relval (AL_PERF_RV_LAST |
<!-- p_thrshdir: relevant direction for violations - above or below threshold -->
p_thrshdir (ABOVE | BELOW) #IMPLIED
<!-- almsgid and almsgno - T100 message identification for alert messages -->
<!-- Defaults to a standard threshold violation message -->
almsgid CDATA #IMPLIED
almsgno CDATA #IMPLIED
<!-- sec_repeat: Interval at which to repeat data collection method - default 0, no repetition -->
sec_repeat #IMPLIED
<!-- sec_inact: Interval after which MTE is set to inactive if no data comes - default 0 -->
sec_inact #IMPLIED
<!-- sec_warmup: Interval after system start during which alerts should be suppressed -->
sec warmup #IMPLIED>
<!-- Element TotalVal - sum of performance values to be reported
<!ELEMENT PRF:TotalVal (#PCDATA)>
<!-- Element NumberVal - number of values in the TotalVal sum
<!ELEMENT PRF:NumberVal (#PCDATA)>
<!-- Reporter of data - should be the external component responsible for data -->
<!ELEMENT PRF:ReportedBy (#PCDATA)>
<!-- Elements and attributes for status message attribute MTEs
<!ELEMENT SMES:StatusParameters (SMES:AlMsgID, SMES:AlMsgNo, (SMES:MsgArg1,
(SMES:MsgArg2, (SMES:MsgArg3, (SMES:MsgArg4?)?)?)?),
SMES:AlMsgVal, SMES:DefaultMsg, SMES:ReportedBy)>
<!ATTLIST SMES:StatusParameters
<!-- agroup: attribute group to which MTE belongs, for customizing (40 char) -->
agroup CDATA #IMPLIED
<!-- subtype: operative subtype of MTE (behavior of performance MTE) -->
subtype (AL_STD_SMES_GREEN_ONLY_EXPLIC |
<!-- severity: weighting of alert within value (green, yellow, red) -->
severity CDATA #IMPLIED
<!-- s_almode: grade of alert suppression - none to complete suppression -->
s_almode (AL_SMSG_ALMODE_ALWAYS |
<!-- s_alshift: optionally shift reported alert values up or down -->
s_alshift (AL_SMSG_ALSHIFT_UNCHG |
<!-- alkptype: Alerts to keep should alerts need to be discarded -->
alkptype (AL_KEEP_NEWEST | AL_KEEP_OLDEST) #IMPLIED
<!-- alkpmax: Number of alerts to hold for an MTE of this class -->
alkpmax CDATA #IMPLIED
<!-- sec_repeat: Interval at which to repeat data collection method - default 0, no repetition -->
sec_repeat CDATA #IMPLIED
<!-- sec_inact: Interval after which MTE is set to inactive if no data comes - default 0 -->
sec_inact CDATA #IMPLIED
<!-- sec_warmup: Interval after system start during which alerts should be suppressed -->
sec_warmup CDATA #IMPLIED
<!-- almsgid and almsgno - T100 message that is to be reported at this time -->
<!-- 00 398 can be used to construct a message out of four variables -->
<!ELEMENT SMES:AlMsgID (#PCDATA)>
<!ELEMENT SMES:AlMsgNo (#PCDATA)>
<!-- Values for variables in messages -->
<!ELEMENT SMES:MsgArg1 (#PCDATA)>
<!ELEMENT SMES:MsgArg2 (#PCDATA)>
<!ELEMENT SMES:MsgArg3 (#PCDATA)>
<!ELEMENT SMES:MsgArg4 (#PCDATA)>
<!-- AlMsgVal: Alert value of this message - AL_VAL_GREEN, AL_VAL_YELLOW or AL_VAL_RED -->
<!ELEMENT SMES:AlMsgVal (#PCDATA)>
<!-- DefaultMsg: Message text with fully resolved variables to display should no T100 message be found -->
<!ELEMENT SMES: DefaultMsg (#PCDATA)>
<!-- Reporter of data - should be the external component responsible for data -->
<!ELEMENT SMES:ReportedBy (#PCDATA)>
<!-- Elements and attributes for message log attribute MTEs -->
<!ELEMENT LOG:LogParameters (LOG:M_RaiseSev?, LOG:M_RaiseVal?, LOG:AlMsgID,
LOG:AlMsgNo, LOG:AlMsgVal?, LOG:AlMsgSev?,
LOG:M_Client?, LOG:M_User?, (LOG:MsgArg1, (LOG:MsgArg2,
(LOG:MsgArg3, (LOG:MsgArg4?)?)?)?),
LOG:DefaultMsg, LOG:ReportedBy)>
<!ATTLIST LOG:LogParameters
<!-- agroup: attribute group to which MTE belongs, for customizing (40 char) -->
agroup CDATA #IMPLIED
<!-- subtype: operative subtype of MTE (type of log MTE, default CACHE - MTE itself stores messages) -->
subtype (AL_STD_MSC_CACHE |
<!-- severity: weighting of alert within value (green, yellow, red) -->
severity CDATA #IMPLIED
<!-- alkptype: Alerts to keep should alerts need to be discarded -->
alkptype (AL_KEEP_NEWEST | AL_KEEP_OLDEST) #IMPLIED
<!-- alkpmax: Number of alerts to hold for an MTE of this class -->
alkpmax CDATA #IMPLIED
<!-- sec_repeat: Interval at which to repeat data collection method - default 0, no repetition -->
sec_repeat CDATA #IMPLIED
<!-- sec_inact: Interval after which MTE is set to inactive if no data comes - default 0 -->
sec_inact CDATA #IMPLIED
<!-- sec_warmup: Interval after system start during which alerts should be suppressed -->
sec_warmup CDATA #IMPLIED
<!-- m_maxalmid: Maximum number of alerts to keep for each message ID represented in message log -->
m_maxalmid CDATA #IMPLIED
<!-- m_kplinetp: Message lines to keep should messages be displaced from the log (type CACHE) -->
m_kplinetp (AL_TD_KL_ALL |
<!-- m_kplinemx: Maximum number of message lines to keep in the log (type CACHE) -->
m_kplinemx CDATA #IMPLIED
<!-- m_amsgmode: Message to present for display - most recent, worst since, most severe -->
m_amsgmode (AL_TD_MSC_VAL_MODE_LAST |
<!-- m_msgtimfr: Time frame within which to evaluate messages (mode WORST_SINCE) -->
m_msgtimfr #IMPLIED>
<!-- M_RaiseSev and M_RaiseVal: Weighting (0–255) within an alert value -->
and alert value (yellow, red) above which an alert should be triggered -->
<!ELEMENT LOG:M_RaiseSev (#PCDATA)>
<!-- M_RaiseSev: Weighting (0–255) of log alerts within alert level (yellow, red) -->
<!ELEMENT LOG:M_RaiseVal (#PCDATA)>
<!-- almsgid and almsgno - T100 message identification of message to report -->
<!ELEMENT LOG:AlMsgID (#PCDATA)>
<!ELEMENT LOG:AlMsgNo (#PCDATA)>
<!-- AlMsgVal: Alert value of message being reported (green, yellow, red) -->
<!ELEMENT LOG:AlMsgVal (#PCDATA)>
<!ELEMENT LOG:AlMsgSev (#PCDATA)>
<!-- M_Client, M_User: Client and user associated with message -->
<!ELEMENT LOG:M_Client (#PCDATA)>
<!ELEMENT LOG:M_User (#PCDATA)>
<!-- Values for variables in messages -->
<!ELEMENT LOG:MsgArg1 (#PCDATA)>
<!ELEMENT LOG:MsgArg2 (#PCDATA)>
<!ELEMENT LOG:MsgArg3 (#PCDATA)>
<!ELEMENT LOG:MsgArg4 (#PCDATA)>
<!-- DefaultMsg: Message text with fully resolved variables to display should no T100 message be found -->
<!ELEMENT LOG:DefaultMsg (#PCDATA)>
<!-- Reporter of data - should be the external component responsible for data -->
<!ELEMENT LOG:ReportedBy (#PCDATA)>
<!-- Elements and attributes for reference attribute MTEs
<!ELEMENT REF:RefParameters (REF:RefText, (REF:ReferenceTID | REF:RefFname)>
<!-- RefText: Text to display with reference MTE -->
<!ELEMENT REF:RefText (#PCDATA)>
<!-- TID of MTE to which reference MTE refers (alternative to MTE full name) -->
<!ELEMENT REF:ReferenceTID (MTE:MTSYSID, MTE:MTMCNAME, MTE:MTNUMRANGE,
<!-- RefFname: Fullname of MTE to which reference MTE refers (alternative to TID) -->
<!ELEMENT REF:RefFname (#PCDATA)>
<!-- Elements and attributes for reference attribute MTEs
<!ELEMENT TXT:TextParameters (TXT:AttrText)
<!ATTLIST TXT:Text Parameters
<!-- sec_repeat: Interval at which to repeat data collection method - default 0, no repetition -->
sec_repeat CDATA #IMPLIED
<!-- sec_inact: Interval after which MTE is set to inactive if no data comes - default 0 -->
sec_inact CDATA #IMPLIED>
<!-- AttrText: Text to display for text attribute (value) -->
<!ELEMENT TXT:AttrText (#PCDATA)>
<!-- Method definition for XML MTEs - not yet supported in SAP_BASIS Release 6.30 -->
<!CCMS_METHOD:MethodDefinition (CCMS_METHOD:Name, CCMS_METHOD:ExecName,
CCMS_METHOD:Desc, ((CCMS_METHOD:Parm1,
CCMS_METHOD:Value1), ((CCMS_METHOD:Parm2,
CCMS_METHOD:Value2), ((CCMS_METHOD:Parm3,
CCMS_METHOD:Value3), ((CCMS_METHOD:Parm4,
CCMS_METHOD:Value4), ((CCMS_METHOD:Parm5,
CCMS_METHOD:Value5), ((CCMS_METHOD:Parm6,
CCMS_METHOD:Value6), ((CCMS_METHOD:Parm7,
CCMS_METHOD:Value7), ((CCMS_METHOD:Parm8,
CCMS_METHOD:Value8), ((CCMS_METHOD:Parm9,
CCMS_METHOD:Value9), ((CCMS_METHOD:Parm10,
<!ATTLIST CCMS_METHOD:MethodDefinition
exectype (REPORT | FUNCTIONMODULE | TRANSACTION | URL) #REQUIRED
dispatcher (MANUAL | DIALOG | BATCH | AGENT) #REQUIRED
runonstart (YES | NO) #REQUIRED
startsrv (CENTRAL | ALL) #REQUIRED
multi_mte (SINGLEMTE | TABLEOFMTES) #REQUIRED
methodtype (DATACOLLECTION | ANALYSIS | AUTOREACTION) #REQUIRED>
<!ELEMENT CCMS_METHOD:Name (#PCDATA)>
<!ELEMENT CCMS_METHOD:ExecName (#PCDATA)>
<!ELEMENT CCMS_METHOD:Desc (#PCDATA)>
<!ELEMENT CCMS_METHOD:Parm1 (#PCDATA)>
<!ELEMENT CCMS_METHOD:Value1 (#PCDATA)>
<!ELEMENT CCMS_METHOD:Parm2 (#PCDATA)>
<!ELEMENT CCMS_METHOD:Value2 (#PCDATA)>
<!ELEMENT CCMS_METHOD:Parm3 (#PCDATA)>
<!ELEMENT CCMS_METHOD:Value3 (#PCDATA)>
<!ELEMENT CCMS_METHOD:Parm4 (#PCDATA)>
<!ELEMENT CCMS_METHOD:Value4 (#PCDATA)>
<!ELEMENT CCMS_METHOD:Parm5 (#PCDATA)>
<!ELEMENT CCMS_METHOD:Value5 (#PCDATA)>
<!ELEMENT CCMS_METHOD:Parm6 (#PCDATA)>
<!ELEMENT CCMS_METHOD:Value6 (#PCDATA)>
<!ELEMENT CCMS_METHOD:Parm7 (#PCDATA)>
<!ELEMENT CCMS_METHOD:Value7 (#PCDATA)>
<!ELEMENT CCMS_METHOD:Parm8 (#PCDATA)>
<!ELEMENT CCMS_METHOD:Value8 (#PCDATA)>
<!ELEMENT CCMS_METHOD:Parm9 (#PCDATA)>
<!ELEMENT CCMS_METHOD:Value9 (#PCDATA)>
<!ELEMENT CCMS_METHOD:Parm1O (#PCDATA)>
<!ELEMENT CCMS_METHOD:Value1O (#PCDATA)>
A number of embodiments of the invention have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the invention. For example, in lieu of http or file polling, FTP could be used to transfer an XML file. Accordingly, other embodiments are within the scope of the following claims.
|Cited Patent
|Filing date
|Publication date
|Jul 22, 1997
|May 18, 1999
|Ncr Corporation
|Client/server distribution of performance monitoring data
|Aug 27, 1998
|Jan 28, 2003
|Internetseer.Com Corp.
|System and method for monitoring informational resources
|Apr 5, 2001
|Nov 14, 2002
|Duggan Richard K.
|Method for providing performance data of a web server
|Aug 27, 2001
|Feb 27, 2003
|Nec Usa, Inc.
|Generic network monitoring tool
|Jul 30, 2004
|Jan 6, 2005
|Microsoft Corporation
|System and method for implementing integrated polling functions in a client management tool
|Jul 27, 2001
|Feb 7, 2002
|Axeda Systems Operating Company, Inc.
|Reporting the state of an apparatus to a remote computer
|Dec 11, 2001
|Jun 20, 2002
|Microsoft Corporation
|Method and system for management of multiple network resources
|Abiteboul et al., The Xyleme project, Computer Networks, vol. 39, No. 3, (Jun. 2002).
|Cox, XML for Instrument Control and Monitoring, Dr. Dobb's Journal, M&T Publ., vol. 26, No. 11, (Nov. 2001).
|Cox, XML for Instrument Control and Monitoring, Dr. Dobb's Journal, M&T Publ., vol. 26, No. 11, Nov. 2001.
|Fung, Decoding XML and the DTD, IBM.COM DEVELOPERWORKS XML, (Jul. 2001).
|Citing Patent
|Filing date
|Publication date
|Sep 10, 2003
|Nov 27, 2007
|Sap Aktiengesellschaft
|Symmetric transformation processing system
|Dec 30, 2003
|Feb 17, 2009
|Sap Ag
|Management architecture and method employed within a clustered node configuration
|Mar 26, 2004
|Apr 28, 2009
|Sap Ag
|Unified logging service with a log viewer
|Dec 30, 2003
|Aug 18, 2009
|Sap Ag
|System and method for monitoring program code
|Sep 5, 2007
|Jan 19, 2010
|Sap Aktiengesellschaft
|Symmetric transformation processing system
|Mar 26, 2004
|May 18, 2010
|Sap Ag
|Unified logging service with a logging formatter
|Dec 30, 2003
|May 25, 2010
|Sap Ag
|Notification architecture and method employed within a clustered node configuration
|May 19, 2005
|Jun 15, 2010
|Bea Systems, Inc.
|Management of J2EE applications
|Dec 30, 2003
|Jul 13, 2010
|Sap Ag
|Method and system for employing a hierarchical monitor tree for monitoring system resources in a data processing environment
|Nov 22, 2004
|Jul 20, 2010
|International Business Machines Corporation
|Performance monitoring within an enterprise software system
|Dec 30, 2003
|Oct 26, 2010
|Sap Ag
|Deployment of a web service
|Dec 30, 2003
|May 10, 2011
|Sap Ag
|Multi-service management architecture employed within a clustered node configuration
|Jun 6, 2005
|May 20, 2014
|Cerner Innovation, Inc.
|Computerized system and method for rendering reports in a healthcare environment
|Jan 30, 2009
|Apr 28, 2015
|Case Western Reserve University
|Internet measurement system application programming interface
|Apr 3, 2013
|Nov 1, 2016
|Sap Se
|System decommissioning through reverse archiving of data
|Dec 30, 2003
|Sep 30, 2004
|Frey Gregor K
|System and method for monitoring program code
|Apr 1, 2003
|Oct 7, 2004
|Straw Phillip Edward
|Collaboration bus apparatus and method
|Sep 10, 2003
|Mar 10, 2005
|Bohlmann Karsten K.
|Symmetric transformation processing system
|Feb 26, 2004
|Jun 30, 2005
|Ichiro Harashima
|Method for managing file transfer actions, method for visualizing file transfer actions, and apparatus for managing file transfer actions and user terminals in file transfer system
|Mar 26, 2004
|Sep 29, 2005
|Reinhold Kautzleben
|System and method to provide a visual administrator in a network monitoring system
|Mar 26, 2004
|Oct 6, 2005
|Frey Gregor K
|Unified logging service with a log viewer
|Mar 26, 2004
|Oct 6, 2005
|Frey Gregor K
|Unified logging service with a logging formatter
|Nov 22, 2004
|Jun 22, 2006
|Mills Michael C
|Performance monitoring within an enterprise software system
|Jun 6, 2005
|Jul 6, 2006
|Cerner Innovation, Inc.
|Computerized system and method for rendering reports in a healthcare environment
|May 19, 2005
|Nov 23, 2006
|Bea Systems, Inc.
|Management of J2EE applications
|Sep 5, 2007
|Dec 27, 2007
|Sap Aktiengesellschaft
|Symmetric transformation processing system
|Oct 24, 2006
|Apr 24, 2008
|Microsoft Corporation
|Managing virtual machines and hosts by property
|Dec 12, 2008
|Apr 9, 2009
|Kaminsky David L
|System and program product for detecting an operational risk of a node
|Jan 16, 2008
|Jul 16, 2009
|Oracle International Corporation
|Smart component monitoring
|Mar 31, 2008
|Oct 1, 2009
|Caterpillar Inc.
|Hierarchy creation and management tool
|Jan 30, 2009
|Oct 22, 2009
|Case Western Reserve University
|Internet measurement system application programming interface
|Dec 9, 2010
|Jun 14, 2012
|S Ramprasad
|Rendering system components on a monitoring tool
|Dec 9, 2010
|Jun 14, 2012
|S Ramprasad
|Rendering an optimized metrics topology on a monitoring tool
|Feb 24, 2014
|Aug 27, 2015
|Ca, Inc.
|Publishing Information Technology Data As A Newsfeed
|Mar 30, 2004
|Oct 21, 2004
|Pnp Networks, Inc.
|Collaboration bus apparatus and method
|Mar 30, 2004
|Nov 1, 2007
|Pnp Networks Inc
|Collaboration bus apparatus and method
|U.S. Classification
|International Classification
|Cooperative Classification
|European Classification
|Dec 3, 2003
Owner name: SAP AKTIENGESELLSCHAFT, GERMANY
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PFEIFFER, STEPHEN;DROESCHER, JULIAN;KETTSCHAU, CHRISTIANE;REEL/FRAME:014175/0664
Effective date: 20031125
|Oct 18, 2010
|Fee payment
Year of fee payment: 4
|Aug 26, 2014
Owner name: SAP SE, GERMANY
Free format text: CHANGE OF NAME;ASSIGNOR:SAP AG;REEL/FRAME:033625/0334
Effective date: 20140707
|Sep 29, 2014
|Fee payment
Year of fee payment: 8


text:
Monarch Mirror Door bottom track
A home owner from Ojai, CA says:
July 16, 2012
I have two bronze/brown colored Monarch mirror double closet doors # AF G-1 5 1789 (which I assume was installed in 1989). One of the tracks is no longer functional and needs to be replaced, but I can't find anything suitable. I'm attaching photos of the track that still works.
A home owner from El Paso, Texas says:
July 18, 2012
I need a replacement track in brass 72" for a Monarch Sliding Door. The wheels are concave. What do you suggest would work for the track?
Tom from SWISCO responded:
July 20, 2012
Thank you both for your patience in this matter. We have not found a replacement for this type of mirror door track at this time, but we are still investigating possible solutions. We will post again in this thread should any information become available for you. Again, we appreciate your patience.
Donna from SWISCO responded:
October 16, 2012

subset: commoncrawl


text:
The title of ''Let's Get Frank,'' Bart Everly's admiring portrait of the pugnacious Massachusetts Congressman Barney Frank in action, is somewhat misleading. ''Let's Get Bill'' might be a more accurate name for a movie that concentrates on this Democratic Representative's aggressive defense of Bill Clinton while sitting on the House Judiciary Committee in 1998.
The film's narrow focus on his public life during the impeachment hearings will disappoint those expecting a fleshed-out biography of the man who made his sexual orientation public in 1987 and subsequently survived his own sex scandal.
Although his mother, Elsie Frank; his sister, Ann Lewis (director of White House communications for Mr. Clinton); and his partner, Sergio Pombo, put in cameo appearances, the documentary, which opens today at Film Forum in the South Village, has no interest in exploring Mr. Frank's family background or love life. This frustrating lack of context leaves you wanting a lot more in the way of texture.
Mr. Frank points out that it was his weathering of his own embarrassing crisis in 1990 that allowed him to confront the Monica Lewinsky affair with more zest than trepidation. That was the year he was reprimanded for allowing a male hustler to use his office to promote prostitution. Mr. Frank confesses that the scandal embarrassed, depressed and angered him and says that his political survival gave him the courage to defend the president as vigorously as he did.
Especially in the wake of 9/11, it's uncomfortable to look back at the Lewinsky mediathon, which by comparison seems even more ado about less than it did six years ago. Mr. Frank is no smoothie. His bullish tenacity is matched by a gruff, tough-gay attitude, and he talks too fast. But he has a sharp sense of humor. And for a politician so outspokenly liberal, he is a blunt political realist who knows how to play the game.Continue reading the main story
Discussing Senator Trent Lott's comparison of homosexuality with alcoholism, sex addiction and kleptomania, he surmises that Mr. Lott doesn't really care one way or the other about the issue, that he is only attacking homosexuality to keep his right-wing constituents happy.
As for the impeachment itself, he says, it was a losing battle in a war his side won, since there was little chance of the Senate voting to convict the president. Mr. Frank's favorite metaphor for the furor surrounding the impeachment is a professional wrestling match, with its huffing and puffing and fakery. The hearings, he says, were a desperate battle in a cultural war in which the right wing dominating the Republican Party truly saw Mr. Clinton as leading the country toward depravity.
His step-by-step description of how the anti-Clinton forces set out to destroy the president is an astute, Congressional insider's take on political strategy. When anti-Clinton forces could offer nothing more than unprovable charges of Mr. Clinton's misconduct, they were forced to concentrate on perjury and the definition of sex.
The film awkwardly sandwiches the drama of the hearings (many of the clips are taken from C-Span) with recycled tidbits of right-wing homophobia: the Rev. Jerry Falwell's condemnation of the Teletubbies for alleged gay advocacy, and former Representative Dick Armey's public slip of the tongue in referring to Mr. Frank as ''Barney Fag.''
All the sturm und drang hasn't destroyed Mr. Frank's faith in the people's tolerance and common sense. ''Most Americans aren't nearly as homophobic as they were brought up to think they were supposed to be,'' he says. And the relative lack of public hysteria around the issue of gay marriage suggests he may be right.
Produced and directed by Bart Everly; edited by David Dawkins; music by the Angel; released by Random Productions. At the Film Forum, 209 West Houston Street, west of Sixth Avenue, South Village. Running time: 75 minutes. This film is not rated.Continue reading the main story


text:
Re: Charles and Matthew McClurg of Co. Down
In reply to:
Charles and Matthew McClurg of Co. Down
Adrian Rea 6/09/08
Hi Adrian,Yes, it always appears that when one little bit of information is found, it opens up two additional questions. But to keep stirring the pot, something always seem to turn up.
The information on your Charles is of recent times but the name Charles may be a bit significant in the over all picture of these McClurgs.
Here's my sad story.Henry McClurg b 1833 in Mercer County PA finally migrated West and by 1862, he had settled in the State of Wasington. He was the first Supertendient of Schools for Snohomish Co WA. He and his Indian Bride, Martha founded the town of Monroe, Washington.
In later life, Henry went over to Vancouver Island, with his son James McClurg. He died here and is buried at the St. John's Angelican Church yard at Cobble Hill. Henry McClurg's father was William McClurg who came from Limavady, Ireland to Mercer County PA prior 1800.
I have searched and found the names of most of Henry's children and probably there are none of his family living.
And at my level of recording genealogy, I have documented Henry fairly well. Until......I find that Henry died in 1908 and buried in row 1 grave 15. In row 1 grave 13 is Charles McClurg b. 1803 and died 22 Jan 1920, and in row 1 grave 14 is Lousia b.1806 died 22 Jan 1919.
So I found the answer to my question as to where and when Henry died and was buried, but this opens two more questions, who is Charles and who is Lousia, they definitely are not the parents of Henry McClurg. And if you do the math on those grave markers, one lived 117 years and the other 113 years. They both out lived this Henry McClurg b 1833.
I surmise Charles McClurg must be from Ireland who came into America at aboutthe time that Joseph & William of Mercer Co PA did. I do not know when William and Margaret McClurg married, so this birth date of 1803 could place him as their son born in Mercer, and an Uncle to the Henry McClurg buried at Cobble Hill, BC.
Therefore, when I see those repeating first names of the McClurg's of Northern Ireland showing in your charts as well, I highly suspect that the name Charles indicates all these folks mentioned are someway related to you as well.
Charles is a name that is mainly from McClurgs of Northern Ireland. It takes a lots of pounding to get a brick knocked loose from the brick wall.
It may seem strange to many that some McClurgs went to Canada from the North of Ireland since most of them all went to Philadelphia and then walked across PA to wherever their relatives had settled.
After reading a letter written by William McClurg in 1839 back home to Ma and Pa about his trip across the north Atlantic in a scooner for America did I find the reason why some did get off the scooner when it came to Nova Scotia.
William said they were becalmed for two weeks in the North Alantic. All were sea sick and when that wind did pick up and send them on to Nova Scotio, about half the passengers got onto land for good. William wanted to walk the rest of the Way to PA to join his brother in Mercer County, PA. but instead went on by scooner to Philly and then hiked across country to Westmoreland Co PA when Uncle James lived and then on up to Mercer County.
There is much data out there on the McClurg surname. But it's from these bits of info that sooner or later we break these brick walls.
William T.
More Replies:
Re: Charles and Matthew McClurg of Co. Down
Adrian Rea 6/18/08


text:
- Home
- Microsoft Office Miscellaneous Training Seminars
- Office 2007 Transition Overview CCE-566
Office 2007 Transition Overview CCE-566
Have you recently upgraded from an earlier version of Office to 2007? If you are a frequent user of the earlier versions, but want to ease into the new features and application integration available with Office 2007 this workshop is perfect for you!
- Course Outline
Have you recently upgraded from an earlier version of Office to 2007? If you are an experienced, frequent user of the earlier versions, but want to ease into the new features and application integration available with Office 2007, then this workshop is a perfect fit for you! The primary focus will be on Word and Excel; however the 2007 layout and new ribbon tools are common across applications.
- Prerequisites & Certificates
Basic understanding of Microsoft Office 2003 or earlier products.
Certificates offered
A letter outlining your participation in the course.
- Cancellation Policy
Participants who withdraw or fail to find a substitute less than 5 business days before the start of their course will be charged a fee based on the workshop duration as follows:
- $50 --- half-day workshop
- $100 --- one-day workshop
- $150 --- two-day workshop
Participants may withdraw or transfer to a different workshop 5 business days or more before the start of the workshop at no penalty. Individuals must notify the Centre for Continuing Education in writing to withdraw from a workshop.
Substitutions for a paid registration are welcome at anytime. The Centre for Continuing Education reserves the right to substitute qualified instructors due to unforeseen circumstances
- Map & Reviews
McMaster University CCE
[ View Provider's Profile ]
ReviewsHere are some reviews of the training vendor.
This course has not yet been rated by one of our members.
If you have taken a course through this vendor please log into your account and leave feedback for this vendor. You will be helping ensure our members get directed to the best training facilities.
This course currently does not have any dates scheduled. Please call 1-877-313-8881 to enquire about future dates or scheduling a private, in house course for your team.
This page has been viewed 140 times.


text:
Jae'Sean Tate, Ohio State throttle Northeastern, 80-55
Jae'Sean Tate made all 10 of his shots from the floor and had a career-high 24 points to lead Ohio State to a 80-55 win against Northeastern on Sunday.
Jae'Sean Tate made all 10 of his shots from the floor and had a career-high 24 points to lead Ohio State to a 80-55 win against Northeastern on Sunday.
Isaac Copeland had 19 of his 30 points in the first half and Nebraska opened up an early double-digit lead and defeated North Dakota 92-70 on Sunday.
Eugene Omoruyi came off the bench to score 19 points and grab eight rebounds while Corey Sanders added another 13 points off the bench to lead Rutgers past Coppin State 64-39 on Sunday at the RAC.
On a crazy weather day across the Big Ten, Wisconsin made a statement with a methodical win vs. Michigan, staying unbeaten and keeping playoff hopes alive. Ohio State blasted Illinois and in the process won the Big Ten East. Here is the Best of Week 12.
Before we turn our attention to Week 13, it's time to revisit how BTN.com senior writer Tom Dienhart and Big Ten fans did with their Week 12 Big Ten game predictions.
Maryland orchestrated a furious comeback after being down 15 at half to win 80-78 over Bucknell to move to 4-0.
No. 19 Purdue torched the nets against Fairfield Saturday, setting a new school record with 19 3-pointers made in a 106-64 win.
No. 13 Penn State blew out Nebraska, 56-44 on Senior Day as running back Saquon Barkley set Penn State's program rushing TD record with No. 39.
No. 17 Michigan State snatched win No. 8 this season with a snow-stricken 17-7 win over Maryland Saturday.
No. 8 Ohio State walloped Illinois, 52-14, to secure a spot in the Big Ten Championship game against Wisconsin.


text:
Nearby points of interest
Distance: 0.22mi
Distance: 0.24mi
Distance: 0.30mi
Distance: 0.46mi
Distance: 0.22mi
Distance: 0.24mi
Distance: 0.30mi
Distance: 0.46mi
Nearby points of interest
Distance: 0.22mi
Distance: 0.24mi
Distance: 0.30mi
Distance: 0.46mi
Distance: 0.22mi
Distance: 0.24mi
Distance: 0.30mi
Distance: 0.46mi
About The Melting Pot - Virginia Beach
The Melting Pot offers an extraordinary dining experience that you won't find at any other restaurant. Here you'll discover all of the ingredients to a perfect evening, including a relaxed atmosphere, private tables, attentive service, fine wines and fabulous four-course fondue dinners. No matter what the occasion from a romantic date to get-togethers with friends, meetings or large groups, The Melting Pot is certain to please. Make reservations today and come dip into something different.
Virginia Beach, VA 23451
Dining Style:
Casual Elegant
Hours of Operation:
Dinner: Monday - Thursday: 5:00pm - 11:00pm, Friday: 5:00pm - 12:00am, Saturday: 4:00pm - 12:00am, Sunday: 4:00pm - 10:00pm
Dress Code:
Business Casual
Price Range:
$31 to $50
Payment Options
AMEX, Diners Club, Discover, MasterCard, Visa
Phone Number:
(757) 425-3463
Parking Details:
Shopping Center Parking
Bar Dining, Full Bar, Gluten-free Menu, Late Night, Private Room, Wheelchair Access, Wine
Restaurant Photos
The Melting Pot - Virginia Beach Ratings and Reviews
Food was good, the cheese appetizer we had the bourbon cheese. A bit strong, maybe less bourbon mixture. Server was attentive at first, but rarely seen as the meal progressed. She said she'd been there a year, couldn't tell. Because of her mistake the main course had trouble when the burner turned off in the middle we noticed toward the end when the food was taking longer to cook. The waitress forgot items we requested throughout, but overall we will go again. This just happened to be a blip for us.
We celebrated our one year anniversary on Saturday and could not have been more thrilled with our experience. Samantha was our server and she was absolutely amazing. She explained everything to us and even brought a plate that said "happy anniversary" on it. We left with a full stomach and a huge smile on our faces. We will be back!
The Melting Pot has a great ambiance. The food is mediocre, but the table side service makes up for it. Our cocktail drinks were not worth it at all as they were 99% soda. When we asked whether there was alcohol in the drink, our waiter said we could buy another shot if that was the case.
Brought my girlfriend here for her birthday dinner and it was phenomenal. We were greeted with smiles as soon as we got to the door. Our server was friendly and very patient with our group. Overall I we really enjoyed our time at the Melting Pot and plan on coming back again very soon.
Went earlier to celebrate our 17th Wedding Anniversary. Very disappointed � Started the moment we entered the establishment, nobody out front, people waiting to be seated. Someone did come out and when it was our turn this guy (not sure if manager or supervisor) asked our last name, we told him then few minutes later he looked at us and asked for our last name AGAIN. We were right in front of him the whole time! When we got seated, server seemed bored out his mind to be there. Super slow service. Menu is confusing and didn't help that server didn't bother making it easy for us. Overall will never be back and definitely will not recommend.
I loved this restaurant for our 40th anniversary dinner. It was romantic and cozy. The dinner was excellent and fun! We loved cooking our own food. The dinner was delicious and fresh. The waiter was extremely attentive and the whole experience was wonderful. Would totally recommend to anyone.
Great experience. Only one thing I wold change. My wife and I were seated directly behind the kitchen and there was a continual grinding noise we could hear through the walls. We were told by our amazing waitress the sound was from heating water in the kitchen. Our waitress was apologetic and offered to move us after our desert, which we declined. We were cozy and already half way through our meal. Overall great time but there shouldn't have been noise of that magnitude distracting from the experience and the overall ambiance.
Food was great! We were celebrating my husband's birthday, and they brought out a cute plate at the end that said happy birthday in chocolate. We had a 4 course meal, fondue was very fun and different. I gave them 4 stars because I they had a flight of wine that was supposed to go with each course. The server forgot the glass that went with the salad, and when I mentioned it, he denied one went with the salad (I'm passive so I assumed I was wrong)...next thing you know I'm having a ton of wine at the end to make up for the fact that he did indeed forget a glass. Wasn't able to enjoy the flight like it was ment (a pairing with appetizer, salad, main course then desert), but other than that the experience was excellent.
I have been going to the melting pot for 11 years, never have I walked out hungry, until October 13th. The portions are now so small and not worth the price that is charged. The quality of the food was also questionable and did not have good flavor. The whole experience was poor and I'm highly disappointed.
The food was good, but I think it is overpriced. The waitress added wine to the cheese and we did not like the strong taste of wine. The chocolate was outstanding, but it seemed there wasn't enough to share for our table. I do not have any plans on going back due to the price. The service was outstanding!
It was our first time coming to Melting Pot and it was my boyfriend's birthday. Our waiter's name was Josh, and he was wonderful. Friendly, struck up conversation without being overbearing, and when there was a miscommunication about what I ordered, he went ahead and gave me what I thought I was missing, even though it was my mistake. The food was wonderful, atmosphere was romantic and quiet. Thank you for a great date :)
Expected bit more for the celebration package. It was my wife's birthday and I had called the restaurant upfront, told them the occasion and took the celebration package. We got a wineglass with few chocolates when we reached there. And when a 4X6 photo when we left the restaurant. That's it; was expecting birthday cake, waiters singing happy birthday to cheer up the occasion etc.
Also, there were long wait times between keeping the ingredients on the table and waiter turning up to explain how things work and turning on the stove.
The person at the reception was courteous to find a quite table for us.
Overall experience was different but don't think we will visit there again.
We have been coming to the Melting Pot for years, but this time our waitress seemed almost non-existent. Took quite awhile before she saw us the first time, and kept apologizing. Then after taking our drinks, she was missing again for awhile. This became a common occurrence on this latest venture to your establishment.
Once the cheese fondue was finished we sat around for an extremely long time before our entree broth was made. Way much longer than is normal.
The bottle of wine couldn't be opened at the table, which I can understand, but no cork or tasting it before simply pouring both our glasses. I asked for another bowl of veggies during our entree portion of the meal and it took 30 minutes before someone, who wasn't our waitress, came by and dropped them off. I love the veggies and tend to get multiple servings during the meal but I had to restrain myself because we didn't want to wait longer to get out. We were there almost 3 hours, which had never happened before. We had told our sitter we would be there roughly 2 hours or so, but all these delays just dragged out our dining experience.
Still enjoy the location, but the server was very substandard this time and made the experience lack luster. I would be turned off from coming back if I hadn't come here before.
Please sign in to record your input. Thanks!
Report this review as inappropriate?
If you believe this review should be removed from OpenTable, please let us know and someone will investigate.


text:
We help you locate a Sandy ukulele tutor. Ukulele lessons are the perfect way to begin an entertaining new hobby, pick up a new talent and gain confidence in ukulele. Try our service to find Sandy ukulele teachers and choose which best matches your needs so you can enjoy your ukulele lessons in Sandy today!
First Tutors: Music is the only place to discover Sandy ukulele teachers in the UK, helping you discover Sandy ukulele tuition close to home and Sandy teachers to help with any instrument like piano, violin or guitar. We can help you find Sandy ukulele lessons or a Sandy ukulele tutor to prepare for ukulele grades and improve your ukulele skills! We order Sandy ukulele tutors in your area by their lesson prices and distance from you.
If you are a ukulele teacher wishing to offer your ukulele tuition services in Sandy or throughout the UK, please register with First Tutors: Music or learn about us here. Becoming a Sandy ukulele tutor is a great way to improve your own skills by providing ukulele lessons while assisting someone else, all in the Sandy area!


text:
Create a "two shot" in which two subjects share an experience.
Putting two people into a frame is a way to generate drama or comedy no matter what kind of film you're making.read more →
"" "
Putting two people into a frame is a way to generate drama or comedy no matter what kind of film you're making.read more →
If you want to create professional looking videos, limit the length of most of your shots. The sweet spot will usually be between 3 and 7 seconds. The payoff will be shots that are stronger and better looking. You'll also have a much easier time editing.read more →
While there are exceptions, mobile movies will almost always look better if they're shot in the wide orientation: horizontally rather than vertically.read more →
End your project with a real movie ending, something that audiences will remember.read more →
To show your audience immediate that you've made a real movie start with a close-up. The image may surprise or puzzle viewers, but for sure it'll grab their attention and make them want to watch more.read more →
This free online course will teach you how to shoot movies that will delight audiences. We will cover every kind of project including travelogues, family documentaries, commercials, music videos, and vblogs. All it takes is 1) a smartphone (or other mobile), 2) the desire to make a short movie, and 3) mastery of about 100 simple techniques. How simple? Here's anread more →


text:
Silver Lace with Blue Crystal Stretchy Bracelet
Feshionn IOBI
Silver Lace with Blue Crystal Bead Bracelet features a stretchy bracelet with blue crystal beads surrounded by sterling plated lacy filigree. Also available in additional colors. Great for gift giving and stacking!
Stretchable to fit most wrist sizes.Material: Crystal Beads. Silver Plated.


text:
Duration: 3min 01sec Views: 9 399 Submitted: 6 years ago Submitted by:
Description: Ravishing tanned MILF with big round melons Tara Holiday loves being drilled long and hard. She is lying on a bed on her tummy with her ass up in the air. Her man sticks his thick boner deep in her wet pussy and bonks her hard.
Channel: Naughty America
Pornstars: Tara Holiday


text:
Looking for a custom Rainmaker theme? Brilliant. Please read on…
The Rainmaker Platform is an online business platform built to handle almost anything you could want in one place.
It handles everything from basic website pages to podcasts, landing pages, memberships and even marketing automation.
The best part is that it is built on the back of WordPress and the Genesis Framework, two of our favourite things in web development.
We live and breathe Genesis, which translates directly onto the Rainmaker Platform.
While they provide a large number of pre-made templates, you are probably looking for something a little more custom. Something that is unique to your business and matches your brand.
The good news is that custom themes are totally OK on Rainmaker.
That said, they have set some pretty strict development standards that developers have to stick to. We've got a big list of things that we go through to make sure our Genesis child themes are ready for Rainmaker.
Use the form below to let us know you are looking for a Rainmaker theme. Name and email are fine, but if you have more info pop it in too.


text:
Home » Racing Games » Bloody Racer
Play online some of the most challenging games Bloody Racer. Just avoid traffic cars to get points. Kill pedestrians to get more points. Drive as far as You can without crash. There is no rules in these bloody games. The only one is to stay alive and destroy everything around on your way not leaving anyone alive. Play bloody racing games - it is just virtual. Have fun!
Please log in to favorite.
Added: 6 August 2015 | Played: 1,924 times
Bloody Racer


text:
(36 reviews)
Lowest price to-date!
Get the LEGO CITY Van & Caravan right now for $19.87!
Search for cart fillers for items to help you reach the $35 FREE Super Saver Shipping level. Or if you haven't yet tried Amazon Prime, sign up for a 30-day trial and get FREE 2-day shipping!


text:
Screen Printed Tshirts
"A picture can say a thousand words!" So can your custom screen printed tshirt at Garment Graphics!
Custom Screen Printed Tshirts by Garment Graphics!
Trust your custom apparel to Garment Graphics
- Apparel and Screen Printing Expertise
- Highest Quality at Competitive Prices
- Awesome Custom Graphic Design
- Great Stock Designs
- Innovative Techniques
- Low Minimums (12 Pieces)
- Fast Turn Around and Reliable Service
- No Screen Charges
Call or Email Us about your project today!
(520) 544-0529 or Screen Print Project Inquiry
At Garment Graphics every screen printing project has it's own unique purpose. Our job isn't just to print a t-shirt or take an online order using preset graphics; we have the expertise to help you accomplish the goals behind the t-shirt. The relationship with our client is more important than the order.
Innovative products and techniques:
- Traditional and Waterbased Inks
- Combination Printing
- Simulated Process Printing
- Process Printing
- Discharge Printing
- Combine Screen Printing and Embroidery
- Name Brand Apparel
- Tie Dyed
- Camo
- Burn Out Tees
- Performance Apparel
Looking for VBS Shirts? Click the I Love VBS image
No posts found


text:
In a statement, the former President pointed out that "though I have never aspired to serve another term or shown interest in contesting the elections", the Trinamool Congress and other political parties "wanted me" to be the candidate.
"Many, many citizens have also expressed the same wish. It only reflects their love and affection for me and the aspiration of the people. I am really overwhelmed by this support. This being their wish, I respect it. I want to thank them for the trust they have in me," he said.
"I have considered the totality of the matter and the present political situation, and decided not to contest the Presidential elections 2012," Kalam added.
West Bengal Chief Minister Mamata Banerjee and Mulayam Singh Yadav of the Samajwadi Party had proposed three names including that of Kalam on Jun 13.
Though the latter changed his stand a day later, the Trinamool Congress supremo continued to back Kalam even after the UPA, of which her party is a constituent, announced that Finance Minister Pranab Mukherjee is their candidate.
The opposition too tried to persuade Kalam to contest and BJP leaders met him several times in this connection. Apparently he was not convinced by their arguments.
The BJP still has the option of aiding BJD and AIADMK in their efforts to get PA Sangma elected as the first citizen of the country. However, this could lead to a split in the NDA as parties like the Shiv Sena and the JD(U) are reportedly not in favour of supporting the NCP leader.
Incidentally Sangma's own party has asked him to back out from the race but he has refused to heed them. As long as he remains in the fray, Pranab's unanimous election is not possible.
OneIndia News


text:
As Lubbock and the West Texas Municipal Power Agency look for new power sources before a 2019 deadline, a planned natural gas power plant more than 100 miles south isn't on the radar screen.
The 726-megawatt, gas-fired power plant set for completion near Colorado City in 2016 has the capacity to meet the needs of Lubbock and the agency's four other member cities.
But the power plant's builders have no plans to sell the gas plant's energy to Lubbock or the WTMPA, and area leaders say they have yet to consider the plant as they prepare to go shopping to build or buy power resources as soon as this summer.
"I haven't heard mention of that plant," said Lubbock Electric Utility Board Vice Chairman Emilio Abeyta, who described Lubbock Power & Light's efforts working with WTMPA to find new power sources. "There are so many variables and so many options and we haven't made any decisions."
Colorado City plant
The planned gas power plant in Colorado City is designed for and contractually marketing to meet the needs of the northern and western areas of the Electric Reliability Council of Texas power pool, which includes most of Texas but excludes Lubbock and the Panhandle, said Ross McCausland, president and CEO of Amarillo-based Protos Energy Advisory, a partner in the project.
"Therefore, it is not suitable for serving requirements load for the West Texas Municipal Power Agency, which are located in the adjacent Southwest Power Pool," he said in an email to the Avalanche-Journal on Friday, March 22. "As such, we do not have plans for discussions with either WTMPA or LP&L about the Colorado City project due to its location."
Protos Energy and FGE Power of Houston announced the Colorado City project March 11.
"The project marks a major milestone in providing for the growing need for clean and affordable power in Texas," Emerson Farrell, president and CEO of FGE Power, said in a statement. "We are now one step closer toward that goal, and one step closer to bringing about a great economic opportunity in the Mitchell County community to which we all owe a great amount of gratitude."
The combined-cycle power plant will be one of the most efficient among gas plants in ERCOT, have class-leading environmental performance for a facility of its type, and possess a unique dispatch flexibility to respond to ERCOT's large wind resource and peak load demands, he said.
"The project is simply a perfect fit for the Texas marketplace at a time in which new resources are critical," Farrell said.
Mitchell County provided the land for the plant, which will benefit from on-site high voltage power lines, and will have plentiful access to natural gas from the area's rapidly developing Cline Shale formation, he said.
In his email Friday, McCausland said his organization is aware of the current contract expiration schedule of the WTMPA/Xcel agreement and potential need created by that event.
"Should the WTMPA desire to discuss suitable resource options within the (Southwest Power Pool), we are advancing a number of generation development projects within the South Plains region that are available for discussion with either WTMPA or LP&L at their discretion in the near future," he said.
Cost and distance likely would have made the Colorado City plant an unrealistic option for the power agency, said President Gary Brown.
The estimated $100 million price tag to build transmission infrastructure connecting agency cities to the proposed plant or any plants in the Electric Reliability Council of Texas grid "wouldn't necessarily make it cost prohibitive," but closer, cheaper options are the more likely goal to provide WTMPA-member cities with power, Brown said.
WTMPA's future
On Tuesday, March 19, a power consultant laid out options for the WTMPA, from building new gas-fired power plants to going to the market to buy power ahead of a 2019 deadline to replace the agency's expiring purchased-power agreement with Xcel Energy.
"This is more of a general direction of what we're going to be looking at as we approach 2019," Lubbock Mayor Glen Robertson said during the agency's meeting.
Robertson on Friday, March 22, said he expects the board will issue requests for proposals in April or May to see what the agency's options are for another purchased-power agreement to prevent incurring the debt of building its own power capacity.
Utility board and power agency leaders should have responses from companies by year's end.
The question then is how to go about funding another purchase-power agreement or power plant — a decision that could make the power agency a moot point, Robertson said.
"It's a decision that needs to be held at the WTMPA level," Robertson said. "Is Lubbock going to build the plant or, if WTMPA builds the plant, (the agency is) going to stick together."
If Lubbock builds the plant, Robertson said, WTMPA cities could enter into a contract to purchase power from the city.
"We're definitely tied in with WTMPA through 2019," Robertson said.
If Lubbock spearheads the funding, through municipally owner Lubbock Power & Light, Brown said he envisions the options for WTMPA-member cities to purchase power through LP&L instead of Xcel. "We wouldn't have to dissolve WTMPA," he said, adding being in the association "shows cohesiveness" among member cities.
On Tuesday, agency board members heard a presentation from Black & Veatch, an Overland Park, Kans., -based firm, which the agency hired last fall to lay out an integrated research plan looking at the agency's projected energy needs and solutions.
For building new generation plants, Black & Veatch focused on natural gas power because of that energy source's low estimated cost projections, availability and relatively low pollution, said Scott Williams, Black & Veatch's managing director.
Options for building gas-fired plants range from $420 million to build three simple-cycle gas plants producing 570 megawatts to $575 million for one combined-cycle plant producing 575 megawatts, according to the presentation.
The agency's four member cities — Lubbock, Brownfield, Floydada and Tulia — are projected to need about 550 megawatts of power production by 2019, with that number expected to increase above 700 megawatts by 2040, according to estimates provided by the agency.
The agency's power capacity will be 114 megawatts after the purchased-power agreement with Xcel ends in 2019, leaving the agency to search for alternatives through building power capacity or finding it elsewhere
Brown, who serves on the board as Floydada's city manager, said he was open to hearing options but is leaning toward purchasing power instead of building power plants, in part, to avoid incurring debt.
"That's if we can get the right company and get a long-term purchased-power agreement," Brown said.
To comment on this story:
• 766-8725
• 766-8706


text: In the Camera app there used to be a bracket that showed where the focus of the picture is going to be and I could move it around to choose where I want it to focus, but I no longer see that. It still autofocuses, but does not show the bracket at all. Any ideas on why this is? Thanks!


text:
How is fasting going for you so far this year, if you are fasting?
How is fasting going for you so far this year, if you are fasting? Have you fallen into a rhythm yet? :) If you are not fasting this year how is that affecting you?
Alhamdullilah my fasting is starting to fall into the familiar lightness I remember from years past, though the first 2 days were pretty hard with bad headaches! It is fun this year because my son is old enough to be very enthused, though he gets a little confused about when Eid is coming and keeps expecting it! He wished our neighbor Eid Mubarak and Ramadan Mubarak this afternoon :)
|All times are GMT -7. The time now is 08:57 AM.
Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2017, vBulletin Solutions, Inc.
Search Engine Optimization by vBSEO 3.6.0
Copyright © 2003-2012 JustMommies.com, All Rights Reserved.