diff options
author | Jim Hahn <jrh3@att.com> | 2020-10-16 14:17:43 +0000 |
---|---|---|
committer | Gerrit Code Review <gerrit@onap.org> | 2020-10-16 14:17:43 +0000 |
commit | 5190c58837149c4599182d211d8ae5bd83003d34 (patch) | |
tree | 6186091f088a43623a2b9ebf9b203fc33e90825a /plugins/plugins-event/plugins-event-protocol/plugins-event-protocol-jms | |
parent | c293413c1c46d3c59ff8a855d683f4614bbe644a (diff) | |
parent | 0cf967c0239a8ab9c8b8831b700b72d9a08f7b03 (diff) |
Merge "Remove apex asciidoc documents"
Diffstat (limited to 'plugins/plugins-event/plugins-event-protocol/plugins-event-protocol-jms')
-rw-r--r-- | plugins/plugins-event/plugins-event-protocol/plugins-event-protocol-jms/src/site-docs/adoc/fragments/ep-jms.adoc | 51 |
1 files changed, 0 insertions, 51 deletions
diff --git a/plugins/plugins-event/plugins-event-protocol/plugins-event-protocol-jms/src/site-docs/adoc/fragments/ep-jms.adoc b/plugins/plugins-event/plugins-event-protocol/plugins-event-protocol-jms/src/site-docs/adoc/fragments/ep-jms.adoc deleted file mode 100644 index aa33a2b8f..000000000 --- a/plugins/plugins-event/plugins-event-protocol/plugins-event-protocol-jms/src/site-docs/adoc/fragments/ep-jms.adoc +++ /dev/null @@ -1,51 +0,0 @@ -// -// ============LICENSE_START======================================================= -// Copyright (C) 2016-2018 Ericsson. All rights reserved. -// ================================================================================ -// This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE -// Full license text at https://creativecommons.org/licenses/by/4.0/legalcode -// -// SPDX-License-Identifier: CC-BY-4.0 -// ============LICENSE_END========================================================= -// -// @author Sven van der Meer (sven.van.der.meer@ericsson.com) -// - -== JMS Event - -The event protocol for JMS is provided by the APEX JMS plugin. -The plugin supports encoding as JSON text or as object. -There is no difference in the configuration for the input and output interface. - -=== JMS Text - -If used as input, APEX will take a JMS message and extract a JSON string, then proceed as if a JSON event was received. -If used as output, APEX will take the event produced by a policy, create a JSON string, and then wrap it into a JMS message. - -The configuration for JMS text is as follows: - -[source%nowrap,json] ----- -"eventProtocolParameters":{ - "eventProtocol" : "JMSTEXT", - "parameterClassName" : - "org.onap.policy.apex.plugins.event.protocol.jms.JMSTextEventProtocolParameters" -} ----- - - -=== JMS Object - -If used as input, APEX will will take a JMS message, extract a Java Bean from the `ObjectMessage` message, construct an APEX event and put the bean on the APEX event as a parameter. -If used as output, APEX will take the event produced by a policy, create a Java Bean and send it as a JMS message. - -The configuration for JMS object is as follows: - -[source%nowrap,json] ----- -"eventProtocolParameters":{ - "eventProtocol" : "JMSOBJECT", - "parameterClassName" : - "org.onap.policy.apex.plugins.event.protocol.jms.JMSObjectEventProtocolParameters" -} ----- |