Change shortening of TEQ to TxEventQ (#481)

* wip : fix txeventq name

* change package name to txeventq

* option ADB_FREE

* fix setup kafka 2 txeventq script name

* add script for remove compartment from lab

Author: pasimoes

workshops/oracleteq-kafka/cloud-setup/cmd/teq-add-topic

@@ -1,21 +1,21 @@
 
-# Simplify Event-driven Apps with TEQ in Oracle Database (with Kafka interoperability) Workshop
+# Simplify Event-driven Apps with TxEventQ in Oracle Database (with Kafka interoperability) Workshop
 
 ## Introduction
 
 ### About this Workshop
 
 This repository contains sample code from the workshop to help you understand Event Mesh using two message brokers and the technical capabilities inside the converged [Oracle Autonomous Database][ATP] to support a scalable event-driven microservices architecture.
 
-You will create four event-driven microservice and two messaging brokers to allow communication between them. In the first lab, you will deploy an Apache Kafka broker to leverage the event-driven communication between two microservices written in Spring Boot. In the second lab, you will create an Oracle Transactional Event Queues (TEQ) and experience the Kafka APIs working in the Kafka compatibility mode. Likewise, this module has the Spring Boot producer and consumer microservices but with Kafka Java client for TEQ, using the okafka library. And finally, in the third lab, you will experiment with the concept of Event Mesh, building a bridge between Kafka and TEQ brokers, and see messages being produced on the Kafka side and consumed on the TEQ side.
+You will create four event-driven microservice and two messaging brokers to allow communication between them. In the first lab, you will deploy an Apache Kafka broker to leverage the event-driven communication between two microservices written in Spring Boot. In the second lab, you will create an Oracle Transactional Event Queues (TxEventQ) and experience the Kafka APIs working in the Kafka compatibility mode. Likewise, this module has the Spring Boot producer and consumer microservices but with Kafka Java client for TxEventQ, using the okafka library. And finally, in the third lab, you will experiment with the concept of Event Mesh, building a bridge between Kafka and TxEventQ brokers, and see messages being produced on the Kafka side and consumed on the TxEventQ side.
 
 Estimated Workshop Time: 50 minutes
 
-> This workshop is part of the [Oracle LiveLabs][LiveLabs] and you can access it through the following address [TEQ in Oracle Database][TEQinOracleDatabase]
+> This workshop is part of the [Oracle LiveLabs][LiveLabs] and you can access it through the following address [TxEventQ in Oracle Database][TxEventQinOracleDatabase]
 
 ### About Product/Technology
 
-* [Oracle Transactional Event Queues][TEQ] is a powerful messaging backbone offered by converged Oracle Database that allows you to build an enterprise-class data-centric microservices architecture.
+* [Oracle Transactional Event Queues][TxEventQ] is a powerful messaging backbone offered by converged Oracle Database that allows you to build an enterprise-class data-centric microservices architecture.
 
 * [Kafka][kafka] is an open-source distributed event streaming platform used for high-performance data pipelines, streaming analytics, data integration, and mission-critical applications.
 
@@ -27,9 +27,9 @@ Estimated Workshop Time: 50 minutes
 
 * The first Lab reviews the Kafka and Spring Boot Microservice built to produce and consume messages.
 
-* The second Lab will use Oracle Transactional Event Queues (TEQ) and okafka library and demonstrate the Kafka compatibility of TEQ. Also, this module has the same Spring Boot producer and consumer microservices but uses okafka in place of Kafka libraries and TEQ in the database in place of Kafka broker.
+* The second Lab will use Oracle Transactional Event Queues (TxEventQ) and okafka library and demonstrate the Kafka compatibility of TxEventQ. Also, this module has the same Spring Boot producer and consumer microservices but uses okafka in place of Kafka libraries and TxEventQ in the database in place of Kafka broker.
 
-* The third Lab will interconnect the Kafka broker and the Oracle Transactional Event Queues (TEQ), applying Kafka connector and Oracle Database Messaging libraries. This laboratory demonstrates the interoperability between the two brokers, with events flowing from the Kafka side to TEQ, finally consumed at the TEQ side.
+* The third Lab will interconnect the Kafka broker and the Oracle Transactional Event Queues (TxEventQ), applying Kafka connector and Oracle Database Messaging libraries. This laboratory demonstrates the interoperability between the two brokers, with events flowing from the Kafka side to TxEventQ, finally consumed at the TxEventQ side.
 
 ## Prerequisites
 
@@ -44,18 +44,18 @@ As shown in the followed diagram, we have:
 
 * A Kafka Broker and a set of services consuming and producing for it.
 
-* An Oracle TEQ Broker with another set of services around it.
+* An Oracle TxEventQ Broker with another set of services around it.
 
-* And connector between Kafka and Oracle TEQ enabling a communication path between them.
+* And connector between Kafka and Oracle TxEventQ enabling a communication path between them.
 
-![Kafka and Oracle TEQ Event Mesh](images/kafka-oracle-teq-event-mesh.png " ")
+![Kafka and Oracle TxEventQ Event Mesh](images/kafka-oracle-txeventq-event-mesh.png " ")
 
 You may now **proceed to the next lab**
 
 ## Want to Learn More?
 
 * [Oracle Autonomous Database][ATP]
-* [Oracle Transactional Event Queues][TEQ]
+* [Oracle Transactional Event Queues][TxEventQ]
 * [Microservices Architecture with the Oracle Database][MicroservicesArch]
 * [https://developer.oracle.com/][DRC]
 
@@ -72,11 +72,11 @@ Copyright (c) 2022 Oracle and/or its affiliates.
 Licensed under the Universal Permissive License v 1.0 as shown at <https://oss.oracle.com/licenses/upl>.
 
 [ATP]: https://docs.oracle.com/en/cloud/paas/autonomous-database/index.html
-[TEQ]: https://docs.oracle.com/en/database/oracle/oracle-database/21/adque/index.html
+[TxEventQ]: https://docs.oracle.com/en/database/oracle/oracle-database/21/adque/index.html
 [kafka]: https://kafka.apache.org
 [okafka]: https://docs.oracle.com/en/database/oracle/oracle-database/21/adque/Kafka_cient_interface_TEQ.html#GUID-94589C97-F323-4607-8C3A-10A0EDF9DA0D
 [LiveLabs]: https://bit.ly/golivelabs
-[TEQinOracleDatabase]: https://bit.ly/TEQinOracleDatabase
+[TxEventQinOracleDatabase]: https://bit.ly/TxEventQinOracleDatabase
 [FreeTier]: https://www.oracle.com/cloud/free/faq.html
 [DRC]: https://developer.oracle.com
 [MicroservicesArch]: https://www.oracle.com/technetwork/database/availability/trn5515-microserviceswithoracle-5187372.pdf

workshops/oracleteq-kafka/springboot-oracleteq/teq-ms-deploy-consumer

@@ -2,4 +2,4 @@
 # Copyright (c) 2021 Oracle and/or its affiliates.
 # Licensed under the Universal Permissive License v 1.0 as shown at https://oss.oracle.com/licenses/upl.
 
-curl -Ss http://localhost:8083/connectors/JmsConnectSync_teqlab/status | jq
+oci iam compartment delete --compartment-id "$(state_get COMPARTMENT_OCID)"

workshops/oracleteq-kafka/springboot-oracleteq/teq-ms-deploy-producer

@@ -2,7 +2,7 @@
 # Copyright (c) 2021 Oracle and/or its affiliates.
 # Licensed under the Universal Permissive License v 1.0 as shown at https://oss.oracle.com/licenses/upl.
 
-KAFKA_TOPIC=${1:-"LABTEQTOPIC"}
+KAFKA_TOPIC=${1:-"LABTXEVENTQTOPIC"}
 
 VAR=$(docker exec broker kafka-topics --bootstrap-server broker:9092 --create --topic "${KAFKA_TOPIC}")