Registering External Applications Using Fusion Middleware Control

25-8 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter

25.2.2 Registering External Applications Using WLST

Use the WLST command createExtAppConnection to create an external application connection. For command syntax and examples, see createExtAppConnection in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. Use the WLST command addExtAppCredential to add shared or public credentials for an existing external application connection. For details, see addExtAppCredential in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. Use the WLST command addExtAppField to define additional login criteria for an existing external application connection. For details, see addExtAppField in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. For information on how to run WLST commands, see Section 1.13.3.1, Running Oracle WebLogic Scripting Tool WLST Commands.

25.2.3 Registering External Applications in WebCenter Spaces

For information about registering external applications in WebCenter Spaces, see the section Registering External Applications Through WebCenter Administration in Oracle Fusion Middleware Users Guide for Oracle WebCenter.

25.2.4 Registering External Applications in WebCenter Portal Applications

For information about registering external applications in WebCenter Portal applications, see section Managing External Applications in Oracle Fusion Middleware Developers Guide for Oracle WebCenter.

25.3 Modifying External Application Connection Details

This section shows you how to modify the external application connection details by: ■ Section 25.3.1, Modifying External Application Connection Using Fusion Middleware Control ■ Section 25.3.2, Modifying External Application Connection Using WLST

25.3.1 Modifying External Application Connection Using Fusion Middleware Control

To update external application connection details: 1. Log in to Fusion Middleware Control and navigate to the home page for your WebCenter Portal application or WebCenter Spaces: ■ Section 6.3, Navigating to the Home Page for WebCenter Portal Applications . ■ Section 6.2, Navigating to the Home Page for WebCenter Spaces 2. Do one of the following: ■ For WebCenter Portal applications - from the Application Deployment menu, choose WebCenter Service Configuration. ■ For WebCenter Spaces - from the WebCenter menu, choose Settings Service Configuration . Managing External Applications 25-9 3. From the list of services on the WebCenter Service Configuration page, choose External Applications .

4. Select the name of the external application you want to modify, and click Edit.

5. Edit connection details, as required. For detailed parameter information, see Table 25–2 . Note that you cannot edit the name of the external application.

6. Click OK to save your changes.

25.3.2 Modifying External Application Connection Using WLST

Use the WLST command setExtAppConnection to edit existing external application connection details. For command syntax and examples, see setExtAppConnection in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. For information on how to run WLST commands, see Section 1.13.3.1, Running Oracle WebLogic Scripting Tool WLST Commands. For information about modifying external applications in WebCenter Spaces, see the section Editing External Application Connection Details in Oracle Fusion Middleware Users Guide for Oracle WebCenter.

25.4 Testing External Application Connections

For external applications that are created using login URLs, ensure that their login URLs are accessible. For information about direct URLs, see the section Automated Single Sign-On in Oracle Fusion Middleware Developers Guide for Oracle WebCenter.

25.5 Deleting External Application Connections

Take care when deleting an external application connection as WebCenter application users will no longer have access to that application, and any services dependent on the external application may not function correctly. In WebCenter Spaces, links to external applications are not automatically removed from the Application Navigator task flow when an external application is deleted. To prevent unsuccessful access attempts, administrators are advised to remove links to unavailable applications. This section includes the following subsections: ■ Section 25.5.1, Deleting External Application Connections Using Fusion Middleware Control ■ Section 25.5.2, Deleting External Application Connections Using WLST ■ Section 25.5.3, Deleting External Applications Connections in WebCenter Spaces Note: To edit details relating to an additional login field, use setExtAppField. To edit existing shared or public credentials, use setExtAppCredential. To delete an additional login field, use removeExtAppField. To delete shared or public credentials, use removeExtAppCredential. 25-10 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter

25.5.1 Deleting External Application Connections Using Fusion Middleware Control

To delete an external application connection:

1. Login to Fusion Middleware Control and navigate to the home page for your

WebCenter application or WebCenter Spaces: ■ Section 6.3, Navigating to the Home Page for WebCenter Portal Applications . ■ Section 6.2, Navigating to the Home Page for WebCenter Spaces

2. Do one of the following:

■ For WebCenter applications - from the Application Deployment menu, choose WebCenter Service Configuration. ■ For WebCenter Spaces - from the WebCenter menu, choose Settings Service Configuration .

3. From the list of services on the WebCenter Service Configuration page, choose

External Applications .

4. Select the name of the external application you want to remove, and click Delete.

25.5.2 Deleting External Application Connections Using WLST

Use the WLST command deleteConnection to remove an external application connection. For command syntax and examples, see deleteConnection in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. For information on how to run WLST commands, see Section 1.13.3.1, Running Oracle WebLogic Scripting Tool WLST Commands.

25.5.3 Deleting External Applications Connections in WebCenter Spaces

For information about deleting external applications in WebCenter Spaces, see the section Deleting External Applications in Oracle Fusion Middleware Users Guide for Oracle WebCenter.

25.5.4 Deleting External Applications Connections in WebCenter Portal Applications

For information about deleting external applications in WebCenter Portal applications, see the section Deleting External Application Registration Details in Oracle JDeveloper in Oracle Fusion Middleware Developers Guide for Oracle WebCenter. Note: To delete an additional login field, use removeExtAppField. To delete shared or public credentials, use removeExtAppCredential. 26 Managing REST Services 26-1 26 Managing REST Services This chapter provides an overview of managing Oracle WebCenter REST services in WebCenter applications. This chapter includes the following sections: ■ Section 26.1, What You Should Know About REST Services ■ Section 26.2, Performing Required Manual Configurations to Enable REST ■ Section 26.3, Understanding Security Tokens ■ Section 26.4, Configuring a Proxy Server ■ Section 26.5, Changing the REST Root Name ■ Section 26.6, Using Compression ■ Section 26.7, Handling Authentication Audience The content of this chapter is intended for Fusion Middleware administrators users granted the Admin or Operator role through the Oracle WebLogic Server Administration Console. For more information, see Section 1.8, Understanding Administrative Operations, Roles, and Tools.

26.1 What You Should Know About REST Services

REST REpresentational State Transfer is an architectural style for making distributed resources available through a uniform interface that includes uniform resource identifiers URIs, well-defined operations, hypermedia links, and a constrained set of media types. Typically, these operations include reading, writing, editing, and removing. Media types include JSON and XMLATOM. REST APIs are commonly used in client-side scripted, Rich Internet Applications. For example, a browser-based application written in Javascript can use Ajax techniques with REST APIs to send and receive application data from the server and update the client view. WebCenter provides a RESTful interface to many of its services, like Discussions, Lists, People Connections, and Search. For a complete list of the services that support REST, see Using Oracle WebCenter REST APIs in the Oracle Fusion Middleware Developer’s Guide for Oracle WebCenter. For a more complete introduction to REST and the WebCenter REST APIs, see Using Oracle WebCenter REST APIs in the Oracle Fusion Middleware Developer’s Guide for Oracle WebCenter. 26-2 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter

26.2 Performing Required Manual Configurations to Enable REST

The WebCenter REST services are not enabled by default. To enable the REST services to work, you must perform a manual configuration procedure. This procedure prepares the credential store to handle encrypted security tokens. For detailed information on the required configuration steps see Before Using REST: Perform This Required Manual Configuration in the Oracle Fusion Middleware Developers Guide for Oracle WebCenter.

26.3 Understanding Security Tokens

A user-scoped security token is embedded in the href and template attributes of every REST service URI. The token is both generated and validated by the server. The purpose of the security token is to prevent Cross-Site Request Forgery CSRF attacks. For example: link template=opaque-template-urime?startIndex={startIndex} itemsPerPage={itemsPerPage}token=generated-token resourceType=urn:oracle:webcenter:messageBoard href=opaque-urime?token=generated-token capabilities=urn:oracle:webcenter:read Security tokens are based on the authenticated user’s name. They do not expire, making it possible to both cache and bookmark the URIs. Security tokens are also salted, a cryptographic technique of adding extra characters to a string before encrypting it. Because of salting, if a security token is compromised, you will not have to change the user’s user name across the entire system to address the problem. This technique prevents cases where a user name is compromised and you don’t want to have to change the user name system wide to fix the problem. For more information on security tokens, see Security Considerations for WebCenter REST APIs in the Oracle Fusion Middleware Developers Guide for Oracle WebCenter.

26.4 Configuring a Proxy Server

This section explains how to set up a simple, response-rewriting reverse HTTP proxy on an Apache server. A proxy server is typically employed to avoid cross-domain request problems associated with making XMLHttpRequest XHR calls from a browser client. These calls are typically associated with the Ajax development technique for creating rich, interactive client-side interfaces. REST APIs are typically used within this kind of client-side development scenario. Note: The security token is not used for authentication or identity propagation.