Applaud Cloud includes a secure global content delivery network (CDN) that accelerates the delivery of web assets. Applaud Cloud:
- Uses a network of over 70 data centers worldwide to provide a CDN
- Automatically delivers content to a user from the closest location, reducing latency
- Uses fine-tuned cache control headers
- Uses secure A-grade HTTPS encrypt
- Is available 24x7 and has near 100% uptime
Is designed to provide 99.999999999% durability of objects over a given year. This durability level corresponds to an average annual expected loss of 0.000000001% of objects. For example, for 10,000 web assets, you can on average expect to incur a loss of a single object once every 10,000,000 years
It's designed to sustain the concurrent loss of data in two facilities
Uses secure access permissions, Cross-Region Replication, versioning, and a functioning, regularly tested backup
You will usually see significant performance improvements using Applaud Cloud than if you were to host the same web assets on-premise.
All server-side data is retrieved using XHR HTTP requests directly to/from the Applaud REST API layer on your Oracle E-Business Suite instance.
In accordance with Oracle Application Development Guides, java classes will be copied to an xxas directory under JAVA_TOP. For example:
Some files may be copied to other application tops. For example, some images are copied to $OA_MEDIA/xxas/.
Applaud Solutions (XXAS) will be registered as a Custom Application. In accordance with Oracle Applications Development Standards, this custom application will own all Applaud seed data such as concurrent programs, messages and lookups.
Some files do not need to be applied to the database, such as installation-only files and Java classes. These are simply copied to the required Product Top directories.
New tables are delivered in SQLPlus scripts and are installed in the selected Custom Schema (typically XXAS). The installation will request the Custom Schema password, which is required to log in and create the tables.
The APPS account is granted all privileges (GRANT ALL) to each table.
Synonyms are delivered in SQLPlus scripts and are created in the APPS schema for each custom table. The synonyms have the same name as the table.
As per Oracle Application Development Guidelines, views are created in the APPS schema. Views are delivered in SQLPlus scripts.
SQL and PL/SQL scripts might perform any combination of the following:
- Load PL/SQL package specifications
- Load PL/SQL package bodies
- Run PL/SQL anonymous blocks that might call package procedures, functions, or APIs
- Run SQL DML statements
These scripts run as the APPS user.
Data files are loader files (typically with a .ldt file extension) that are loaded into Oracle E-Business Suite using the FNDLOAD executable. These load various types of Applaud Solutions seed data, the most common of which are:
- Custom Applications
- Concurrent Programs
- Descriptive and Key Flexfields
- Forms Personalization
- Menus and Functions
- Profile Options
- Request Groups
- Request Sets
- User Management Roles
- XML Publisher Definitions
Log files are created in the current working directory for each Data File loaded.
Applaud desktop and mobile apps use a service-oriented architecture and interact with the server via REST APIs, which are implemented using Java Servlets. Each REST API is defined in metadata stored in a custom table called xxas_com_service_repository. REST APIs can be added, changed or removed dynamically without any need to restart Application Tier services.
The custom Java Servlets maps the REST method and path to the corresponding REST API in the above table and invoke that service at run-time – typically running a SQL statement to retrieve data or running a PL/SQL anonymous block to change data.
Some Applaud products deliver a small number of OA Framework-based pages. These include XML files that must be loaded into Oracle’s MetaData Services (MDS) repository using the Java utility oracle.jrad.tools.xml.importer.XMLImporter.
XML Publisher files, which include both Data Definitions and Data Templates, are loaded using the Java utility oracle.apps.xdo.oa.util.XDOLoader.
Applaud uses Oracle-provided APIs to load data into standard Oracle tables. It also makes use of HRMS API User Hooks to add additional functionality, such as additional validation or firing new Workflow Business Events.
API User Hooks are delivered in SQL Scripts and follow Oracle HRMS API Guidelines when delivering new User Hooks.
A small number of installation steps cannot always be automated and must be completed as manual steps. For example, One-time Install will prompt you to run AutoConfig.
You will be prompted to complete any manual steps at the appropriate time during install, if applicable. These will be a detailed set of on-screen instructions that must be completed before continuing with patch installation.
Do not interrupt the current patch session; these steps should be performed in a separate session.
Many Applaud Products integrate with Oracle HRMS applications and other applications that use the Business Group partition. These products automate as much of the configuration as possible, which allows for rapid deployment.
Business Group-specific installation and configuration is performed by launching a concurrent request. The concurrent request is called Install Business Group Data and is available from the Applaud Administrator's responsibility. When running this concurrent request, you specify the Patch to install and the Business Group into which the configuration will be loaded. This gives you the flexibility to roll out each Business Group as and when required. This also reduces downtime, by bringing this part of installation online.