Nav

Anypoint Service Registry 4.0.0 Release Notes

Anypoint Service Registry has been rolled up into a new product called API Manager.
Visit API Manager’s documentation for the latest information.

October 3, 2013

MuleSoft is pleased to announce the latest release of Anypoint Service Registry, a multitenant service registry/repository and SOA governance tool. 

Document Revision History

October 3, 2013, v.1.0 initial publication.

New Features and Functionality

Version 4.0.0 of the Anypoint Service Registry agent introduces the following new features and upgraded functionality:

  • Service Auto-Discovery: You can now configure your Mule Studio applications to be automatically registered by the Anypoint agent to your Anypoint Service Registry account. 

  • Streamlined policy and environment management: The lists of policies and environments now have "In Use" indicators. Policies and environments that are currently in use can now be deleted, resulting in a "batch unapply" functionality. 

  • Improved Search functionality: The search tool in the web application now supports search by tags and taxonomies.

  • Support for additional endpoints: You can now associate VM and JMS endpoints with a service, and use the service virtualization lookup method of invocation on these endpoints. Note that out-of-the-box policies are only supported on HTTP endpoints.

  • Backward Compatibility: Older versions of the Anypoint Service Registry agent running on Mule ESB versions 3.3.2, 3.3.3, 3.4.0, and 3.4.1 will continue to work without any action on behalf of users.

Hardware and Software System Requirements

Please refer to the detailed setup instructions in the setup guide for ESB on-premise or the setup guide for CloudHub.

The Anypoint Service Registry application (https://anypoint.mulesoft.com) supports the following browsers:

  • Firefox (latest version)

  • Chrome (latest version)

  • IE 9 (10 is preferred)

Important Notes and Known Issues in this Release

JIRA Issue Workaround

STUDIO-3800

Validation error when creating a global element for service auto discovery if serviceName attribute contains spaces

Enter serviceName attribute without spaces, then edit the name via the registry console or API after registration.

HABITAT-1039

Studio throws an error when you specify a <sr:service> global element without referencing it via <sr:auto-register-as>.

Comment out any auto-register-as global element configurations in your applications while they are not referenced in any endpoints.

HABITAT-1037

When creating contract-based throttling or rate-limiting policy, contract expression is shown and editable.

Do not edit the contract expression in this window. Instead, set the contract expression only on the contract enforcement policy.

HABITAT-999

Search cannot find services and consumers if name contains "-".

Omit special characters in the search tool.

HABITAT-960

Analytics incorrectly reports http requests received via a browser.

Calling endpoints via Postman, for example, results in correct tracking.

HABITAT-247

Once SLA tiers are defined for a service, the registry does not permit contracts unless a tier is selected.

Service owner can delete existing tiers, allow the contract to be requested while no tiers are defined, and then reinstate the tiers after the contract request has been made. Any contracts that were based on the tiers before their deletion will not be affected.

HABITAT-333

The registry does not recognize endpoints of http proxies using inboundAddress and outboundAddress elements.

Define a proxy using the following method:

HABITAT-932

Dynamic lookup invokes outbound endpoints using factory defaults; no customization or override of the defaults is possible.

None at this time. However, note that all HTTP outbound endpoints will be invoked using the POST method (which is the default for the HTTP protocol) and that overriding with a GET method is not currently supported.

Fixed in this Release

View Fixed Issues

HABITAT-1067

When requesting a contract, if modal error message is displayed, then closing the modal does not remove the modal backgorund.

HABITAT-1066

Once agent is offline, it does not come online again, even if network connection is re established.

HABITAT-1064

On user profile, if email is removed, then user cannot login into ASR anymore.

HABITAT-1052

Contract Enforcement Policy accepts not allowed contract keys

HABITAT-1046

When stopping mule, the aypoint-plugin throws a NPE when is being stopped.

HABITAT-1044

Policy details pop-up does not include description

HABITAT-1041

We need to make configurable the max-age header

HABITAT-1036

When creating a consumer/service, validation messages are incorrect when "." is on the name.

HABITAT-1033

Change error when a wrong environment id is set in consumer version creation

HABITAT-1022

When creating duplicate consumer, system displays unfriendly/ not informative error.

HABITAT-997

Search is not finding services and consumers after updating name/description or summary fields

HABITAT-967

Environments should retrieve paging in order to make UI aligned with the rest of the pages

HABITAT-962

On Landing page, most consumed services displays incorrect message when there are services created.

HABITAT-947

Services disappear when there is a faulty search

HABITAT-946

There is no error message when trying to add a service owner/ technical contact/ business contact by pressing Add contact button without writing the name

HABITAT-945

After adding a service owner/ technical contact/ business contact to a service, it is not possible to add another one

HABITAT-944

Is not possible to add an endpoint with uppercase letters

HABITAT-938

When creating a new endpoint, environments are not always being displayed

HABITAT-933

On taxonomies, after adding a new one, success icon does not disappear.

HABITAT-926

Error message when typing a service or consumer name is not friendly

HABITAT-925

Once a consumer is registered, there is no way in the UI to edit the Summary

HABITAT-915

System does not allow any protocol to be used as endpoint.

HABITAT-908

Users Listing Filters are Inconsistent

HABITAT-907

Policy Listing Sort by Name is not Working

HABITAT-906

Refresh Users Page redirects to home

HABITAT-905

User Listing problem when 2 organization owners exists

HABITAT-904

Form Submit after hit enter on Add Endpoint during Service Edition

HABITAT-903

Wrong label when Maximum amount of request allowed is entered

HABITAT-902

When trying to delete an environment that is being used, no error message is displayed

HABITAT-901

Service rating is not shown after login with another user.

HABITAT-900

When the agent reconnects, it remains unstable, losing and reestablishing connection constantly

HABITAT-897

When removing a taxonomy, grid is incorrectly refreshed.

HABITAT-896

When removing owners on a service/consumer, grid is incorrectly refreshed.

HABITAT-894

On a service, endpoint list is not refreshed after removing two endpoints.

HABITAT-891

When varnish fails to authenticate there should be no reconnection strategy

HABITAT-889

Agent throws exception when closing mule

HABITAT-888

Logged user should not be able to see consumer key on a service if not org owner or consumer owner.

HABITAT-887

When using Dynamic Round Robin, router returns first result always, when inbound endpoint has no path.

HABITAT-885

When adding metadata to an endpoint, the info is persisted but it is not shown.

HABITAT-883

When a mule application using dynamic lookup requires endpoints with metadata, and none of the registered endpoints have that characteristic, the error message is unfriendly

HABITAT-880

When reloading any page, forbidden call to get environments is done.

HABITAT-876

When filtering a consumer using the search bar, the filter on the left does not appear.

HABITAT-875

When filtering a service using the search bar, the filter on the left does not appear.

HABITAT-874

When reloading analytics url, if top consumer info was displayed, then it is not displayed anymore.

HABITAT-873

When a varnish instance is degraded the agent cannot finish the handshake successfully

HABITAT-871

Changes when editing endpoint on a service cannot be saved.

HABITAT-863

Logged user should not be able to see consumer key on a service if not org owner or consumer owner.

HABITAT-853

When clicking on a policy to see its details, the specific name of the parameters for that policy is missing in its description

HABITAT-840

Invalid 409 Conflict when adding a taxonomy node

HABITAT-839

Endpoints are no longer tracked when the service registry is restarted with 3.4 agent plugin

HABITAT-831

On Studio, dynamic router strategies should be redefined to include Round Robin.

HABITAT-828

On Environments, grid is not correctly refreshed if environments are removed too fast.

HABITAT-827

On Policies, grid is not correctly refreshed if policies are removed too fast.

HABITAT-826

When filtering a user using the search bar, the filter on the left does not appear.

HABITAT-823

Consumer list when requesting a contract shows only up to ten consumers

HABITAT-821

On Login page, "Powered By Mule" icon should be displayed.

HABITAT-820

Error message when creating a duplicate user should not expose LDAP details.

HABITAT-813

When loading Policy details, loading icon should be displayed.

HABITAT-811

On IE 9, service reviews are not shown after creation.

HABITAT-810

On IE 9, after updating user profile settings, info is not refreshed.

HABITAT-805

When changing the environment of an endpoint, stats from one environment are shown on the other one.

HABITAT-796

Last seen online does not display the selected agent token data

HABITAT-782

Version review average is not refreshed for the selected version

HABITAT-766

Clicking on Service in Contracts grid redirects to the service details page without information of the service

HABITAT-747

On Service analytics, Top consumer info and consumer break down is not shown.

HABITAT-746

When attempting to delete a policy that is being used, load icon is shown forever.

HABITAT-745

When policy is applied/revoked to an endpoint, the characteristics are not displayed on the service page.

HABITAT-743

Update the policy templates API in order to provide more information about each configuration

HABITAT-736

When access token is revoked, modal window is not shown automatically.

HABITAT-735

Consumer environment is not refreshed after editing it.

HABITAT-734

When attempting to delete last owner of a consumer, load icon is shown forever.

HABITAT-730

When attempting to create a duplicate environment, spinner icon is shown forever, no error message.

HABITAT-728

When a service/consumer is modified, modified by information is not updated on service/consumer details.

HABITAT-722

Service rating average is not shown.

HABITAT-710

On taxonomies there is a hard limit of 10 results when there should be no limit.

HABITAT-706

Policy configuration values are not displayed correctly

HABITAT-702

New policy - Error causes all field entered to be set to blank

HABITAT-673

API does not validate metadata key and value limits, neither the data types

HABITAT-668

API allows to create service/consumer versions using negative numbers

HABITAT-624

Services/Consumers validations for description fields are incorrect.

HABITAT-616

When adding an endpoint, the port number is not validated

HABITAT-589

Policies templates have double vertical scroll.

HABITAT-476

On Consumer breakdown, labels can be overlapped on the pie chart when rendered.

HABITAT-355

State of applied policies at endpoint level is not always shown correctly.

HABITAT-345

Endpoint shows as Tracked even when all tokens invalidated

HABITAT-323

When creating an IP blacklist/white list policy, there is no check if an actual IP address/range was included on it.

HABITAT-269

After defining second level taxon, clicking on it n times, open n edit level windows.

Migration Guide

If you have services registered on Anypoint Service Registry with an agent versions 117, 119, or 2.11.1 and migrate to the CloudHub Mule Runtime (October 2013) with the 4.0.0 Anypoint Service Registry agent, please be aware that within the element <service-lookup>, the attribute serviceName has changed to serviceId. Please update your consumer applications that are performing dynamic lookup and replace any instances of serviceName with serviceId.

In addition, the attribute serviceRoundRobin has been removed and replaced with a new element: <dynamic-round-robin>. Please update your consumer applications that were performing dynamic lookup to delete any references to the deprecated attribute. To enable round robin routing strategy, use the new <`dynamic-round-robin`> element instead.

Support Resources

Please refer to the following resources for assistance using Anypoint Service Registry.

Documentation

Refer to the documentation for instructions on how to use Anypoint Service Registry.

Anypoint Service Registry is now known as API Manager.

Getting Help

To access MuleSoft’s expert support team, log in to the http://www.mulesoft.com/support-login[Customer Portal].

Sending Feedback

Send MuleSoft feedback about Anypoint Service Registry by clicking the Send Feedback link in the lower right corner of any screen in the application.