README for Oracle Cloud - PaaS for SaaS Sample

Sample Name

Credit Health Score

Author

Justin Liang, Oracle A-Team

Source Code Location

Oracle Cloud Products Involved

Demonstrates

This sample demonstrates the following aspects of Oracle Cloud integration:

Primary Goals

Secondary Goals

Functional Overview

ABC Inc, attaches a Credit Health Score to every account/opportunity. This score ranges from 1 to 10 and is calculated based on a complex logic involving data from several internal and external systems. This score is used by the Sales Team, Service team, and Order Management team. The score logic is developed and maintained by a dedicated development team. In addition to providing the credit score for a given account, this application also logs each request to credit score. This logging mechanism is not implemented in this sample for the sake of simplicity.

Technical Overview

The Credit Health Score logic is exposed as a JAX-WS web service deployed on Oracle Java Cloud Service - SaaS Extension. Oracle Sales Cloud invokes this web service by passing an account ID as an input parameter and getting back the credit score which is then displayed in the Oracle Sales Cloud UI. In a more realistic implementation, this ID will be used to fetch additional information from Oracle Sales Cloud prior to calculating the credit score. For the sake of simplicity this web service is implemented with no real logic and simply returns a randomly generated credit score. The purpose of this sample is to demonstrate that no SAML set up is required between Oracle Java Cloud Service - SaaS Extension and Oracle Sales Cloud for this web service interaction. The only prerequisite is that the same user ID should exist in both Oracle Java Cloud Service - SaaS Extension and Oracle Sales Cloud identity stores. Because they are associated, Oracle Sales Cloud is automatically set up for SAML-based authentication with the Oracle Java Cloud Service - SaaS Extension instance, so there is no need to provide a user account password during the web service call.

Disclaimer

All sample code is provided by Oracle for illustrative purposes only. The objective of this sample is only to demonstrate the goals defined above and may not represent other best practices, functional or technical. These sample code examples have not been thoroughly tested under all conditions. Oracle, therefore, cannot guarantee or imply security, reliability, serviceability, or function of the sample code. All sample code contained herein are provided to you AS IS without any warranties of any kind. The implied warranties of non-infringement, merchantability and fitness for a particular purpose are expressly disclaimed.

User and Role Setup

Setting up the Sample

  1. The Oracle Java Cloud Service - SaaS Extension and Oracle Sales Cloud instances should be associated. Refer to Learn About Signing Up for an Oracle Cloud Subscription and Learn About Authorization Strategies for Oracle Java Cloud Service - SaaS Extension and Oracle SaaS Interactions for more details.
  2. For Oracle Java Cloud Service - SaaS Extension, a user with the Java Administrator Role to deploy an application to the Oracle Java Cloud Service - SaaS Extension instance is required. Refer to Chapter 7, "Managing Users and Roles" in Getting Started with Oracle Cloud for more details on creating users.

Running the Sample

Create a new user or use an existing user that exists in both Oracle Sales Cloud and Oracle Java Cloud Service - SaaS Extension. The role of this user in Oracle Sales Cloud could be Sales Administrator. There is no role logic for the user in Oracle Java Cloud Service - SaaS Extension in this sample.

Install Instructions

Oracle Java Cloud Service - SaaS Extension

  1. Clone the git repository to your local working directory. You can also download the code from OTN to your local working directory and follow the same steps below. However the remaining steps will assume that you are using git. The steps below should be executed using a user as defined in User and Role Setup Setting up the Sample section above.
  2. Open the .jws in JDeveloper or Eclipse. Further steps in this readme will refer to JDeveloper although similar steps can be performed in Eclipse.
  3. Deploy the application (CHSApp-CHS.war) to your Oracle Java Cloud Service - SaaS Extension instance. Right click on Application Name, and then go to application properties and select Deployment, Edit, Application Assembly, and select everything. You can deploy a WAR using the same process as deploying an EAR. Refer to Deploy Applications Individually Using Oracle Java Cloud Service - SaaS Extension Control for more details.
  4. Obtain the WSDL endpoint of the deployed application. It should be of the format https://jcs-host/chs/CreditHealthScorePort?WSDL

Oracle Sales Cloud

NOTE: It is critical to perform all Oracle Sales Cloud development/customization work in an activated sandbox. Not only does this aid in testing and debugging, but it also greatly simplifies un-installing/rolling back sample application extensions when required. Given that all customizations will be isolated to a sandbox, it is necessary to communicate sandbox details to others so that they can interact with sample application customizations while acting in different roles.

The steps involved in rolling back Oracle Sales Cloud customizations published from sandboxes to the main code line will not be documented here.

  1. Create a few Accounts in case there are none existing.
  2. Log in as a user that has access to Application Composer.
  3. Create or activate a sandbox as required.
  4. In the application composer, create a new web service with the following details.
  1. Create the custom CreditHealthScore field for the Account object.
  2. In Application Composer, expand the Standard Objects accordion, expand the Account object accordion, and click on the Fields link.
  3. Create a text field with the following attributes:
  1. To Place the custom field on the Default Layout page:

Running the Sample

  1. Log in to Oracle Sales Cloud using a user that is available on both Oracle Sales Cloud and Oracle Java Cloud Service - SaaS Extension.
  2. Go to Accounts, and create a new account.
  3. You should be able to see a new attribute on the default page called Credit Health Score with the number provided by the remote SOAP Web Service.

Additional information

For more details about this sample and other related samples refer to Oracle Cloud Solutions at https://docs.oracle.com/solutions.

Uninstall Instructions

Oracle Java CLoud Service - SaaS Extension

Undeploy the application from Oracle Java Cloud Service - SaaS Extension. Refer to the Undeploy section in Deploy Applications Individually Using Oracle Java Cloud Service - SaaS Extension Control for more details.

Oracle Sales Cloud

Deactivate and delete the development sandbox. This will roll back all Oracle Sales Cloud customizations.

Documentation

To learn how to further extend this sample, explore other implementation options, or develop your own application, visit the Oracle Cloud Solutions page at https://docs.oracle.com/solutions.

Known Issues

None

Copyright (c) 2015, 2018 Oracle and/or its affiliates. All rights reserved