Skip to content

Commit f3ed3fd

Browse files
author
sliu
committed
DATAGO-5250: fixed redirects and missing alts
1 parent 72e9101 commit f3ed3fd

6 files changed

+27
-18
lines changed

CONTRIBUTING.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -108,4 +108,4 @@ That's it! Thank you for your contribution!
108108

109109
## <a name="questions"></a> Do you have questions about the source code?
110110

111-
* Ask any question about the code or how to use Solace messaging in the [Solace community](http://dev.solace.com/community/).
111+
* Ask any question about the code or how to use Solace messaging in the [Solace community](https://solace.com/support/).

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
The "Getting Started" tutorials will get you up to speed and sending messages with Solace technology as quickly as possible. There are three ways you can get started:
66

77
- Follow [these instructions](https://cloud.solace.com/learn/group_getting_started/ggs_signup.html) to quickly spin up a cloud-based Solace messaging service for your applications.
8-
- Follow [these instructions](https://docs.solace.com/Solace-VMR-Set-Up/Setting-Up-VMRs.htm) to start the Solace VMR in leading Clouds, Container Platforms or Hypervisors. The tutorials outline where to download and how to install the Solace VMR.
8+
- Follow [these instructions](https://docs.solace.com/Solace-SW-Broker-Set-Up/Setting-Up-SW-Brokers.htm) to start the Solace VMR in leading Clouds, Container Platforms or Hypervisors. The tutorials outline where to download and how to install the Solace VMR.
99
- If your company has Solace message routers deployed, contact your middleware team to obtain the host name or IP address of a Solace message router to test against, a username and password to access it, and a VPN in which you can produce and consume messages.
1010

1111
## Contents
@@ -47,7 +47,7 @@ Note: the code in the `master` branch of this repository depends on Solace JavaS
4747

4848
These samples depend on version 10 or later of the Solace JavaScript API library.
4949

50-
The Solace JavaScript API library can be [downloaded here](http://dev.solace.com/downloads/). The instructions in this tutorial assume you have downloaded the Web Messaging API for JavaScript library and unpacked it to a known location. The samples assume a `lib` directory containing the API libraries will be installed in the current `solace-samples-javascript` directory at the root of the cloned repo:
50+
The Solace JavaScript API library can be [downloaded here](https://solace.com/downloads/). The instructions in this tutorial assume you have downloaded the Web Messaging API for JavaScript library and unpacked it to a known location. The samples assume a `lib` directory containing the API libraries will be installed in the current `solace-samples-javascript` directory at the root of the cloned repo:
5151

5252
```bash
5353
cp -R <path_to_unzipped_API_distribution_package>/lib/ .
@@ -83,6 +83,6 @@ This project is licensed under the Apache License, Version 2.0. - See the [LICEN
8383
For more information try these resources:
8484

8585
- The Solace Developer Portal website at: http://dev.solace.com
86-
- Get a better understanding of [Solace technology](http://dev.solace.com/tech/).
86+
- Get a better understanding of [Solace technology](https://solace.com/products/tech/).
8787
- Check out the [Solace blog](http://dev.solace.com/blog/) for other interesting discussions around Solace technology
88-
- Ask the [Solace community.](http://dev.solace.com/community/)
88+
- Ask the [Solace community.](https://solace.com/support/)

_config.yml

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -8,21 +8,21 @@ repository: https://github.com/SolaceSamples/solace-samples-javascript
88

99
# Links
1010
advanced-samples: //github.com/SolaceSamples/solace-samples-javascript/tree/master/src/advanced-samples
11-
links-downloads: //dev.solace.com/downloads/
12-
links-community: //dev.solace.com/community/
11+
links-downloads: //solace.com/downloads/
12+
links-community: //solace.com/support/
1313
links-get-started-javascript: //dev.solace.com/get-started/javascript-tutorials/
14-
links-tech-other: //dev.solace.com/tech/#other
15-
links-solaceCloud-setup: //cloud.solace.com/create-messaging-service/
16-
docs-core-concepts: //docs.solace.com/Features/Core-Concepts.htm
14+
links-tech-other: //solace.com/products/tech/
15+
links-solaceCloud-setup: //solace.com/cloud/
16+
docs-core-concepts: //docs.solace.com/PubSub-Basics/Core-Concepts.htm
1717
docs-session-events: //docs.solace.com/Solace-Messaging-APIs/Creating-Client-Sessions-1.htm#Handle-Sess-Events
1818
docs-api-reference: //docs.solace.com/API-Developer-Online-Ref-Documentation/js/index.html
19-
docs-semp: //docs.solace.com/SEMP/Using-SEMP-to-Manage-and-Monitor-Routers.htm
20-
docs-topic-mapping: //docs.solace.com/Features/Core-Concepts.htm#topic-queue-mapping
21-
docs-dte: //docs.solace.com/Features/Endpoints.htm
19+
docs-semp: //docs.solace.com/SEMP/Using-Legacy-SEMP.htm
20+
docs-topic-mapping: //docs.solace.com/PubSub-Basics/Core-Concepts.htm
21+
docs-dte: //docs.solace.com/PubSub-Basics/Endpoints.htm
2222
docs-active-flow-indication: //docs.solace.com/Solace-PubSub-Messaging-APIs/Developer-Guide/Creating-Flows.htm#Active-Flow-Indication
2323
docs-psplus-manager: //docs.solace.com/Solace-PubSub-Manager/PubSub-Manager-Overview.htm
2424
docs-semp-api: //docs.solace.com/SEMP/Using-SEMP.htm
25-
docs-endpoints: //docs.solace.com/Messaging-Basics/Endpoints.htm#Endpoints
25+
docs-endpoints: //docs.solace.com/PubSub-Basics/Endpoints.htm
2626
docs-api-errorresponse-subcode-ex: //docs.solace.com/API-Developer-Online-Ref-Documentation/js/solace.ErrorSubcode.html
27-
docs-replay-use-cases: //docs.solace.com/Features/Message-Replay.htm#Applicat
27+
docs-replay-use-cases: //docs.solace.com/Configuring-and-Managing/Message-Replay.htm
2828
docs-replay-cli-config: //docs.solace.com/Configuring-and-Managing/Msg-Replay-Config.htm

_docs/feature_MessageReplay.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -175,6 +175,6 @@ This will replay all logged messages including the live one published in step 2.
175175
{% for item in page.links %}
176176
<li>Related Source Code: <a href="{{ site.repository }}{{ item.link }}" target="_blank">{{ item.label }}</a></li>
177177
{% endfor %}
178-
<li><a href="https://docs.solace.com/Features/Message-Replay.htm" target="_blank">Solace Feature Documentation</a></li>
178+
<li><a href="https://docs.solace.com/Configuring-and-Managing/Message-Replay.htm" target="_blank">Solace Feature Documentation</a></li>
179179
</ul>
180180

_docs/topic-to-queue-mapping.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ In addition to persistent messages published directly to a durable queue, it is
1313

1414
The following diagram illustrates this feature.
1515

16-
<img src="{{ site.baseurl }}/assets/images/topic-to-queue-mapping-details.png" width="500" height="206" />
16+
<img src="{{ site.baseurl }}/assets/images/topic-to-queue-mapping-details.png" alt="Javascript Queue Mapping" width="500" height="206" />
1717

1818
If you have a durable queue named “Q”, it will receive messages published directly to the queue destination named “Q”. However, it is also possible to add subscriptions to this queue in the form of topics. This example adds topics “A” and “B”. Once these subscriptions are added, the queue will start receiving messages published to topic destinations “A” and “B”. When you combine this with wildcard support provided by Solace topics, this opens up a number of interesting use cases.
1919

@@ -23,7 +23,7 @@ The Solace JavaScript API does not provide a way for applications to directly ta
2323

2424
However Solace JavaScript web applications wishing to take advantage of this Solace feature can use a management interface to administratively configure the topic to queue mapping, by adding topic subscriptions to the queue. This can either be done through CLI or the SolAdmin management application, or by the SEMP programmatic management API. The SEMP API enables applications to fully configure Solace message routers. Applications can use this API by logging into the Solace message router using a Message-VPN admin account. This concept is introduced in [Technology – Messaging Platform Features]({{ site.links-tech-other }}){:target="_top"} and further details are available in the [Solace Message Router Product Documentation]({{ site.docs-semp }}){:target="_top"}.
2525

26-
Once having Topic to Queue Mapping configured, the `QueueConsumer` sample from the [Persistence with Queues]({{ site.baseurl }}/persistence-with-queues) tutorial can be used to consume messages.
26+
Once having Topic to Queue Mapping configured, the `QueueConsumer` sample from the [Persistence with Queues]({{ site.baseurl }}/persistence-with-queues/) tutorial can be used to consume messages.
2727

2828
## Summary
2929

solace-samples-javascript.iml

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
<?xml version="1.0" encoding="UTF-8"?>
2+
<module type="WEB_MODULE" version="4">
3+
<component name="NewModuleRootManager" inherit-compiler-output="true">
4+
<exclude-output />
5+
<content url="file://$MODULE_DIR$" />
6+
<orderEntry type="inheritedJdk" />
7+
<orderEntry type="sourceFolder" forTests="false" />
8+
</component>
9+
</module>

0 commit comments

Comments
 (0)