- Load balancing can be used to stop clustering and retain a virtual IP
- Channels are synchronized after their initial state is changed to PAUSED
- Channel DEPLOY triggers synchronization via Appliance Plugin on active node:
- A deploy event is fired off - log entry:
- com.mirth.connect.plugins.appliance.Appliance
onDeploy() called, waking up MirthConnectSync - Channel REMOVE does not trigger synchronization
- Configuration is retrieved through:
- http://standby/cp/api/mirthconnect/config
... which is forwarded on standby node to: - http://localhost:8027/api/configuration
Friday, 19 December 2014
Mirth Appliance Clustering Notes
Tuesday, 9 December 2014
Deployit Tricks
- Use udm for script rules to avoid creation of unwanted steps
- Use generic otherwise: this will create create/destroy steps and make templating in properties available
- Use dictionaries and moustaches for package parameters to change checksum and force update
- Use container properties for script parameters that do not require update when they change
- Never use file.File but rather generic.File
Thursday, 7 August 2014
WSO2 STS RequestSecurityToken Example
Valid for action types:
- Issue
- Renew
- Cancel
- Validate
<
soap:Envelope
xmlns:wsse
=
"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns:wsa
"http://www.w3.org/2005/08/addressing"
xmlns:wst
=
"http://schemas.xmlsoap.org/ws/2005/02/trust"
xmlns:wsid
=
"http://schemas.xmlsoap.org/ws/2005/05/identity"
>
<
soap:Header
>
<
wsse:Security
soap:mustUnderstand
=
"true"
>
<
wsu:Timestamp
wsu:Id
=
"Timestamp-62"
>
<
wsu:Created
>2014-07-22T08:34:17Z</
wsu:Created
>
<
wsu:Expires
>2014-07-22T08:34:18Z</
wsu:Expires
>
</
wsu:Timestamp
>
<
wsse:UsernameToken
wsu:Id
=
"UsernameToken-61"
>
<
wsse:Username
>admin</
wsse:Username
>
<
wsse:Password
Type
=
"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText"
>admin</
wsse:Password
>
<
wsse:Nonce
EncodingType
=
"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"
>4TFLJ3AAewWtCkolCRvYbQ==</
wsse:Nonce
>
<
wsu:Created
>2014-07-22T08:34:17.806Z</
wsu:Created
>
</
wsse:UsernameToken
>
</
wsse:Security
>
<
wsa:MessageID
>uuid:d54cb478-fdd1-4495-84df-2fde515a4591</
wsa:MessageID
>
</
soap:Header
>
<
soap:Body
>
<
wst:RequestSecurityToken
>
<
wst:TokenType
>http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV2.0</
wst:TokenType
>
</
wst:Claims
>
</
wst:RequestSecurityToken
>
</
soap:Body
>
</
soap:Envelope
>
Subscribe to:
Posts (Atom)