Skip to content

Update the external client FAQ to discuss 'unknown host' handling, plus... #1842

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Aug 4, 2020
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
minor doc tweaks
  • Loading branch information
Tom Barnes committed Jul 31, 2020
commit 0f5525e4753fa1db94fa8a56e0c5f34c9a44da8f
6 changes: 3 additions & 3 deletions docs-source/content/faq/external-clients.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,12 +27,12 @@ description: "This FAQ describes approaches for giving external WebLogic clients

#### Overview

There are two supported approaches for giving WebLogic clients and servers that are external to Kubernetes, access to Kubernetes hosted WebLogic cluster EJBs and JMS:
When WebLogic clients and servers are external to Kubernetes, and you want to give them access to Kubernetes hosted WebLogic cluster EJBs and JMS, there are two supported approaches:

* [Load balancer tunneling](#load-balancer-tunneling) (preferred)
* [Kubernetes `NodePorts`](#kubernetes-nodeports)

Conversely, if giving a Kubernetes hosted WebLogic Server access to an external WebLogic Server EJBs, JMS, or JTA, then consider the following:
Conversely, if giving a Kubernetes hosted WebLogic Server access to external WebLogic Server EJBs, JMS, or JTA, then consider the following:

* You may need to [enable unknown host access](#enabling-unknown-host-access) on the external WebLogic Servers.
* Plus, if the target server can be accessed only through a load balancer using HTTP:
Expand Down Expand Up @@ -178,7 +178,7 @@ In this example:

- Channel configuration for a configured cluster requires configuring the same network access point on each server. The operator currently doesn't test or support network channels that have a different configuration on each server in the cluster.

- Additional steps are required for external clients beyond configuring the custom channel - see [Approaches](#approaches).
- Additional steps are required for external clients beyond configuring the custom channel - see [Overview](#overview).

#### Setting up a `NodePort`

Expand Down