Skip to content
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.

Sign up for GitHub

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

Jump to bottom

BXMSDOC-4423 RN and other updates pre 7.4 GA #179

Merged
merged 3 commits into from
Jul 15, 2019
Merged

BXMSDOC-4423 RN and other updates pre 7.4 GA #179

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
876dd71
BXMSDOC-4423 added deprecated languages section to RN
emmurphy1 Jul 15, 2019
943b158
updated SSO doc
emmurphy1 Jul 15, 2019
f7abed8
BXMSDOC-4423 updated language section of RN
emmurphy1 Jul 15, 2019
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
5 changes: 1 addition & 4 deletions doc-content/enterprise-only/installation/clustering-bc-testing-proc.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ After configuring the cluster for {PRODUCT}, create an asset to verify that the
. Enter the `admin` user credentials that you created during installation. The {CENTRAL} home page appears.
. Select *Menu* -> *Design* -> *Projects*.
. Click *Try Samples* -> *Mortgages* -> *OK*. The *Assets* window appears.
. Click *Create New Asset* -> *Data Object*.
. Click *Add Asset* -> *Data Object*.
. Enter `MyDataObject` in the *Data Object* field and click *OK*.
. Click *Spaces* -> *MySpace* -> *Mortgages* and confirm that `MyDataObject` is in the list of assets.
. Enter the following URL in a web browser, where `<node_IP_address>` is the address of a different node of the cluster:
Expand All @@ -19,6 +19,3 @@ After configuring the cluster for {PRODUCT}, create an asset to verify that the
. Select the *Mortgages* project.
. Verify that `MyDataObject` is in the asset list.
. Delete the *Mortgages* project.



21 changes: 9 additions & 12 deletions doc-content/enterprise-only/installation/ssh-configuring-proc.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
[id='ssh-configuring-proc_{context}']

= Configuring SSH to use RSA
SSH is used to clone Git repositories. By default, the DSA encryption algorithm is provided by Business Central. However, some SSH clients, for example SSH clients in the Fedora 23 environment, use the RSA algorithm instead of the DSA algorithm. Business Central contains a system property that you can use to switch from DSA to RSA if required.
SSH is used to clone Git repositories. By default, the DSA encryption algorithm is provided by Business Central. However, some SSH clients, for example SSH clients in the Fedora 23 environment, use the RSA algorithm instead of the DSA algorithm. Business Central contains a system property that you can use to switch from DSA to RSA if required.

[NOTE]
====
SSH clients on supported configurations, for example Red Hat Enterprise Linux 7, are not affected by this issue. For a list of supported configurations, see
SSH clients on supported configurations, for example Red Hat Enterprise Linux 7, are not affected by this issue. For a list of supported configurations, see
ifdef::PAM[]
https://access.redhat.com/articles/3405381[Red Hat Process Automation Manager 7 Supported Configurations].
endif::[]
Expand All @@ -25,12 +25,12 @@ Complete one of the following tasks to enable this system property:
Host <SERVER_IP>
HostKeyAlgorithms +ssh-dss
----

* Include the `-Dorg.uberfire.nio.git.ssh.algorithm=RSA` parameter when you start {CENTRAL}, for example:
+
[source]
----
$ ./standalone.sh -c standalone-full.xml
$ ./standalone.sh -c standalone-full.xml
-Dorg.uberfire.nio.git.ssh.algorithm=RSA
----

Expand Down Expand Up @@ -58,35 +58,32 @@ If you deployed {CENTRAL} without {KIE_SERVER}, you can start {CENTRAL} with the
+
ifdef::PAM[]
`\http://www.example.com:8080/{URL_COMPONENT_CENTRAL}`
endif::[]
endif::[]
ifdef::DM[]
`\http://www.example.com:8080/{URL_COMPONENT_CENTRAL}`
endif::[]
* If {PRODUCT} has been configured to run in a cluster, replace `localhost` with the IP address of a particular node, for example:
+
ifdef::PAM[]
`\http://<node_IP_address>:8080/{URL_COMPONENT_CENTRAL}`
endif::[]
endif::[]
ifdef::DM[]
`\http://<node_IP_address>:8080/{URL_COMPONENT_CENTRAL}`
endif::[]
endif::[]
. Enter the `admin` user credentials that you created during installation. The {CENTRAL} home page appears.
. Select *Menu* -> *Deploy* -> *Execution Servers*.
. Confirm that *default-kieserver* is listed under *Server Configurations*.
. Select *Menu* -> *Design* -> *Projects*.
. Click *Try Samples* -> *Mortgages* -> *OK*. The *Assets* window appears.
. Click *Create New Asset* -> *Data Object*.
. Click *Add Asset* -> *Data Object*.
. Enter `MyDataObject` in the *Data Object* field and click *OK*.
. Click *Spaces* -> *MySpace* -> *Mortgages* and confirm that `MyDataObject` is in the list of assets.
//. If you are verifying a clustered installation:
//* Enter the following URL, where `<node_IP_address>` is the address of a different node of the cluster.
//* Enter the following URL, where `<node_IP_address>` is the address of a different node of the cluster.
//* Enter same credentials that you used to log in to {CENTRAL} on the first node, where you created the `MyDataObject` asset.
//+
//`http://<node_IP_address>:8080/{URL_COMPONENT_CENTRAL}`
//* Select *Menu*-> *Design* -> *Projects*.
//* Select the *Mortgages* project.
//* Verify that `MyDataObjec`t is in the asset list.
. Delete the *Mortgages* project.



7 changes: 6 additions & 1 deletion doc-content/enterprise-only/integration/sso-central-client-create-proc.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,12 @@ The *Add Client* page opens.
* *Client ID*: kie
* *Client protocol*: openid-connect
* *Root URL*: `http://_localhost_:8080/{URL_COMPONENT_CENTRAL}`

+
[NOTE]
====
If you are configuring RH-SSO with {OPENSHIFT}, enter the URL that is exposed by the {KIE_SERVER} routes. Your OpenShift administrator can provide this URL if necessary.
====
+
. Click *Save* to save your changes.
+
After you create a new client, its *Access Type* is set to `public` by default. Change it to `confidential`.
Expand Down
5 changes: 5 additions & 0 deletions doc-content/enterprise-only/integration/sso-kie-server-client-proc.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,5 +20,10 @@ The *Add Client* page opens.
* *Root URL*: `http://_localhost_:8080/kie-server`
* *Client protocol*: `openid-connect`
+
[NOTE]
====
If you are configuring RH-SSO with {OPENSHIFT}, enter the URL that is exposed by the {KIE_SERVER} routes. Your OpenShift administrator can provide this URL if necessary.
====
+
. The new client *Access Type* is set to `public` by default. Change it to `confidential` and click *Save* again.
. Navigate to the *Credentials* tab and copy the secret key. The secret key is required to configure the `kie-execution-server` client.
3 changes: 3 additions & 0 deletions doc-content/enterprise-only/release-notes/rn-support-ref.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,9 @@ The following component versions have been updated in this release:
== Deprecated components
The components listed in this section have been deprecated in this release or in a recent release.

=== Supported languages
Starting with the 7.5 release, the {PRODUCT} user interface will be localized in English and Japanese only. Support for other languages that exist in the product will be deprecated.

ifdef::PAM[]
=== Legacy process designer
The legacy process designer in {CENTRAL} is deprecated in {PRODUCT} 7.4.0. It will be removed in a future {PRODUCT} release. The legacy process designer will not receive any new enhancements or features. If you intend to use the new process designer, start migrating your processes to the new designer. Create all new processes in the new process designer. For information about migrating to the new designer, see {URL_MANAGING_PROJECTS}#migrating-from-legacy-designer-proc[_{MANAGING_PROJECTS}_].
Expand Down