...
Table of Contents |
---|
While registering the node, it will take all the hub settings in the Experience Designer memory (In the form of an object, the keyname will be the pathname).
Once the request is made into the node, then it will look for Hub setting based on the hub name which is presented in the URL path as a parameter.
To make an http request and can access the data of the configured hubname. ( Works similar to http-in node except the /oeapi path.(ie)Instead of /oeapi, we are using /hub)
|
Hub Listener node
The Hub Listener node will listen to the path which is configured in the URL property of the node. This node is similar to the http in node with a prefix /hub/
and the method defaulted to Get
.
...
Project - Name of the project.
...
URL - The URL should be in the format of /hub/:hubname/
sample
Name - Name of the node.
The page view URL button will be visible Post-deployment.
You can find the kgraphId in the payload property msg.payload.orbita.facts.
kgraphId kgraphId
You can find the hubsettings in the payload property msg.payload.orbita.facts.hubSettings
How to use Hub Listener node
Create an Engage hub in https://yourdomain.orbita.cloud:8443/engage/hub. In our example, we created an Engage hub named sample.
Give the hub name in the URL field of the Hub Listener node.
Connect the Hub Listener node, Template node and the http out nodes in this sequence.
Construct your web page design in the template node.
Use the URL to access the web page https://yourdomain.orbita.cloud:8443/hub/sample
The hub listener node will also populate the payload properties with the kgraph Id and the hub settings at msg.payload.orbita.facts.kgraphId
and msg.payload.orbita.facts.hubSettings
respectively.
Related Articles
Filter by label (Content by label) | ||||||||
---|---|---|---|---|---|---|---|---|
|