The following pages and posts are tagged with
| Title | Type | Excerpt |
|---|---|---|
| Deploy using dependency management. | Page | Using a dependency management system to deploy your Interlok instance can make deployments a little bit easier as you can collect and download the required l... |
| Interlok Clustering | Page | This page explains Interlok instance clustering. |
| Interlok configuration with logic blocks | Page | This page describes how to configure logic blocks inside your Interlok configuration (since 3.9.0) |
| Configuration Pre Processing | Page | Pre-processors allow us to perform actions on the Interlok configuration before it is unmarshalled and the Interlok instance starts up. |
| Enabling a Custom Class Loader for Jetty | Page | This page describes how to configure a custom class loader for use with Jetty (since 3.5.1). |
| Interlok in Docker | Page | There is now a public docker image for Interlok hosted on hub.docker.com This is a cut-down standard installation that exposes the ports 5555 (for JMX) and 8080 (for the web UI). If you have docker installed, then you can run it simply by doing docker run... |
| Resolvable Expressions | Page | This page describes how to use the expressions available for metadata lookup |
| Interlok Failover | Page | This page describes how to configure multiple Interlok instances to start up in failover mode (since 3.3) |
| Workflow Interceptors | Page | Multiple WorkflowInterceptor instances may be applied to any workflow type. Every message that is processed by a workflow will have each WorkflowInterceptor applied to it, at the start and at the end of the workflow, in order of configuration. The WorkflowInterceptor interface itself is very simple and... |
| Interlok Kubernetes Scaling | Page | Interlok scaling for Kubernetes in 15 minutes |
| Interlok JMS performance samples. | Page | Sample JMS bridging performance. |
| JMX over JMS | Page | In a factory fresh installation of Interlok; the JMXServiceURL property in bootstrap.properties is set to be the reference implementation jmxmp. This implementation is fine if the adapter is running in the local network and there are no issues with making connections to the Interlok instance from your browser.... |
| JMX Monitoring and Management | Page | The adapter supports monitoring over JMX. This allows developers and administrators to connect to the adapter JVM with standard tools (JConsole, JVisualVM an... |
| Memory Requirements | Page | This document will describe Interlok's memory requirements and how various components can have an effect on those requirements. Finally, we will show some sa... |
| Multi-Payload Messages | Page | This page describes how to use the Multi-Payload Adaptris Message |
| Profiling with New Relic | Page | This page describes how to profile Interlok and inject statistics into New Relic |
| Storing Passwords in XML | Page | It has been a requirement for some organisations that passwords should never be stored in plain text in the configuration file; for these scenarios, it is now possible to encrypt the passwords. Because we have to recover the plain text password to pass to various subsystems reversible encryption has to... |
| Performance Metrics | Page | One of the things that we’re always asked is to provide some performance metrics for the adapter. The answer here, is that it depends. Raw performance numbers are almost always meaningless in the real world; it depends on too many things, the complexity of your environment, the quality of the... |
| Interlok Failover with AspectJ | Page | This page describes how to configure multiple Interlok instances to start up in failover mode (since 3.0.6) |
| Automagically adding mapped diagnostic context data for logging | Page | Automatically added message-id to logging context. |
| Interlok Prometheus profiling | Page | Using Prometheus and Grafana to view Interlok metrics. |
| Management using a remote shell | Page | Interlok supports an integrated Java shell called CRaSH. You can use CRaSH to ssh into your running interlok instance. Important: This is deprecated notice because Interlok Shell will not work with Java 11, and the underlying libraries are well out... |
| Interlok SSL with Solace | Page | This page describes how to configure Interlok to use SSL with Solace. |
| Using Interlok in a Sonic Container | Page | This document is aimed at developers and system administrators who wish to run an instance of Interlok inside a SonicMQ container. You will be instructed on ... |
| Triggered Channels | Page | There are some subtle differences between a triggered-channel and a normal channel; the consumers inside each workflow should really be based around things that actively poll (i.e. AdaptrisPollingConsumer implementations) rather than consumers that are passively receiving messages (like a jms-queue-consumer or the like, if you need JMS... |
| Version Control with command line executable | Page | Configure Interlok to automatically check out config from VCS when starting. |
| Version Control with GIT | Page | Configure Interlok to automatically check out config from GIT when starting. |
| Version Control with Subversion | Page | Configure Interlok to automatically check out config from SVN when starting. |
| Version Control Configuration | Page | Since 3.0.2 Interlok will support configuration that is controlled by a version control systems automagically. Configuration files can be stored in VCS, checked out/updated prior to any management components / adapter instances starting up. The properties mentioned here are in addition to any properties that are normally defined in <code... |
| Clustered Workflows / Services | Page | This page describes how to configure Interlok workflow/service clustering (since 3.5.0) |
| Interlok SSL with WebsphereMQ | Page | This page describes how to configure Interlok and Websphere MQ for SSL communication. |
| XA transaction management | Page | This page describes how to configure XA transaction management for JMS bridging. |
