rogin

MichaelLeeHobbs

/*** GLOBAL Scope ***/

/*** GLOBAL Scope --- Map Functions --- ***/

function $co(key, value) { if (arguments.length == 1) { return connectorMap.get(key); } else { return connectorMap.put(key, value); } }
function $c(key, value) { if (arguments.length == 1) { return channelMap.get(key); } else { return channelMap.put(key, value); } }
function $s(key, value) { if (arguments.length == 1) { return sourceMap.get(key); } else { return sourceMap.put(key, value); } }
function $gc(key, value) { if (arguments.length == 1) { return globalChannelMap.get(key); } else { return globalChannelMap.put(key, value); } }
function $g(key, value) { if (arguments.length == 1) { return globalMap.get(key); } else { return globalMap.put(key, value); } }
function $cfg(key, value) { if (arguments.length == 1) { return configurationMap.get(key); } else { return configurationMap.put(key, value); } }

MichaelLeeHobbs

-- 20201125T1403 EST - Fix bug in xpath not correctly matching values to correct channel
-- 20201125T1430 EST - Updated formatting only using: http://poorsql.com/ with minor hand edits
-- 20201125T1430 EST - Updated formatting only using: http://poorsql.com/ with minor hand edits
-- 20210321T1140 EST - Postgres 12+ XPATH works differently and required entry/ where as 9.6 requires it to be missing
--
-- Jon Bartels
-- Similar query for SQL Server is here - https://stackoverflow.com/questions/58942371/get-space-used-by-mirth-per-channel-in-sql-server
--

SELECT NAME AS CHANNEL_NAME

MichaelLeeHobbs

/**
 * ChannelUtils
 * @param config: {name, user, password, url, dbClass, cacheConnection, cacheName}
 * @param config.name: a db connection name must be unique or will cause issues
 * @param config.user: user name to use for db connection
 * @param config.password: db user password
 * @param config.url: db url
 * @param config.dbClass: db class - Default: org.postgresql.Driver
 * @param config.cacheConnection: Should cache the connection? true/false
 * @param config.cacheName: default - cachedConnection:ChannelUtils:channelName:config.name

zer0vuln

FROM node:13-alpine as base

LABEL maintainer="Isaak Eriksson <isaak.eriksson@gmail.com>"

ENV PUPPETEER_SKIP_CHROMIUM_DOWNLOAD true
ENV PUPPETEER_EXECUTABLE_PATH /usr/bin/chromium-browser

WORKDIR /src

RUN apk update && apk add --no-cache --virtual \

MichaelLeeHobbs

-- 20201125T1403 EST - Fix bug in xpath not correctly matching values to correct channel
-- 20201125T1430 EST - Updated formatting only using: http://poorsql.com/ with minor hand edits
-- 20201125T1432 EST - Removed CID from final output as it was only there for debugging xpath issues
-- 20210321T1140 EST - Postgres 13+ XPATH works differently see: https://gist.github.com/MichaelLeeHobbs/40b4b7cf70ecbe30b73eed763367e626
--
-- Jon Bartels
-- Similar query for SQL Server is here - https://stackoverflow.com/questions/58942371/get-space-used-by-mirth-per-channel-in-sql-server
--

SELECT NAME AS CHANNEL_NAME

jonbartels

Mirth Connect is awesome! One common question on the forums and Slack is how to manage SSL connctions. These questions mainly focus on HTTPS but also include TCP connections.

The quick rundown is:

1. The built-in MC HTTP Sender connector will do HTTPS if:

• The endpoint has a certificate which is signed by a CA already present in the JVM truststore and has the right DN or SAN for the hostname. This is logically equivalent to the "green check" if you open the URL in a browser.
• The certificate has been added to the truststore for the JVM that MC is running under
• Changes to DNS or host files allow a hostname to match the DN or SAN already present in the cert (not reccomended)
• The connector may flag these connections with a warning or red x. Test the channel first as the validator makes assumptions about SSL that may not apply in this case.

2. The built-in MC HTTP Listener connector will not do SSL directly. A plugin or a proxy is necessary.

• Tony Germano has a plugin implemented for SSL l

onodai145

FORTIDATE %{YEAR:year}\-%{MONTHNUM:month}\-%{MONTHDAY:day}

danielepolencic

3 Virtual Machines Kubernetes cluster

Dependencies

You should install VirtualBox and Vagrant before you start.

Creating the cluster

You should create a Vagrantfile in an empty directory with the following content:

lk321

import fs from 'fs';

export default class X12 {

    constructor(file) {
        if (file.includes('/')) {
            fs.readFile(file, 'utf8', (err, contents) => {
                return this.parseTextToJSON(contents);
            });
        } else {