ERROR - Connection failed for Connector 'MyLocal_MSSQL' to server 'localhost' for DataBase 'SomeDB'. Error '"encrypt" property is set to "true" and "trustServerCertificate" property is set to "false" but the driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption ......

Include the following properties in the Connector:
1. Property: encrypt
2. Property: trustServerCertificate

Here is an example:

<Connector id="MyLocal_MSSQL">
  <Connection xsi:type="MSSQL">
     <RetryDelay>30</RetryDelay>
     <Server>localhost</Server>
     <User>User</User>
     <Password>Password</Password>
     <DBName>SomeDB</DBName>
     <Properties>
       <Property name="encrypt" value="false"/>
       <Property name="trustServerCertificate" value="true"/>
     </Properties>
     <Port>1433</Port>
  </Connection>
  <ReturnCodes>
    <Success />
    <DefaultError type="Non-Recoverable">
       <ExceptionCodes>
         <Code>^.*I/O Error.*$</Code>
         <Code>^.*Timeout occurred.*$</Code>
         <Code>.+Read timed out.+</Code>
         <Code>.*Invalid state.+</Code>
         <Code>.*SHUTDOWN is in progress.+</Code>
        </ExceptionCodes>
    </DefaultError>
  </ReturnCodes>
</Connector>

{
    "myFirstArrayElement": [
        {
            "json": {
                "Problem Ticket Number": "INC00012345",
                "Reference Person ID": "cr:000123"
           }
        }
    ]
}

You need to use both XLayer Configuration and XSLT

The XSLT must look as follows:

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <xsl:output method="xml" indent="yes" omit-xml-declaration="yes"/>
    <xsl:template match="/">
<root class="object">
    <myFirstArrayElement class="array">
        <blank class="object">
            <json type="string"><xsl:value-of select="//*[local-name() = 'mBuildBody']"></xsl:value-of></json>
        </blank>
    </workItems>
</root>
    </xsl:template>
</xsl:stylesheet>

then in your XLayer configuration you need a datadefinition with the following:

<sxi:DataDefinition name="callRPABotAPI">
      <sxi:Fields>
...
        <sxi:Field name="na_3">
          <sxi:Rules>
            <sxi:Concatenation>
              <sxi:Delimiter></sxi:Delimiter>
              <sxi:Fields>
                <sxi:Field staticValue="yes">{&quot;Problem Ticket Number&quot;: &quot;</sxi:Field>
                <sxi:Field>mRef_num</sxi:Field>
                <sxi:Field staticValue="yes">&quot;,&quot;Reference Person ID&quot;: &quot;</sxi:Field>
                <sxi:Field>mPersid</sxi:Field>
                <sxi:Field staticValue="yes">&quot;}</sxi:Field>
              </sxi:Fields>
            </sxi:Concatenation>
          </sxi:Rules>
          <sxi:OutputField>mBuildBody</sxi:OutputField>
        </sxi:Field>
...
      </sxi:Fields>
    </sxi:DataDefinition>

where the fields mRef_num contains the value "INC00012345" and mPersid contains the value "cr:000123"

Refer to Correct JSON format from XML Stylesheet for RESTConnector for additional information on how to convert XML to JSON

Add the following line to the bottom of the grant { section.

Your policy file should end looking something like this:

spring.datasource.url=jdbc:sqlserver://127.0.0.1:1433;databaseName=TestDB;integratedSecurity=true;encrypt=false;authenticationScheme=NTLM;user=xxx;password=xxx

19:58:27.256 - ERROR - Failed to open or close the folder Inbox. Reason: Failed to load IMAP envelope
javax.mail.MessagingException: Failed to load IMAP envelope
at com.sun.mail.imap.IMAPMessage.loadEnvelope(IMAPMessage.java:1532)
at com.sun.mail.imap.IMAPMessage.getSubject(IMAPMessage.java:441)
at plugins.collectors.MailCollector$MessageToElementConverter.setSubject(MailCollector.java:959)
at plugins.collectors.MailCollector$MessageToElementConverter.getSubjectText(MailCollector.java:1319)
at plugins.collectors.MailCollector.pollForEvents(MailCollector.java:529)
at plugins.collectors.AbstractPoller$EventProcessor.monitoredRun(AbstractPoller.java:182)
at za.co.sxi.concurrent.MonitoredTimerTask.run(MonitoredTimerTask.java:25)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)

This issue can be resolved by marking the oldest unprocessed/unread email as "read". This action can be performed within the email client (i.e Outlook).

Please feel free to provide any additional insights or suggestions related to this matter.

To get Oxygen to automatically generate this prefix when xpaths are copied, and to get Oxygen to automatically recognize this prefix when copying xpath expressions from the Xlayer logs to Oxygen do the following:

1/ Start Oxygen
2/ Open the Xpath/XQuery Builder (Window-Show View-XPath/XQuery Builder)
3/ Find the little settings cog click on that and go into options
4/ Click the New button to create a new Default prefix-namespace mapping
5/ Set the Prefix to - default
6/ Set the Namespace URI to -  http://www.sxi.co.za/XMLSchema

MYSQL

select table_schema as database_name,
       table_name,
       update_time
from information_schema.tables tab
where update_time > (current_timestamp() - interval 30 day)
      and table_type = 'BASE TABLE'
      and table_schema not in ('information_schema', 'sys',
                               'performance_schema','mysql')
      -- and table_schema = 'sigreg' 
order by update_time desc;

The result will look something like the following:

You can now save the update_time and if, on a later query, the update time is newer than the last update time you know that the table changed somewhere.

NOTE:  The update_time will change if a record is added / deleted or updated.

An explaination of the query can be found here

This is useful for MYSQL and MariaDB. 

1. What other ways have you found to monitor a table in a database for changes?

2. What suggestions are there is we only want to know about new records being added?

The X-Service Broker has a built-in debug facility and is activated by changing VM options in the X-ServiceBroker.vmoptions file located in the X:\SXI\X-ServiceBroker\bin folder.
The file looks like this:

# Enter one VM parameter per line
# For example, to adjust the maximum memory usage to 512 MB, uncomment the following line:
# To include another file, uncomment the following line:
# -include-options [path to other .vmoption file]

By add in "-Djavax.net.debug=ssl:handshake:keymanager:trustmanager:plaintext" to the file we can be able to see what messages are actually being sent and received in the X-ServiceBroker.StdOut_nnnnnnnn.log file located the this folder $\SXI\X-ServiceBroker\logs
Please take note the log file size will grow very fast when using the debugging op in the VM options file.

Here is how to Read the Debug output log file.

To turn on SSL/TSL debugging in X-ServiceBroker.vmoptions file use this -Djavax.net.debug:ssl 
The following parameters can be used with SSL/TLS Debugging:

record			"Enable per-record tracing"
handshake		"Print each handshake message"
keygen			"Print key generation data"
session			"Print session activity"
defaultctx		"Print default SSL initialization"
sslctx			"Print SSL Context tracing"
sessioncache		"Print session cache tracing"
keymanager		"Print key manager tracing"
trustmanagerprint	"Trust manager tracing"
pluggability		"Print pluggability tracing"

Handshake debugging can be widened with:

data		"hex dump of each handshake message"
verbose		"verbose handshake message printing"

Record debugging can be widened with:

plaintext	"hex dump of record plaintext"
packet		"print raw SSL packets"

The Debugging SSL Connections parameters can be used as following to display specific levels of detail in the log file. :

-Djavax.net.debug=ssl:record

or

-Djavax.net.debug=ssl:handshake

Here is an example to specify more than one option in X-ServiceBroker.vmoptions file. : 

-Djavax.net.debug=ssl:keymanager:record

1. Download the DigiCert Certificate Utility from DigiCert.

2. Open the DigiCert Certificate Utility and Click on Import

   

3. Browse to where you have saved the Certificate you received from the Client.

   

4. In this case the file name is "client_wildcard_new.pfx" select the file and click Open.

   

5. The wizard will assist you with importing the Certificate, Click Next.

   

6. Enter the password you received from the Client, then Click Next.

   

7. The following screen will appear with the Name, Serial number, etcetera.. Don't change anything, Click Finish.

   

8. The following message will appear saying You have successfully imported the Certificate to DigiCert Certificate Utility, Click OK.

   

9. Click on the Lock SSL on the left side.

   

10. Now we going to Export the Certificate to use with Tomcat / XLayer API.
    Click on the SSL Certificate you want to Export, when you click on the Certificate it will highlight the line.
    In this case it will be the one at the top, then Click on Export Certificate.

    

11. The Certificate Export screen will appear, Don't change anything.
    The fille will be saved as a "pfx" file, Click on Next.

    

12. Now we going to add a Password to the Certificate we exporting.
    You need to take note of this Password you going to use here.
    This Password you entered will be used going forward to import the Certificate in to Tomcat / XLayer API, Click on Next.

    

13. Browse to where you what to save the Certificate, by clicking on the the three dots.
    In this cases the file name used is "wildcard_client_com.pfx", the file will be saved as a "pfx" file extension, Click on Finish.

    

14. The following message will appear saying You have successfully exported the Certificate, Click OK.

    

15. Now you can close the DigiCert Certificate Utility App and use the pfx file you exported in step 13 with Tomcat / XLayer API.
    

    Done.

The PortQueryUI contains several predefined sets of queries to check the availability of the popular Microsoft services:

• Domain and trusts (checking ADDS services on an Active Directory domain controller)

• Exchange Server

• SQL Server

• Networking

• IP Sec

• Web Server

• Net Meeting

PortQryUI - https://www.microsoft.com/en-us/downloa … x?id=24009

The Rule can be applied to a new field in which case you would have  <Input newField="yes"/>
In the example you can see a static value is set simply by putting in the static value i.e.    <Field>this is static</Field>
In the example below you can set the contents of an element addressed by an xPath statement simply by inserting the xPath as shown below i.e.  <Field>//default:FileNameZwido</Field>

<RuleDefinition name="ConcatForZwido">
      <Fields>
        <Field id="3">
          <Input newField="yes"/>
          <Rules>
            <Concatenation>
              <Delimiter> </Delimiter>
              <Fields>
                <Field>//default:mServer</Field>
                <Field>reported by:</Field>
                <Field>//default:mFName</Field>
                <Field>-</Field>
                <Field>//default:mLName</Field>
              </Fields>
            </Concatenation>
          </Rules>
          <OutputElement>short_description</OutputElement>
        </Field>
      </Fields>
</RuleDefinition>

In the example below you can set the contents of a variable simply by specifying the variable name i.e.  <Field>~#~LocalVariable1~#~</Field>
The Rule can be applied to an existing element as in this example where you have  <Input newField="no">//default:FileNameZwido</Input>

<RuleDefinition name="ConcatForZwido">
      <Fields>
        <Field id="FID1">
          <Input newField="no">//default:FileNameZwido</Input>
          <Rules>
            <Concatenation>
              <Delimiter>-</Delimiter>
              <Fields>
                <Field>this is static</Field>
                <Field>~#~LocalVariable1~#~</Field>
                <Field>//default:FileNameZwido</Field>
              </Fields>
            </Concatenation>
          </Rules>
          <OutputElement>ZwidosConcatTest</OutputElement>
        </Field>
      </Fields>
    </RuleDefinition>

1. Open Resource Monitor

   • Found by searching for Resource Monitor on the Start menu

   • Typing resmon.exe in the Run Menu

   • On the Performance tab in your Task Manager
     

2. Go to the CPU tab (1)

   1. Use the search field in the Associated Handles section (2)     
      

   2. When you've found the handle, you can identify the process by looking at the Image and/or PID column.

   3. You can then try to close the application as you normally would, or, if that's not possible, just right-click the handle and kill the process directly from there.

Easy peasy!