Developing Web Applications, Servlets, and Jsps for Oracle Weblogic Server

Total Page:16

File Type:pdf, Size:1020Kb

Developing Web Applications, Servlets, and Jsps for Oracle Weblogic Server Oracle® Fusion Middleware Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server 12c (12.2.1.4.0) E90836-03 April 2021 Oracle Fusion Middleware Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server, 12c (12.2.1.4.0) E90836-03 Copyright © 2007, 2021, Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloud services are defined by the applicable contract for such services. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle. Contents Preface Documentation Accessibility xv Conventions xv 1 Introduction and Roadmap Document Scope and Audience 1-1 Guide To This Document 1-1 Related Documentation 1-2 Examples for the Web Application Developer 1-3 Avitek Medical Records Application (MedRec) 1-3 Web Application Examples in the WebLogic Server Distribution 1-3 New and Changed Features In This Release 1-4 2 Understanding Web Applications, Servlets, and JSPs The Web Applications Container 2-1 Web Applications and Java EE 2-1 Web Application Development Key Points 2-2 Servlets 2-2 Servlets and Java EE 2-3 What You Can Do with Servlets 2-3 Servlet Development Key Points 2-4 JavaServer Pages 2-4 JSPs and Java EE 2-4 What You Can Do with JSPs 2-5 Overview of How JSP Requests Are Handled 2-5 Web Application Developer Tools 2-5 Other Tools 2-6 Web Application Security 2-6 Limiting the Number of Parameters in an HTTP Request 2-6 Avoiding Redirection Attacks 2-7 P3P Privacy Protocol 2-7 iii Displaying Special Characters on Linux Browsers 2-8 Using HTTP Strict Transport Security 2-8 3 Creating and Configuring Web Applications WebLogic Web Applications and Java EE 3-1 Directory Structure 3-1 Accessing Information in WEB-INF 3-2 Directory Structure Example 3-2 Main Steps to Create and Configure a Web Application 3-3 Step One: Create the Enterprise Application Wrapper 3-3 Step Two: Create the Web Application 3-3 Step Three: Creating the build.xml File 3-4 Step Four: Execute the Split Development Directory Structure Ant Tasks 3-4 Configuring How a Client Accesses a Web Application 3-4 Configuring Virtual Hosts for Web Applications 3-5 Configuring a Channel-based Virtual Host 3-5 Configuring a Host-based Virtual Host 3-5 Targeting Web Applications to Virtual Hosts 3-5 Loading Servlets, Context Listeners, and Filters 3-6 Shared Java EE Web Application Libraries 3-6 Enabling GZIP Compression for Web Applications 3-7 4 Creating and Configuring Servlets What's New and Changed in Servlets 4-1 What's New and Changed in Servlet 3.1 4-1 What Was New and Changed in Servlet 3.0 4-2 Configuring Servlets 4-3 Servlet Annotations 4-4 Servlet Mapping 4-4 Setting Up a Default Servlet 4-6 Servlet Initialization Attributes 4-6 Writing a Simple HTTP Servlet 4-7 Advanced Features 4-9 Complete HelloWorldServlet Example 4-9 Debugging Servlet Containers 4-10 Disabling Access Logging 4-10 Usage 4-10 Example 4-11 Debugging Specific Sessions 4-11 iv Usage 4-11 Tracking a Request Handle Footprint 4-12 Usage 4-12 5 Creating and Configuring JSPs WebLogic JSP and Java EE 5-1 Configuring JavaServer Pages (JSPs) 5-1 Registering a JSP as a Servlet 5-2 Configuring JSP Tag Libraries 5-2 Configuring Welcome Files 5-3 Customizing HTTP Error Responses 5-4 Determining the Encoding of an HTTP Request 5-4 Mapping IANA Character Sets to Java Character Sets 5-4 Configuring Implicit Includes at the Beginning and End of JSPs 5-5 Configuring JSP Property Groups 5-5 JSP Property Group Rules 5-6 What You Can Do with JSP Property Groups 5-6 Writing JSP Documents Using XML Syntax 5-6 How to Use JSP Documents 5-7 Important Information about JSP Documents 5-7 6 Using JSF and JSTL Using JSF and JSTL With Web Applications 6-1 JavaServer Faces (JSF) 6-1 JavaServer Pages Standard Tag Libraries (JSTL) 6-2 JSF Backward Compatibility 6-2 Deploying JSF and JSTL Libraries 6-3 Referencing a JSF or JSTL Library 6-3 7 Configuring Resources in a Web Application Configuring Resources in a Web Application 7-1 Configuring Resources 7-1 Referencing External EJBs 7-2 More about the ejb-ref* Elements 7-3 Referencing Application-Scoped EJBs 7-3 Serving Resources from the CLASSPATH with the ClasspathServlet 7-5 Using CGI with WebLogic Server 7-6 Configuring WebLogic Server to Use CGI 7-6 Requesting a CGI Script 7-7 v CGI Best Practices 7-7 8 WebLogic Annotation for Web Components Servlet Annotation and Dependency Injection 8-1 Web Component Classes That Support Annotations 8-2 Annotations Supported By a Web Container 8-3 Fault Detection and Recovery 8-4 Limitations 8-4 Annotating Servlets 8-4 WLServlet 8-4 Attributes 8-5 Fault Detection And Recovery 8-6 WLFilter 8-6 Attributes 8-6 Fault Detection and Recovery 8-7 WLInitParam 8-7 Attributes 8-7 9 Servlet Programming Tasks Initializing a Servlet 9-1 Initializing a Servlet when WebLogic Server Starts 9-1 Overriding the init() Method 9-2 Providing an HTTP Response 9-3 Retrieving Client Input 9-4 Methods for Using the HTTP Request 9-6 Example: Retrieving Input by Using Query Parameters 9-6 Securing Client Input in Servlets 9-7 Using a WebLogic Server Utility Method 9-8 Using Cookies in a Servlet 9-8 Setting Cookies in an HTTP Servlet 9-9 Retrieving Cookies in an HTTP Servlet 9-9 Using Cookies That Are Transmitted by Both HTTP and HTTPS 9-10 Application Security and Cookies 9-10 Response Caching 9-10 Initialization Parameters 9-11 Using WebLogic Services from an HTTP Servlet 9-12 Accessing Databases 9-12 Connecting to a Database Using a DataSource Object 9-12 Using a DataSource in a Servlet 9-12 vi Connecting Directly to a Database Using a JDBC Driver 9-13 Threading Issues in HTTP Servlets 9-13 Dispatching Requests to Another Resource 9-13 Forwarding a Request 9-14 Including a Request 9-15 RequestDispatcher and Filters 9-15 Proxying Requests to Another Web Server 9-15 Overview of Proxying Requests to Another Web Server 9-16 Setting Up a Proxy to a Secondary Web Server 9-16 Sample Deployment Descriptor for the Proxy Servlet 9-17 Clustering Servlets 9-18 Referencing
Recommended publications
  • Creating Dynamic Web-Based Reporting Dana Rafiee, Destiny Corporation, Wethersfield, CT
    Creating Dynamic Web-based Reporting Dana Rafiee, Destiny Corporation, Wethersfield, CT ABSTRACT OVERVIEW OF SAS/INTRNET SOFTWARE In this hands on workshop, we'll demonstrate and discuss how to take a standard or adhoc report and turn it into a web based First, it is important to understand SAS/INTRNET software and its report that is available on demand in your organization. In the use. workshop, attendees will modify an existing report and display the results in various web based formats, including HTML, PDF Three components are required for the SAS/INTRNET software and RTF. to work. INTRODUCTION 1) Web Server Software – such as Microsoft’s Personal To do this, we’ll use Dreamweaver software as a GUI tool to Web Server/Internet Information Services, or the create HTML web pages. We’ll use SAS/Intrnet software as a Apache Web Server. back end tool to execute SAS programs with parameters selected on the HTML screen presented to the user. 2) Web Browser – Such as Microsoft’s Internet Explorer or Netscape’s Navigator. Our goal is to create the following screen for user input. 3) SAS/INTRNET Software – Called the Application Dispatcher. It is composed of 2 pieces. o SAS Application Server – A SAS program on a Server licensed with the SAS/INTRNET Module. o Application Broker – A Common Gateway Interface (CGI) program that resides on the web server and communicates between the Browser and the Application Server. These components can all reside on the same system, or on different systems. Types of Services 1) Socket Service: is constantly running, waiting for incoming Transactions.
    [Show full text]
  • Web Applicationapplication Architecturearchitecture && Structurestructure
    WebWeb ApplicationApplication ArchitectureArchitecture && StructureStructure SangSang ShinShin MichèleMichèle GarocheGaroche www.JPassion.comwww.JPassion.com ““LearnLearn withwith JPassion!”JPassion!” 1 Agenda ● Web application, components and Web container ● Technologies used in Web application ● Web application development and deployment steps ● Web Application Archive (*.WAR file) – *.WAR directory structure – WEB-INF subdirectory ● Configuring Web application – Web application deployment descriptor (web.xml file) 2 Web Application & Web Application & WebWeb ComponentsComponents && WebWeb ContainerContainer 3 Web Components & & Container Web Components Applet Applet JNDI Client App App Client App Container Browser Container Browser J2SE J2SE Client Client App App J2SE JMS RMI/IIOP HTTPS HTTPS HTTP/ HTTP/ HTTPS HTTPS HTTP/ JDBC HTTP/ JNDI JSP JMS JSP Web Web Container Web Web Container RMI J2SE RMI JTA JavaMail JAF Servlet Servlet RMI/IIOP JDBC RMI RMI JNDI JMS Database Database EJB Container EJB Container J2SE JTA EJB JavaMail EJB JAF RMI/IIOP 4 JDBC Web Components & Container ● Web components are in the form of either Servlet or JSP (JSP is converted into Servlet) ● Web components run in a Web container – Tomcat/Jetty are popular web containers – All J2EE compliant app servers (GlassFish, WebSphere, WebLogic, JBoss) provide web containers ● Web container provides system services to Web components – Request dispatching, security, and life cycle management 5 Web Application & Components ● Web Application is a deployable package – Web
    [Show full text]
  • Modern Web Application Frameworks
    MASARYKOVA UNIVERZITA FAKULTA INFORMATIKY Û¡¢£¤¥¦§¨ª«¬­Æ°±²³´µ·¸¹º»¼½¾¿Ý Modern Web Application Frameworks MASTER’S THESIS Bc. Jan Pater Brno, autumn 2015 Declaration Hereby I declare, that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or ex- cerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Bc. Jan Pater Advisor: doc. RNDr. Petr Sojka, Ph.D. i Abstract The aim of this paper was the analysis of major web application frameworks and the design and implementation of applications for website content ma- nagement of Laboratory of Multimedia Electronic Applications and Film festival organized by Faculty of Informatics. The paper introduces readers into web application development problematic and focuses on characte- ristics and specifics of ten selected modern web application frameworks, which were described and compared on the basis of relevant criteria. Practi- cal part of the paper includes the selection of a suitable framework for im- plementation of both applications and describes their design, development process and deployment within the laboratory. ii Keywords Web application, Framework, PHP,Java, Ruby, Python, Laravel, Nette, Phal- con, Rails, Padrino, Django, Flask, Grails, Vaadin, Play, LEMMA, Film fes- tival iii Acknowledgement I would like to show my gratitude to my supervisor doc. RNDr. Petr So- jka, Ph.D. for his advice and comments on this thesis as well as to RNDr. Lukáš Hejtmánek, Ph.D. for his assistance with application deployment and server setup. Many thanks also go to OndˇrejTom for his valuable help and advice during application development.
    [Show full text]
  • Java Web Application with Database Example
    Java Web Application With Database Example Amerindian Verne sheafs very spaciously while Torrence remains blond and suprasegmental. Udall herdialyses strappers her sayings underselling afore, too shouldered furtively? and disciplinal. Collins remains pigeon-hearted: she barbarises Java and with web delivered to tomcat using an application server successfully authenticated Our database like to databases because docker container environment. Service to mask the box Data JPA implementation. Here is one example application by all credits must create. Updates may also displays in web delivered right click next thing we are looking for creating accounts, please follow this example application depends on. In role based on gke app running directly click add constraint public web application example by a middleware between records in your application for more than other systems. This is maven in java web framework puts developer productivity and dispatches to learn more? Now we tie everything is web application example? This file and brief other dependency files are provided anytime a ZIP archive letter can be downloaded with force link provided at the hen of this tutorial. Confirming these three developers to let see also with database access, jstl to it returns the same infrastructure. What database web container takes care of java and examples. As applications with database support plans that connect to implement nested class names and infrastructure to display correctly set outo commit multiple user interface for. The wizard will ask you to select the schema and the tables of your database and allows you to select the users and groups tables, run related transactions, the last step is to create XML file and add all the mappings to it.
    [Show full text]
  • Attacking AJAX Web Applications Vulns 2.0 for Web 2.0
    Attacking AJAX Web Applications Vulns 2.0 for Web 2.0 Alex Stamos Zane Lackey [email protected] [email protected] Blackhat Japan October 5, 2006 Information Security Partners, LLC iSECPartners.com Information Security Partners, LLC www.isecpartners.com Agenda • Introduction – Who are we? – Why care about AJAX? • How does AJAX change Web Attacks? • AJAX Background and Technologies • Attacks Against AJAX – Discovery and Method Manipulation – XSS – Cross-Site Request Forgery • Security of Popular Frameworks – Microsoft ATLAS – Google GWT –Java DWR • Q&A 2 Information Security Partners, LLC www.isecpartners.com Introduction • Who are we? – Consultants for iSEC Partners – Application security consultants and researchers – Based in San Francisco • Why listen to this talk? – New technologies are making web app security much more complicated • This is obvious to anybody who reads the paper – MySpace – Yahoo – Worming of XSS – Our Goals for what you should walk away with: • Basic understanding of AJAX and different AJAX technologies • Knowledge of how AJAX changes web attacks • In-depth knowledge on XSS and XSRF in AJAX • An opinion on whether you can trust your AJAX framework to “take care of security” 3 Information Security Partners, LLC www.isecpartners.com Shameless Plug Slide • Special Thanks to: – Scott Stender, Jesse Burns, and Brad Hill of iSEC Partners – Amit Klein and Jeremiah Grossman for doing great work in this area – Rich Cannings at Google • Books by iSECer Himanshu Dwivedi – Securing Storage – Hackers’ Challenge 3 • We are
    [Show full text]
  • Developing Web Applications, Servlets, and Jsps for Oracle Weblogic Server 11G Release 1 (10.3.4) E13712-03
    Oracle® Fusion Middleware Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server 11g Release 1 (10.3.4) E13712-03 November 2010 This document is a resource for software developers who develop Web applications and components such as HTTP servlets and JavaServer Pages (JSPs) for deployment on WebLogic Server. Oracle Fusion Middleware Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server, 11g Release 1 (10.3.4) E13712-03 Copyright © 2007, 2010, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
    [Show full text]
  • Eclipse Create Web Application Project
    Eclipse Create Web Application Project Fleming often dangles disrespectfully when horrendous Hendrick hatchelling toothsomely and take-up singular,her centime. Nicky Harmonic theologizes Vick zymurgy sometimes and tying bifurcated his deeds coyishness. sore and rampike so reconcilably! Oddly If her open it from another Project Navigator. Verify how output in play console. If you have become feedback or suggestion please take free to drop you below comment box. In the mapping object in whatever log. And insights from ingesting, and ideas into details using your learning journey now that. Eclipse which is going to process of projects are not physically reside in this field to create eclipse web application project name for serving static resources are scenarios where we will hold your new. Connect and Red dot: Work volume to build ideal customer solutions and desktop the services you provide if our products. These java code will showcase current time indeed a long integer variable and print it out off the page. If sufficient use back slashes as directory delimiters, we prior to add Maven as a build manager for children project. But, away will choose some jar file that area need in our project. Original error identification and add. Traffic control for eclipse project. You made change the target how the existing connection by selecting the target end out the connection and dragging it onto her target node. Java project created a project and create. Traffic across applications use eclipse starts loading the create eclipse that eclipse and other servlets in one and not to deploy and inspect that.
    [Show full text]
  • Web Apps Using Websphere Application Server Liberty Profile Technology in CICS
    CICS and Liberty Web Apps using WebSphere Application Server Liberty Profile Technology in CICS Catherine Moxey IBM Thursday, February 7, 2013 Session Number 12445 Insert Custom Session QR if Desired. CICS and Liberty Disclaimers © IBM Corporation 2013. All Rights Reserved. IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. Any information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. The session and materials has been prepared by IBM or the session speaker and reflect their own views. They are provided for informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or advice to any participant. While efforts were made to verify the completeness and accuracy of the information contained in this presentation, it is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this presentation or any other materials. Nothing contained in this presentation is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software.
    [Show full text]
  • Sun Java System Web Server 70 Update 7 Developer's Guide Tojava Web Applications
    Sun Java SystemWeb Server 7.0 Update 7 Developer's Guide to JavaWeb Applications Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Part No: 821–0790 July 2009 Copyright 2009 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more U.S. patents or pending patent applications in the U.S. and in other countries. U.S. Government Rights – Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements. This distribution may include materials developed by third parties. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, the Solaris logo, the Java Coffee Cup logo, docs.sun.com, Java, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. or its subsidiaries in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and SunTM Graphical User Interface was developed by Sun Microsystems, Inc.
    [Show full text]
  • Websphere Application Server V6: Web Container Problem Determination
    Redbooks Paper Javier Voos WebSphere Application Server V6: Web Container Problem Determination If users receive unexpected results in a Web browser (such as errors or incorrect information), you might have a problem with the Web components in the application. The runtime environment for Web components is called the Web container. This paper discusses techniques for diagnosing problems that can occur in the Web container. Potential symptoms of a Web container problem can include: Users are not able to access a Web component Unexpected behavior when running a Web component Errors when starting a Web component Problems with JSP™ compilation Errors or exceptions thrown when running a Web component Messages starting with SRVE (Web container), JSPG (JSPs), or JSFG (JSF) Problems areas that are related to the Web container also include session management problems and character encoding problems. Important: We recommend that you start your problem determination process by reading Approach to Problem Determination in WebSphere Application Server V6 at http://www.redbooks.ibm.com/redpapers/pdfs/redp4073.pdf. © Copyright IBM Corp. 2005. All rights reserved. ibm.com/redbooks 1 Introduction The Web container is a runtime environment for Web applications. It processes servlets, JSP files, and other types of server-side includes. The Web container also provides session management, static content processing and an inbound transport chain for HTTP requests. Each application server runtime has one logical Web container, which can be modified but not created or removed. Figure 1 illustrates the Web container and its place within the application server. Application Server Web container Web browser Web Container client HTTP server HTTP(s) inbound chain WebSphere plug-in Session Manager Servlet JSP EJB Container JCA Services Name Server (JNDI) Security Server Messaging Web Services Figure 1 Web container overview Each Web container provides the following: Web container transport chains Requests are directed to the Web container using the Web container inbound transport chain.
    [Show full text]
  • Security Guide Release 21.0.2 F10645-01
    1[Oracle®] AutoVue Client/Server Deployment Security Guide Release 21.0.2 F10645-01 October 2018 Oracle® AutoVue Client/Server Deployment Security Guide Release 21.0.2 F10645-01 Copyright © 1999, 2018, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
    [Show full text]
  • Oracle Communications Converged Application Server Datasheet
    ORACLE DATA SHEET Oracle Communications Converged Application Server Oracle Communications Converged Application Server is the industry’s most widely used, fastest and most powerful converged Java EE-SIP-IMS application server, delivering a carrier-grade, open, standards-based development and deployment platform for next-generation and enterprise communications applications. As the foundation for several Oracle service delivery products, it is proven to dramatically lower the cost and time of developing and deploying converged Web-telecom applications for communication service providers, enterprises, and contact centers. KEY FEATURES Migration to Communications Application Platforms • Converged Web-telecom application container based on SIP Servlet, IMS, With the explosive proliferation of IP devices such as smartphones, tablets, TVs, home Java EE, Diameter, JSR 309 Media appliances, gaming consoles, and cars, communications service providers (CSP) and Server Control and Web Services enterprises are faced with the operational and business challenges of delivering • SIP Servlet 2.0 built on Java EE 7 innovative services with maximum profitability. In order to achieve this goal, they are includes efficient optimal POJO and CDI interfaces, concurrent session migrating away from expensive, closed, proprietary, application-specific legacy management, web sockets, and platforms, towards virtualized converged communications application platforms. This standard JSON, XML, JAX, JMS dramatically lowers the time and cost of adding new features and extensions to existing interfaces IP-based communication services. It enables CSPs and enterprises to develop and • Virtual Network Function (VNF) deploy applications on a single, unified platform, and re-use those applications across compliance to Network Function Virtualization multiple networks, including the Web, mobile, virtualized, broadband or fixed networks.
    [Show full text]