You are not logged in.
Example of an Html formatted email body before rule application:
<div dir="ltr"><div class="gmail_quote"><div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm 0cm 0cm"><br>
<p class="MsoNormal"><u></u> <u></u></p>
<table border="0" cellspacing="1" cellpadding="0" width="100%" style="width:100.0%">
<tbody>
<tr>
<td colspan="2" style="background:#e0e0e0;padding:3.75pt 3.75pt 3.75pt 3.75pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">This is an auto generated e-mail triggered because of the following entities being monitored :
</span><u></u><u></u></p>
</td>
</tr>
<tr>
<td width="120" style="width:90.0pt;background:#cccccc;padding:3.75pt 3.75pt 3.75pt 3.75pt">
<p align="right" style="text-align:right"><span style="font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">Monitor</span><u></u><u></u></p>
</td>
<td width="580" style="width:435.0pt;background:#f9f9f5;padding:3.75pt 3.75pt 3.75pt 3.75pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">ho-vmspapp-01</span><u></u><u></u></p>
</td>
</tr>
<tr>
<td width="120" style="width:90.0pt;background:#cccccc;padding:3.75pt 3.75pt 3.75pt 3.75pt">
<p align="right" style="text-align:right"><span style="font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">Attribute</span><u></u><u></u></p>
</td>
<td width="580" style="width:435.0pt;background:#f9f9f5;padding:3.75pt 3.75pt 3.75pt 3.75pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">Health</span><u></u><u></u></p>
</td>
</tr>
<tr>
<td width="120" style="width:90.0pt;background:#cccccc;padding:3.75pt 3.75pt 3.75pt 3.75pt">
<p align="right" style="text-align:right"><span style="font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">Reasons</span><u></u><u></u></p>
</td>
<td width="580" style="width:435.0pt;background:#f9f9f5;padding:3.75pt 3.75pt 3.75pt 3.75pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">Health of ho-vmspapp-01 is critical</span><u></u><u></u></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><u></u> <u></u></p>
<table border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%">
<tbody>
<tr>
<td width="698" style="width:523.5pt;background:#aaaaaa;padding:3.75pt 3.75pt 3.75pt 3.75pt">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;;color:white">Root Cause</span></b><u></u><u></u></p>
</td>
</tr>
<tr>
<td width="698" style="width:523.5pt;background:#f9f9f5;padding:3.75pt 3.75pt 3.75pt 3.75pt">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">Root Cause :
<br>
1. Total Disk Utilization(%) 91 &gt; 90 (threshold).<br>
2. SharePoint Server Search 14 is down</span><u></u><u></u></p>
</td>
</tr>
</tbody>
</table>
<p style="margin:0cm;margin-bottom:.0001pt"><u></u> <u></u></p>
<table border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%">
<tbody>
<tr>
<td width="698" style="width:523.5pt;background:#aaaaaa;padding:3.75pt 3.75pt 3.75pt 3.75pt">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;;color:white">Additional information</span></b><u></u><u></u></p>
</td>
</tr>
<tr>
<td width="698" style="width:523.5pt;background:#f9f9f5;padding:3.75pt 3.75pt 3.75pt 3.75pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">This information has been generated by the Applications Manager</span><u></u><u></u></p>
</td>
</tr>
<tr>
<td width="698" style="width:523.5pt;background:#f9f9f5;padding:3.75pt 3.75pt 3.75pt 3.75pt">
</td>
</tr>
</tbody>
</table>
<p><u></u> <u></u></p>
<table border="0" cellspacing="1" cellpadding="0" width="100%" style="width:100.0%">
<tbody>
<tr>
<td style="padding:3.75pt 3.75pt 3.75pt 3.75pt">
<p align="right" style="text-align:right"><b><span style="font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;;color:#999999">Reported By :
<a href="9090?fea"" target=""_blank"">Applications Manager</a></span></b><u></u><u></u></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span style="color:windowtext"><u></u> <u></u></span></p>
<br>
<table border="0" cellspacing="0" cellpadding="0"><tbody><tr><td><img border=""0"" src="114021409091601043@za-mta-7.za.mimecast.lan"" /></td></tr></tbody></table>
<font face="arial" size="1">
<hr>
<b>Disclaimer</b>
<br>
Everything in this e-mail and any attachments relating to the official business of Acme Holdings Ltd. and its subsidiaries ('Acme') is proprietary to Acme. It is confidential, legally privileged and protected by law. Acme does not own and endorse any other content.
Views and opinions are those of the sender unless clearly stated as being that of Acme. The person addressed in the e-mail is the sole authorised recipient. Please notify the sender immediately if it has unintentionally reached you and do not read, disclose or use the content in any way.
Acme cannot assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference.
<br>
</font>
<hr>
<table border="0" cellspacing="0" cellpadding="0"><tbody><tr><td><img border=""0"" src="114021409091600943@za-mta-7.za.mimecast.lan"" /></td></tr></tbody></table>
<br>
<br>
null null</pre>Configure the following rule to remove unwanted html tags:
<sxi:Field name="Body">
<sxi:Rules>
<sxi:Substitute>
<sxi:Find>&lt;(.|n)*?&gt;</sxi:Find>
<sxi:Replace/>
</sxi:Substitute>
</sxi:Rules>
<sxi:OutputField>NewBody</sxi:OutputField>
</sxi:Field>Output after rule application:
This is an auto generated e-mail triggered because of the following entities being monitored :
Monitor
ho-vmspapp-01
Attribute
Health
Reasons
Health of ho-vmspapp-01 is critical
Root Cause
Root Cause :
1. Total Disk Utilization(%) 91 &gt; 90 (threshold).
2. SharePoint Server Search 14 is down
Additional information
This information has been generated by the Applications Manager
Reported By :
Applications Manager
Disclaimer
Everything in this e-mail and any attachments relating to the official business of Acme Holdings Ltd. and its subsidiaries ('Acme') is proprietary to Acme. It is confidential, legally privileged and protected by law. Acme does not own and endorse any other content.
Views and opinions are those of the sender unless clearly stated as being that of Acme. The person addressed in the e-mail is the sole authorised recipient. Please notify the sender immediately if it has unintentionally reached you and do not read, disclose or use the content in any way.
Acme cannot assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference.If you copy the permission line (permission javax.management.MBeanTrustPermission “register”;) from this forum into the java.policy file you will have to change the Unicode quotes represented in this forum, to ASCII quotes after the copy, otherwise the line will be ignored and you will still get mbean registration error.
For additional information on java management beans see https://en.wikipedia.org/wiki/Java_Mana … Extensions
Hi Gideon.
This has already been changed in the newer versions of X-ServiceBroker. Now it will not show an error but it will show that the Default rule is being run on that field.
Cheers
Yes, that is correct, both lines will need to be removed.
We have discussed this and agreed that from now when ever a new release is made available clients will be notified of the changes in the release. Watch the forums and web site for additional information.
HOW DOES THE SOAPWEBSERVICE CONNECTOR DEAL WITH THE SOAPACTION HEADER
If the user does not specifically add a SOAPAction Header using the Custom Headers node in the connector the SOAPWebServices Connector will automatically create a SOAPAction as follows:
---- If the Source attribute in the Create mapping used to send the Request does not contain a / then the value specified in the <Namespace> element in the connector is concatenated with the value specified in the Source attribute of the Create mapping
---- If the Source attribute in the Create mapping used to send the Request does contain a / then the value of the Source attribute itself is used
In the case of the client in question where a successful response would only be returned if the SOAPAction was empty you need to specify a Custom header as follows in the connector node:
<sxi:CustomHeaders>
<sxi:Header name="SOAPAction" value="&quot;&quot;"/>
</sxi:CustomHeaders>The WSDL contains a attribute in the <soap:address> element called "location" The value of the Location attribute must be used as the URL in the SOAPWebService connector. (Don't just assume the URL is the URL of the WSDL without the ?wsdl)
If you come across a StdError logfile and in it on about line 4 you see the following
java.security.AccessControlException: access denied ("javax.management.MBeanTrustPermission" "register")X-Layer will not be running correctly. This may be because you are not using the embedded version of the JRE that is distributed with the XLayer or you may be running on a unix system where no JRE is embedded in the XLayer.
To fix this issue you need to find where java is running from. In most cases this will be found in the JAVA_HOME environment variable.
Search for the JRE and locate the following file - java.policy (it will be in the jre\lib\security directory)
add the following
permission javax.management.MBeanTrustPermission "register";to the bottom of the file inside the grant { block above the };
You should be good to go now.
Delete the StdError log file and restart XLayer.
We were trying to start X-ServiceBroker on a linux server using the following command
sudo X-ServiceBroker startit seems as if something has change with sudo after some patches were applied. The new command should be as follows:
sudo -b X-ServiceBroker startthe -b tells sudo to start the process in the background as a service/daemon should.
In some of the case exchange integrations I've worked on, I've found it helpful to create new tags with default values unique to the collector action by referencing a source field that does not exist in the source form. This works fine, but the logs give an error message saying the field does not exist, even though it creates the tag.
Should this not perhaps be a WARNING message instead of an ERROR message?
When trying to connect to a MSSQL database server that uses Windows Authentication please remember the following:
Include the following property: useNTLMv2
Include the following Domain property: domain=mydomain.local (where "mydomain.local" is the trusted windows domain of the user allowed to access the database)
These can be set in the applications configuration.
In Sql Server Configuration Manager, make sure:
SQL Server is running
SQL Server Browser is running.
In the Protocols for SQLEXPRESS that TCP/IP is on.
This can be done as follows:
Enabling TCP/IP First we must tell SQL Server Express to listen on TCP/IP, to do this perform the following steps:
Launch the SQL Server Configuration Manager from the "Microsoft SQL Server 2005 CTP" Program menu
Click on the "Protocols for SQLEXPRESS" node,
Right click on "TCP/IP" in the list of Protocols and choose, "Enable"
For a more in-depth discussion on this topic please see http://blogs.msdn.com/b/sqlexpress/arch … 15084.aspx
Error:
[za.co.sxi.concurrent.MonitoredThreadFactory$RecoverableThreadRunner.uncaughtException] java.lang.NullPointerException: Thread 'XNotifyXml' stopped unexpectedly: null, will restart it
[za.co.sxi.concurrent.MonitoredThreadFactory$RecoverableThreadRunner.uncaughtException] StackTrace:
[za.co.sxi.concurrent.MonitoredThreadFactory$RecoverableThreadRunner.uncaughtException] bin.NotificationService.sendNotification(NotificationService.java:197)
[za.co.sxi.concurrent.MonitoredThreadFactory$RecoverableThreadRunner.uncaughtException] plugins.input.InputAbstractPlugin.sendNotification(InputAbstractPlugin.java:61)
[za.co.sxi.concurrent.MonitoredThreadFactory$RecoverableThreadRunner.uncaughtException] plugins.input.XNotifyXml.processFile(XNotifyXml.java:44)
[za.co.sxi.concurrent.MonitoredThreadFactory$RecoverableThreadRunner.uncaughtException] plugins.input.XNotifyXml.loopIteration(XNotifyXml.java:84)
[za.co.sxi.concurrent.MonitoredThreadFactory$RecoverableThreadRunner.uncaughtException] plugins.input.InputAbstractPlugin.run(InputAbstractPlugin.java:69)
[za.co.sxi.concurrent.MonitoredThreadFactory$RecoverableThreadRunner.uncaughtException] java.lang.Thread.run(Unknown Source)
Cause:
In X-Notify/xml/Initialisation.xml, the Notifiers element children might be configured as follows (note the highlighted lines):
<Notifiers>
<EMail id="EMail">
<SmtpServer>127.0.0.1</SmtpServer>
<FromAddress>from@company.co.za</FromAddress>
<SmtpAuthentication>
<Basic Username="username@company.co.za" Password="mypassword"/>
</SmtpAuthentication>
<SmtpPort>25</SmtpPort>
</EMail>
<XDec id="XDec"/>
</Notifiers>Below the Notifiers element is the ApplicationGroups element, which is where the cause of the problem is located (see highlighted line):
<ApplicationGroups>
<ApplicationGroup applicationName="MyTest">
<NotificationGroup name="Heartbeat Failure">
<XDec notifier="EMail">
<Destination>127.0.0.1</Destination>
<ESMTool>ServiceBroker</ESMTool>
<MD>ServiceBroker1</MD>
<Agent_Class>X-ServiceBroker</Agent_Class>
<Agent_Instance>X-ServiceBroker</Agent_Instance>
<Instance_Detail>X-ServiceBroker</Instance_Detail>
<Server>ServiceBroker1</Server>
<Client>ACME</Client>
<Source>ServiceDesk</Source>
</XDec>
</NotificationGroup>
</ApplicationGroup>
</ApplicationGroups>Effectively this means that we want to create an XDEC document using the EMAIL Notifier plugin, which is not possible. An XDEC document can only be created by using an XDEC Notifier plugin. The same applies to all Notifier plugins.
Resolution:
Change the ID in the affected ApplicationGroup config to reflect the correct Notifier ID:
<ApplicationGroups>
<ApplicationGroup applicationName="MyTest">
<NotificationGroup name="Heartbeat Failure">
<XDec notifier="XDec">
<Destination>127.0.0.1</Destination>
<ESMTool>ServiceBroker</ESMTool>
<MD>ServiceBroker1</MD>
<Agent_Class>X-ServiceBroker</Agent_Class>
<Agent_Instance>X-ServiceBroker</Agent_Instance>
<Instance_Detail>X-ServiceBroker</Instance_Detail>
<Server>ServiceBroker1</Server>
<Client>ACME</Client>
<Source>ServiceDesk</Source>
</XDec>
</NotificationGroup>
</ApplicationGroup>
</ApplicationGroups>A complete ASCII (including the extended chars)
Hi
Can SXI not setup an Released Notification to your vendors, When a new X-layer patch is released.
Stephan
Hi
Can you please give a more detailed configuration on Global Notifications in WorkFlow
<GlobalNotifications>
<Error enabled="yes" dataDefinition="Notifier" transmitMethod="HIGH" destination="localhost" />
<General enabled="yes" dataDefinition="Notifier" transmitMethod="LOW" destination="localhost" />
</GlobalNotifications>Stephan
Whilst working with one of our clients using the XLayer SOAPWebService connector to consume their SOAP web Service we were unable to receive a successful response until we sent them an Empty SOAPAction header. This was surprising to me as I was under the impression the SOAP specification made the SOAPAction on the request mandatory, until I read on the internet the following:
“I guess nobody has encountered such a problem. I know that if some application claims to be a web service client it should be able to set SOAPAction parameters but, unfortunately, it is not mandatory, just sending it with a null value ("") is enough according to SOAP specifications.”
“ The presence and content of the SOAPAction header field can be used by servers such as firewalls to appropriately filter SOAP request messages in HTTP. The header field value of empty string ("") means that the intent of the SOAP message is provided by the HTTP Request-URI. No value means that there is no indication of the intent of the message.”
After doing some tests I noticed that almost all SOAP Web Services (Including our SOAPImporter) will work successfully when supplying an empty SOAPAction header. The operation/action is determined by the SOAP envelope. (Note you must get the Namespace right for both the operation and the parameters which sometimes differ)
Often when needing to connect to a share on another windows machine from our XLayer server.
I keep forgetting how to include the domain, username and password into the single string for the XLayer file connectors, so this is how should look.
smb://domain;username:password@server/sharename
The separator between the domain and username is a ";" (semicolon) and between the username and password is a ":" (colon)
This was taken from here.
We will just need to put in a specific check for that exact message as it's a general SSLSocket exception, which is a valid error in many other cases, but should be able to read the message text and give the warning message where applicable
Yes that is correct, it is just warning you that a non SSL connection is attempting to connect. I am thinking though that we should change that level to Warning to make not sound so serious.
Non SSL Connection
Yes, this message is correct, telnet operates without any encryption (plain text), where as Station expects SSL connections which are treated as a different kind connection.
This message "Unrecognized client, possibly telnet session or similar non-SSL connection" was added to to the log to indicate that the connection was either from telnet or a similar program not using the SSL protocol. There are some non-standard telnet-like tools that do offer SSL support though, however we have never needed them as we have the Station Tester application for this purpose.
Added additional test to the stylesheet.
Added an additional test to the stylesheet to check that the request being dealt with is a LicAboutToExpire request, as there may be other requests that need to be processed on the localhost.
<?xml version="1.0" encoding="iso-8859-1"?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns="http://www.sxi.co.za/XMLSchema" xmlns:sxi="http://www.sxi.co.za/XMLSchema">
<xsl:output indent="yes"/>
<xsl:template match="@*|node()">
<xsl:copy>
<xsl:apply-templates select="@*|node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="//sxi:Destination">
<xsl:element name="{local-name()}">
<xsl:value-of select="//sxi:Destination"/>
<xsl:if test="/sxi:XNotification/sxi:NotificationGroup[1]/@name = 'LicAboutToExpire'">
<!-- replacement destination inserted below -->
<xsl:value-of select="'NEW_DESTINATION_SERVER'"/>
</xsl:if>
</xsl:element>
</xsl:template>
</xsl:stylesheet>Hi
To send LicAboutToExpire X-Notify xmls (see below example)
<?xml version="1.0" encoding="UTF-8"?>
<XNotification xmlns="http://www.sxi.co.za/XMLSchema">
<XHeader>
<XPress>
<Destination>localhost</Destination>
</XPress>
</XHeader>
<NotificationGroup application="XPress/Station" name="LicAboutToExpire" />
<Message>License for X-Layer will expire on Sat Sep 13 00:00:00 CAT 2014, please contact a representitive soon</Message>
</XNotification>to another server via XPress, do the following:
1. Copy the stylesheet below into a blank document and save it as LicAboutToExpire_change_dest.xsl
<?xml version="1.0" encoding="iso-8859-1"?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns="http://www.sxi.co.za/XMLSchema" xmlns:sxi="http://www.sxi.co.za/XMLSchema">
<xsl:output indent="yes"/>
<xsl:template match="@*|node()">
<xsl:copy>
<xsl:apply-templates select="@*|node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="//sxi:Destination">
<xsl:element name="{local-name()}">
<!-- replacement destination inserted below -->
<xsl:value-of select="'NEW_DESTINATION_SERVER'"/>
</xsl:element>
</xsl:template>
</xsl:stylesheet>2. Replace NEW_DESTINATION_SERVER in the stylesheet above with the IP address of the server you wish to send the notification to. Do not remove the single quotes!
3. Copy the stylesheet to the following directory: Program Files/Southern X Integrators/XPress/Dispatch/stylesheet
4. Open your Program Files/Southern X Integrators/XPress/Dispatch/xml/Initialisation.xml file and add the following: (Note: if you already have a ContentTransformations rule configured, you only need to copy the contents of the <Transformation> element below):
<ContentTransformations>
<Transformation sendOriginal="no" stylesheetPath="../stylesheet/LicAboutToExpire_change_dest.xsl">
<Condition xpath="/sxi:XNotification/sxi:NotificationGroup/@name" value="LicAboutToExpire"/>
</Transformation>
</ContentTransformations>5. Save the XPress Dispatch Initialisation.xml file and restart the XPress Dispatch service and you are done.
Is it correct to receive the following error when someone attempts to telnet on port 9751 to check connectivity?
12:01:49 - - ****************************************************************************************************
12:01:49 - - * Southern X Integrators XPress/Station Started. (X-Layer Version 9.1.11)
12:01:49 - - ****************************************************************************************************
12:01:49 - -
12:01:49 - - 0 Log files with prefix >XPress/Station< deleted from C:Program FilesSouthern X IntegratorsXPressStationlogs
12:01:49 - -
12:01:49 - - Logging Level ==> INFORMATION
12:01:49 - - Log Directory ==> C:Program FilesSouthern X IntegratorsXPressStationlogs
12:01:49 - - Log file retention ==> 7
12:01:49 - INFORMATION - Default output directory: C:Program FilesSouthern X IntegratorsXPressXmlOut
12:01:49 - INFORMATION - Other configured directories are:
12:01:49 - INFORMATION - 1) (?i)^CustomFilenameHere~.*.xml$ : C:Program FilesSouthern X IntegratorsXPressXmlOutCustomFilename
12:01:49 - INFORMATION - Server is listening on port 9751
12:04:31 - ERROR - javax.net.ssl.SSLException: Socket error: Unrecognized SSL message, plaintext connection?
12:04:31 - WARNING - Unrecognized client, possibly telnet session or similar non-SSL connection
12:11:59 - ERROR - javax.net.ssl.SSLException: Socket error: Unrecognized SSL message, plaintext connection?
12:11:59 - WARNING - Unrecognized client, possibly telnet session or similar non-SSL connectionAnother viable option is Oracle JDeveloper.