How to Integrate Oracle Digital Assistance in Oracle VBCS

 Integrating Oracle Digital Assistant (ODA) with Oracle Visual Builder Cloud Service (VBCS) involves embedding the chatbot into a VBCS application. Here's a step-by-step guide:

1. Create Oracle Digital Assistant (ODA)

  • If you don’t have an Oracle Digital Assistant, create one using the ODA console.
  • Train your chatbot with intents, entities, and skills.

2. Enable Channel in Oracle Digital Assistant

  • In ODA, go to Settings > Channels.
  • Create a new Web channel, where you will get the Channel ID, URL, and Secret Key.
  • Make sure you configure it with the proper chatbot that you want to embed in your VBCS application.

3. Embed ODA in VBCS

Open your VBCS Application:

  • In Oracle VBCS, go to the application where you want to integrate ODA.
  • In the Page Designer, open the page where you wish to include the chatbot.

Add ODA as a Component:

  • Add a new HTML component (or use a static HTML resource).
  • In the HTML component, embed the following JavaScript to load your ODA

<script>
window.Oracle = {
ODA: {
tenantId: '<TENANT_ID>',
chatWidget: {
uri: 'https://<ODA_INSTANCE_URL>/client.html',
channelId: '<CHANNEL_ID>',
secret: '<SECRET_KEY>',
initUserHiddenMessage: 'Hello! How can I assist you today?'
}
}
};
</script>
<script src="https://<ODA_INSTANCE_URL>/loader.js"></script>

Replace:

  • <TENANT_ID>: with your ODA tenant ID.
  • <ODA_INSTANCE_URL>: with your Oracle Digital Assistant instance URL.
  • <CHANNEL_ID>: the channel ID from the web channel created earlier.
  • <SECRET_KEY>: the secret key from the web channel.

4. Customize the Appearance

  • You can style the chatbot widget using custom CSS or configure ODA settings (via the ODA console) for the chatbot's appearance to align with your app’s branding.

5. Test the Integration

  • Once the changes are applied, run the VBCS app and verify the chatbot is properly loaded and responding as expected.
  • Ensure that communication between VBCS and ODA is working seamlessly.

6. Deploy Your VBCS Application

  • After successful integration and testing, deploy your VBCS application. The Oracle Digital Assistant should now be embedded, providing chatbot functionality to your users.

This integration allows your VBCS app to offer a seamless user experience with interactive chatbot support from Oracle Digital Assistant.

If you need any specific configurations or tips for enhancing this setup, let me know!

Comments

Post a Comment

Popular posts from this blog

Creating Physical Standby using RMAN Duplicate Without Shutting down The Primary

Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 10.2.0.4 - Release: 10.1 to 10.2 Information in this document applies to any platform. Oracle Server Enterprise Edition - Version: 10.2.0.1 to 10.2.0.4 Goal  - Ref Metalink ID - 789370.1 The following note describes step-by-step procedure to create physical standby by using RMAN duplicate without shutting down the primary (Production) database. Database Name :- prim Primary db_unique_name :- prim standby db_unique_name :- stdby Primary Hostname :- raca.idc.oracle.com standby Hostname :- core1.idc.oracle.com Solution 1.Enable force logging. 2.Create SRL(standby redo logs). 3.Make proper changes in the parameter file of primary. 4.Backup the database that includes backup of datafiles, archivelogs and controlfile for standby and copy the backups to standby server. 5.Create the parameter file for standby, 6.Establish the connectivity from primary to standby. 7. Move backup to standby. 8 and 9. Start the standby instance. 10.U
Read more

How to Configure Logging for EM 12c Management Agent

The goal of this article is to provide instruction on how to enable logging for the Enterprise Manager 12c Management Agent.. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The logging properties for the agent are stored in $EMSTATE/sysman/config/emd.properties file, same as in 11.1. But the properties that control logging follow the log4j configuration syntax instead of the syntax supported by the 11.1 agent. To active changes to the logging parameters, you can use either of the emctl commands: emctl reload agent emctl setproperty agent Overview Agent logging entries look similar to the standard log4j logging, with the only significant difference being the prefix 'Logger.' that you will see on each line. For example: # logging properties Logger.log4j.appender.Rolling=org.apache.log4j.RollingFileAppender Logger.lo
Read more

index rebuild candidates oracle

Steps... CREATE TABLE index_log (  owner          VARCHAR2(30),  index_name     VARCHAR2(30),  last_inspected DATE,  leaf_blocks    NUMBER,     target_size    NUMBER,  idx_layout     CLOB); ALTER TABLE index_log ADD CONSTRAINT pk_index_log PRIMARY KEY (owner,index_name); CREATE TABLE index_hist (  owner          VARCHAR2(30),  index_name     VARCHAR2(30),  inspected_date DATE,  leaf_blocks    NUMBER,     target_size    NUMBER,  idx_layout     VARCHAR2(4000)); ALTER TABLE index_hist ADD CONSTRAINT pk_index_hist PRIMARY KEY  (owner,index_name,inspected_date); CREATE OR REPLACE PACKAGE index_util AUTHID CURRENT_USER IS vMinBlks     CONSTANT POSITIVE := 1000; vScaleFactor CONSTANT NUMBER := 0.6; vTargetUse   CONSTANT POSITIVE := 90;  -- equates to pctfree 10  vHistRet     CONSTANT POSITIVE := 10;  -- (#) records to keep in index_hist  procedure inspect_schema (aSchemaName IN VARCHAR2);  procedure inspect_index (aIndexOwner IN VARCHAR2, aIndexName IN VARCHAR2, a
Read more