Service Operation Routings

A routing is a key piece of configuration in service operations. They play different roles depending on if you are using REST or non-REST operations.

  • REST Routings

    • There is only ever one routing
    • The routing is created automatically by the Service Operations pages.
    • The routing can control logging and other advanced behavior.
  • Standard Service Operations (non-REST) Routings

    • Controls what NODE the Service Operation can publish and subscribe
    • Are generally manually configured

Synchronous Logging

A routing is where you can turn on or off logging. By default, a Synchronous operation will not log it’s request.

Todo

Why no Async logging?

Todo

  • Operation Alias
  • Transformations

Best Practices

  • When configuring Service Operation Routings be sure to never us “Any to Local” routings. Always explicitly define your nodes in the routings to tell the systems what integrations go where.
    • This can be self documenting of who uses the integration as well as more secure if someone improperly configures a node.
  • For Synchronous Operations you likely want at least header logging so we can have some visibility in the usage of your service. Otherwise, there is no other way to see successful operations.

Author Info
Chris Malek

Chris Malek is a PeopleTools® Technical Consultant with two decades of experience working on PeopleSoft enterprise software projects. He is available for consulting engagements.

About Chris Work with Chris