Automic Continuous Delivery Automation

  • Private Community

  • 1.  The Release Automation perspective is not available when login to ECC

    Posted Sep 05, 2016 12:40 AM
    Symptoms:

    The Release Automation perspective is not available when login to ECC.

    2016-08-05 06:57:30,084 pool-2-thread-94       [ERROR] AUTOMIC:100/AUTOMIC/AUTOMIC 0 0000000001006622 +313 [entrypoint.navigation.PluginInstantiator] - Failed to start plugin instance 'com.uc4.ecc.plugins.bond.entrypoint.BondPluginInstance@77123dfb' com.uc4.ecc.plugins.bond.exception.BondNotAvaiableException: Check failed. cannot create sso token SSO Endpoint is not found in Deployment Manager.     at com.uc4.ecc.plugins.bond.entrypoint.BondPluginInstance.checkBondAvailability(BondPluginInstance.java:69) ~[na:na]     at com.uc4.ecc.plugins.bond.entrypoint.BondPluginInstance.start(BondPluginInstance.java:44) ~[na:na]     at com.uc4.ecc.framework.entrypoint.navigation.PluginInstantiator.startPluginInstances(PluginInstantiator.java:145) [ecc-framework-entrypoint.jar:na] ... Caused by: com.uc4.ecc.plugins.bond.exception.SsoException: SSO Endpoint is not found in Deployment Manager.     at com.uc4.ecc.plugins.bond.backend.sso.BondSsoService.createToken(BondSsoService.java:87) ~[na:na]     at com.uc4.ecc.plugins.bond.entrypoint.BondPluginInstance.checkBondAvailability(BondPluginInstance.java:60) ~[na:na]
    Cause:

    ARA_URL is not correct in connection.properties config file.  

    Solution:

    Correct ARA_URL in connection.properties file
    Example: url=http://localhost/rm_main


  • 2.  The Release Automation perspective is not available when login to ECC

    Posted Sep 08, 2016 03:51 AM
    Another reason that can caused the Release Automation perspective is not shown in ARA is the login user does not exist in ARA database.  We can easily identify this by check the ECC logs:

    Caused by: java.lang.Throwable: Deployment Manager error: User 100/API1/API does not exist or inactive
        ... 15 common frames omitted
    We can also check if the login user is exist in our ARA Database by using ImportExportCLI.exe
    The command to export an User:

    C:\Automic\Tools\ARA\Utilities\ImportExportCLI>ImportExportCLI.exe EXPORT export -con http://vvnsatara04/ARA -usr AUTOMIC/100/AUTOMIC/AUTOMIC -pwd automic -mt user -format xml -fi C:\exportUser.xml -where "system_name eq '100/API1/API'"
    So to move forward with this issue, you should use an existing login user to login ARA or create a new one.


  • 3.  The Release Automation perspective is not available when login to ECC

    Posted Sep 11, 2016 11:12 PM
    In my previous Post I already pointed out there are 02 reasons (ARA_URL is not correct in connection.properties config file or  the login user does not exist in ARA database) which can cause the Release Automation perspective is not available when login to ECC.

    I just found out another reason can cause this issue: The ARA Deployment Service is not available.

    Symptom: 

    When you check the deployment Service: http://vvnsatara04/ARA/service/DeploymentService.svc

    You will see that the Service is not available.

    a6ng8ab31wef.pnghttps://us.v-cdn.net/5019921/uploads/editor/pn/a6ng8ab31wef.png" width="1600">
    Cause:

    Some endpoint in web.config is not correct.

    Solution:

    we need to comment 2 Endpoints in web.config file like as:
    <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>



  • 4.  The Release Automation perspective is not available when login to ECC

    Posted Nov 09, 2016 05:40 AM
    In the previous post, I already listed 03 reason that caused Release Manager tab is not available on ECC: 

    1. ARA_URL is not correct in connection.properties config file
    2. The login user does not exist in ARA database
    3. The ARA Deployment Service is not available.

    Today, I just found out another reason can cause this issue: When you install ARA, please using the ECC and the webui-plugin-bond from the same service pack, because different version of ECC or webui-plugin-bond can caused the conflict that lead to the ARA perspective is not available in ARA. 

    Please also don't copy and paste the uc4config.xml (ECC) and connection.properties (webui-plugin-bond) from the old install to the new one. Please manually config it.

    The strange thing about this issue that you can't find any error/ java exception from the Ecc log.

    Hope this help.


  • 5.  The Release Automation perspective is not available when login to ECC

    Posted Apr 18, 2017 01:17 PM
    Hi

    Duong Nguyen Nhat

    , 
    To clarify the solution you provided in the September 2016 comment, that's specifically for HTTP only, right?  
    Not for https configuration.
    Thanks!



  • 6.  The Release Automation perspective is not available when login to ECC

    Posted Apr 21, 2017 02:44 AM
    Harriet_Kim_1764
    In general, yes, we have to make sure that the ARA is running fine with http before we go for the https setting.



  • 7.  The Release Automation perspective is not available when login to ECC

    Posted Apr 24, 2017 11:09 AM
      |   view attached
    I have attached a Word document, which lists possible troubleshooting steps to try that may help arrive to the solution.

    In my case, the solution ended up being:
    In IIS, navigate to your ARA site (globe icon) > in the middle window pane, click on SSL settings > in the right window pane, click on Open Feature > click on "Require SSL" > leave Client Certificates as "Ignore" 

    Note: Solutions may vary depending on the user's settings.  In my case, the user was using https setting for ARA.

    Attachment(s)

    docx
    Checklist_MissingARA_Perspective.docx   246 KB 1 version


  • 8.  The Release Automation perspective is not available when login to ECC

    Posted Apr 24, 2017 06:00 PM
    Note that the ARA site does not have to be under "Default Web Site". This can be outside of this, depending on how ARA was setup.

    I had a case where the issue turned out to be a simple one - the ARA site is not started in IIS.

    Another case was ARA site can't be started because port 80 is in use.
    Running netstat -anb | findstr :80 showed that it is being used by the same server and it turned out to be "Default web site" (ARA site on this setup is outside "Default web site"). 

    We ended up stopping "Default web site" to release port 80. 
    Another option would be to change the port ARA is using if stopping "Default web site" is not acceptable.