When inbound Request Parameters need to simply be received and saved in the GLU Object Model (i.e. within the GLU.Engine at transaction processing time) for later re-use (i.e. they are not received in a list or array), you must first configure the ‘Unmarshalling’ of the specific Parameters.
In the example below …
- the Parameter has a data type of ‘Text’,
- the Parameter is passed and received in the ‘Header’,
- the ‘Parameter Name’ for the Parameter is ‘USERNAMER’
These configurations define the Type, Location (Header/Body/Query), Parameter Value (Parameter Name), and the Type of the Parameter.
You should configure these settings according to your specific Parameter Type, Location and Name.
Next, the received Parameter must be saved in the GLU Object Model for later re-use, see example below:
- the Parameter type is ‘Text’,
- the Parameter name is translated in this example from ‘USERNAME’ to be saved a ‘userName’,
This defines how the Parameter is stored in GLU and in this example we have translated the Parameter name from ‘USERNAME’ to ‘userName’.
