User Profiles
A user profile is a set of changeable options that affects the way your applications run. Oracle Application Object Library establishes a value
for each option in a user’s profile when the user logs on or changes responsibility. Your user can change the value of profile options at any
time. Oracle Application Object Library provides many options that your users can set to alter the user interface of your applications to
satisfy their individual preferences.
User Profile Levels
User profile options exist at Site, Application, Responsibility and User levels. Oracle Application Object Library treats user profile levels as a
hierarchy, where User is the highest level of the hierarchy, followed by Responsibility, Application and at the lowest level, Site. Higher–level
option values override lower–level option values. Each user profile option ordinarily exists at each level. For example, Oracle Application
Object Library provides a site–level Printer option, an application–level Printer option, and so on. As a result, if your Site–level Printer value
is ”New York”, but your User–level Printer value is ”Boston”, your reports print on the Boston printer.
Site Level
Site is the lowest user profile level. Site–level option values affect the way all applications run at a given installation.
Application Level
Application is the user profile level immediately above Site. Application–level option values affect the way a particular application runs.
Responsibility Level
Responsibility is the user profile level immediately above Application. Responsibility–level option values affect the way applications run for
all users of a responsibility.
User Level
User is the highest user profile level and is immediately above Responsibility. User–level option values affect the way applications run for an
application user.
Wednesday, January 30, 2008
JSP Application Components
JSP Application Components
A typical JSP application involves the following components: a browser for client access, a database for enterprise data and a web application server ("middle tier") where the application objects live.
Ø The browser communicates with the middle tier using HTTP (Hyper Text Transfer Protocol) which involves sending a request message to which the middle tier replies with a response message.
Ø A JSP is a file with some HTML and Java code that executes top to bottom. At runtime, it is compiled into a Java class which is actually a servlet.
Ø A servlet is a Java-based web application server extension program that implements a standard API.
Ø A servlet session is a mechanism for maintaining state between HTTP requests during a period of continuous interaction between a browser and a web application. A session may be initiated at any time by the application and terminated by the application, by the user closing the browser, or by a period of user inactivity. A session usually corresponds to an application login/logout cycle
Ø A JavaBean (or "bean" for short) is simply a reusable component that implements specific design patterns to make it easy for programmers and development tools to discover the object's properties and behavior.
Ø Any objects in the middle tier that communicate with the database use a JDBC (Java Database Connectivity) driver.
Sambavi.
A typical JSP application involves the following components: a browser for client access, a database for enterprise data and a web application server ("middle tier") where the application objects live.
Ø The browser communicates with the middle tier using HTTP (Hyper Text Transfer Protocol) which involves sending a request message to which the middle tier replies with a response message.
Ø A JSP is a file with some HTML and Java code that executes top to bottom. At runtime, it is compiled into a Java class which is actually a servlet.
Ø A servlet is a Java-based web application server extension program that implements a standard API.
Ø A servlet session is a mechanism for maintaining state between HTTP requests during a period of continuous interaction between a browser and a web application. A session may be initiated at any time by the application and terminated by the application, by the user closing the browser, or by a period of user inactivity. A session usually corresponds to an application login/logout cycle
Ø A JavaBean (or "bean" for short) is simply a reusable component that implements specific design patterns to make it easy for programmers and development tools to discover the object's properties and behavior.
Ø Any objects in the middle tier that communicate with the database use a JDBC (Java Database Connectivity) driver.
Sambavi.
Monday, January 28, 2008
Apache
Apache:
It is the most common web server (or HTTP server) software on the Internet. Apache is an open-source application originally created from a series of changes (“patches”) made to a web server written at the National Center for Supercomputing Applications, the same place the Mosaic web browser was created. Apache is designed as a set of modules, enabling administrators to choose which features they wish to use and making it easy to add features to meet specific needs including handling protocols other than the web-standard HTTP.
The Apache HTTP Server, commonly referred to simply as Apache, is a web server notable for playing a key role in the initial growth of the World Wide Web. Apache was the first viable alternative to the Netscape Communications Corporation web server (currently known as Sun Java System Web Server), and has since evolved to rival other Unix-based web servers in terms of functionality and performance.
Apache is developed and maintained by an open community of developers under the auspices of the Apache Software Foundation. The application is available for a wide variety of operating systems, including Unix, FreeBSD, Linux etc. Released under the Apache License, Apache is free software / open source software. Since April 1996 Apache has been the most popular HTTP server on the World wide Web.
It is the most common web server (or HTTP server) software on the Internet. Apache is an open-source application originally created from a series of changes (“patches”) made to a web server written at the National Center for Supercomputing Applications, the same place the Mosaic web browser was created. Apache is designed as a set of modules, enabling administrators to choose which features they wish to use and making it easy to add features to meet specific needs including handling protocols other than the web-standard HTTP.
The Apache HTTP Server, commonly referred to simply as Apache, is a web server notable for playing a key role in the initial growth of the World Wide Web. Apache was the first viable alternative to the Netscape Communications Corporation web server (currently known as Sun Java System Web Server), and has since evolved to rival other Unix-based web servers in terms of functionality and performance.
Apache is developed and maintained by an open community of developers under the auspices of the Apache Software Foundation. The application is available for a wide variety of operating systems, including Unix, FreeBSD, Linux etc. Released under the Apache License, Apache is free software / open source software. Since April 1996 Apache has been the most popular HTTP server on the World wide Web.
Basic Understanding about Canonicals
Basic Understanding about Canonicals
Pre-requisite : Basic knowledge on XML and XML related terms.
XML Schema Definition (XSD) is used to define the legal building blocks of an XML document. It describes the structure of an XML document.
Open Applications Group’s Integration Specification (OAGIS) provides a standard canonical business language that enables streamlined communication between businesses and/or business applications. OAGIS contains a collection of message sets for common business transactions, formatted in XML. These message sets are known as Business Object Document (BOD). But, it is also not possible to completely identify the unique characteristics that may provide value for a given customers implementation. In other words, there are always going to be extension needed such that a company can communicate its unique needs. Building up of these extensions in order to decrease the bridge between the OAGi standards and that need by the customer is known as Canonicals. OAGIS provides the user a unique form of extensibility to stretch the standard without breaking it.
Terms used :
A BOD consists of :-
An Application Area.
A DataArea that contains the Verb and the indicated Noun.
Verbs describe the action (for example : Process, Acknowledge, Change, etc.) and Nouns contain the business content (for instance: Invoice, Quotes, PurchaseOrder, etc.). The name of the BOD is always the VerbNoun combination. Eg: ProcessPurchaseOrder.
The following figure shows the structure of a BOD.
The ApplicationArea includes the following elements: the sender of the message; the CreationDateTime; the signature; the BODId, the unique identifier for the BOD instance; and a UserArea. The DataArea contains the instance(s) of the data values for the business transactions.
Canonicals can be extended using two techniques.
UserArea extensions which allow simple extensions of a few fields to an existing OAGIS component. In addition to this, we may use UserArea in order to shuffle the sequence of the fields/components based on the requirement.
Overlay extensions which allow users to extend an OAGIS Business object document, noun, and component to meet their own needs, even adding new BODs, verbs, nouns, and components where necessary. It is used when extensive additions or the creation of new BOD is needed.
Both of these extension mechanisms use XML namespaces to separate the extended content from the standard content and definitions. By using XML namespaces, extensions can be made without editing any of the OAGIS XML Schema files.
For Arrow, we are following the second approach, overlay extensions. Generally we can and should reuse the already extended field and component types for the new extensions.
Tool used : Altova XML Spy
Useful Links : www.w3schools.com - For detail understanding on XML and XSDs.
www.openapplications.org - Knowing more about OAGIS.
Pre-requisite : Basic knowledge on XML and XML related terms.
XML Schema Definition (XSD) is used to define the legal building blocks of an XML document. It describes the structure of an XML document.
Open Applications Group’s Integration Specification (OAGIS) provides a standard canonical business language that enables streamlined communication between businesses and/or business applications. OAGIS contains a collection of message sets for common business transactions, formatted in XML. These message sets are known as Business Object Document (BOD). But, it is also not possible to completely identify the unique characteristics that may provide value for a given customers implementation. In other words, there are always going to be extension needed such that a company can communicate its unique needs. Building up of these extensions in order to decrease the bridge between the OAGi standards and that need by the customer is known as Canonicals. OAGIS provides the user a unique form of extensibility to stretch the standard without breaking it.
Terms used :
A BOD consists of :-
An Application Area.
A DataArea that contains the Verb and the indicated Noun.
Verbs describe the action (for example : Process, Acknowledge, Change, etc.) and Nouns contain the business content (for instance: Invoice, Quotes, PurchaseOrder, etc.). The name of the BOD is always the VerbNoun combination. Eg: ProcessPurchaseOrder.
The following figure shows the structure of a BOD.
The ApplicationArea includes the following elements: the sender of the message; the CreationDateTime; the signature; the BODId, the unique identifier for the BOD instance; and a UserArea. The DataArea contains the instance(s) of the data values for the business transactions.
Canonicals can be extended using two techniques.
UserArea extensions which allow simple extensions of a few fields to an existing OAGIS component. In addition to this, we may use UserArea in order to shuffle the sequence of the fields/components based on the requirement.
Overlay extensions which allow users to extend an OAGIS Business object document, noun, and component to meet their own needs, even adding new BODs, verbs, nouns, and components where necessary. It is used when extensive additions or the creation of new BOD is needed.
Both of these extension mechanisms use XML namespaces to separate the extended content from the standard content and definitions. By using XML namespaces, extensions can be made without editing any of the OAGIS XML Schema files.
For Arrow, we are following the second approach, overlay extensions. Generally we can and should reuse the already extended field and component types for the new extensions.
Tool used : Altova XML Spy
Useful Links : www.w3schools.com - For detail understanding on XML and XSDs.
www.openapplications.org - Knowing more about OAGIS.
Types of Oracle Apps Patch
Before taking about various types of patches available, first take a look on definition of Patch:
What is patch?
Patch is program (set of instructions) to fix a particular problem or enhance/ add a particular feature in existing program/product/software.
Assuming all of us now understand basic definition of patch, let’s discuss types of patches:
What are various types of Oracle Apps Patch?
These are major classification of oracle apps patch
Standalone/Oneoff patches This is used to define patch created to fix single/particular problem.
Mini Pack This is group of oneoff patches for a particular product like INV, GL, AP and named like 11i.GL.E ( means this group of patches contain fix for 11i GL product (General Ledger till time E is released ) This is commutative which means it will include 11i.GL.A, 11i.GL.B ....11iGL.D till 11i.GL.E earlier in 10.7 it used to called as patchset.
Family Pack Group of mini packs in one family bundled together is called as family pack. They are usually named as 11i_PF. Few example of families are SCM (11i.SCM_PF.G), ATG (11i.ATG_PF.H) _PF indicate Product Family Pack
Maintenance Pack Group of family pack together is called as maintenance pack. So if you say your Version is 11.5.10 then its maintenance pack 10 (3rd digit is maintenance pack)
What is patch?
Patch is program (set of instructions) to fix a particular problem or enhance/ add a particular feature in existing program/product/software.
Assuming all of us now understand basic definition of patch, let’s discuss types of patches:
What are various types of Oracle Apps Patch?
These are major classification of oracle apps patch
Standalone/Oneoff patches This is used to define patch created to fix single/particular problem.
Mini Pack This is group of oneoff patches for a particular product like INV, GL, AP and named like 11i.GL.E ( means this group of patches contain fix for 11i GL product (General Ledger till time E is released ) This is commutative which means it will include 11i.GL.A, 11i.GL.B ....11iGL.D till 11i.GL.E earlier in 10.7 it used to called as patchset.
Family Pack Group of mini packs in one family bundled together is called as family pack. They are usually named as 11i_PF. Few example of families are SCM (11i.SCM_PF.G), ATG (11i.ATG_PF.H) _PF indicate Product Family Pack
Maintenance Pack Group of family pack together is called as maintenance pack. So if you say your Version is 11.5.10 then its maintenance pack 10 (3rd digit is maintenance pack)
JDBC (Java Database Connectivity)
The JDBC (Java Database Connectivity) API defines interfaces and classes for writing database applications in Java by making database connections. Using JDBC you can send SQL, PL/SQL statements to almost any relational database. JDBC is a Java API for executing SQL statements and supports basic SQL functionality. It provides RDBMS access by allowing you to embed SQL inside Java code. The Java application calls JDBC classes and interfaces to submit SQL statements and retrieve results.
The main objects of the JDBC API include:
Ø A DataSource object is used to establish connections. Although the Driver Manager can also be used to establish a connection, connecting through a DataSource object is the preferred method.
Ø A Connection object controls the connection to the database. An application can alter the behavior of a connection by invoking the methods associated with this object. An application uses the connection object to create statements.
Ø Statement, PreparedStatement, and CallableStatement objects are used for executing SQL statements. A PreparedStatement object is used when an application plans to reuse a statement multiple times. The application prepares the SQL it plans to use. Once prepared, the application can specify values for parameters in the prepared SQL statement. The statement can be executed multiple times with different parameter values specified for each execution. A CallableStatement is used to call stored procedures that return values. The CallableStatement has methods for retrieving the return values of the stored procedure.
Ø A ResultSet object contains the results of a query. A ResultSet is returned to an application when a SQL query is executed by a statement object. The ResultSet object provides methods for iterating through the results of the query.
The main objects of the JDBC API include:
Ø A DataSource object is used to establish connections. Although the Driver Manager can also be used to establish a connection, connecting through a DataSource object is the preferred method.
Ø A Connection object controls the connection to the database. An application can alter the behavior of a connection by invoking the methods associated with this object. An application uses the connection object to create statements.
Ø Statement, PreparedStatement, and CallableStatement objects are used for executing SQL statements. A PreparedStatement object is used when an application plans to reuse a statement multiple times. The application prepares the SQL it plans to use. Once prepared, the application can specify values for parameters in the prepared SQL statement. The statement can be executed multiple times with different parameter values specified for each execution. A CallableStatement is used to call stored procedures that return values. The CallableStatement has methods for retrieving the return values of the stored procedure.
Ø A ResultSet object contains the results of a query. A ResultSet is returned to an application when a SQL query is executed by a statement object. The ResultSet object provides methods for iterating through the results of the query.
Form Personalization
Form Personalization:
Personalization enables you to declaratively tailor the UI look-and-feel, layout or visibility of page content to suit a business need or a user preference.
Form personalization allows to alter the behavior of the product that oracle has provided.
It allows making declarative changes to a form.
Changes get applied at runtime when the proper trigger event occurs.
There are only limited trigger events they are
When new form instance,
When new block instance
When new item instance
When new record instance
Changes can get applied based on the condition specified in the conditions tab in the personalization form.
We can set the trigger event and the trigger object and the condition on which it has to be implemented.
We can also set the Context level whether it can be at Site level or responsibility level, User level or Industry level.
We can enable or disable a particular action.
In actions we can specify the property of a particular item and what value it should display.
Apply the changes immediately to test their effect
Personalization enables you to declaratively tailor the UI look-and-feel, layout or visibility of page content to suit a business need or a user preference.
Form personalization allows to alter the behavior of the product that oracle has provided.
It allows making declarative changes to a form.
Changes get applied at runtime when the proper trigger event occurs.
There are only limited trigger events they are
When new form instance,
When new block instance
When new item instance
When new record instance
Changes can get applied based on the condition specified in the conditions tab in the personalization form.
We can set the trigger event and the trigger object and the condition on which it has to be implemented.
We can also set the Context level whether it can be at Site level or responsibility level, User level or Industry level.
We can enable or disable a particular action.
In actions we can specify the property of a particular item and what value it should display.
Apply the changes immediately to test their effect
Subscribe to:
Posts (Atom)