Endpoints Manager Hot

https://serenacentralphotos.s3.amazonaws.com/original/e5/28/98/em-2-1443457521.png
by Vitaliy Olexandrovych Tkachenko on September 28, 2015

It is not enough a kind of automatic control in the Application Repository of relations between Endpoint and corresponding applications (orchestrations) that use this endpoint. It would be good to see which applications require redeployment which use the endpoint that has been recently changed to redeploy them.

  • The idea occurred implementing the enhancement for the ENH249570. I've found that there are situations where users can be frustrated trying to identify which applications must be redeployed when the ednpoint which is in use by that application has been changed.
    As you know when an endpoint in the Application Repository has been changed all applications which use this endpoint must be redeployed to use its new setting. User is forced to either remember which applications use this endpoint or waste time later trying to undertand why that or that mechanism stopped working, investigating logs and determining missed applications. Or just redeploy everything just for a case - anyway it looks we definitely should have some automatic control which shows applications that must be redeployed after the corresponding endpoint change. Also good to have some "one click" way to redeploy all that is required when endpoint is changed.
    For example it can be something like red stars which shows applicaations that must be redeployed and "redeploy all" function allowing to redeploy all at once on the attached picture.

  • Please login to view any attachments.

  • What's frustrating for me as an admin is multiple users deploying workflows and dynamically creating endpoints that are incorrect for the environment. For example:

    https://localhost/gsoap/gsoap_ssl.dll?sbmadminservices72
    User was developing on a single-server environment. User is deploying into an environment that uses multiple servers

    http://myserver/gsoap/gsoap_ssl.dll?sbmadminservices72
    User is deploying into an environment that only allows secure (https)


    I would like to prevent a deployment from creating an endpoint on-the-fly. Alternatively, allow the endpoint to be created but in a "disabled" or unusable state where an Admin must verify the endpoint then enable it.
    Paul Thompson Commented by Paul Thompson October 10, 2015
    Top 50 Reviewer  -  

    What's frustrating for me as an admin is multiple users deploying workflows and dynamically creating endpoints that are incorrect for the environment. For example:

    https://localhost/gsoap/gsoap_ssl.dll?sbmadminservices72
    User was developing on a single-server environment. User is deploying into an environment that uses multiple servers

    http://myserver/gsoap/gsoap_ssl.dll?sbmadminservices72
    User is deploying into an environment that only allows secure (https)


    I would like to prevent a deployment from creating an endpoint on-the-fly. Alternatively, allow the endpoint to be created but in a "disabled" or unusable state where an Admin must verify the endpoint then enable it.

    Definitely a good enhancement suggestion Vitaliy
    Jackie  Gilmour Commented by Jackie Gilmour September 30, 2015
    Top 50 Reviewer  -  

    Definitely a good enhancement suggestion Vitaliy

     

Print