Axway Application Studio 1.0.1 release notes

Axway Application Studio is a rapid application-development environment for building web applications that implement business processes. It is also the application execution environment ultimately managed by information technology operations. In short, Application Studio is a Dev + Ops or DevOps environment.

Installing and upgrading

The Axway Application Studio Installation and Prerequisites Guide has information about installing and upgrading the product. See Related documentation for where to get it.

New features and enhancements

The following are new key features of Application Studio.

More databases supported

Support has been added for Oracle 11g Release 2 (11.2) and Axway Database 4.6.

Tomcat web server upgraded

The Apache Tomcat web server is upgraded from 6.0.37 to 7.0.52. In a new installation of Application Studio, Tomcat 7.0.52 is installed. If you upgrade from Application Studio 1.0 to 1.0.1, the following occurs:

Known issues

The following are known issues in this version.

Possible process image generation failure

If Application Studio is accessed by using a server alias configured in the local hosts file, the process image generation will fail. If this occurs, access the user interface with a URL in the following format:

https://<host>/appstudio/web/login

Where <host> is the fully qualified domain name or IP address of the computer running Application Studio.

Application Studio might not close on Windows

When running on Windows, executing the stop command might fail to stop Application Studio. If it is still running one minute after executing the stop command, close the command window that has the title "Start App Studio" at the top left. This stops Application Studio manually.

Changing system settings requires restarting cluster nodes

When Application Studio is running in a cluster of multiple nodes and you change system settings in the administrator user interface on one node, you must restart all nodes for the changes to become effective across the cluster. For example, you must restart all nodes if you click System Settings in the UI and change values of one or more fields under General Settings or Directory Manager Settings.

LDAP authentication

There are two possible issues with LDAP authentication when local and LDAP users have the same names. The following describes the issues and manual resolutions.

When a user tries to log on, Application Studio first attempts to authenticate the user against the local user store. If the user does not exist in the local store, Application Studio then authenticates against the LDAP directory.

There are two possible error conditions that can arise when an LDAP user and a local user have the same name:

  1. If the LDAP user has logged on at least once, neither the LDAP or local user can log on.
  2. If the LDAP user never has logged on, only the local user is able to log on.

When users cannot log on, the work-around is one of the following:

or

or

Related documentation

Refer to the Application Studio Help Center for information about installing, upgrading, getting started and using Application Studio. Product documentation also is available on Axway Sphere. The URLs are:

Application Studio Help Center

http://app-studio-help-center.squarespace.com/

You also can click Help Center in the user interface to access it.

Axway Sphere

https://support.axway.com/

Support services

The Axway Global Support team provides worldwide support 24/7. You can find support numbers by country on Axway Sphere at https://support.axway.com/. In addition, you can download the latest information from Axway Sphere relating to Application Studio including:

For information about Axway training services, go to www.axway.com.


Copyright © 2014 Axway. All rights reserved.