Merge branch 'main' into JDE-Sol-def

Author: palaparthy

ai-and-app-modernisation/content-management/webcenter-content-management/webcenter-ebs-adapter/README.md

@@ -1,13 +1,25 @@
 # Oracle E-Business Suite Adapter for WebCenter Content 
 
-* The Oracle E-Business Suite Adapter for WebCenter enables business users to easily   access, view and initiate tasks on documents associated with transactions 
+* The Oracle E-Business Suite Adapter for WebCenter enables business users to easily access, view and initiate tasks on documents associated with transactions 
  directly from within or outside the E-Business Suite environment*
 
 Reviewed: 30.01.2024
 
+# Managed Attachment Solution 
+
+Content Server documents are listed as managed attachments to business application entities in a customizable window launched from a link, button, or menu, depending on business application configuration. For example, a business application user displays an Employee record, invokes the Managed Attachment functionality by clicking a button, and attaches a passport image and supporting identity documents.
+
+The Managed Attachments Solution, shown in Figure 1-10, enables business users to attach, scan, and retrieve attachments stored in a Content Server repository. An Oracle WebCenter Content Server repository enables users throughout an enterprise to view, collaborate on, and retire content, ensuring that content is secure, accurate, and up-to-date.
+
+<img src="./images/managedattachment.gif"></img>
+
 # How to use this asset?
 
-This asset is provided as an example. Please tailor the code according to your needs and your context.
+This asset is provides demo to integrate Oracle E-Business suite with WebCenter Content application to upload Invoices from the Payable module as an example. Please tailor the code according to your needs and your context.
+
+<video autoplay loop style="width:100%; height: auto; position:absolute; z-index: -1;">
+  <source src="./files/video/EBusinessIntegrationwithWebCenterContent.mp4" type="video/mp4" />
+</video>
 
 # License
 

ai-and-app-modernisation/content-management/webcenter-content-management/webcenter-ebs-adapter/files/images/managedattachment.gif

@@ -2,6 +2,8 @@
 
 We play with the OCI services and Oracle Software. Here is the list of our favorite components we have expertise in. Our skills include WebLogic Server, WebCenter Content, developer tools, frameworks, low code platforms, data management, and blockchain.
 
+Reviewed: 08.05.2024
+
 # Team Publications
 
 - [About Setting up a custom content management system secured by Oracle Blockchain Platform](https://docs.oracle.com/en/solutions/oracle-blockchain-platform-cms/index.html#GUID-D346CE74-FE02-4255-B1A6-82672474A259)[February 2023]

ai-and-app-modernisation/content-management/webcenter-content-management/webcenter-ebs-adapter/files/video/EBusinessIntegrationwithWebCenterContent.mp4

@@ -1 +1,17 @@
+# Blockchain
 
+Reviewed: 08.05.2024
+
+# Team Publications
+
+- [Implement a metaverse instance on OCI](https://docs.oracle.com/en/solutions/oci-metaverse-instance/index.html#GUID-B1943B07-C5BA-4C0E-9911-87CB1DDF1585)
+    - This reference architecture utilizes current metaverse technology and understanding to best deploy it to OCI.
+
+
+# License
+ 
+Copyright (c) 2024 Oracle and/or its affiliates.
+ 
+Licensed under the Universal Permissive License (UPL), Version 1.0.
+ 
+See [LICENSE](https://github.com/oracle-devrel/technology-engineering/blob/main/LICENSE) for more details.

app-dev/developer-tools-and-lowcode/README.md

@@ -2,36 +2,31 @@
 
 OCI DevOps, OCI Resource Manager, Visual Builder Studio, Open Source tools
 
+Reviewed: 08.05.2024
 
-# Table of Contents
- 
-1. [Team Publications](#team-publications)
-2. [Useful Links](#useful-links)
-3. [Reusable Assets Overview](#reusable-assets-overview)
- 
-## Team Publications
+# Team Publications
 
 - [Deploying Jenkins on Oracle Container Engine for Kubernetes](https://docs.oracle.com/en/solutions/oci-jenkins-oke/index.html#GUID-23A8EB94-DFFC-4D5C-897F-5F59423447D2)
 
 
-## Useful Links
+# Useful Links
 
 - [A DevOps Engineer's guide to OCI](https://docs.oracle.com/en-us/iaas/Content/GSG/Reference/getting-started-as-devops.htm)
 - [Selecting an appropriate CI/CD architecture](https://docs.oracle.com/en/solutions/select-cicd-architecture/index.html#GUID-A7048F76-5D10-4541-A105-CCF1CEFABEE1)
 
-### OCI DevOps
+## OCI DevOps
 
 - [OCI DevOps Build Pipeline collection](https://github.com/oracle-devrel/oci-devops-examples)
 - [OCI CLI documentation](https://docs.oracle.com/iaas/tools/oci-cli/latest/oci_cli_docs/)
 - [Deploying a Helm chart with Provenance liveLab](https://apexapps.oracle.com/pls/apex/r/dbpm/livelabs/view-workshop?wid=3664&clear=RR,180&session=109957900717640)
 - [Sample build-spec.yaml](./devops-graalvm-native-image/build-spec.yaml) and [associated Dockerfile](./devops-graalvm-native-image/Dockerfile) to use with OCI Devops. These are very configurable and show the installing of specific versions of software (GraalVM and Maven) into the build environment, creating of a native image executable using the installed software, determining version information dynamically and creating a docker image. The example used is the Quarkus getting-started example, but the build command should be the same for all quarkus examples, for Helidon and others you may need to change it slightly. This also assumes that the projects code base is in a sub directory of the gir repo (callsed getting-started in this case) you will need to modify the PROJECT_PATH_TO_BUILD to reflect a different location. To use this in a devops build pipeline place the Dockerfile and build-spec.yml in your projects code root (where the pom.xml file is). Adjust the PROJECT_PATH_TO_BUILD in the build spec and other variables as needed, add the files to your git repo. Change the output stage names for the image if needed. Configure the git repo as the primary GIT repo for the projects build stage and specify the build-spec.yaml file location.
 
-### Terraform
+## Terraform
 
 - [OCI Terraform provider](https://registry.terraform.io/providers/oracle/oci/latest/docs)
 - [Oracle quick start - automated deployments](https://github.com/oracle-quickstart)
 
-### Ansible
+## Ansible
 
 - [Getting starter - Ansible with OCI](https://docs.oracle.com/en-us/iaas/Content/API/SDKDocs/ansiblegetstarted.htm#Getting_Started_with_Oracle_Cloud_Infrastructure_and_Ansible)
 - [OCI Ansible Collection documentation](https://docs.oracle.com/en-us/iaas/tools/oci-ansible-collection/latest)

app-dev/developer-tools-and-lowcode/blockchain/README.md

@@ -2,18 +2,14 @@
 
 OCI Functions
 
+Reviewed: 08.05.2024
 
-# Table of Contents
- 
-1. [Team Publications](#team-publications)
-2. [Useful Links](#useful-links)
- 
-## Team Publications
+# Team Publications
 
 - [Building a minimal and secure container for serverless functions](https://medium.com/@comes94/building-a-minimal-and-secure-container-for-serverless-functions-with-micronaut-and-graalvm-4765da26e6a8)
 
 
-## Useful Links
+# Useful Links
 
 - [Functions sample repository](https://github.com/oracle-samples/oracle-functions-samples)
 - [Functions quickstart](https://docs.oracle.com/en-us/iaas/Content/Functions/Tasks/functionsquickstartguidestop.htm)

app-dev/developer-tools-and-lowcode/blockchain/metaverse/README.md

@@ -1,128 +1,19 @@
-<!--
-Copyright (c) 2024 Oracle and/or its affiliates.
-
-The Universal Permissive License (UPL), Version 1.0
-
-Subject to the condition set forth below, permission is hereby granted to any
-person obtaining a copy of this software, associated documentation and/or data
-(collectively the "Software"), free of charge and under any and all copyright
-rights in the Software, and any and all patent rights owned or freely
-licensable by each licensor hereunder covering either (i) the unmodified
-Software as contributed to or provided by such licensor, or (ii) the Larger
-Works (as defined below), to deal in both
-
-(a) the Software, and
-(b) any piece of software and/or hardware listed in the lrgrwrks.txt file if
-one is included with the Software (each a "Larger Work" to which the Software
-is contributed by such licensors),
-
-without restriction, including without limitation the rights to copy, create
-derivative works of, display, perform, and distribute the Software and make,
-use, sell, offer for sale, import, export, have made, and have sold the
-Software and the Larger Work(s), and to sublicense the foregoing rights on
-either these or other terms.
-
-This license is subject to the following condition:
-The above copyright notice and either this complete permission notice or at
-a minimum a reference to the UPL must be included in all copies or
-substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
--->
-
-## OCI queue overview
-[Document queue-overview](files/queue_overview.pdf)
-
-### Author
-<a href="https://github.com/mikarinneoracle">mikarinneoracle</a>
-
-## OCI Queue example in NodeJS with GitHub Actions
-
-### OCI Queue
-
-Create Queue and copy the Queue <i>OCID</i> and <i>Messages endpoint</i>:
-
-<p>
-<img src="files/endpoint.png" width="800" />
-
-<p>
-When using another <code>region</code> than <code>EU_FRANKFURT_1</code> please modify the 
-<a href="index.js#L48">
-<code>index.js</code></a> Line #48 accordingly:
-
-<pre>
-const region = common.Region.EU_FRANKFURT_1;
-</pre>
-
-### Policies
+# OCI Queue
 
-Setup policies for your user in the tenancy
+TEXT
 
-e.g. <code>Allow &lt;USER_GROUP&gt; to manage queues in compartment &lt;COMPARTMENT&gt;</code>
+Reviewed: 08.05.2024
 
-More on OCI Queue IAM policies: https://docs.oracle.com/en-us/iaas/Content/queue/policy-reference.htm
+# Team Publication
 
-### Secrets
+- [Document queue-overview](example-usage/files/queue_overview.pdf)
 
-Setup secrets to run this example with GitHub Actions:
-
-<ul>
-    <li><b>OCI_TENANCY</b>: OCI Tenancy OCID</li>
-    <li><b>OCI_USER</b>: OCI User OCID</li>
-    <li><b>OCI_FINGERPRINT</b>: OCI User Fingerprint</li>
-    <li><b>OCI_KEY</b>: OCI User Private Key</li>
-    <li><b>OCI_PASSPHRASE</b>: OCI User Private Key passphrase (optional)</li>
-    <li><b>Q_ID</b>: OCI Queue OCID</li>
-    <li><b>Q_ENDPOINT</b>: OCI Queue Messages endpoint</li>
-</ul>
-
-### Run Action
-
-Monitor the GitHub action to run:
-
-<p>
-<img src="files/action.png" width="800" />
-
-<p>
-This example will poll for messages in the queue and finally writes a new message to it.
-
-### View messages in the Queue
-
-<img src="files/messages.png" width="800" />
-
-### Running locally
-
-Clone this repo, setup npm and <code>oci cli</code> and modify <a href="index.js#L46">index.js</a> line 46 by uncommenting it and removing/commenting lines 49-56 and replace lines 59-60
-with Queue details :
-
-<pre>
-// Use this locally instead of env vars and region:
-const provider = new common.ConfigFileAuthenticationDetailsProvider();
-
-// Q settings
-const queueId = 'ocid1.queue.oc1.eu-frankfurt-1.ama....a5z4ic2tslq';
-const endpoint = 'https://cell-1.queue......oci.oraclecloud.com';
-</pre>
-
-Then run:
-
-<pre>
-npm install
-node index.js
-</pre>
-
-### Sending messages to Queue
+# License
+ 
+Copyright (c) 2024 Oracle and/or its affiliates.
+ 
+Licensed under the Universal Permissive License (UPL), Version 1.0.
+ 
+See [LICENSE](https://github.com/oracle-devrel/technology-engineering/blob/main/LICENSE) for more details.
 
-You can manually send messages to the queue using the OCI Queue Console  
-<code>Actions/Send Message</code> and then see them being received by re-running the build.
 
-<p>
-You can also play with the queue's <code>Dead Letter Queue</code> settings to see how many
-times the same message is being received (default is 5). To do this comment the 
-<a href="index.js#L99">line 99 of the index.js</a> and re-run the build by committing the change.