FranciscoLeiria Trusted Contributor.
Trusted Contributor.
632 views

Dinamically Launch Flow - Exception

Jump to solution

Hello Folks

I am not able to "Dinamically Launch Flow" I am getting the below error message on Central. The flow I am trying to run is a test flow with a "sleep" operation and no inputs. Also tried with "Display Message" with the two inputs separated by comma, and the same error.

I am using OO 10.60 and
Base 1.11.0
HPE Solutions 1.13.0

I am trying with the admin account and no luck.

Any clue?

2018-08-06 18:37:51,693 [1_WorkerExecutionThread-17_1303433204] (PluginAdapterImpl.java:331) ERROR - com.hp.oo.content.oo.utils.http.HttpResponseException: <html>
<head>
<title>HPE Operations Orchestration</title>
<meta http-equiv="REFRESH" content="0;url=/oo">
</head>
<body>
You are about to be redirected to HPE Operations Orchestration web application
</body>
</html>
at com.hp.oo.PlatformVersionService.getPlatformVersion(PlatformVersionService.java:50)
at com.hp.oo.content.oo.services.impl.ExecutionServiceImpl.dynamicallyLaunchFlow(ExecutionServiceImpl.java:167)
at com.hp.oo.content.oo.actions.general.DynamicallyLaunchFlow.dynamicallyLaunchFlow(DynamicallyLaunchFlow.java:102)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at com.hp.oo.sdk.plugins.abstracts.BaseActionPlugin.execute(BaseActionPlugin.java:53)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at com.hp.oo.maven.PluginAdapterImpl.executePlugin(PluginAdapterImpl.java:328)
at com.hp.oo.maven.PluginAdapterImpl.execute(PluginAdapterImpl.java:248)
at com.hp.oo.execution.control.actions.contentexecution.ContentExecutionActions.executeContentAction(ContentExecutionActions.java:97)
at sun.reflect.GeneratedMethodAccessor689.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at io.cloudslang.worker.execution.reflection.ReflectionAdapterImpl.executeControlAction(ReflectionAdapterImpl.java:62)
at io.cloudslang.worker.execution.services.ExecutionServiceImpl.executeStep(ExecutionServiceImpl.java:326)
at io.cloudslang.worker.execution.services.ExecutionServiceImpl.execute(ExecutionServiceImpl.java:80)
at io.cloudslang.worker.management.services.SimpleExecutionRunnable.executeRegularStep(SimpleExecutionRunnable.java:167)
at io.cloudslang.worker.management.services.SimpleExecutionRunnable.run(SimpleExecutionRunnable.java:120)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at io.cloudslang.worker.management.services.WorkerThreadFactory$1.run(WorkerThreadFactory.java:33)
at java.lang.Thread.run(Thread.java:745)
<html>
<head>
<title>HPE Operations Orchestration</title>
<meta http-equiv="REFRESH" content="0;url=/oo">
</head>
<body>
You are about to be redirected to HPE Operations Orchestration web application
</body>
</html>

0 Likes
1 Solution

Accepted Solutions
Outstanding Contributor.. JarodMB Outstanding Contributor..
Outstanding Contributor..

Re: Dinamically Launch Flow - Exception

Jump to solution

Have you tried without the /oo appended ?

8 Replies
FranciscoLeiria Trusted Contributor.
Trusted Contributor.

Re: Dinamically Launch Flow - Exception

Jump to solution

UPDATE:

Removed all inputs but Central url, even usr/pass or flow UUID and getting the same result. Any clue?

0 Likes
AndreiTruta Outstanding Contributor.
Outstanding Contributor.

Re: Dinamically Launch Flow - Exception

Jump to solution

how did you provide the Central related inputs?

Andrei Vasile Truta
FranciscoLeiria Trusted Contributor.
Trusted Contributor.

Re: Dinamically Launch Flow - Exception

Jump to solution

Andrei

Thanks for your response.

centralServer: oo-dev.xxx.yyy.hpe.com
centralUsername: admin
centralPassword: ********
centralProtocol: https
centralPort: 443
authType: basic

If I include "https://" I get " For input string: "//oo-dev.xxx.yyy.hpe.com/oo " as the error message.

Tried with domain credentials (domain\user), incorrect credentials, and no credentials at all with the same result.

Thank you,

 

 

0 Likes
Outstanding Contributor.. JarodMB Outstanding Contributor..
Outstanding Contributor..

Re: Dinamically Launch Flow - Exception

Jump to solution

Are you traversing a load balancer?
Can you try to hit central directly...

CP: Micro Focus Solutions 2.0.1

My configuration:
centralServer : host.xyz.com
centralUsername: my domain acct
centralPassword: my domain pwd
centralFlowPath: UUID of flow
socketTimeout: 0
logLevel: Extended
authType: basic
runName: test
centralProtocol: https
centralPort: 8443
trustAllRoots: true


0 Likes
FranciscoLeiria Trusted Contributor.
Trusted Contributor.

Re: Dinamically Launch Flow - Exception

Jump to solution

Thanks for your response

Yes, is a cluster of two nodes behind an F5 so I tried:

localhost/oo
{VIP-FQDN}/oo
(VIP-IP}/oo
{node1-FQDN}/oo
{node1-IP}/oo

I am reaching central everytime, but always with the same result, below
(I am using the same inputs as your example, the only difference is the port, 443 instead of 8443)

Also tried in two environments (10.60 and 10.80),  HPESolutions 1.13.0 and Microfocus Solutions 2.0.1

exception=com.hp.oo.content.oo.utils.http.HttpResponseException: <html>
<head>
<title>HPE Operations Orchestration</title>
<meta http-equiv="REFRESH" content="0;url=/oo">
</head>
<body>
You are about to be redirected to HPE Operations Orchestration web application
</body>
</html>
at com.hp.oo.PlatformVersionService.getPlatformVersion(PlatformVersionService.java:50)
at com.hp.oo.content.oo.services.impl.ExecutionServiceImpl.dynamicallyLaunchFlow(ExecutionServiceImpl.java:167)
at com.hp.oo.content.oo.actions.general.DynamicallyLaunchFlow.dynamicallyLaunchFlow(DynamicallyLaunchFlow.java:102)
at sun.reflect.GeneratedMethodAccessor3469.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at com.hp.oo.sdk.plugins.abstracts.BaseActionPlugin.execute(BaseActionPlugin.java:53)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at com.hp.oo.maven.PluginAdapterImpl.executePlugin(PluginAdapterImpl.java:328)
at com.hp.oo.maven.PluginAdapterImpl.execute(PluginAdapterImpl.java:248)
at com.hp.oo.execution.control.actions.contentexecution.ContentExecutionActions.executeContentAction(ContentExecutionActions.java:97)
at sun.reflect.GeneratedMethodAccessor774.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at io.cloudslang.worker.execution.reflection.ReflectionAdapterImpl.executeControlAction(ReflectionAdapterImpl.java:62)
at io.cloudslang.worker.execution.services.ExecutionServiceImpl.executeStep(ExecutionServiceImpl.java:326)
at io.cloudslang.worker.execution.services.ExecutionServiceImpl.execute(ExecutionServiceImpl.java:80)
at io.cloudslang.worker.management.services.SimpleExecutionRunnable.executeRegularStep(SimpleExecutionRunnable.java:167)
at io.cloudslang.worker.management.services.SimpleExecutionRunnable.run(SimpleExecutionRunnable.java:120)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at io.cloudslang.worker.management.services.WorkerThreadFactory$1.run(WorkerThreadFactory.java:33)
at java.lang.Thread.run(Thread.java:745)
;returnCode=-1;returnResult=<html>
<head>
<title>HPE Operations Orchestration</title>
<meta http-equiv="REFRESH" content="0;url=/oo">
</head>
<body>
You are about to be redirected to HPE Operations Orchestration web application
</body>
</html>;Result=<html>
<head>
<title>HPE Operations Orchestration</title>
<meta http-equiv="REFRESH" content="0;url=/oo">
</head>
<body>
You are about to be redirected to HPE Operations Orchestration web application
</body>
</html>;}

0 Likes
Outstanding Contributor.. JarodMB Outstanding Contributor..
Outstanding Contributor..

Re: Dinamically Launch Flow - Exception

Jump to solution

Have you tried without the /oo appended ?

FranciscoLeiria Trusted Contributor.
Trusted Contributor.

Re: Dinamically Launch Flow - Exception

Jump to solution

Seems that this did the trick!

I removed the "/oo" and was able to get to the rest of the inputs.

Also I tried back with the F5 VIP and is also resolving correctly.

Thank you guys!

So much appreciate it!

 

Francisco

0 Likes
AndreiTruta Outstanding Contributor.
Outstanding Contributor.

Re: Dinamically Launch Flow - Exception

Jump to solution

Great. That is exactly how it should be done. one of the reasons the operation asks about port and protocol is that it constructs the URL itself thus you only need to supply FQDN/IP to the actual Central/LB server.

 

Andrei Vasile Truta
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.