Create a Node
post
/v1/nodes
Creates a node in the Node Manager.
Request
There are no request parameters for this operation.
Supported Media Types
- application/json;charset=utf-8
Root Schema : schema
Type:
object
The payload schema to create add a node to a Node Manager.
Show Source
-
dcNodeConfigData(required):
dcNodeConfigData
-
displayName(required): string
Minimum Length:
1
The display name of the node.Example:CC Node 1
-
nodeContext(required): string
Minimum Length:
1
The context of the node. -
nodeManagerID(required): string
The identifier of the Node Manager.
-
ruleFileDisplayName(required): string
The selected rule file display name for the node.
-
ruleFileName(required): string
Minimum Length:
1
The selected rule file name for the node.Example:ASCII_Sample.npl
Nested Schema : dcNodeConfigData
Match All
The configuration data of the node.
Show Source
-
object
DCNodeConfigDataRSM
The schema defining node configuration data for a node.
-
The configuration data of the node.
Nested Schema : DCNodeConfigDataRSM
Type:
object
The schema defining node configuration data for a node.
Show Source
-
configRules: array
configRules
The secondary configuration data of the node.
-
nodeConfigVariables: array
nodeConfigVariables
The general configuration data of the node.
-
ruleName: string
The selected rule file name for the node.
Nested Schema : configRules
Type:
array
The secondary configuration data of the node.
Show Source
-
Array of:
object SecondaryConfigData
The schema defining secondary configuration data for a node.
Nested Schema : nodeConfigVariables
Type:
array
The general configuration data of the node.
Show Source
-
Array of:
object NodeConfigVariable
The schema defining configuration variable for a node.
Nested Schema : SecondaryConfigData
Type:
object
The schema defining secondary configuration data for a node.
Show Source
-
fileConfigVariables(required): array
fileConfigVariables
The list of secondary configuration variables for the node.
-
fileName(required): string
The secondary configuration data file name.
Nested Schema : fileConfigVariables
Type:
array
The list of secondary configuration variables for the node.
Show Source
-
Array of:
object NodeConfigVariable
The schema defining configuration variable for a node.
Nested Schema : NodeConfigVariable
Type:
object
The schema defining configuration variable for a node.
Show Source
-
name(required): string
The key name of the configuration variable.Example:
processedFileSuffix
-
value(required): string
TThe value of the configuration variable for a key.Example:
complete
Response
Supported Media Types
- application/json
201 Response
The node has been added successfully.
Root Schema : NodeResponse
Type:
object
The response schema for getting a node's information.
Show Source
-
@type: string
Defines the sub-class entity when sub-classing.
-
dcNodeConfigData:
dcNodeConfigData
-
dcNodeType:
dcNodeType
-
destinationNode: array
destinationNode
The details of destination nodes for routes originating from the node.
-
displayName(required): string
The display name of the node.Example:
CC Node 1
-
marketSegment(required): string
The market segment of the node.Example:
CartridgeKit
-
NMhref(required): string
(uri)
The reference to get Node Manager information.
-
nodeContext(required): string
The context of a node.
-
nodeId(required): string
The node identifier.Example:
z8kfsx-16it-l0mbm95p
-
nodeLabel(required): string
The node label.Example:
3
-
nodeManagerID(required): string
The Node Manager identifier.
-
ruleFileDisplayName(required): string
The selected rule file display name of the node.
-
ruleFileName(required): string
The selected rule file name of the node.Example:
ASCII_Sample.npl
-
startState(required): boolean
The starting state of the node.Example:
STOPPED
Nested Schema : dcNodeConfigData
Match All
The configuration data of the node.
Show Source
-
object
DCNodeConfigDataRSM
The schema defining node configuration data for a node.
-
The configuration data of the node.
Nested Schema : dcNodeType
Match All
The node type information of the node.
Show Source
-
object
DCNodeTypeRSM
The schema defining node type information for a node.
-
The node type information of the node.
Nested Schema : destinationNode
Type:
array
The details of destination nodes for routes originating from the node.
Show Source
-
Array of:
object DestinationNodeConfig
The schema defining destination node's reference for a route.
Nested Schema : DCNodeConfigDataRSM
Type:
object
The schema defining node configuration data for a node.
Show Source
-
configRules: array
configRules
The secondary configuration data of the node.
-
nodeConfigVariables: array
nodeConfigVariables
The general configuration data of the node.
-
ruleName: string
The selected rule file name for the node.
Nested Schema : configRules
Type:
array
The secondary configuration data of the node.
Show Source
-
Array of:
object SecondaryConfigData
The schema defining secondary configuration data for a node.
Nested Schema : nodeConfigVariables
Type:
array
The general configuration data of the node.
Show Source
-
Array of:
object NodeConfigVariable
The schema defining configuration variable for a node.
Nested Schema : SecondaryConfigData
Type:
object
The schema defining secondary configuration data for a node.
Show Source
-
fileConfigVariables(required): array
fileConfigVariables
The list of secondary configuration variables for the node.
-
fileName(required): string
The secondary configuration data file name.
Nested Schema : fileConfigVariables
Type:
array
The list of secondary configuration variables for the node.
Show Source
-
Array of:
object NodeConfigVariable
The schema defining configuration variable for a node.
Nested Schema : NodeConfigVariable
Type:
object
The schema defining configuration variable for a node.
Show Source
-
name(required): string
The key name of the configuration variable.Example:
processedFileSuffix
-
value(required): string
TThe value of the configuration variable for a key.Example:
complete
Nested Schema : DCNodeTypeRSM
Type:
object
The schema defining node type information for a node.
Show Source
-
configDataClass(required): string
The config data class name of the node.Example:
com.oracle.nm.collector.file.FtpEIConfigData
-
configDataGuiClass(required): string
The config data GUI class name of the node.Example:
com.oracle.nm.collector.file.FileEIConfigGUI
-
displayString(required): string
The display string represented as 'majorType : minorType'.Example:
EI : FileEI
-
majorType(required): string
The major type of the node.Example:
EI
-
minorType(required): string
The minor type of the node.Example:
FileEI
-
nodeClass(required): string
The class name of the node.Example:
com.oracle.nm.collector.file.FileEINode
Nested Schema : DestinationNodeConfig
Type:
object
The schema defining destination node's reference for a route.
Show Source
-
channelID(required): string
The identifier of the channel.Example:
1
-
destinationNodeID(required): string
The identifier of the destination node.Example:
z8kfsx-16it-3res21sew
-
Returns an object of type RoutingConfig(required): string
(uri)
The reference to get channel information for the route between the given node and its destination node.Example:
server:port/nodes/{id}/route/{destNodeId}
400 Response
The request cannot be processed due to a client error.
Root Schema : Error
Type:
object
Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).
Show Source
-
@type: string
Defines the sub-class entity when sub-classing.
-
cause: string
The cause of the exception.
-
code(required): string
The application relevant details defined in the API or a common list.
-
message: string
The details and corrective actions for the error shown to the client user.
-
reason(required): string
The reason for the error, which is shown to a client user.
-
referenceError: string
(uri)
The URI of the documentation describing the error.
-
status: string
The HTTP error code describing the error.
401 Response
The client does not have the correct privileges.
Root Schema : Error
Type:
object
Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).
Show Source
-
@type: string
Defines the sub-class entity when sub-classing.
-
cause: string
The cause of the exception.
-
code(required): string
The application relevant details defined in the API or a common list.
-
message: string
The details and corrective actions for the error shown to the client user.
-
reason(required): string
The reason for the error, which is shown to a client user.
-
referenceError: string
(uri)
The URI of the documentation describing the error.
-
status: string
The HTTP error code describing the error.
403 Response
The request was not authorized.
Root Schema : Error
Type:
object
Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).
Show Source
-
@type: string
Defines the sub-class entity when sub-classing.
-
cause: string
The cause of the exception.
-
code(required): string
The application relevant details defined in the API or a common list.
-
message: string
The details and corrective actions for the error shown to the client user.
-
reason(required): string
The reason for the error, which is shown to a client user.
-
referenceError: string
(uri)
The URI of the documentation describing the error.
-
status: string
The HTTP error code describing the error.
404 Response
The requested resource cannot be found.
Root Schema : Error
Type:
object
Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).
Show Source
-
@type: string
Defines the sub-class entity when sub-classing.
-
cause: string
The cause of the exception.
-
code(required): string
The application relevant details defined in the API or a common list.
-
message: string
The details and corrective actions for the error shown to the client user.
-
reason(required): string
The reason for the error, which is shown to a client user.
-
referenceError: string
(uri)
The URI of the documentation describing the error.
-
status: string
The HTTP error code describing the error.
405 Response
This method is not allowed.
Root Schema : Error
Type:
object
Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).
Show Source
-
@type: string
Defines the sub-class entity when sub-classing.
-
cause: string
The cause of the exception.
-
code(required): string
The application relevant details defined in the API or a common list.
-
message: string
The details and corrective actions for the error shown to the client user.
-
reason(required): string
The reason for the error, which is shown to a client user.
-
referenceError: string
(uri)
The URI of the documentation describing the error.
-
status: string
The HTTP error code describing the error.
409 Response
The request cannot be processed due to a conflict in the existing state of the resource.
Root Schema : Error
Type:
object
Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).
Show Source
-
@type: string
Defines the sub-class entity when sub-classing.
-
cause: string
The cause of the exception.
-
code(required): string
The application relevant details defined in the API or a common list.
-
message: string
The details and corrective actions for the error shown to the client user.
-
reason(required): string
The reason for the error, which is shown to a client user.
-
referenceError: string
(uri)
The URI of the documentation describing the error.
-
status: string
The HTTP error code describing the error.
500 Response
The system has encountered an internal server error.
Root Schema : Error
Type:
object
Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).
Show Source
-
@type: string
Defines the sub-class entity when sub-classing.
-
cause: string
The cause of the exception.
-
code(required): string
The application relevant details defined in the API or a common list.
-
message: string
The details and corrective actions for the error shown to the client user.
-
reason(required): string
The reason for the error, which is shown to a client user.
-
referenceError: string
(uri)
The URI of the documentation describing the error.
-
status: string
The HTTP error code describing the error.
Examples
The following example shows how to add a new node to the Node Manager by submitting a POST request on the REST resource using cURL. For more information about cURL, see Use cURL.
The -d option specifies the file to attach as the request body.
curl -X POST 'http://host:port/nodes' -d @sampleAddaNodetoNodeManager.json
Example of Request Body
The following is an example of the contents of the sampleAddaNodetoNodeManager.json file sent as the request body.
{
"dcNodeConfigData": {
"nodeConfigVariables": [
{
"name": "fileLocation",
"value": "/"
},
{
"name": "useFtp",
"value": "false"
},
{
"name": "pollingInterval",
"value": "600000"
},
{
"name": "intervalUnits",
"value": "Minutes"
},
{
"name": "filePatternMode",
"value": "simple"
},
{
"name": "processedFileSuffix",
"value": ".done"
},
{
"name": "unprocessedFileSuffix",
"value": ".complete"
},
{
"name": "deleteLocalFiles",
"value": "false"
},
{
"name": "mtCheck",
"value": "false"
},
{
"name": "fileleveltransaction",
"value": "false"
},
{
"name": "fdCheck",
"value": "false"
},
{
"name": "fsCheck",
"value": "false"
},
{
"name": "inputBackupDir",
"value": ""
}
],
"configRules" : [
]
},
"displayName": "Node-abc",
"nodeContext": "CartridgeKit#EI#FlexibleAsciiEINode",
"nodeManagerID": "NMGR-31eoel-otm-lnij9v9p",
"ruleFileDisplayName": "NewFile1",
"ruleFileName": "NewFile1.npl"}
Example of Response Body
The following is an example of a response
body.
{
"dcNodeConfigData": {
"configRules": [],
"nodeConfigVariables": [
{
"name": "fileLocation",
"value": "/"
},
{
"name": "osarsperfile",
"value": "2000"
},
{
"name": "idleosarwritetime",
"value": "60"
},
{
"name": "debuglevel",
"value": "OFF"
},
{
"name": "backup",
"value": "false"
},
{
"name": "filePatternMode",
"value": "simple"
},
{
"name": "unprocessedFileSuffix",
"value": ".complete"
},
{
"name": "asCodebase",
"value": "file:/home/ocomcuser/install/ocomc/config/31eoen-otm-lne95s3y"
},
{
"name": "bulkio",
"value": "false"
},
{
"name": "mtCheck",
"value": "false"
},
{
"name": "useFtp",
"value": "false"
},
{
"name": "ftpcfgfile",
"value": "/home/ocomcuser/install/ocomc/config/31eoen-otm-lne95s3y/ftp.cfg"
},
{
"name": "pollingInterval",
"value": "600000"
},
{
"name": "intervalUnits",
"value": "Minutes"
},
{
"name": "secondaryConfigFile",
"value": "secondary.cfg"
},
{
"name": "monitorinput",
"value": "false"
},
{
"name": "checkforosarstimer",
"value": "20"
},
{
"name": "fdCheck",
"value": "false"
},
{
"name": "fileleveltransaction",
"value": "false"
},
{
"name": "maxlogfilesize",
"value": "100000"
},
{
"name": "processedFileSuffix",
"value": ".done"
},
{
"name": "fsCheck",
"value": "false"
},
{
"name": "deleteLocalFiles",
"value": "false"
},
{
"name": "monitorinputtime",
"value": "1"
},
{
"name": "rulesfile",
"value": "file:/home/ocomcuser/install/ocomc/config/31eoen-otm-lne95s3y/?class=com.nt.udc.rules.EI.FileEI.NewFile1_npl"
},
{
"name": "monitorinputtimeunit",
"value": "Day"
},
{
"name": "inputBackupDir",
"value": ""
}
],
"ruleName": "file:/home/ocomcuser/install/ocomc/config/31eoen-otm-lne95s3y/?class=com.nt.udc.rules.EI.FileEI.NewFile1_npl"
},
"dcNodeType": {
"configDataClass": "com.metasolv.nm.collector.file.FtpEIConfigData",
"configDataGuiClass": "com.metasolv.nm.collector.file.FileEIConfigGUI",
"displayString": "EI : FileEI",
"majorType": "EI",
"minorType": "FileEI",
"nodeClass": "com.metasolv.nm.collector.file.FileEINode"
},
"destinationNode": [],
"displayName": "Node-abc",
"marketSegment": "CartridgeKit",
"nodeContext": "CartridgeKit#EI#FlexibleAsciiEINode",
"nodeId": "31eoen-otm-lne95s3y",
"nodeLabel": "12",
"ruleFileDisplayName": "NewFile1",
"ruleFileName": "NewFile1.npl",
"startState": false
}