PeopleSoft is a metadata-driven application. It stands to reason, therefore, that the solutions we create require metadata. Sometimes metadata, which is supposed to be configurable, forces us down an immutable (non-configurable) path. Integration Broker is a fantastic example of semi-mutable, bordering on immutable metadata. As we prototype, we often make changes. But the testing associated with prototyping locks various metadata pieces. Sometimes we just want to test without metadata and backfill after we choose the proper path.
Here is a very simple metadata-free REST request example I run from a local App Engine program for prototyping and testing purposes.
Now, an important question:
Once you have a working "simple" solution, do you backfill and update with proper Integration Broker metadata?
Let us know your thoughts in the comments below!
At JSMpros, we teach Integration Tools concepts regularly. Check out our website to see what we are offering next!
