Versions Compared

Old Version 4

changes.mady.by.user Hyzer

Saved on

compared with

New Version 5

changes.mady.by.user Hyzer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


That will cause all WS servers to listen on a queue or topic for messages

Sample message input

Code Block
{
  "grouperHeader": {
    "messageVersion": "1",  //mandatory
    "grouperWebServicesVersion": "v2_3_000",      //mandatory 
    "timestamptimestampInput": "20122017-0407-23T18:25:43.511Z", //timestamp message sent, mandatory
    "type": "grouperMessagingToWebService",       //says what type of message, mandatory
    "endpoint" : "WsRestAddMemberRequest",         //which endpoint, mandatory, matches the container name below
    "messageUuidmessageInputUuid", : "abc123",                 //for logging, mandatory, make up a uuid
    "replyToQueueOrTopicName",: "someQueue",       //if replying, optional
    "replyToQueueOrTopic",: "queue"                //if replying, "queue" or "topic", optional
  },
  // this is simply the json body of any grouper json web service normal or lite
  "WsRestAddMemberRequest":{
    "subjectLookups":[
      {
        "subjectId":"test.subject.0",
        "subjectSourceId":"jdbc"
      }
    ]
    ,
    "wsGroupLookup":{
      "groupName":"test:testGroup"
    }
  }
}

Sample message output

If there is a "reply to", then this is the message that will be sent

Code Block
{
  "grouperHeader": {
    "messageVersion": "1",                         //mandatory
    "timestampInput": "2017-07-23T18:23:43.511Z",  //timestamp message input sent, mandatory
    "timestampOutput": "2012-07-23T18:25:45.511Z", //timestamp message putput sent, mandatory
    "type": "grouperMessagingFromWebService",      //says what type of message, mandatory
    "endpoint": "WsRestAddMemberRequest",          //which endpoint, mandatory, matches input container
    "messageInputUuid": "abc123",                  //for logging, mandatory, matches the input uuid
    "httpResponseCode": 201,                       //http response code that would have been sent over WS, mandatory
    "httpHeader_X-Grouper-resultCode": "SUCCESS",  //http header that would have been sent over WS, mandatory
    "httpHeader_X-Grouper-success": "T",           //http header that would have been sent over WS, mandatory
    "httpHeader_X-Grouper-resultCode2": "NONE"     //http header that would have been sent over WS, mandatory
  },
  // this is simply the json body of any grouper json web service normal or lite
  "WsAddMemberResults":{
    "responseMetadata":{
      "millis":"120",
      "serverVersion":"2.2.0"
    },
    "resultMetadata":{
      "resultCode":"SUCCESS",
      "resultMessage":"Success for: clientVersion: 2.2.0, wsGroupLookup: WsGroupLookup[pitGroups=[],groupName=test:testGroup], subjectLookups: Array size: 1: [0]: WsSubjectLookup[subjectId=test.subject.0,subjectSourceId=jdbc]\n\n, replaceAllExisting: false, actAsSubject: null, fieldName: null, txType: NONE, includeGroupDetail: false, includeSubjectDetail: false, subjectAttributeNames: null\n, params: null\n, disabledDate: null, enabledDate: null",
      "success":"T"
    },
    "results":[
      {
        "resultMetadata":{
          "resultCode":"SUCCESS",
          "success":"T"
        },
        "wsSubject":{
          "id":"test.subject.0",
          "name":"my name is test.subject.0",
          "resultCode":"SUCCESS",
          "sourceId":"jdbc",
          "success":"T"
        }
      }
    ]
    ,
    "wsGroupAssigned":{
      "displayExtension":"testGroup",
      "displayName":"test:testGroup",
      "extension":"testGroup",
      "idIndex":"10000",
      "name":"test:testGroup",
      "typeOfGroup":"group",
      "uuid":"81cb5aa761fb477ca152738691a93e8b"
    }
  }
}