Merge pull request #7 from datastax/using-s4j-guide

Revising documents and removed quickstart

Author: mendonk

antora.yml

@@ -5,9 +5,8 @@ start_page: index.adoc
 
 asciidoc:
   attributes:
-    starlight_jms: 'Starlight for JMS'
-    product_version: '3.x'
     jms_repo: 'https://github.com/datastax/pulsar-jms/'
+    allow-uri-read: '' # this has no effect in antora, but does help development in Intellij
 
 nav:
   - modules/ROOT/nav.adoc

modules/ROOT/pages/index.adoc

@@ -1,29 +1,29 @@
-= About {starlight_jms}
+= About Starlight for JMS
 :navtitle: Starlight for JMS
 :page-tag: starlight-jms,planner,dev,admin,pulsar,jms
 :page-aliases: docs@starlight-jms::index.adoc,
 
-{starlight_jms} is the first highly compliant JMS implementation designed to run on a modern streaming platform. It allows enterprises to take advantage of the scalability and resiliency of a modern streaming platform to run their existing JMS applications. Because Apache Pulsar™ is open-source and cloud-native, {starlight_jms} enables enterprises to move their JMS applications to run on-premises and in any cloud environment.
+Starlight for JMS is the first highly compliant JMS implementation designed to run on a modern streaming platform. It allows enterprises to take advantage of the scalability and resiliency of a modern streaming platform to run their existing JMS applications. Because Apache Pulsar™ is open-source and cloud-native, Starlight for JMS enables enterprises to move their JMS applications to run on-premises and in any cloud environment.
 
 == Key Features
 
-{starlight_jms} key features include:
+Starlight for JMS key features include:
 
 * *Blazing fast JMS performance*: Achieve 1 million JMS messages per second with 99 percentile publish to acknowledge latency of less than 10 ms. 
 * *Drop-in replacement for existing JMS applications*: Supports JMS/Jakarta 2.0 and is backwards compatible with JMS 1.1. 100% pass rate on JMS compliance test for supported features.
 * *Horizontally scalable JMS*: Apache Pulsar is a horizontally scaled distributed streaming platform. You can scale up or down without operational hassles. Pulsar separates compute from storage, which means you can scale those dimensions independently, as required. Pulsar supports offloading old data to object storage for practically infinite storage capacity.
 * *Reduced total cost of ownership*: Because Apache Pulsar is natively multi-tenant and high performance, you can consolidate JMS applications spread across multiple legacy JMS brokers onto a single Apache Pulsar installation. And since Pulsar is easily horizontally scaled, you don’t need to overprovision. 
 * *Future proof*: Apache Pulsar can support traditional messaging workloads, but it can also support modern streaming use cases such as log collection, microservices integration, event streaming, event sourcing. New workloads can run alongside Legacy JMS applications. 
-* *Open source to avoid lock in*: {starlight_jms} and Apache Pulsar are 100% open source. You can run on-premise, in any cloud provider, or in Kubernetes.
+* *Open source to avoid lock in*: Starlight for JMS and Apache Pulsar are 100% open source. You can run on-premise, in any cloud provider, or in Kubernetes.
 * *Adds message replay to JMS*: Apache Pulsar natively supports message retention and replay. This allows applications using Fast JMS for Apache Pulsar to travel back in time and replay previously consumed messages to recover from misconfiguration issues, recover from bugs in application code, and test new applications against real data.
 
 == What's next?
 
 * *xref:jms-migration:pulsar-jms-quickstart-sa.adoc[]*: Create a simple command line Java JMS client that connects to a local Pulsar installation.
-* *xref:jms-migration:pulsar-jms-quickstart-astra.adoc[]*: Create a simple command line Java JMS client that connects to an Astra Streaming instance.
-* *xref:jms-migration:pulsar-jms-install.adoc[]*: Install {starlight_jms} in your own JMS project.
+* *xref:streaming-learning:use-cases-architectures:starlight/jms/index.adoc[]*: Create a simple command line Java JMS client that connects to an Astra Streaming instance.
+* *xref:jms-migration:pulsar-jms-install.adoc[]*: Install Starlight for JMS in your own JMS project.
 * *xref:reference:pulsar-jms-mappings.adoc[]*: Understand Pulsar concepts in the context of JMS.
-* *xref:examples:pulsar-jms-implementation.adoc[]*: Understand key implementation details for {starlight_jms}.
-* *xref:pulsar-jms-faq.adoc[]*: Frequently asked questions about {starlight_jms}.
-* *xref:reference:pulsar-jms-reference.adoc[]*: {starlight_jms} configuration reference.
-* *{jms_repo}[{starlight_jms} Github repo,window=_blank]*
+* *xref:examples:pulsar-jms-implementation.adoc[]*: Understand key implementation details for Starlight for JMS.
+* *xref:pulsar-jms-faq.adoc[]*: Frequently asked questions about Starlight for JMS.
+* *xref:reference:pulsar-jms-reference.adoc[]*: Starlight for JMS configuration reference.
+* *{jms_repo}[Starlight for JMS Github repo,window=_blank]*

modules/ROOT/pages/pulsar-jms-faq.adoc

@@ -1,18 +1,18 @@
-= {starlight_jms} FAQs 
+= Starlight for JMS FAQs
 
 :page-tag: starlight-jms,planner,dev,admin,pulsar,jms
 
-Answers to the (arguably) most common {starlight_jms} questions.
+Answers to the (arguably) most common Starlight for JMS questions.
 
-== What is the pricing for {starlight_jms}?
+== What is the pricing for Starlight for JMS?
 
-{starlight_jms} is free open-source software. Enterprise support is available through https://www.datastax.com/products/luna-streaming[Luna Streaming,window=_blank], the DataStax commercial support offering for Apache Pulsar™.
+Starlight for JMS is free open-source software. Enterprise support is available through https://www.datastax.com/products/luna-streaming[Luna Streaming,window=_blank], the DataStax commercial support offering for Apache Pulsar™.
 
-== How is {starlight_jms} licensed?
+== How is Starlight for JMS licensed?
 
-{starlight_jms} is licensed under https://www.apache.org/licenses/LICENSE-2.0.txt[Apache version 2.0,window=_blank].
+Starlight for JMS is licensed under https://www.apache.org/licenses/LICENSE-2.0.txt[Apache version 2.0,window=_blank].
 
-== How can I use {starlight_jms} in a JakartaEE® or JavaEE® application?
+== How can I use Starlight for JMS in a JakartaEE® or JavaEE® application?
 
 You can use the `resourceAdapter` {jms_repo}blob/master/resource-adapter[here,window=_blank].
 
@@ -51,9 +51,9 @@ We've provided the following integration examples:
 * {jms_repo}blob/master/examples/payara-micro[Payara Micro®,window=_blank]
 * {jms_repo}blob/master/resource-adapter-tests[Apache TomEE®,window=_blank]
 
-== How can I build {starlight_jms} from source?
+== How can I build Starlight for JMS from source?
 
-If you'd like to fork or contribute to {starlight_jms}:
+If you'd like to fork or contribute to Starlight for JMS:
 
 . Clone the git repo:
 +
@@ -77,9 +77,9 @@ This https://javaee.github.io/jms-spec/[website,window=_blank] is useful as well
 == What's next?
 
 * *xref:jms-migration:pulsar-jms-quickstart-sa.adoc[]*: Create a simple command line Java JMS client that connects to a local Pulsar installation.
-* *xref:jms-migration:pulsar-jms-quickstart-astra.adoc[]*: Create a simple command line Java JMS client that connects to an Astra Streaming instance.
-* *xref:jms-migration:pulsar-jms-install.adoc[]*: Install {starlight_jms} in your own JMS project.
+* *xref:streaming-learning:use-cases-architectures:starlight/jms/index.adoc[]*: Create a simple command line Java JMS client that connects to an Astra Streaming instance.
+* *xref:jms-migration:pulsar-jms-install.adoc[]*: Install Starlight for JMS in your own JMS project.
 * *xref:reference:pulsar-jms-mappings.adoc[]*: Understand Pulsar concepts in the context of JMS.
-* *xref:examples:pulsar-jms-implementation.adoc[]*: Understand key implementation details for {starlight_jms}.
-* *xref:reference:pulsar-jms-reference.adoc[]*: {starlight_jms} configuration reference.
-* *{jms_repo}[{starlight_jms} Github repo,window=_blank]*
+* *xref:examples:pulsar-jms-implementation.adoc[]*: Understand key implementation details for Starlight for JMS.
+* *xref:reference:pulsar-jms-reference.adoc[]*: Starlight for JMS configuration reference.
+* *{jms_repo}[Starlight for JMS Github repo,window=_blank]*

modules/examples/pages/pulsar-jms-batch-ack.adoc

@@ -1,7 +1,7 @@
 = Batch index acknowledgement
 :page-aliases: docs@starlight-jms::pulsar-jms-batch-ack.adoc
 
-{starlight_jms} version {product_version} improves acknowledgement of batched messages by supporting the tracking of 'ack' status by *batch index*. +
+Starlight for JMS improves acknowledgement of batched messages by supporting the tracking of 'ack' status by *batch index*. +
 
 By default, filtering works on the *entry* level in Pulsar. An *entry* is a *single message* or a *single batch of messages*. The client will not filter out a few messages in a batch; it either passes completely or fails completely. +
 
@@ -37,7 +37,7 @@ acknowledgmentAtBatchIndexLevelEnabled=true
 == What's next?
 
 For more on *server-side filtering*, see xref:pulsar-jms-server-side-filters.adoc[Server side filters]. +
-For more on acknowledgements in {starlight_jms}, see xref:reference:pulsar-jms-mappings.adoc#consumer-mappings[Consumer Mappings].
+For more on acknowledgements in Starlight for JMS, see xref:reference:pulsar-jms-mappings.adoc#consumer-mappings[Consumer Mappings].