updated readme with WebIntegrationURL settings
This commit is contained in:
parent
7046796e4d
commit
8712d25400
44
README.md
44
README.md
@ -28,9 +28,9 @@ Parameters prefixed with 'tps:' will fetch values from the Tenant Properties Ser
|
||||
| integrationCardTitle | Title over Integration card |
|
||||
| integrationCardDoc | HTML document for contents of integration card |
|
||||
|
||||
# Installing into an Innovation Lab
|
||||
## Installing into an Innovation Lab
|
||||
|
||||
## Prerequisites
|
||||
### Prerequisites
|
||||
|
||||
Make sure npm is installed and node us up to date
|
||||
|
||||
@ -41,35 +41,45 @@ sudo n stable
|
||||
hash -r
|
||||
```
|
||||
|
||||
## Build the project
|
||||
### Build the project
|
||||
|
||||
Clone this project, install and build.
|
||||
|
||||
```sh
|
||||
|
||||
cd /opt/em/projects/current/demo/static
|
||||
git clone https://git.mortons.site/verint.com/ca_vue_apps.git
|
||||
cd ca_vue_apps
|
||||
npm install
|
||||
touch .env
|
||||
```
|
||||
|
||||
Edit the .env file to hold the Channel Automation api username & password we cannot use the '__Host-VRNTOTCT' cookie because it is HttpOnly and not passed to browser side javascript. So we use the oidc-token-service to grant us a token using username/password.
|
||||
|
||||
```env
|
||||
// file .env
|
||||
VITE_API_USERNAME=apiclient
|
||||
VITE_API_PASSWORD=apiclient
|
||||
```
|
||||
|
||||
Build the distribution
|
||||
|
||||
```sh
|
||||
npm run build
|
||||
```
|
||||
|
||||
## Proxy Apache to the distribution
|
||||
The 'static' directory is already served by Apache so this Application is now available. Configure the Web Integration URL to use it. See Screenshot below:
|
||||
|
||||
Add the following directive to the apache site configuration:
|
||||

|
||||
|
||||
```apache
|
||||
## Development
|
||||
|
||||
```
|
||||
|
||||
# Development
|
||||
|
||||
## Install
|
||||
### Install
|
||||
|
||||
```sh
|
||||
npm install
|
||||
```
|
||||
|
||||
## Running
|
||||
### Running
|
||||
|
||||
List options using:
|
||||
|
||||
@ -85,7 +95,7 @@ VITE_API_USERNAME=apiclient
|
||||
VITE_API_PASSWORD=apiclient
|
||||
```
|
||||
|
||||
## CORS Work Around
|
||||
### CORS Work Around
|
||||
|
||||
When developing this on localhost against Channel Automation APIs hosted elsewhere, you will need to apply a work around for CORS because the preflight check will fail with a 401 Not Authorized error.
|
||||
|
||||
@ -104,15 +114,15 @@ The fix is to use Apache Rewrite on the API host server to respond OK to the pre
|
||||
</Location>
|
||||
```
|
||||
|
||||
# Vue 3 + TypeScript + Vite
|
||||
## Vue 3 + TypeScript + Vite
|
||||
|
||||
This template should help get you started developing with Vue 3 and TypeScript in Vite. The template uses Vue 3 `<script setup>` SFCs, check out the [script setup docs](https://v3.vuejs.org/api/sfc-script-setup.html#sfc-script-setup) to learn more.
|
||||
|
||||
## Recommended IDE Setup
|
||||
### Recommended IDE Setup
|
||||
|
||||
- [VS Code](https://code.visualstudio.com/) + [Volar](https://marketplace.visualstudio.com/items?itemName=Vue.volar) (and disable Vetur) + [TypeScript Vue Plugin (Volar)](https://marketplace.visualstudio.com/items?itemName=Vue.vscode-typescript-vue-plugin).
|
||||
|
||||
## Type Support For `.vue` Imports in TS
|
||||
### Type Support For `.vue` Imports in TS
|
||||
|
||||
TypeScript cannot handle type information for `.vue` imports by default, so we replace the `tsc` CLI with `vue-tsc` for type checking. In editors, we need [TypeScript Vue Plugin (Volar)](https://marketplace.visualstudio.com/items?itemName=Vue.vscode-typescript-vue-plugin) to make the TypeScript language service aware of `.vue` types.
|
||||
|
||||
|
||||
BIN
screenshots/WebIntegrationURL_TelephonyContextExample.png
Normal file
BIN
screenshots/WebIntegrationURL_TelephonyContextExample.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 208 KiB |
Loading…
x
Reference in New Issue
Block a user