######################################################################
# This messages file is intented for use by the SSA Connector.
# It follows the same numbering scheme as the CwConnectorAgentMessages.txt
# file described below.
######################################################################
# The CwConnectorAgentMessages.txt, in the %CROSSWORLDS%\Connectors\Messages\ 
# directory, contains generic message numbers and text for all connectors 
# in the CrossWorlds System. Each connector uses a range of message numbers, 
# with a range of numbers reserved for generic messages common to all connectors. 
# This file includes a comment line to separate connector to specify the range 
# of message numbers for that connector.
#
# Messages have the following form:
#
# number
# text
#
# 'number' is the message number and must appear on one line.
# 'text' is the message text and can span multiple lines, with a
# carriage return terminating each line. An example follows:
#
# 2125
# Business object definition "{1}" does not contain any attributes.
#
# The {} characters enclose a parameter. The number of parameters in a
# message is unlimited; however, a parameter marker cannot be divided
# across lines. The CrossWorlds System maintains an internal array of
# parameter values. The number within the marker identifies the
# position of the parameter in the internal parameter array. If this
# text were written in another language, the parameter marker's
# position could change to accommodate the language rules. Each
# CrossWorlds System should include an ConnectorMessages.txt file for
# every supported language.
#
# This file also contains explanations for some messages, such as the
# explanation for message 2125:
#
# [EXPL]
# A business object definition must contain at least one attribute.
#
#
# ****** Notice that the text line cannot start with a number.
#
#
# USAGE:
# 
# Use the message number in your C++ code for message loggin and/or tracing,
# by providing the message number to the generateMsg() method before logging 
# the message using logMsg() or traceWrite()
#
# Example:
#
# generateMsg(int msgID, int msgType, char * info, int argCount, va_list vl)

# logMsg(generateMsg(20017, CxMsgFormat::XRD_FATAL, NULL, 0, NULL));
#
# where the first parameter is the message number for a message defined in this file, 
# the second parameter is a message type with the following valid values:
#
# XRD_UNKNOWN, XRD_WARNING, XRD_ERROR, XRD_FATAL, XRD_INFO, XRD_INT_WARNING, 
# XRD_INT_ERROR, XRD_INT_FATAL, XRD_INT_INFO, XRD_TRACE
#
# the third parameter is information string, followed by the number of 
# arguments passed to generateMsg(), and finally a variable list of arguments.
#
# All arguments must be passed to this method as character strings only.
#
# The range for CWConnectorAPI messages is between 10000 and 11000
# 10000-10250 - CWConnectorAgent
# 10251-10500 - CWConnectorBusObj
# 10501-10750 - CWConnectorBOHandler
# 10751-11000 - CWConnectorUtil
######################################################################




######################################################################
#
# SsaAgent Messages
#
######################################################################
50001
Initializing the SsaAgent...

50002
The SsaAgent retrieved the following properties from the product information properties file:
 ProductName = {1}
 Version = {2}
 PatchLevel = {3}
 BuildNumber = {4}
 BuildGuid = {5}
 BuildDate = {6}
 BuildUserName = {7}
 SourceConfiguration = {8}
[EXPL] {1}="ProductName"
[EXPL] {2}="Version"
[EXPL] {3}="PatchLevel"
[EXPL] {4}="BuildNumber"
[EXPL] {5}="BuildGuid"
[EXPL] {6}="BuildDate"
[EXPL] {7}="BuildUserName"
[EXPL] {8}="SourceConfiguration"

50003
The SsaAgent could not establish a connection with the backend.

50004
The SsaAgent could not start the Java Method Execution Server.
 Technical Details: {1}
[EXPL] {1}="Stack trace of exception."

50005
SsaAgent has been successfully initialized.

50006
Terminating the SsaAgent...

50007
The SsaAgent has been terminated.

50008
The SsaAgent encountered an exception while terminating.
 Technical Details: {1}
[EXPL] {1}="Stack trace of exception."

50009
The SsaAgent is receiving an event...

50010
The event handling thread was stopped asynchronously. 
 Technical Details: a java.lang.ThreadDeath exception was thrown.

50011
An unexpected exception was caught in the event handling thread.
 Technical Details: {1}
[EXPL] {1}="Stack trace of exception."

50012
The SsaAgent could not retrieve a valid license for the SSA TA Connector for WBI.



######################################################################
#
# SsaAgentProperties Messages
#
######################################################################
50101
The connector property "{1}" is not specified or has an empty value in the connector specific properties.
 Please, check the connector configuration properties with the Connector Configurator tool in the system manager.
 Technical Details:  {2}
[EXPL] {1}="Name of Property."
[EXPL] {1}="Stack trace of exception."


50102
The connector property "{1}" is not specified or has an empty value in the connector specific properties.
 THIS MAY BE INTENTIONAL since the property value is not required.  If it is not intentional, please check the
 connector configuration properties with the Connector Configurator tool in the system manager.
 Technical Details:  {2}
[EXPL] {1}="Name of the method."
[EXPL] {1}="Stack trace of exception."




######################################################################
#
# SsaProductInfo Messages
#
######################################################################
50201
The SsaProductInfo class could not retrieve the Product Information Properties from
 the properties file.
 Technical Details: {1}
[EXPL] {1}="Stack trace of exception."

50202
The SsaProductInfo class could not retrieve the value for: {1}
[EXPL] {1}="Name of the property."




######################################################################
#
# SsaBOHandler Messages
#
######################################################################
50301
The SsaBOHandler could not initialize the transaction log.
 Technical Details: {1}
[EXPL] {1}="Stack trace of exception."

50302
The SsaBOHandler has received a request to process a verb (doVerbFor).

50303
The incoming business object {1} is null.
 Technical Details: The SsaBOHandler received a business object that is null.
[EXPL] {1}="The name of the received business object."  
 
50304
There is no active verb specified for the received business object ({1}).
 Make sure the active verb is neither null nor empty.
 Technical Details: The SsaBOHandler received a business object without an active verb.
[EXPL] {1}="The name of the received business object."

50305
The SsaBOHandler is processing a BO with the following structure: {1}
[EXPL] {1}="Structure of the business object." 




######################################################################
#
# SsaXMLBOHandler Messages
#
######################################################################
50501
The SsaXMLBOHandler is establishing the backend connection...

50502
The SsaXMLBOHandler has established the backend connection.

50503
The SsaXMLBOHandler is terminating the backend connection...

50504
The SsaXMLBOHandler has terminated the backend connection.

50505
The SsaXMLBOHandler encountered an exception while terminating.
 Technical Details: {1}
[EXPL] {1}="Stack trace of exception."

50505
The "{1}" attribute is not specified for the definition of the received business object.
 The business object (called the envelope) must have some specific attributes namely 
 the "Request" and "Response" attributes. 
 The SSA connector needs these attributes to create a call to the SSA enterprise information system. 
 The types of these attributes are references to the "Request" and "Response" business object definitions. 
 Check with the "Business Object Designer" tool the structure of the business object (envelope).
 The structure of the business object: {2}
 Technical Details: {3}
[EXPL] {1}="Name of the missing attribute."
[EXPL] {2}="Structure of the business object." 
[EXPL] {3}="Stack trace of exception."

50507
The Request business object could not be translated into a XML string document. 
 Technical Details: {1}
[EXPL] {1}="Stack trace of exception."

50510
The response business object could not be created.
 Technical Details: {1}
[EXPL] {1}="Stack trace of exception."

50511
The "Response" XML document received from the SSA enterprise information system could not be translated into a "Response" business object. 
 The structure of the XML document is: {1}
 Technical Details: {2}
[EXPL] {1}="XML document"
[EXPL] {2}="Stack trace of exception."

50514
It was not possible to update the business object with the response received from the SSA enterprise information system. 
 Technical Details: {1}
[EXPL] {1}="Stack trace of exception."

50518
A Functional exception was returned from the SSA enterprise information system.
 Technical Details: {1}
[EXPL] {1}="Stack trace of exception."

50519
A Connection exception was returned from the SSA enterprise information system.
 Technical Details: {1}
[EXPL] {1}="Stack trace of exception."

50520
When processing the business object a runtime exception occurred.
 Technical Details: {1}
[EXPL] {1}="Stack trace of exception."

50521
The "XML-connector" could not process the request from the business object envelope.

50522
The "XML-connector" could not setup a connection with the SSA backend during execution.
 Check the error response for more detailed information.

50523
The SSA enterprise information system could not process the request from the business object envelope.
 Check the error response for more detailed information.

50524
The SSA enterprise information system could not process the request from the business object envelope.
 Check the error response for more detailed information.

50531
The {1} locale could not be set in the Response Business object.
 Check if specified locale is supported for this business object.
 Technical Details: {2}
[EXPL] {1}="Locale"
[EXPL] {2}="Stack trace of exception."




######################################################################
#
# SsaBDEBOHandler Messages
#
######################################################################
50601
The SsaBDEBOHandler is establishing the backend connection...

50602
The SsaBDEBOHandler has established the backend connection.

50603
The SsaBDEBOHandler encountered an exception while establishing the backend connection.
 Technical Details: {1}
[EXPL] {1}="Stack trace of exception."

50604
The SsaBDEBOHandler is terminating the backend connection...

50605
The SsaBDEBOHandler has terminated the backend connection.

50606
The SsaBDEBOHandler encountered an exception while terminating.
 Technical Details: {1}
[EXPL] {1}="Stack trace of exception."

50609
A fatal processing error was returned from the SSA enterprise information system.
 Message Details: {1}
[EXPL] {1}="Message"

50610
A general exception was encountered.
 Technical Details: {1}
[EXPL] {1}="Stack trace of exception."

50611
The SsaBDEBOHandler is calling the SSA enterprise information system with the request...

50612
The SsaBDEBOHandler is finished calling the SSA enterprise information system with the request.

50613
The SsaBDEBOHandler is iterating the results from the SSA enterprise information system...

50614
The SsaBDEBOHandler is finished iterating the results from the SSA enterprise information system.

50615
The SsaBDEBOHandler is mapping an element to a business object...

50616
The SsaBDEBOHandler is finished mapping an element to a business object.

50617
The SsaBDEBOHandler encountered an exception while mapping a result to a business object.
 Attribute Name: {1}
 Technical Details: {2}
[EXPL] {1}="Attribute Name."
[EXPL] {1}="Stack trace of exception."

50618
The SsaBDEBOHandler encountered an invalid data type while mapping a result to a business object.
 Attribute Name: {1}
[EXPL] {1}="Attribute Name."

50619
The SsaBDEBOHandler encountered an attribute that is not part of the business object definition and will be ignored.
 Attribute Name: {1}
[EXPL] {1}="Attribute Name."

50620
The SsaBDEBOHandler is mapping a business object to an XML element...

50621
The SsaBDEBOHandler encountered an exception when mapping a business object to an XML element.
 Technical Details: {1}
[EXPL] {1}="Stack trace of exception."

50622
The SsaBDEBOHandler has successfully mapped a BO to an XML element with the following structure: {1}
[EXPL] {1}="Structure of the XML element." 

50623
The SSAERP returned an XML element with the following structure: {1}
[EXPL] {1}="Structure of the XML element." 

50624
The SsaBDEBOHandler is checking for non-fatal processing warnings or errors from the SSA enterprise information system...

50625
The SsaBDEBOHandler found a non-fatal processing warning or error from the SSA enterprise information system.
 Message Details: {1}
[EXPL] {1}="Message"

50626
The SsaBDEBOHandler did not find any non-fatal processing warnings or errors from the SSA enterprise information system.

50627
The SsaBDEBOHandler encountered an exception while checking for non-fatal processing warnings or errors from the SSA enterprise information system.
 Technical Details: {1}
[EXPL] {1}="Stack trace of exception."

50628
The SsaBDEBOHandler encountered an exception while mapping a message from the SSA enterprise information system to a fault message.
 Technical Details: {1}
[EXPL] {1}="Stack trace of exception."

50640
Error parsing xml. Technical information: the '{1}' element contains a
 non-text node.
[EXPL] {1}="The name of the element that should only contain text nodes."

50641
Error parsing xml. Technical information: the '{1}' element contains no text.
[EXPL] {1}="The name of the element that should have contained text."




######################################################################
#
# SsaEventHandler Messages
#
######################################################################
50701
A null event was received.

50702
An event was received that was not an XML document or an XML element.

50703
An empty event was received. Technical Details: the XML root node could not
 be found.

50704
Could not determine the type of the received event. Technical Details: the
 'ControlArea' element could not be found as a child of the root element.

50705
Error parsing event. Technical Details: the '{1}' element could not be found
 as a child of the '{2}' element.
[EXPL] {1}="The name of the element that could not be found."
[EXPL] {2}="The name of the parent element of the element that could not be found."

50706
The combination of verb "{4}" and business object "{3}" is not supported.
 Check if the business object {3} supports the "{4}" verb and check in the 
 SSA Connector properties if this "{3}" business object is listed in the supported business objects. 
 Check also if the SSA connector is bound to one or more Collaboration Objects.
 Technical information: The {2} function within the {1} method has thrown the "NO_SUBSCRIPTION_FOUND" exception. 
[EXPL] {1}="Name of the method."
[EXPL] {2}="Name of the function."
[EXPL] {3}="The name of the received business object".  
[EXPL] {4}="The name of the Supported verb".  

50707
The SSA Connector could not process the "{3}" event received from the SSA enterprise information system.
 The name of the verb is "{5}" and the locale is "{6}".
 Technical information: The {2} function within the {1} method has thrown the {7} as exception.
 The structure of the {3} document is: {4}.
 Detail error information: {8}
[EXPL] {1}="Name of the method."
[EXPL] {2}="Name of the function."
[EXPL] {3}="The name of the received business object".  
[EXPL] {4}="XML document".  
[EXPL] {5}="The name of the Supported verb".  
[EXPL] {6}="Locale".  
[EXPL] {7}="Exception type".  
[EXPL] {8}="Error message".  

50708
The SSA Connector could not send the "{3}" event received from the SSA enterprise
 information sysetm to the WBI Server. 
 Technical information: The {2} function within the {1} method didn't received
 a guarantee delivery status from the WBI Server.
[EXPL] {1}="Name of the method."
[EXPL] {2}="Name of the function."
[EXPL] {3}="The name of the received business object".  

50709
The SSA Connector could not send the "{3}" request received from the 
 SSA enterprise information sysetm to the WBI Server. Reason of failure is that the connector 
 is paused and therefore it is unable to receive documents. 
 Please send request document again. 
 The {2} function within the {1} method didn't received the guarantee delivery 
 status from the WBI Server.
[EXPL] {1}="Name of the method."
[EXPL] {2}="Name of the function."
[EXPL] {3}="The name of the received business object".  

50710
The SSA Connector is processing an event receiving from the SSA enterprise information system 
 for the business object '{1}' verb '{2}' messageId '{3}' locale '{4}'.
[EXPL] {1}="The type of the business object."
[EXPL] {2}="the name of the verb"
[EXPL] {3}="The messageId".
[EXPL] {4}="The locale".

50715
The "{4}" attribute is not specified for the definition of the received {3} business object.
 The business object must have the specific "{4}" attribute. 
 Check with the "Business Object Designer" tool the structure of the {3} business object.
 Technical information: The {2} function of the {1} method has received a {3} business object without 
 the required "{4}" attribute. 
 The {5} is thrown.
 Show the structure of the {3} business object: {6} 		
[EXPL] {1}="Name of the method."
[EXPL] {2}="Name of the function."
[EXPL] {3}="Name of the business object."
[EXPL] {4}="Name of the attribute."
[EXPL] {5}="Exception type."
[EXPL] {6}="Structure of the business object." 

50716
The "{4}" attribute is not of type string. 
 Check the structure of the {3} business object. 
 Technical information: The {2} function of the {1} method has received a wrong type as "{4}" argument. 
 The {5} is thrown.
 Show the structure of the {3} business object: {6} 	
[EXPL] {1}="Name of the method."
[EXPL] {2}="Name of the function."
[EXPL] {3}="Name of the business object."
[EXPL] {4}="Name of the attribute."
[EXPL] {5}="Exception type."
[EXPL] {6}="Structure of the business object." 

50740
The XML event document received from the SSA enterprise information system could not be 
 translated into a business object.  
 The structure of the XML document is: {1}
 Technical Details: {2}
[EXPL] {1}="Structure of the XML document."
[EXPL] {2}="Stack trace of exception."

50741
The {1} verb is not supported for this {2} business object.
 Check with the "Business Object Designer" tool which verbs are supported for the {2} business object.
 Technical Details: {3}
[EXPL] {1}="Name of the Verb."
[EXPL] {2}="Name of the business object."
[EXPL] {3}="Stack trace of exception."

50742
The {1} locale could not be set in the {2} Business object.
 Check if specified locale is supported for this business object.
 Technical Details: {3}
[EXPL] {1}="Locale"
[EXPL] {2}="Name of the business object."
[EXPL] {3}="Stack trace of exception."




######################################################################
#
# SsaBDEResult Messages
#
######################################################################
50851
A javax.xml.parsers.DocumentBuilder class could not be instantiated in the {1} class.
 Technical Details: {2}
[EXPL] {1}="Name of the class that tried to instantiate a DocumentBuilder."
[EXPL] {2}="Stack trace of exception."




######################################################################
#
# SsaVerbMapper Messages
#
######################################################################
50932
Error parsing event.
 Technical Details: the '{1}' element must contain a string starting with an ASCII letter
 (upper or lower case). Instead it was '{2}'.
[EXPL] {1}="Name of the element that cannot be parsed."
[EXPL] {2}="The value of the element."




######################################################################
#
# SsaLicenseHandler Messages
#
######################################################################
51001
Obtaining a license for the SSA TA WBI Connector...

51002
The license for the SSA TA WBI Connector has expired.
 Technical Details: {1}
[EXPL] {1}="License Message Details."

51003
The license for the SSA TA WBI Connector was obtained successfully.
 Host Name: {1}
 Expiration Date: {2}
[EXPL] {1}="Name of the Host."
[EXPL] {2}="Expiration Date of the License."

51004
The license for the SSA TA WBI Connector could not be obtained.
 Technical Details: {1}
[EXPL] {1}="License Message Details."

51005
The license handler for the SSA TA WBI Connector received notification of a license change.
 Reason: {1}
[EXPL] {1}="Reason for Notification."

51006
Checking the current license for the SSA TA WBI Connector.

51007
The current license for the SSA TA WBI Connector is valid.

51008
The current license for the SSA TA WBI Connector is not valid.
