AppScan Source for Development (plug-in for Eclipse, IBM MobileFirst Platform, and Rational Application Developer for WebSphere Software (RAD))

If you are installing the AppScan® Source for Development plug-in for Eclipse, Rational® Application Developer for WebSphere® Software (RAD), or IBM® MobileFirst Platform, you will need to apply the plug-ins to your workbench after installing them to your computer.

The application of the AppScan Source for Development Eclipse plug-in depends on the application of some Eclipse tools (the Graphical Editing Framework (GEF) and Draw2d). Most versions of Eclipse that are supported by AppScan Source for Development include these features. If yours does not, install these components into your Eclipse environment using the appropriate eclipse.org update site before installing AppScan Source for Development. Failure to do this may result in errors while applying the AppScan Source for Development plug-in to Eclipse.

If you are upgrading the AppScan Source product to a new product version and want to apply the upgrade to theAppScan Source for Development Eclipse plug-ins, you must first uninstall the plug-ins from your Eclipse or Eclipse-based product. After you have upgraded AppScan Source, you can then install the updated plug-ins back to Eclipse or supported Eclipse-based products. Instructions for this are located in Upgrading previously-installed versions of the AppScan Source for Development Eclipse plug-in to a new product version.

If you are upgrading the AppScan Source product as part of a fix pack upgrade, you do not need to uninstall the plug-ins before upgrading. Instructions for installing fix packs (and applying upgraded AppScan Source for Development plug-ins) can be found in Fix pack installation.

Note:

Attempts to run some actions in AppScan Source for Development (Eclipse plug-in) (for example, launching a scan or starting actions that require a login) can result in this error message (or one that is similar to it):

Unable to link native library shared-win32-x64.dll. 
You may need to install an appropriate Microsoft Visual C++ 
2017 x86 Redistributable Package for your system.

When running on a 64-bit Java™ Runtime Environment, this typically indicates that the 64-bit Microsoft™ Visual C++ runtime library is unavailable. To resolve this problem, install the Microsoft Visual C++ Redistributable Package appropriate to your Visual Studio version, available here.