‘Deep Links’ or ‘Direct Page Links’ allow users to directly open a specific tab or sub-tab in the Oracle Sales Cloud Simplified User Interface.
In my first post of this series, I talked about subscriptions. The next post in this series is about cookie sharing in APEX, I hope you enjoy it.
Saturday night I returned from my trip to Oslo where I attended the OUGN2015 conference. Myself, I presented some exciting WebLogic 12.1.3 features doing a rather technical hands-on demo with a few slides only. As usually, I tried to mention the existing show stoppers. Indeed I had no fixed agenda, instead I tried to make best use of the allotted […]
During this week, Oracle’s real-time streaming analytics platform known as OEP (Oracle Event Processing) had a strategic rebrand, being called now as Oracle Stream Explorer. It still includes the complete, highly scalable, high performance event-driven runtime from OEP, but now with a new collection of visually impactful web tooling features.
Oracle Stream Explorer is available now for download. For those unfamiliar with the product, it is a new tool based on Oracle Event Processing (OEP, formerly known as Complex Event Processing). It’s a graphical interface on OEP, hiding the rather daunting CQL (Continuous Query Language) from the user.
Installation is pretty straightforward. You start with installation of OEP 12.1.3.
The P2T – Prodution to Test – procedure is a very popular feature that FA customers utilize. It allows them to have their production data copied to another environment. Nowadays, P2T is a very common cloud SAAS and on-premise procedure. An important aspect that is not discussed frequently is the post-process of P2T. This approach is very important to avoid security issues, such as production passwords and emails being available in a different environment.
An important part of working with ODI is analysing the performance when it runs, and identifying steps that might be inefficient as well as variations in runtime against a baseline trend. The Operator tool in ODI itself is great for digging down into individual sessions and load plan executions, but for broader analysis we need a different approach. We also need to make sure we keep the data available for trend analysis, as it’s often the case that tables behind Operator are frequently purged for performance reasons.
In issue #8 we learned how we could create a framework with a closure and return object. We can extend this template for creating modules for a previously defined framework or parent module.
By modifying the framework template a little bit, we can create a module that plugs into another object.