Duong_Nguyen-Nhat_2335

ARA is not available when configure to work with both http and https

Discussion created by Duong_Nguyen-Nhat_2335 on Sep 13, 2016
Symptom:

If we want to use both http and https in ARA, so we have to configure Release Automation work with both http mode and https mode
See the connection.properties file. Example:
url=http://localhost/rm_main url=https://ara-test.dzbank.vrnet
url=https://ara-test.dzbank.vrnet
timeout=60000 package_folder=/PACKAGES search_page_size=10
and after the configuration, The Release Automation perspective is not available.

In the ECC log file we found the following:
2016-06-16 11:23:30,828 http-bio-8443-exec-13  [ERROR] AUTOMIC:100/XN07119/AUTOMIC 0 0000000001094006  [controls.messageprovider.MessageProvider] - Loading failed.
com.uc4.bond.api.errorhandling.BondApiException: Error in asynchronous call.
at com.uc4.bond.api.errorhandling.BondCheckedFuture.mapException(BondCheckedFuture.java:30) ~[na:na]     at com.uc4.bond.api.errorhandling.BondCheckedFuture.get(BondCheckedFuture.java:18) ~[na:na]     at com.uc4.ecc.plugins.bond.extensions.user.sheets.permission.PermissionSheetPresenter$2.loadWithNullAsDefault(PermissionSheetPresenter.java:162) ~[na:na]     at com.uc4.ecc.plugins.bond.extensions.user.sheets.permission.PermissionSheetPresenter$2.loadWithNullAsDefault(PermissionSheetPresenter.java:146) ~[na:na]     at com.uc4.webui.common.async.NullAsDefaultLoader.load(NullAsDefaultLoader.java:10) ~[na:na]
    at com.uc4.webui.common.async.NullAsDefaultLoader.load(NullAsDefaultLoader.java:6) ~[na:na]     at com.uc4.ecc.framework.core.async.BaseRequestCoordinator$1$1.call(BaseRequestCoordinator.java:214) ~[na:na]     at com.uc4.ecc.framework.core.pool.ContextAwareExecutorService$CallableImplementation.call(ContextAwareExecutorService.java:72) ~[na:na]     at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_60]     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_60]     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_60]     at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_60]

Solution:

Don't comment any endpoints of services in web.config file.

The configuration should be as below:

<services> <service behaviorConfiguration="Ventum.Bond2.Web.Service.DeploymentServiceBehavior" name="Ventum.Bond2.Web.Service.DeploymentService"> <endpoint address="" binding="basicHttpBinding" contract="Ventum.Bond2.Services.Deployments.IDeploymentService" bindingConfiguration="DeploymentServiceBinding">
<identity> <dns value="localhost"/> </identity> </endpoint> <endpoint address="" binding="basicHttpBinding" contract="Ventum.Bond2.Services.Deployments.IDeploymentService" bindingConfiguration="DeploymentServiceBindingNoSec"> <identity> <dns value="localhost" /> </identity> </endpoint> <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" /> </service>
<service behaviorConfiguration="Ventum.Bond2.Web.Service.IntegrationServiceBehavior" name="Ventum.Bond2.Web.Service.IntegrationService"> <endpoint address="" binding="basicHttpBinding" contract="Ventum.Bond2.Services.Integrations.IIntegrationService" bindingConfiguration="DeploymentServiceBinding"> <identity> <dns value="localhost"/> </identity> </endpoint> <endpoint address="" binding="basicHttpBinding" contract="Ventum.Bond2.Services.Integrations.IIntegrationService" bindingConfiguration="DeploymentServiceBindingNoSec"> <identity> <dns value="localhost" /> </identity> </endpoint> <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" /> </service> </services>

Outcomes