From d1f71faadc61b2ee2b9998a19f7bf8631c4e045a Mon Sep 17 00:00:00 2001 From: Valentyn Solomko Date: Mon, 1 Jun 2020 15:20:22 +0300 Subject: [PATCH] Rebranding from "CloudBees Flow" to "CloudBees CD". --- README.md | 2 +- build.gradle | 2 +- help/changelog.yaml | 2 + help/overview.md | 2 +- .../procedures/AddServerToCluster/postface.md | 4 +- help/procedures/AddUserToGroup/postface.md | 4 +- .../procedures/ChangeUserPassword/postface.md | 4 +- .../procedures/CheckClusterStatus/postface.md | 2 +- help/procedures/CheckPageStatus/postface.md | 4 +- help/procedures/CheckServerStatus/postface.md | 2 +- .../ConfigureUserLockoutManager/postface.md | 2 +- help/procedures/CreateCluster/postface.md | 2 +- .../procedures/CreateConfiguration/preface.md | 2 +- help/procedures/CreateDatasource/postface.md | 2 +- help/procedures/CreateDomain/postface.md | 2 +- help/procedures/CreateGroup/postface.md | 2 +- .../CreateManagedServer/postface.md | 2 +- .../postface.md | 2 +- .../CreateOrUpdateDatasource/postface.md | 2 +- .../CreateOrUpdateJMSModule/postface.md | 2 +- .../postface.md | 2 +- .../CreateOrUpdateJMSQueue/postface.md | 2 +- .../CreateOrUpdateJMSServer/postface.md | 2 +- .../CreateOrUpdateJMSTopic/postface.md | 2 +- help/procedures/CreateTemplate/postface.md | 2 +- help/procedures/CreateUser/postface.md | 2 +- help/procedures/DeleteCluster/postface.md | 2 +- .../DeleteConnectionFactory/postface.md | 2 +- help/procedures/DeleteDatasource/postface.md | 2 +- help/procedures/DeleteGroup/postface.md | 2 +- help/procedures/DeleteJMSModule/postface.md | 2 +- .../DeleteJMSModuleSubdeployment/postface.md | 2 +- help/procedures/DeleteJMSQueue/postface.md | 2 +- help/procedures/DeleteJMSServer/postface.md | 2 +- help/procedures/DeleteJMSTopic/postface.md | 2 +- .../DeleteManagedServer/postface.md | 2 +- help/procedures/DeleteUser/postface.md | 2 +- help/procedures/DeployApp/postface.md | 2 +- .../RemoveUserFromGroup/postface.md | 4 +- help/procedures/ResumeServer/postface.md | 2 +- help/procedures/RunDeployer/postface.md | 2 +- help/procedures/RunWLST/postface.md | 2 +- help/procedures/StartAdminServer/postface.md | 2 +- help/procedures/StartApp/postface.md | 2 +- help/procedures/StartCluster/postface.md | 2 +- .../procedures/StartManagedServer/postface.md | 2 +- help/procedures/StartNodeManager/postface.md | 2 +- help/procedures/StopAdminServer/postface.md | 2 +- help/procedures/StopApp/postface.md | 2 +- help/procedures/StopCluster/postface.md | 2 +- help/procedures/StopManagedServer/postface.md | 2 +- help/procedures/StopNodeManager/postface.md | 2 +- help/procedures/SuspendServer/postface.md | 2 +- help/procedures/UndeployApp/postface.md | 2 +- help/procedures/UnlockUserAccount/postface.md | 2 +- help/procedures/UpdateApp/postface.md | 2 +- help/procedures/UpdateAppConfig/postface.md | 2 +- pages/EC-WebLogic_help.xml | 142 +++++++++--------- src/main/resources/project/lib/EC/WebLogic.pm | 2 +- .../ec_parameterForm-Discover.xml | 8 +- src/main/resources/project/project.xml | 12 +- 61 files changed, 149 insertions(+), 139 deletions(-) diff --git a/README.md b/README.md index 04afeecb..99976920 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,7 @@ EC-WebLogic ============ -The CloudBees Flow WebLogic integration +The CloudBees CD WebLogic integration ## Compile ## diff --git a/build.gradle b/build.gradle index b1760e7c..934c4a96 100644 --- a/build.gradle +++ b/build.gradle @@ -28,7 +28,7 @@ repositories { group = "com.electriccloud" description = "Plugins : EC-WebLogic" -version = "3.5.0" +version = "3.5.1" apply plugin: 'flow-gradle-plugin' apply plugin: 'license' diff --git a/help/changelog.yaml b/help/changelog.yaml index 73d19483..0f37f096 100644 --- a/help/changelog.yaml +++ b/help/changelog.yaml @@ -1,3 +1,5 @@ +3.5.1: + - Rebranding from "CloudBees Flow" to "CloudBees CD". 3.5.0: - Add checking connection while creating a configuration. - Jobs for the successful "CreateConfiguration" and "EditConfiguration" run is now preserved. diff --git a/help/overview.md b/help/overview.md index 32ac2a7b..e838dc08 100644 --- a/help/overview.md +++ b/help/overview.md @@ -14,7 +14,7 @@ applications and secure. For more information about WebLogic, go to WebLogic home page. -## CloudBees Flow Integration to WebLogic +## CloudBees CD Integration to WebLogic Use this plugin to interact with the Oracle WebLogic server for application and server management, interacting or editing existing applications, and deploying new applications. diff --git a/help/procedures/AddServerToCluster/postface.md b/help/procedures/AddServerToCluster/postface.md index 926e11b3..33a7dc27 100644 --- a/help/procedures/AddServerToCluster/postface.md +++ b/help/procedures/AddServerToCluster/postface.md @@ -1,9 +1,9 @@ -

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the page was checked successfully.

+

After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the page was checked successfully.

In the AddServerToCluster step, click the Log button to see the diagnostic information:


- Note: In the URL, the protocol is http. For this procedure,CloudBees Flow uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers. + Note: In the URL, the protocol is http. For this procedure,CloudBees CD uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.

diff --git a/help/procedures/AddUserToGroup/postface.md b/help/procedures/AddUserToGroup/postface.md index 3d483725..87f099f6 100644 --- a/help/procedures/AddUserToGroup/postface.md +++ b/help/procedures/AddUserToGroup/postface.md @@ -3,9 +3,9 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the page was checked successfully.

+

After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the page was checked successfully.

In the AddUserToGroup step, click the Log button to see the diagnostic information:


-

Note: In the URL, the protocol is http. For this procedure, CloudBees Flow uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.

+

Note: In the URL, the protocol is http. For this procedure, CloudBees CD uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.

diff --git a/help/procedures/ChangeUserPassword/postface.md b/help/procedures/ChangeUserPassword/postface.md index d9d40565..e83a4f63 100644 --- a/help/procedures/ChangeUserPassword/postface.md +++ b/help/procedures/ChangeUserPassword/postface.md @@ -1,9 +1,9 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the page was checked successfully.

+

After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the page was checked successfully.

In the ChangeUserPassword step, click the Log button to see the diagnostic information:


-

Note: In the URL, the protocol is http. For this procedure, CloudBees Flow uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.

+

Note: In the URL, the protocol is http. For this procedure, CloudBees CD uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.

diff --git a/help/procedures/CheckClusterStatus/postface.md b/help/procedures/CheckClusterStatus/postface.md index 65ad6d8f..accd2cbd 100644 --- a/help/procedures/CheckClusterStatus/postface.md +++ b/help/procedures/CheckClusterStatus/postface.md @@ -1,7 +1,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the cluster was checked successfully.

+

After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the cluster was checked successfully.

In the CheckClusterStatus step, click the Log button to see the diagnostic information:
diff --git a/help/procedures/CheckPageStatus/postface.md b/help/procedures/CheckPageStatus/postface.md index e0e10afd..bb08feba 100644 --- a/help/procedures/CheckPageStatus/postface.md +++ b/help/procedures/CheckPageStatus/postface.md @@ -1,10 +1,10 @@ -After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the page was checked successfully. +After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the page was checked successfully. In the *CheckPageStatus* step, click the Log button to see the diagnostic information: -

Note: In the URL, the protocol is http. For this procedure, CloudBees Flow uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.

+

Note: In the URL, the protocol is http. For this procedure, CloudBees CD uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.

diff --git a/help/procedures/CheckServerStatus/postface.md b/help/procedures/CheckServerStatus/postface.md index 2af950ef..fded0c85 100644 --- a/help/procedures/CheckServerStatus/postface.md +++ b/help/procedures/CheckServerStatus/postface.md @@ -1,7 +1,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the server was checked successfully.

+

After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the server was checked successfully.

In the CheckServerStatus step, click the Log button to see the diagnostic information:
diff --git a/help/procedures/ConfigureUserLockoutManager/postface.md b/help/procedures/ConfigureUserLockoutManager/postface.md index 5c144ce1..5311ed8d 100644 --- a/help/procedures/ConfigureUserLockoutManager/postface.md +++ b/help/procedures/ConfigureUserLockoutManager/postface.md @@ -2,7 +2,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the server was checked successfully.

+

After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the server was checked successfully.

In the ConfigureUserLockoutManager step, click the Log button to see the diagnostic information:
diff --git a/help/procedures/CreateCluster/postface.md b/help/procedures/CreateCluster/postface.md index aec40f62..791be074 100644 --- a/help/procedures/CreateCluster/postface.md +++ b/help/procedures/CreateCluster/postface.md @@ -2,7 +2,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the server was checked successfully.

+

After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the server was checked successfully.

In the CreateCluster step, click the Log button to see the diagnostic information:
diff --git a/help/procedures/CreateConfiguration/preface.md b/help/procedures/CreateConfiguration/preface.md index 8712dc05..04e401c8 100644 --- a/help/procedures/CreateConfiguration/preface.md +++ b/help/procedures/CreateConfiguration/preface.md @@ -1,4 +1,4 @@ -**After you perform the setup below it is important to make sure that the CloudBees Flow agent machine on which WebLogic runs is registered as a resource that can be pinged.** +**After you perform the setup below it is important to make sure that the CloudBees CD agent machine on which WebLogic runs is registered as a resource that can be pinged.** diff --git a/help/procedures/CreateDatasource/postface.md b/help/procedures/CreateDatasource/postface.md index 09a4aac7..e8be2d0e 100644 --- a/help/procedures/CreateDatasource/postface.md +++ b/help/procedures/CreateDatasource/postface.md @@ -2,7 +2,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was created successfully.

+

After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was created successfully.

In the CreateDatasource step, click the Log button to see the diagnostic information:
diff --git a/help/procedures/CreateDomain/postface.md b/help/procedures/CreateDomain/postface.md index 98348457..916b826c 100644 --- a/help/procedures/CreateDomain/postface.md +++ b/help/procedures/CreateDomain/postface.md @@ -2,7 +2,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was created successfully.

+

After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was created successfully.

In the CreateDomain step, click the Log button to see the diagnostic information:
diff --git a/help/procedures/CreateGroup/postface.md b/help/procedures/CreateGroup/postface.md index 6b99d80f..3d53256f 100644 --- a/help/procedures/CreateGroup/postface.md +++ b/help/procedures/CreateGroup/postface.md @@ -2,7 +2,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was created successfully.

+

After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was created successfully.

In the CreateGroup step, click the Log button to see the diagnostic information:
diff --git a/help/procedures/CreateManagedServer/postface.md b/help/procedures/CreateManagedServer/postface.md index 41e6e386..d2f9bd61 100644 --- a/help/procedures/CreateManagedServer/postface.md +++ b/help/procedures/CreateManagedServer/postface.md @@ -3,7 +3,7 @@ ## Output -After the job runs, you can view the results on the Job Details page in CloudBees Flow. The Managed Server was created successfully. +After the job runs, you can view the results on the Job Details page in CloudBees CD. The Managed Server was created successfully. In the CreateManagedServer step, click the Log button to see the diagnostic information: diff --git a/help/procedures/CreateOrUpdateConnectionFactory/postface.md b/help/procedures/CreateOrUpdateConnectionFactory/postface.md index 00a2ad53..582737f5 100644 --- a/help/procedures/CreateOrUpdateConnectionFactory/postface.md +++ b/help/procedures/CreateOrUpdateConnectionFactory/postface.md @@ -2,7 +2,7 @@ ## Output -After the job runs, you can view the results on the Job Details page in CloudBees Flow. The Connection Factory was created successfully. +After the job runs, you can view the results on the Job Details page in CloudBees CD. The Connection Factory was created successfully. diff --git a/help/procedures/CreateOrUpdateDatasource/postface.md b/help/procedures/CreateOrUpdateDatasource/postface.md index 15195eb6..3cccd936 100644 --- a/help/procedures/CreateOrUpdateDatasource/postface.md +++ b/help/procedures/CreateOrUpdateDatasource/postface.md @@ -2,7 +2,7 @@ ## Output -After the job runs, you can view the results on the Job Details page in CloudBees Flow. The Datasource was created successfully. +After the job runs, you can view the results on the Job Details page in CloudBees CD. The Datasource was created successfully. diff --git a/help/procedures/CreateOrUpdateJMSModule/postface.md b/help/procedures/CreateOrUpdateJMSModule/postface.md index c329141e..a4748dbe 100644 --- a/help/procedures/CreateOrUpdateJMSModule/postface.md +++ b/help/procedures/CreateOrUpdateJMSModule/postface.md @@ -2,7 +2,7 @@ ## Output -After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Module was created successfully. +After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Module was created successfully. diff --git a/help/procedures/CreateOrUpdateJMSModuleSubdeployment/postface.md b/help/procedures/CreateOrUpdateJMSModuleSubdeployment/postface.md index 754e0e7a..5aae6a75 100644 --- a/help/procedures/CreateOrUpdateJMSModuleSubdeployment/postface.md +++ b/help/procedures/CreateOrUpdateJMSModuleSubdeployment/postface.md @@ -2,7 +2,7 @@ ## Output -After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Module Subdeployment was created successfully. +After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Module Subdeployment was created successfully. diff --git a/help/procedures/CreateOrUpdateJMSQueue/postface.md b/help/procedures/CreateOrUpdateJMSQueue/postface.md index 8d833e99..8988344b 100644 --- a/help/procedures/CreateOrUpdateJMSQueue/postface.md +++ b/help/procedures/CreateOrUpdateJMSQueue/postface.md @@ -2,7 +2,7 @@ ## Output -After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Queue was created successfully. +After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Queue was created successfully. diff --git a/help/procedures/CreateOrUpdateJMSServer/postface.md b/help/procedures/CreateOrUpdateJMSServer/postface.md index d91a5751..6c0a6b0f 100644 --- a/help/procedures/CreateOrUpdateJMSServer/postface.md +++ b/help/procedures/CreateOrUpdateJMSServer/postface.md @@ -2,7 +2,7 @@ ## Output -After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Server was created successfully. +After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Server was created successfully. diff --git a/help/procedures/CreateOrUpdateJMSTopic/postface.md b/help/procedures/CreateOrUpdateJMSTopic/postface.md index b0ec0a14..47c00085 100644 --- a/help/procedures/CreateOrUpdateJMSTopic/postface.md +++ b/help/procedures/CreateOrUpdateJMSTopic/postface.md @@ -2,7 +2,7 @@ ## Output -After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Topic was created successfully. +After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Topic was created successfully. diff --git a/help/procedures/CreateTemplate/postface.md b/help/procedures/CreateTemplate/postface.md index e3a8da5e..48dd3ff7 100644 --- a/help/procedures/CreateTemplate/postface.md +++ b/help/procedures/CreateTemplate/postface.md @@ -2,7 +2,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was created successfully.

+

After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was created successfully.

In the CreateTemplate step, click the Log button to see the diagnostic information:
diff --git a/help/procedures/CreateUser/postface.md b/help/procedures/CreateUser/postface.md index 57fb38d0..3ef3f8e8 100644 --- a/help/procedures/CreateUser/postface.md +++ b/help/procedures/CreateUser/postface.md @@ -2,7 +2,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was created successfully.

+

After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was created successfully.

In the CreateUser step, click the Log button to see the diagnostic information:
diff --git a/help/procedures/DeleteCluster/postface.md b/help/procedures/DeleteCluster/postface.md index 920ba873..f2d475db 100644 --- a/help/procedures/DeleteCluster/postface.md +++ b/help/procedures/DeleteCluster/postface.md @@ -2,7 +2,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the server was checked successfully.

+

After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the server was checked successfully.

In the DeleteCluster step, click the Log button to see the diagnostic information:
diff --git a/help/procedures/DeleteConnectionFactory/postface.md b/help/procedures/DeleteConnectionFactory/postface.md index 755a0f14..365da389 100644 --- a/help/procedures/DeleteConnectionFactory/postface.md +++ b/help/procedures/DeleteConnectionFactory/postface.md @@ -3,7 +3,7 @@ ## Output -After the job runs, you can view the results on the Job Details page in CloudBees Flow. The Connection Factory was deleted. +After the job runs, you can view the results on the Job Details page in CloudBees CD. The Connection Factory was deleted. diff --git a/help/procedures/DeleteDatasource/postface.md b/help/procedures/DeleteDatasource/postface.md index acc1485b..93c37fde 100644 --- a/help/procedures/DeleteDatasource/postface.md +++ b/help/procedures/DeleteDatasource/postface.md @@ -1,7 +1,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was deleted successfully.

+

After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was deleted successfully.

In the DeleteDatasource step, click the Log button to see the diagnostic information:
diff --git a/help/procedures/DeleteGroup/postface.md b/help/procedures/DeleteGroup/postface.md index 13b5056c..71491d59 100644 --- a/help/procedures/DeleteGroup/postface.md +++ b/help/procedures/DeleteGroup/postface.md @@ -2,7 +2,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was created successfully.

+

After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was created successfully.

In the DeleteGroup step, click the Log button to see the diagnostic information:
diff --git a/help/procedures/DeleteJMSModule/postface.md b/help/procedures/DeleteJMSModule/postface.md index 0e2f23c0..429f325b 100644 --- a/help/procedures/DeleteJMSModule/postface.md +++ b/help/procedures/DeleteJMSModule/postface.md @@ -3,7 +3,7 @@ ## Output -After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Module was deleted. +After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Module was deleted. diff --git a/help/procedures/DeleteJMSModuleSubdeployment/postface.md b/help/procedures/DeleteJMSModuleSubdeployment/postface.md index c08e7de3..341b0e3d 100644 --- a/help/procedures/DeleteJMSModuleSubdeployment/postface.md +++ b/help/procedures/DeleteJMSModuleSubdeployment/postface.md @@ -2,7 +2,7 @@ ## Output -After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Subdeployment was deleted. +After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Subdeployment was deleted. diff --git a/help/procedures/DeleteJMSQueue/postface.md b/help/procedures/DeleteJMSQueue/postface.md index 36893aac..12cf93fc 100644 --- a/help/procedures/DeleteJMSQueue/postface.md +++ b/help/procedures/DeleteJMSQueue/postface.md @@ -2,7 +2,7 @@ ## Output -After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Queue was deleted. +After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Queue was deleted. diff --git a/help/procedures/DeleteJMSServer/postface.md b/help/procedures/DeleteJMSServer/postface.md index 9ef87545..28147241 100644 --- a/help/procedures/DeleteJMSServer/postface.md +++ b/help/procedures/DeleteJMSServer/postface.md @@ -2,7 +2,7 @@ ## Output -After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Server was deleted. +After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Server was deleted. diff --git a/help/procedures/DeleteJMSTopic/postface.md b/help/procedures/DeleteJMSTopic/postface.md index 827fd51f..1a96dc5a 100644 --- a/help/procedures/DeleteJMSTopic/postface.md +++ b/help/procedures/DeleteJMSTopic/postface.md @@ -2,7 +2,7 @@ ## Output -After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Queue was deleted. +After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Queue was deleted. diff --git a/help/procedures/DeleteManagedServer/postface.md b/help/procedures/DeleteManagedServer/postface.md index 7b6a0a1d..c8454991 100644 --- a/help/procedures/DeleteManagedServer/postface.md +++ b/help/procedures/DeleteManagedServer/postface.md @@ -2,7 +2,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The Managed Server was deleted successfully.

+

After the job runs, you can view the results on the Job Details page in CloudBees CD. The Managed Server was deleted successfully.

In the DeleteManagedServer step, click the Log button to see the diagnostic information:
diff --git a/help/procedures/DeleteUser/postface.md b/help/procedures/DeleteUser/postface.md index fd77d819..f7aeab42 100644 --- a/help/procedures/DeleteUser/postface.md +++ b/help/procedures/DeleteUser/postface.md @@ -2,7 +2,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was created successfully.

+

After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was created successfully.

In the DeleteUser step, click the Log button to see the diagnostic information:
diff --git a/help/procedures/DeployApp/postface.md b/help/procedures/DeployApp/postface.md index 05e276ae..528cf94f 100644 --- a/help/procedures/DeployApp/postface.md +++ b/help/procedures/DeployApp/postface.md @@ -2,7 +2,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. +

After the job runs, you can view the results on the Job Details page in CloudBees CD. The application was deployed successfully.

In the DeployApp step, click the Log button to see the diagnostic information:

diff --git a/help/procedures/RemoveUserFromGroup/postface.md b/help/procedures/RemoveUserFromGroup/postface.md index 91acb0bf..52d85fd8 100644 --- a/help/procedures/RemoveUserFromGroup/postface.md +++ b/help/procedures/RemoveUserFromGroup/postface.md @@ -2,9 +2,9 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the page was checked successfully.

+

After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the page was checked successfully.

In the RemoveUserFromGroup step, click the Log button to see the diagnostic information:


-

Note: In the URL, the protocol is http. For this procedure,CloudBees Flow uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.

+

Note: In the URL, the protocol is http. For this procedure,CloudBees CD uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.

diff --git a/help/procedures/ResumeServer/postface.md b/help/procedures/ResumeServer/postface.md index 4f62c351..84fe1f08 100644 --- a/help/procedures/ResumeServer/postface.md +++ b/help/procedures/ResumeServer/postface.md @@ -2,7 +2,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The server instance successfully +

After the job runs, you can view the results on the Job Details page in CloudBees CD. The server instance successfully moved from the STANDBY state to the RUNNING state.

In the ResumeServer step, click the Log button to see the diagnostic information:

diff --git a/help/procedures/RunDeployer/postface.md b/help/procedures/RunDeployer/postface.md index ee9e0b2c..3042bc58 100644 --- a/help/procedures/RunDeployer/postface.md +++ b/help/procedures/RunDeployer/postface.md @@ -1,7 +1,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The weblogic.Deployer tool was run +

After the job runs, you can view the results on the Job Details page in CloudBees CD. The weblogic.Deployer tool was run successfully.

In the RunDeployer step, click the Log button to see the diagnostic information:

diff --git a/help/procedures/RunWLST/postface.md b/help/procedures/RunWLST/postface.md index 2a2472e1..c743197d 100644 --- a/help/procedures/RunWLST/postface.md +++ b/help/procedures/RunWLST/postface.md @@ -2,7 +2,7 @@ ### Output -After the job runs, you can view the results on the Job Details page in CloudBees Flow. +After the job runs, you can view the results on the Job Details page in CloudBees CD.

In the RunWLST step, click the Log button to see the diagnostic information similar to this:

diff --git a/help/procedures/StartAdminServer/postface.md b/help/procedures/StartAdminServer/postface.md index 737a5d0a..7e4fc2f2 100644 --- a/help/procedures/StartAdminServer/postface.md +++ b/help/procedures/StartAdminServer/postface.md @@ -1,7 +1,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The server was started +

After the job runs, you can view the results on the Job Details page in CloudBees CD. The server was started successfully.

In the StartAdminServer step, click the Log button to see the diagnostic information:

diff --git a/help/procedures/StartApp/postface.md b/help/procedures/StartApp/postface.md index 799ebc8d..e03ffd12 100644 --- a/help/procedures/StartApp/postface.md +++ b/help/procedures/StartApp/postface.md @@ -1,7 +1,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The application +

After the job runs, you can view the results on the Job Details page in CloudBees CD. The application was started successfully.

In the StartApp step, click the Log button to see the diagnostic information:

diff --git a/help/procedures/StartCluster/postface.md b/help/procedures/StartCluster/postface.md index 6bef0644..3200ab5f 100644 --- a/help/procedures/StartCluster/postface.md +++ b/help/procedures/StartCluster/postface.md @@ -2,7 +2,7 @@

Output

-After the job runs, you can view the results on the Job Details page in CloudBees Flow. The cluster was started successfully. +After the job runs, you can view the results on the Job Details page in CloudBees CD. The cluster was started successfully.

diff --git a/help/procedures/StartManagedServer/postface.md b/help/procedures/StartManagedServer/postface.md index ee0988cf..d14441cb 100644 --- a/help/procedures/StartManagedServer/postface.md +++ b/help/procedures/StartManagedServer/postface.md @@ -1,7 +1,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The server was started +

After the job runs, you can view the results on the Job Details page in CloudBees CD. The server was started successfully.

In the StartManagedServer step, click the Log button to see the diagnostic information:

diff --git a/help/procedures/StartNodeManager/postface.md b/help/procedures/StartNodeManager/postface.md index b8ae400d..1ef5b825 100644 --- a/help/procedures/StartNodeManager/postface.md +++ b/help/procedures/StartNodeManager/postface.md @@ -1,7 +1,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The Node Manager was started +

After the job runs, you can view the results on the Job Details page in CloudBees CD. The Node Manager was started successfully.

In the StartNodeManager step, click the Log button to see the diagnostic information:

diff --git a/help/procedures/StopAdminServer/postface.md b/help/procedures/StopAdminServer/postface.md index 05ed2c46..72444afe 100644 --- a/help/procedures/StopAdminServer/postface.md +++ b/help/procedures/StopAdminServer/postface.md @@ -2,7 +2,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The server was stopped +

After the job runs, you can view the results on the Job Details page in CloudBees CD. The server was stopped successfully.

In the StopAdminServer step, click the Log button to see the diagnostic information:

diff --git a/help/procedures/StopApp/postface.md b/help/procedures/StopApp/postface.md index ec76e43d..061265c8 100644 --- a/help/procedures/StopApp/postface.md +++ b/help/procedures/StopApp/postface.md @@ -2,7 +2,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The application was stopped +

After the job runs, you can view the results on the Job Details page in CloudBees CD. The application was stopped successfully.

In the StopApp step, click the Log button to see the diagnostic information:

diff --git a/help/procedures/StopCluster/postface.md b/help/procedures/StopCluster/postface.md index 23af8b04..d0129f81 100644 --- a/help/procedures/StopCluster/postface.md +++ b/help/procedures/StopCluster/postface.md @@ -3,7 +3,7 @@

Output

-After the job runs, you can view the results on the Job Details page in CloudBees Flow. The cluster was stopped successfully. +After the job runs, you can view the results on the Job Details page in CloudBees CD. The cluster was stopped successfully.

diff --git a/help/procedures/StopManagedServer/postface.md b/help/procedures/StopManagedServer/postface.md index 2f2afd6d..c67a85d5 100644 --- a/help/procedures/StopManagedServer/postface.md +++ b/help/procedures/StopManagedServer/postface.md @@ -2,7 +2,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The server was stopped successfully.

+

After the job runs, you can view the results on the Job Details page in CloudBees CD. The server was stopped successfully.

In the StopManagedServer step, click the Log button to see the diagnostic information:


diff --git a/help/procedures/StopNodeManager/postface.md b/help/procedures/StopNodeManager/postface.md index a81f29a9..2ecbe18c 100644 --- a/help/procedures/StopNodeManager/postface.md +++ b/help/procedures/StopNodeManager/postface.md @@ -2,7 +2,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The Node Manager was stopped +

After the job runs, you can view the results on the Job Details page in CloudBees CD. The Node Manager was stopped successfully.

In the StopNodeManager step, click the Log button to see the diagnostic information:

diff --git a/help/procedures/SuspendServer/postface.md b/help/procedures/SuspendServer/postface.md index 69e63d5d..5ca1e73d 100644 --- a/help/procedures/SuspendServer/postface.md +++ b/help/procedures/SuspendServer/postface.md @@ -2,7 +2,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The server was suspended +

After the job runs, you can view the results on the Job Details page in CloudBees CD. The server was suspended successfully.

In the SuspendServer step, click the Log button to see the diagnostic information:

diff --git a/help/procedures/UndeployApp/postface.md b/help/procedures/UndeployApp/postface.md index 5fba14f1..e993212c 100644 --- a/help/procedures/UndeployApp/postface.md +++ b/help/procedures/UndeployApp/postface.md @@ -3,7 +3,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The application was undeployed +

After the job runs, you can view the results on the Job Details page in CloudBees CD. The application was undeployed successfully.

In the UndeployApp step, click the Log button to see the diagnostic information:

diff --git a/help/procedures/UnlockUserAccount/postface.md b/help/procedures/UnlockUserAccount/postface.md index 07904dfd..d3e00520 100644 --- a/help/procedures/UnlockUserAccount/postface.md +++ b/help/procedures/UnlockUserAccount/postface.md @@ -2,7 +2,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The application was undeployed +

After the job runs, you can view the results on the Job Details page in CloudBees CD. The application was undeployed successfully.

In the UnlockUserAccount step, click the Log button to see the diagnostic information:

diff --git a/help/procedures/UpdateApp/postface.md b/help/procedures/UpdateApp/postface.md index 6c87bae3..29b430a1 100644 --- a/help/procedures/UpdateApp/postface.md +++ b/help/procedures/UpdateApp/postface.md @@ -2,7 +2,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The application was undeployed successfully.

+

After the job runs, you can view the results on the Job Details page in CloudBees CD. The application was undeployed successfully.

In the UpdateApp step, click the Log button to see the diagnostic information:


diff --git a/help/procedures/UpdateAppConfig/postface.md b/help/procedures/UpdateAppConfig/postface.md index f8e4c0a1..d641b05a 100644 --- a/help/procedures/UpdateAppConfig/postface.md +++ b/help/procedures/UpdateAppConfig/postface.md @@ -2,7 +2,7 @@

Output

-

After the job runs, you can view the results on the Job Details page in CloudBees Flow. The application was undeployed successfully.

+

After the job runs, you can view the results on the Job Details page in CloudBees CD. The application was undeployed successfully.

In the UpdateAppConfig step, click the Log button to see the diagnostic information:


diff --git a/pages/EC-WebLogic_help.xml b/pages/EC-WebLogic_help.xml index f59abe41..92a56d51 100644 --- a/pages/EC-WebLogic_help.xml +++ b/pages/EC-WebLogic_help.xml @@ -14,7 +14,7 @@

@PLUGIN_KEY@

Plugin version @PLUGIN_VERSION@

-

Revised on September 17, 2019

+

Revised on June 01, 2020

Contents

@@ -62,7 +62,7 @@ support for the encryption of data transmissions, as well as authentication and authorization mechanisms, make applications and secure.

For more information about WebLogic, go to WebLogic home page.

-

CloudBees Flow Integration to WebLogic

+

CloudBees CD Integration to WebLogic

Use this plugin to interact with the Oracle WebLogic server for application and server management, interacting or editing existing applications, and deploying new applications. You can start and stop both the Managed Servers and the Administration Server @@ -102,7 +102,7 @@ or to enter a new embedded file.

Creating Plugin Configurations

-

To create plugin configurations in CloudBees Flow, +

To create plugin configurations in CloudBees CD, do these steps:

  • Go to Administration > Plugins to open the Plugin Manager.
    • @@ -111,7 +111,7 @@ or to enter a new embedded file.

    Configurations page.
  • Click Create Configuration as per the description of parameters below.
    • -

    After you perform the setup below it is important to make sure that the CloudBees Flow agent machine on which WebLogic runs is registered as a resource that can be pinged.

    +

    After you perform the setup below it is important to make sure that the CloudBees CD agent machine on which WebLogic runs is registered as a resource that can be pinged.

    Note: In the URL, the protocol is "t3" or "t3s". The RMI communications in WebLogic Server use @@ -123,7 +123,8 @@ which it connects, and creates a single "t3" connection to carry all traffic for a JVM.

    - Configuration Parameters + +

    Configuration Procedure Parameters

    @@ -290,7 +291,7 @@ to carry all traffic for a JVM.


    Output

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the server was checked successfully.

    +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the server was checked successfully.

    In the CreateCluster step, click the Log button to see the diagnostic information:
    @@ -380,7 +381,7 @@ to carry all traffic for a JVM.

    Output

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was created successfully.

    +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was created successfully.

    In the CreateDomain step, click the Log button to see the diagnostic information:
    @@ -454,7 +455,7 @@ to carry all traffic for a JVM.


    Output

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The Managed Server was created successfully. +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The Managed Server was created successfully.

    In the CreateManagedServer step, click the Log button to see the diagnostic information:

    @@ -519,13 +520,13 @@ to carry all traffic for a JVM.

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the page was checked successfully.

    +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the page was checked successfully.

    In the AddServerToCluster step, click the Log button to see the diagnostic information:


    - Note: In the URL, the protocol is http. For this procedure,CloudBees Flow uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers. + Note: In the URL, the protocol is http. For this procedure,CloudBees CD uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.

    @@ -584,7 +585,7 @@ to carry all traffic for a JVM.


    Output

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the server was checked successfully.

    +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the server was checked successfully.

    In the DeleteCluster step, click the Log button to see the diagnostic information:
    @@ -644,7 +645,7 @@ to carry all traffic for a JVM.


    Output

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The Managed Server was deleted successfully.

    +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The Managed Server was deleted successfully.

    In the DeleteManagedServer step, click the Log button to see the diagnostic information:
    @@ -721,7 +722,7 @@ to carry all traffic for a JVM.


    Output

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The server was started +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The server was started successfully.

    In the StartAdminServer step, click the Log button to see the diagnostic information:

    @@ -797,7 +798,7 @@ successfully.

    Output

    -After the job runs, you can view the results on the Job Details page in CloudBees Flow. The cluster was started successfully. +After the job runs, you can view the results on the Job Details page in CloudBees CD. The cluster was started successfully.

    @@ -898,7 +899,7 @@ For example:


    Output

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The server was started +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The server was started successfully.

    In the StartManagedServer step, click the Log button to see the diagnostic information:

    @@ -964,7 +965,7 @@ applications with high availability requirements.


    Output

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The Node Manager was started +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The Node Manager was started successfully.

    In the StartNodeManager step, click the Log button to see the diagnostic information:

    @@ -1020,7 +1021,7 @@ successfully.


    Output

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The server was stopped +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The server was stopped successfully.

    In the StopAdminServer step, click the Log button to see the diagnostic information:

    @@ -1116,7 +1117,7 @@ successfully.

    Output

    -After the job runs, you can view the results on the Job Details page in CloudBees Flow. The cluster was stopped successfully. +After the job runs, you can view the results on the Job Details page in CloudBees CD. The cluster was stopped successfully.

    @@ -1182,7 +1183,7 @@ Manager must be running before you run this procedure.


    Output

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The server was stopped successfully.

    +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The server was stopped successfully.

    In the StopManagedServer step, click the Log button to see the diagnostic information:


    @@ -1279,7 +1280,7 @@ Manager must be running before you run this procedure.


    Output

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The Node Manager was stopped +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The Node Manager was stopped successfully.

    In the StopNodeManager step, click the Log button to see the diagnostic information:

    @@ -1370,7 +1371,7 @@ successfully.


    Output

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The server was suspended +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The server was suspended successfully.

    In the SuspendServer step, click the Log button to see the diagnostic information:

    @@ -1440,7 +1441,7 @@ successfully.


    Output

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The server instance successfully +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The server instance successfully moved from the STANDBY state to the RUNNING state.

    In the ResumeServer step, click the Log button to see the diagnostic information:

    @@ -1646,7 +1647,7 @@ moved from the STANDBY state to the RUNNING state.


    Output

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The application was deployed successfully.

    In the DeployApp step, click the Log button to see the diagnostic information:

    @@ -1747,7 +1748,7 @@ The application was deployed successfully.


    Output

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The application was undeployed successfully.

    +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The application was undeployed successfully.

    In the UpdateAppConfig step, click the Log button to see the diagnostic information:


    @@ -1848,7 +1849,7 @@ Contrary to the weblogic documentation in section 'Undeploying a Retiring Applic

    Output

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The application was undeployed +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The application was undeployed successfully.

    In the UndeployApp step, click the Log button to see the diagnostic information:

    @@ -1926,7 +1927,7 @@ successfully.


    Output

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The application was undeployed successfully.

    +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The application was undeployed successfully.

    In the UpdateApp step, click the Log button to see the diagnostic information:


    @@ -2036,7 +2037,7 @@ provides a command-line interface to the WebLogic Server deployment API.


    Output

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The weblogic.Deployer tool was run +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The weblogic.Deployer tool was run successfully.

    In the RunDeployer step, click the Log button to see the diagnostic information:

    @@ -2120,7 +2121,7 @@ successfully.


    Output

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The application +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The application was started successfully.

    In the StartApp step, click the Log button to see the diagnostic information:

    @@ -2204,7 +2205,7 @@ was started successfully.


    Output

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The application was stopped +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The application was stopped successfully.

    In the StopApp step, click the Log button to see the diagnostic information:

    @@ -2324,7 +2325,7 @@ By default, the JNDI name is the name of the Datasource. Applications that look

    Output

    -

    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The Datasource was created successfully.

    +

    After the job runs, you can view the results on the Job Details page in CloudBees CD. The Datasource was created successfully.

    In the CreateOrUpdateDatasource step, click the Log button to see the diagnostic information:

    Using plugin EC-WebLogic-3.4.0.0
@@ -2434,7 +2435,7 @@ DONE
         
    
             
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was deleted successfully.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was deleted successfully.
    
 
 
    In the DeleteDatasource step, click the Log button to see the diagnostic information:
 
    
@@ -2554,7 +2555,7 @@ DONE
             
    
 
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was created successfully.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was created successfully.
    
 
 
    In the CreateDatasource step, click the Log button to see the diagnostic information:
 
    
@@ -2702,7 +2703,7 @@ FlowControlParams.FlowControlEnabled=true
         
    
             
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The Connection Factory was created successfully.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The Connection Factory was created successfully.
    
 
 
    In the CreateOrUpdateConnectionFactory step, click the Log button to see the diagnostic information:
    
 
    Using plugin EC-WebLogic-3.3.0.0
@@ -2836,7 +2837,7 @@ This parameter controls as to what the Update Action should be when a JMS Module
         
    
             
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Module was created successfully.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Module was created successfully.
    
 
 
    In the CreateOrUpdateJMSModule step, click the Log button to see the diagnostic information:
    
 
    Using plugin EC-WebLogic-3.3.0.0
@@ -2955,7 +2956,7 @@ Selective Update - The procedure would update target servers for the existing JM
         
    
             
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Module Subdeployment was created successfully.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Module Subdeployment was created successfully.
    
 
 
    In the CreateOrUpdateJMSModuleSubdeployment step, click the Log button to see the diagnostic information:
    
 
    Using plugin EC-WebLogic-3.3.0.0
@@ -3106,7 +3107,7 @@ DeliveryFailureParams.RedeliveryLimit=3
         
    
             
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Queue was created successfully.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Queue was created successfully.
    
 
 
    In the CreateOrUpdateJMSQueue step, click the Log button to see the diagnostic information:
    
 
    Using plugin C-WebLogic-3.3.0.0
@@ -3235,7 +3236,7 @@ This parameter controls as to what the Update Action should be when a JMS Module
         
    
             
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Server was created successfully.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Server was created successfully.
    
 
 
    In the CreateOrUpdateJMSServer step, click the Log button to see the diagnostic information:
    
 
    Using plugin C-WebLogic-3.3.0.0
@@ -3380,7 +3381,7 @@ DeliveryFailureParams.RedeliveryLimit=5
         
    
             
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Topic was created successfully.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Topic was created successfully.
    
 
 
    In the CreateOrUpdateJMSTopic step, click the Log button to see the diagnostic information:
    
 
    Using plugin EC-WebLogic-3.3.0.0
@@ -3500,7 +3501,7 @@ DONE
         
    
             
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The Connection Factory was deleted.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The Connection Factory was deleted.
    
 
 
    In the DeleteConnectionFactory step, click the Log button to see the diagnostic information:
    
 
    Using plugin EC-WebLogic-3.3.0.0
@@ -3589,7 +3590,7 @@ DONE
         
    
             
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Module was deleted.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Module was deleted.
    
 
 
    In the DeleteJMSModule step, click the Log button to see the diagnostic information:
    
 
    Using plugin EC-WebLogic-3.3.0.0
@@ -3685,7 +3686,7 @@ DONE
         
    
             
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Subdeployment was deleted.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Subdeployment was deleted.
    
 
 
    In the DeleteJMSModuleSubdeployment step, click the Log button to see the diagnostic information:
    
 
    Using plugin EC-WebLogic-3.3.0.0
@@ -3784,7 +3785,7 @@ DONE
         
    
             
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Queue was deleted.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Queue was deleted.
    
 
 
    In the DeleteJMSQueue step, click the Log button to see the diagnostic information:
    
 
    Using plugin EC-WebLogic-3.3.0.0
@@ -3873,7 +3874,7 @@ DONE
         
    
             
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Server was deleted.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Server was deleted.
    
 
 
    In the DeleteJMSServer step, click the Log button to see the diagnostic information:
    
 
    Using plugin EC-WebLogic-3.3.0.0
@@ -3970,7 +3971,7 @@ DONE
         
    
             
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Queue was deleted.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Queue was deleted.
    
 
 
    In the DeleteJMSTopic step, click the Log button to see the diagnostic information:
    
 
    Using plugin EC-WebLogic-3.3.0.0
@@ -4098,7 +4099,7 @@ DONE
             
    
 
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was created successfully.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was created successfully.
    
 
 
    In the CreateUser step, click the Log button to see the diagnostic information:
 
    
@@ -4189,7 +4190,7 @@ DONE
             
    
 
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was created successfully.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was created successfully.
    
 
 
    In the CreateGroup step, click the Log button to see the diagnostic information:
 
    
@@ -4273,12 +4274,12 @@ DONE
             
    
 
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the page was checked successfully.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the page was checked successfully.
    
 
 
    In the AddUserToGroup step, click the Log button to see the diagnostic information:
    
 
    
 
-
    Note: In the URL, the protocol is http. For this procedure, CloudBees Flow uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.
    
+
    Note: In the URL, the protocol is http. For this procedure, CloudBees CD uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.
    
 
         
    
         
@@ -4356,12 +4357,12 @@ DONE
         
    
             
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the page was checked successfully.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the page was checked successfully.
    
 
 
    In the ChangeUserPassword step, click the Log button to see the diagnostic information:
    
 
    
 
-
    Note: In the URL, the protocol is http. For this procedure, CloudBees Flow uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.
    
+
    Note: In the URL, the protocol is http. For this procedure, CloudBees CD uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.
    
 
         
    
         
@@ -4440,12 +4441,12 @@ DONE
             
    
 
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the page was checked successfully.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the page was checked successfully.
    
 
 
    In the RemoveUserFromGroup step, click the Log button to see the diagnostic information:
    
 
    
 
-
    Note: In the URL, the protocol is http. For this procedure,CloudBees Flow uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.
    
+
    Note: In the URL, the protocol is http. For this procedure,CloudBees CD uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.
    
 
         
    
         
@@ -4517,7 +4518,7 @@ DONE
             
    
 
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the server was checked successfully.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the server was checked successfully.
    
 
 
    In the ConfigureUserLockoutManager step, click the Log button to see the diagnostic information:
 
    
@@ -4595,7 +4596,7 @@ DONE
             
 
    
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The application was undeployed
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The application was undeployed
 successfully.
    
 
 
    In the UnlockUserAccount step, click the Log button to see the diagnostic information:
    
@@ -4672,7 +4673,7 @@ successfully.
    
             
    
 
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was created successfully.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was created successfully.
    
 
 
    In the DeleteGroup step, click the Log button to see the diagnostic information:
 
    
@@ -4749,7 +4750,7 @@ successfully.
    
             
    
 
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was created successfully.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was created successfully.
    
 
 
    In the DeleteUser step, click the Log button to see the diagnostic information:
 
    
@@ -4825,7 +4826,7 @@ successfully.
    
         
    
             
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the cluster was checked successfully.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the cluster was checked successfully.
    
 
 
    In the CheckClusterStatus step, click the Log button to see the diagnostic information:
 
    
@@ -4901,7 +4902,7 @@ successfully.
    
         
    
             
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the server was checked successfully.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the server was checked successfully.
    
 
 
    In the CheckServerStatus step, click the Log button to see the diagnostic information:
 
    
@@ -5011,7 +5012,7 @@ control statements.
    
             
    
 
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD.
    
 
 
    In the RunWLST step, click the Log button to see the diagnostic information similar to this:
    
 
@@ -5074,7 +5075,7 @@ control statements.
    
             
    
 
 
    Output
    
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was created successfully.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was created successfully.
    
 
 
    In the CreateTemplate step, click the Log button to see the diagnostic information:
 
    
@@ -5142,11 +5143,11 @@ control statements.
    
         
         
    
             
-
    After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the page was checked successfully.
    
+
    After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the page was checked successfully.
    
 
 
    In the CheckPageStatus step, click the Log button to see the diagnostic information:
    
 
-
    Note: In the URL, the protocol is http. For this procedure, CloudBees Flow uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.
    
+
    Note: In the URL, the protocol is http. For this procedure, CloudBees CD uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.
    
 
         
    
         
@@ -5157,7 +5158,7 @@ control statements.
    
         
    Discover
    
         
         
-        
    This procedure connects to a Weblogic environment, discovers objects specified by user and creates a Weblogic plugin configuration and an Application/Environment model in CloudBees Flow based on objects discovered.
    
+        
    This procedure connects to a Weblogic environment, discovers objects specified by user and creates a Weblogic plugin configuration and an Application/Environment model in CloudBees CD based on objects discovered.
    
         
         
             
    After the procedure runs the following are created:
    
@@ -5198,21 +5199,21 @@ control statements.
    - + - + - + @@ -5261,7 +5262,7 @@ control statements.

     - + @@ -5331,6 +5332,13 @@ The list of supported object types:

    Release Notes

    +

    @PLUGIN_KEY@ 3.5.1

    +
      + +
    • Rebranding from "CloudBees Flow" to "CloudBees CD".
      • + +
    +

    @PLUGIN_KEY@ 3.5.0

      diff --git a/src/main/resources/project/lib/EC/WebLogic.pm b/src/main/resources/project/lib/EC/WebLogic.pm index 811376f5..f50a4986 100644 --- a/src/main/resources/project/lib/EC/WebLogic.pm +++ b/src/main/resources/project/lib/EC/WebLogic.pm @@ -472,7 +472,7 @@ sub configurationErrorWithSuggestions { my $suggestions = q{Reasons could be due to one or more of the following. Please ensure they are correct and try again.: 1. WebLogic URL - Is your URL complete and reachable? 2. WLST Script Absolute Path - Is your Path to the Script correct? -3. Test Resource - Is your Test resource correctly wired with Flow? Is your Test Resource correctly setup with WebLogic? +3. Test Resource - Is your Test resource correctly wired with CloudBees CD? Is your Test Resource correctly setup with WebLogic? 4. Credentials - Are your credentials correct? Are you able to use these credentials to log in to WebLogic using its console? }; diff --git a/src/main/resources/project/parameterForms/ec_parameterForm-Discover.xml b/src/main/resources/project/parameterForms/ec_parameterForm-Discover.xml index 4d09eebb..8a182173 100644 --- a/src/main/resources/project/parameterForms/ec_parameterForm-Discover.xml +++ b/src/main/resources/project/parameterForms/ec_parameterForm-Discover.xml @@ -22,21 +22,21 @@ ecp_weblogic_resourceName 0 - Name of the CloudBees Flow resource that represents the WebLogic environment that needs to be discovered. + Name of the CloudBees CD resource that represents the WebLogic environment that needs to be discovered. entry ecp_weblogic_hostname 0 - Hostname of a machine with WebLogic and CloudBees Flow Agent running on it. Either Resource hostname (and port) or Resource Name should be specified. + Hostname of a machine with WebLogic and CloudBees CD Agent running on it. Either Resource hostname (and port) or Resource Name should be specified. entry ecp_weblogic_resPort 0 - Port of CloudBees Flow agent running on the machine. Default is 7800. + Port of CloudBees CD agent running on the machine. Default is 7800. entry @@ -95,7 +95,7 @@ ecp_weblogic_envName 0 - If specified, will be used to create CloudBees Flow environment. + If specified, will be used to create CloudBees CD environment. entry diff --git a/src/main/resources/project/project.xml b/src/main/resources/project/project.xml index ed322bc4..c23c61d8 100644 --- a/src/main/resources/project/project.xml +++ b/src/main/resources/project/project.xml @@ -9348,7 +9348,7 @@ By default, the JNDI name is the name of the Datasource. Applications that look - This procedure connects to a Weblogic environment, discovers objects specified by user and creates a Weblogic plugin configuration and an Application/Environment model in CloudBees Flow based on objects discovered. + This procedure connects to a Weblogic environment, discovers objects specified by user and creates a Weblogic plugin configuration and an Application/Environment model in CloudBees CD based on objects discovered. weblogic-discover-$[jobId] Discover @PLUGIN_KEY@-@PLUGIN_VERSION@ @@ -9501,21 +9501,21 @@ By default, the JNDI name is the name of the Datasource. Applications that look - Name of the CloudBees Flow resource with the WebLogic instance running. + Name of the CloudBees CD resource with the WebLogic instance running. ecp_weblogic_resourceName 0 entry - Hostname of a machine with WebLogic and CloudBees Flow Agent running on it. Either Resource hostname (and port) or Resource Name should be specified. + Hostname of a machine with WebLogic and CloudBees CD Agent running on it. Either Resource hostname (and port) or Resource Name should be specified. ecp_weblogic_hostname 0 entry - Port of CloudBees Flow agent running on the machine. Default is 7800. + Port of CloudBees CD agent running on the machine. Default is 7800. ecp_weblogic_resPort 0 entry @@ -9564,14 +9564,14 @@ By default, the JNDI name is the name of the Datasource. Applications that look - If specified, will be used to create CloudBees Flow environment. + If specified, will be used to create CloudBees CD environment. ecp_weblogic_envProjectName 0 entry - If specified, will be used to create CloudBees Flow environment. + If specified, will be used to create CloudBees CD environment. ecp_weblogic_envName 0 entry
    Resource NameName of the CloudBees Flow resource that represents the WebLogic environment that needs to be discovered.Name of the CloudBees CD resource that represents the WebLogic environment that needs to be discovered.
    Resource HostnameHostname of a machine with WebLogic and CloudBees Flow Agent running on it. Either Resource hostname (and port) or Resource Name should be specified.Hostname of a machine with WebLogic and CloudBees CD Agent running on it. Either Resource hostname (and port) or Resource Name should be specified.
    Resource PortPort of CloudBees Flow agent running on the machine. Default is 7800.Port of CloudBees CD agent running on the machine. Default is 7800.
    Environment NameIf specified, will be used to create CloudBees Flow environment.If specified, will be used to create CloudBees CD environment.