Posts Tagged ‘XML’
Protected: Coming Soon: Leveraging BPM 11g Capabilities – Argument Mapping
February 11th, 2010 by Mark Peterson • Comments OffComments Off
XML Publisher Issue
December 2nd, 2008 by Anonymous • No Comments »From our Guest Author, Jeff Vold, Hazelton Foundation:
We encountered an issue with XML Publisher that we reported to Oracle Support. After providing Oracle with all the information, they were able to reproduce the issue on their end as well. They then created a patch that resolved our issue.
Main issue: XML Publisher worked on our single node install, but did not work on our multi-node environment. Our hardware is set up with physical and logical host names with their own ip addresses. We are using logical host names. Plus, our two application tiers are fronted-ended with a load balancing content switch.
XML publisher works in a two-step process. It first produces the XML file and then calls the Output Post Processor (OPP) to convert it to the final published format. The first step would always complete, but trying to publish the report in the final format would error with “java.net.ConnectException: Connection timed out”. It appears that OPP was trying find the CCM Request Id from the first step and then do a remote file transfer of the XML file to the app tier to output the report.
Resolution: Oracle created Patch 7449694, which creates a new profile option called “Concurrent: Force Local Output File Mode”. Setting this “YES” forces the transfer to take place locally via FNDFS.
Good Metalink Notes:
MetaLink Doc ID: 753395.1, Java.Net.Connectexception:Connection Timed Out Error For XML Reports
MetaLink Doc ID: 364547.1 – Troubleshooting Oracle XML Publisher For The Oracle E-Business Suite 2.1 Two step publishing method
- Submit a Concurrent Program with the Output Format set to XML
- Submit the XML Report Publisher concurrent request to produce the final output. At submission time, specify the Request ID from step 1, choose the desired template and the Output Format (PDF, RTF,…).
MetaLink Doc ID: 291792.1 – Using the Output Post Processor (OPP) in Oracle Applications Concurrent Processing
MetaLink Doc ID: 362496.1 – How to Determine the Version of Oracle XML Publisher for Oracle E-Business Suite 11i and Release 12
AIA Foundation Pack Business Objects
February 29th, 2008 by Robert McMillen • No Comments »This post is more technical and will drill down into the various Enterprise artifacts that come with the Foundation Pack.
The first are the Enterprise Business Objects (EBO). There are about 30 of these in v2.01 but new ones will be added in subsequent releases. EBO’s are define for Customer, Supplier, Invoice and other common business artifacts.
Each EBO contains all of the attributes necessary to describe the particular object. As mentioned previously Oracle has researched multiple applications to come up with just about every attribute possible for a best-of-breed capability. These attributes are described in XML using an XML Schema Definition (XSD) file.
Using EBO’s provides several clear benefits:
EBO’s eliminate Point to Point Duplication- P2P works when connecting two systems but requires a complete re-implementation when you introduce a second service provider / requester
EBO’s support a One to Many Model – For Integrations that map one service request to many service providers (or vice versa), EBOs allow re-use of initial implementation and reduces overall number of transformation maps to generate
EBO’s are Hot Pluggable- Common Objects abstracts application service providers from service requesters and centralizes routing and mediation which allows any application to plug into the integrated process flow
EBO’s provide standards based content to drive interoperability- EBOs are based on the Open Applications Group content known as OAGIS and have been extended to incorporate best-of-breed attributes.
But what if you need something that is not in the provided EBO for Supplier, as an example?
AIA provides a construct for customizing the EBO which will survive future upgrades.
AIA Origins – Service Oriented Architecture
February 29th, 2008 by Robert McMillen • No Comments »With the introduction of Services, XML, Java and the introduction of WSDL, WSIF there came other new supporting software products. Java had always depending on the Java Virtual Machine because it is essentially an interpreted language (but it can be compiled to machine language..).
The new supporting software products included the Enterprise Service Bus (ESB), the Business Processing Execution Language (BPEL) and the Business Process Engine.
BPEL was an XML language for grouping the execution of individual Services together. BPEL is sort of like a batch language. It provides If-Then-Else capabilities and can start a Service, send it a message, and handle the result. BPEL needs a Business Process Engine (written in Java) to execute. The nice thing about BPEL is that it is a configuration language that doesn’t require complex programming. It relies on the Services to do the low-level work. If a Services is an employee, then a BPEL document is the Manager telling who to do what and when.
The ESB was a solution for the problem of automating connections between different environments and doing any necessary translation. Many systems have different formats for their information and it made sense to create something in-between to translate the format and pass it automatically on to the destination. ESB is a Java program that does this using XML instructions. It is called a Service Bus because like a Data Bus in that it manages the transmission of information between two parties.
ESB, BPEL and the Business Process Manager/Engine along with several other components are typically bundled into a SOA Suite. The other components could be a Service Repository which is a directory of the registered Services or a Web Services Manager (WSM) which enforces certain security restrictions. What security you ask? Well suppose you have a Service that returns compensation from the Payroll system. You would want to restrict who could call that Service, right? The WSM allows restrictions to be defined so that doesn’t happen.
So now we have a Service Oriented Architecture Suite. That seems nice and tidy. Why would we need anything more? And that’s where AIA Foundation Pack comes in…