Application Development Plug-in Messages

JmxServiceConnectError Designer was unable to physicaly connect to the server over JMX on port {0}. Verify that the Server view's JMX port configuration matches the port configuration for the server. Verify the server is started and listening for socket connections on this port.
Explanation

Application Platform uses a JMX service to communicate with a server at design time.

Action

Verify that the Server view's JMX port configuration matches the port configuration for the server. Verify the server is started and listening for socket connections on this port.


JmxServiceNoInstanceError Designer is connected to the server over JMX as required. However, the Application Platform remote service is unavailable. Verify that the 'Application Platform Support' component is installed for this server.
Explanation

Application Platform uses a JMX service to communicate with the server on port {0}. Server connection is established but the service is not available.

Action

Verify that the 'Application Platform Support' component is installed for each server.


JmxServiceServerError An error occurred while executing an Application Platform Designer remote JMX service on the server.
Explanation

Application Platform uses a JMX service to communicate with the server. An exception occurred on the server side while executing a task.

Action

Review the logs and try to determine the source of this server-side error.


PLDBBCE0000 Unable to establish a JMX connection to the {0} server over port {1}. Cause: {2}
Explanation

Designer failed to establish a JMX to the remote development server.

Action

Verify that the server is started and that the installed PLS bundle deploy service bundle is active.


PLDBBCE0001 Unable to access the bundle publisher service.
Explanation

The Dependency Manager was unable to access the publisher service when the remote server was started. The dependency manager needs the publisher service in order to obtain the list of deployed bundles in the server's OSGi container.

Action

Restart Designer and verify that the PLD bundle deploy client bundle is active.


PLDBBCE0002 Unable to access the Dependency Manager service.
Explanation

The Dependency Manager service is contributed to the OSGi service registry but it is not registered to it.

Action

Restart Designer and verify that the PLD bundle builder core bundle is active.


PLDBBUE0000 An error occurred while resolving the list of libraries in the Application Platform common classpath container for project: {0}. Cause: {1}
Explanation

The list of libraries that are automatically created by Application Platform for the project cannot be resolved. One or more libraries, provided by Application Platform, must be present for projects with Application Platform project facets.

Action

Remove the Application Platform core project facet from the project and add it again. Verify that the Application Platform bundles exist in the target installation path under 'common/runtime/bundles/pls-core/eclipse/plugins' and 'common/runtime/bundles/applatform/eclipse/plugins'. If these directories do not exist, verify that all of the Application Platform components were selected during installation.


PLDBBUE0001 An error occurred while initializing the Application Platform classpath container for project {0}. Cause: {1}
Explanation

Designer could not initialize the classpath container for the existing project during the workspace initialization. The error is isolated to the initializer of this container.

Action

Remove the Application Platform core project facet from the project and add it again. Verify that the Application Platform bundles exist in the target installation path under 'common/runtime/bundles/pls-core/eclipse/plugins' and 'common/runtime/bundles/applatform/eclipse/plugins'. If these directories do not exist, verify that all of the Application Platform components were selected during installation.


PLDBBUE0002 Unable to locate the WebContent folder for project {0}
Explanation

The builder could not locate the project folder meant to store content in the root folder of the archive. The default location for Eclipse is 'WebContent'.

Action

Verify that the project folder structure is valid for a Dynamic Web project.


PLDBMGE0000 An exception occurred while reloading the Bundle Manager view. Cause: {0}
Explanation

Designer could not reload the Bundle Manager view. Reloading the Bundle Manager view involves the following sources: a selected project, a connected server, and a configured set of directories.

Action

Determine the source where the error occurred (directory, project or server).


PLDBMGE0001 An exception was produced while accessing the Dependency Manager Service.
Explanation

Designer could not access the Dependency Manager Service. The Dependency Manager Service is an OSGi service. Aplication Platform uses this service for verifying bundles and their relationships to other bundles.

Action

Restart Designer and try again. If the error persists, contact Software AG Global Support.


PLDBMGE0002 An exception was produced while accessing the Bundle Manager Service.
Explanation

Designer could not access the Bundle Manager Service. The Bundle Manager Service is an OSGi service used by the Application Platform Bundle Manager View.

Action

Restart Designer and try again. If the error persists, contact Software AG Global Support.


PLDBMGE0003 An error occurred while restoring the Bundle Manager to its default settings. Cause: {0}
Explanation

An error occurred while resetting the Bundle Manager to its default values. The configuration settings of the Bundle Manager are stored by the Eclipse preferences API.

Action

Check the details of the exception and try to resolve the problem.


PLDBMGE0005 Error opening Bundle Manager configuration settings dialog. Cause: {0}
Explanation

The Bundle Manager configuration settings dialog failed to open. The configuration settings dialog contains configuration settings that impact the Bundle Manager view.

Action

Restart Designer and try again. Try to access the Bundle Manager configuration settings dialog from the Windows/Preferences/SoftwareAG/Bundle Manager menu path.


PLDBMGE0006 Invalid number format for the App Platform server configuration key: {0}. Value: {1}
Explanation

The server configuration property received an invalid value. A numeric value is required for the App Platform server configuration key.

Action

Verify that the server configuration value is non-null and that it is numeric.


PLDBMGE0007 Bundle Manager encountered an error while publishing bundle {0} into the server's repository. Cause: {1}
Explanation

The Bundle Manager could not publish the selected bundle to the server's bundle repository. The bundle must be published to the repository before it can be installed to the server's OSGi container. For this purpose, the bundle is first copied to a staging directory. Designer transfers the bundle to this directory by using a JMX interface via the port number, configured in the WST server

Action

Review the contents of the staging directory under the server's installation directory, for example: profiles/IS_default/workspace/temp/app-platform/deployer/bundles/. Verify that the configuration of the WST server is correct and that the server is started and it is listening on the JMX port.


PLDBMGE0008 Bundle Manager encountered an error while installing bundle {0} to the server's OSGi container. Cause: {1}
Explanation

The Bundle Manager failed to install the bundle to the server's OSGi container.

Action

Verify that the bundle was copied from the staging directory to the repository directory under the installation directory, for example: profiles/IS_default/workspace/app-platform/deployer/bundles/. If required bundles or imported packages are missing, review the OSGi dependencies to ensure that all required dependencies are met.


PLDBMGE0009 Bundle Manager encountered an error while unpublishing the bundle {0} from the server's repository. Cause: {1}
Explanation

The Bundle Manager failed to unpublish the bundle from the server's repository. The bundle can be unpublished from the server's repository after it is uninstalled from the OSGi container.

Action

Verify that the bundle was successfully removed from the repository directory under the installation folder, for example: profiles/IS_default/workspace/app-platform/deployer/bundles/. If the bundle is still in the directory, delete it manually by removing the file from this directory and restarting the server.


PLDBMGE0010 Bundle Manager encountered an error while removing bundle {0} from the server's OSGi container. Cause: {1}
Explanation

The Bundle Manager failed to uninstall the bundle from the server's OSGi container. The bundle must be uninstalled from the OSGi container before it can be unpublished from the p2 repository.

Action

Verify that the bundle was successfully removed from the repository directory under the installation folder, for example: profiles/IS_default/workspace/app-platform/deployer/bundles/. If the bundle is still in the directory, delete it manually by removing the file from this directory and restarting the server.


PLDBMGE0011 The Bundle Manager encountered an unexpected error while executing the update server task. Cause: {0}
Explanation

The Bundle Manager failed to update the server. The Bundle Manager runs an update server task when a server is started or bundle changes are committed.

Action

Review the contents of the staging directory under the server's installation directory. Verify that the configuration of the WST server is correct and that the server is started and it is listening on the JMX port. If you have uninstalled bundles from the server, verify that they bundle were successfully removed from the repository directory under the installation folder. If one or more bundles are still in the directory, delete it manually by removing the file from this directory and restarting the server.


PLDBMGE0012 An Application Platform server must be configured and started for this operation.
Explanation

This Application Platform operation in Designer requires access to a server instance. A server configuration must be created and successfully started.

Action

From the Servers view create an Application Platform server and start it.


PLDBMGE0015 Error creating wrapper bundle. Cause: {0}
Explanation

An unexpected error occurred while creating a wrapper bundle for the set of jars.

Action

Verify that the jar files and the bundle manifest are valid. If they are valid and the error persists, contact Software AG Global Support.


PLDBMGE0017 An error occurred while creating a wrapper bundle. Cause: {0}
Explanation

The Bundle Manager view failed to create a wrapper bundle for the given plain jar(s).

Action

Verify that the jars to be included in the wrapper jar are valid Java archives. Review the generated OSGi manifest entry in the jar (META-INF/MANIFEST.MF) and verify that the target directory, where the bundle is to be created, exists and has appropriate file permissions for the current user.


PLDBMGE0019 Error removing wrapper bundle. Cause: {0}
Explanation

An unexpected error occurred while removing one or more wrapper bundles.

Action

Verify that the associated jar files exist and that they are not opened in another application.


PLDBMGE0021 File {0} was not installed on the server. The file is not a bundle.
Explanation

The file you attempted for publishing to the server is not an OSGi bundle. Designer can only publish OSGi bundlers to the product server.

Action

Review the file contents and publish only OSGi bundles to the server.


PLDBMGE0022 Unable to validate project {0}'s bundle file before attempting to publish or unpublish.
Explanation

The file could not be validated by Designer. Designer needs a valid project archive file with OSGi bundle headers before it can perform publisher-related operations against a server.

Action

Rebuild the project to ensure its contents are up to date.


PLDBMGI0020 The server must be started before bundles can be removed. The server is used to confirm they the bundles are not installed.
Explanation

You cannot remove bundles when the server is started. Published bundles cannot be removed, so the server must first confirm that the selected bundles for removal are not installed.

Action

Start the Application Platform server in Designer and select unpublished bundles for removal.


PLDBMGW0014 Clear the text filter to ensure that all bundles or jars are included in this action.
Explanation

The filter cannot be cleared programmatically before the selected task is runned because the task is running on the same UI thread.

Action

Clear the text box and repeat the operation.


PLDCDGE0000 Unknown data type from DataKey annotation for field {0}; type: {1}
Explanation

The DataKey annotation is incorrect. The DataKey annotation identifies an element to be used in IS service signature. These signatures support only a limited set of data types. The data type of the field identified here is not supported.

Action

Update the DataKey annotation to use a supported data type.


PLDCDGE0001 Unable to create POJO wrappers for IS node: {0}
Explanation

The node is not recognized by the IS server as a defined service or a shared doctype or specification reference.

Action

Make sure that the selected node is valid on the selected IS server.


PLDCDGE0002 Unexpected Integration Server node-type {0} for node {1}, expecting {2}
Explanation

An unexpected node-type was found in the Integration Server node that was retrieved. This may be caused by an incorrect node name.

Action

Correct the Integration Server node name.


PLDCDGE0003 Unable to retrieve Integration Server {0} description for node {1}; caught: {2}
Explanation

Retrieving the service or record details for the given Integration Server node was unsuccessful. This error may result from improper configuration either in the IS server identification, or in the IS service.

Action

Check the error logs for more details about this error.


PLDCDGE0004 Unexpected signature node type: {0}; field is {1}, generating bean: {2}.{3}
Explanation

The field-type used when generating a Java source for the IS service signature was not recognized. This may occur because of an unsupported IS serice configuration.

Action

Contact Software AG Global Support.


PLDCDGE0005 Cannot use a connection that is null or disconnected: {0}
Explanation

Failed to connect to Integration Server. Application Platform attempted to generate a code for an IS service but the connection is not working.

Action

Verify that the connection to Integration Server is working. If the error persists with a working connection, contact Software AG Global Support.


PLDCDGE0006 Unable to retrieve Integration Server {0} description for package {1}; caught: {2}
Explanation

Retrieving the details for the given Integration Server package was unsuccessful. This error may result from improper configuration either in the IS server identification, or in the IS package.

Action

Check the error logs for more details about this error.


PLDCFTE0000 An error occurred while creating Application Platform project facets in the project template. Cause: {0}
Explanation

The creation of Application Platform project facets failed. Designer uses a template of Eclipse project facets when creating a service project. The Application Platform server uses these facets to determine if it can publish a project's module.

Action

Verify that all of the Application Platform components were installed in Designer.


PLDCFTE0001 An error occurred in the Application Platform service project wizard while creating a project. Cause: {0}
Explanation

The Application Platform service project wizard failed to create a project. The service project wizard creates a Designer project and performs tasks for each of the selected project facets.

Action

Review the error and verify that the project facet selections are valid.


PLDCSPE0001 An error occurred while unpublishing a project resource from the server, configured for Application Platform.
Explanation

An unexpected error occurred while unpublishing a project resource to the configured server.

Action

Verify that the project is still deployed on the server, that the server configuration is complete, and that the server can be started successfully.


PLDCSPE0003 An error occurred while publishing a project resource to the Application Platform server.
Explanation

An unexpected error occurred while publishing a project resource to the configured server.

Action

Verify that the project contents are valid, that the server configuration is complete, and that the server can be started successfully.


PLDCSPE0004 Designer was unable to confirm the server's status during startup/shutdown. Details: {0}
Explanation

The configured Application Plaform server uses a polling ping approach to confirm if the remote server was successfully started or stopped. An error occurred during the ping operation and the status of the server could not be confirmed.

Action

If you are running the server via its native shell scripts, stop the server. Then try to restart the server in Designer.


PLDCSPE0005 An exception was encountered while trying to synchronize the Application Platform server {0}'s run status in the Servers view. Cause: {1}
Explanation

Designer was unable to synchronize the status of the Application Platform server. The Servers view for Application Platform has a configuration setting, which is used to control how Designer synchronizes its status against the server.

Action

Verify that the configuration parameters are correct. If the server properties section does not show any properties, delete the server configuration and recreate it.


PLDCSPE0006 An error occurred while refreshing the Bundle Manager during the server status update to {1}. Cause: {2}
Explanation

Designer failed to refresh the Bundle Manager when the server was started or stopped.

Action

Restart Designer. If the error persists, contact Software AG Global Support.


PLDCSPE0009 An error occured while updating the Application Platform server run status {0}. Cause: {1}
Explanation

The Server's view for the Application Platform includes an entry for each configured server. Designer has received a WST server event, but an error has occurred while Designer attempted to update a server's run state.

Action

Review the server configuration in the Servers view and verify that the required server data is present. If the data is incorrect or some server properties are not displayed, delete the server configuration and recreate it.


PLDCSPE0010 Error getting a URL for server {0} for verifying the run status of Integration Server. Cause: {1}
Explanation

Designer was unable to obtain a URL for the server. The URL is needed in order to perform a ping operation against the server and to determine its current status.

Action

Verify that the server configuration properties are correct and try again.


PLDCSPE0011 Unable to create Application Platform custom module.
Explanation

Application Platform was unable to create a custom module. Application Platform uses a custom module in order to differentiate its server from other servers, like Tomcat, for example. The custom module is needed for adding all application projects containing the Application Platform project facets to the server. This is a critical component required for publishing bundles to the server.

Action

Contact Software AG Global Support.


PLDCSPE0012 An unexpected error occured while validating a project facet for module {0}. Cause: {1}
Explanation

Designer could not validate a project facet for the module. Designer projects use facets in order to define capabilities, supported by the servers that host the projects. This ensures that no attempts for publishing a project to a server that does not support that project can be made.

Action

Review the error details and verify that the correct project facets are added to the project.


PLDCSPE0013 An error occurred while adding server {0} to the lifecycle listener. Cause: {1}
Explanation

Designer failed to add the server to the lifecycle listener. A collection of listeners is maintained for servers that are added or removed from Designer. The listeners contain all the information that is needed for performing server actions, like publishing or unpublishing project bundles.

Action

Restart Designer.


PLDCSPE0014 An error occurred while synchronizing WST Servers View configuration updates. Cause: {0}
Explanation

Application Platform uses the Eclipse WST subsystem server configuration data. An exception occurred while updating Application Platform plugins.

Action

Restart Designer.


PLDCSPE0015 Missing credentials for server connection to the following url: {0}
Explanation

No credentials have been provided to verify the server status.

Action

Verify that the server connection has appropriate credentials.


PLDCSPW0000 An attempt was made to publish or unpublish a project module to a server that is not started.
Explanation

An error occurred while publishing or unpublishing the project module because the server is not started. You can only publish or unpublish Application Server projects to a server, which is started.

Action

Verify that the server is started and repeat the action.


PLDCSPW0002 No project modules were specified for the Application Platform publish operation.
Explanation

The Application Platform publisher received a publish request but no project modules were included in the request.

Action

Confirm that there is at least one project added to the Application Platform server configuration and try to publish again.


PLDCSPW0008 You must stop and restart the server after you change and save the server settings.
Explanation

You must restart the server after you change the server settings. Many of the server settings you can configure in Designer update server configurations, such as port numbers.

Action

Restart the server, and then restart the configured server in Designer.


PLDCUIE0001 An unexpected error occurred while configuring an Application Platform runtime environment.
Explanation

The Application Platform runtime configuration failed. The runtime preference page is used to define the runtime instance used for Application Platform server and project configurations.

Action

Go to the Window/Preferences/Server/Runtime Environments preference panel and create a runtime instance for the Application Platform server. If no server entry is displayed, confirm that all the required Application Platform components were installed.


PLDCUIE0002 Unable to verify preference setting {0} from the imported preferences file. Cause: {1}
Explanation

Application Platform verifies all directory path preference settings during the import step. An error occurred while verifying one of the preference settings.

Action

Update the preference setting manually.


PLDCUIE0003 {0} preference setting's directory path does not exist. ({1})
Explanation

While importing Designer preferences, Application Platform encountered a preference setting that contains a non-existent directory path.

Action

Update the imported preference setting with a valid directory path.


PLDCUII0000 No Application Platform runtime instance configuration was found.
Explanation

Designer could not find an Application Platform runtime instance configuration. The Application Platforrm server and projects require a runtime configuration.

Action

Create a runtime instance in the 'Runtime Environments' preference page in Designer.


PLDISPE0000 No Integration Server connections with valid URLs are defined in 'Window/Preferences/SoftwareAG/Integration Servers' for this Designer instance.
Explanation

The Application Platform server was not able to start because there are no valid Integration Server connections defined.

Action

Configure a valid connection to a local Integration Server via the configuration panel. You can find the configuration panel in Window/Preferences/Software AG/Integration Servers.


PLDISPE0007 An error occurred while retrieving the list of Integration Server connections. Details: {0}
Explanation

Designer failed to retrieve the list of Integration Server connections. Designer maintains the list of connections in Window/Preferences/SoftwareAG/Integration Servers view.

Action

Contact Software AG Global Support.


PLDISPE0008 No server connections are accessible in Window/Preferences/SoftwareAG/Integration Servers.
Explanation

The Application Platform server configuration must have a Designer Integration Server connection defined for the same host and port. No servers were returned from the server connection manager.

Action

Verify that at least one server connection is defined in the preference view.


PLDISPE0017 Error creating the list of Eclipse jobs to create the project jar. Details: {0}
Explanation

Eclipse reported an error in response to Application Platform querying metadata on the project.

Action

The project may be corrupted or Eclipse may require a restart. Review the CoreException error in the Eclipse workspace log file and take appropriate action.


PLDISWE0000 An error occurred while executing a task in the IS service wizard.
Explanation

An error occurred while using the IS service wizard for creating POJO bean wrappers for Integration Server services.

Action

Restart Designer and try again.


PLDISWE0001 The IS service wizard encountered an error while generating POJO classes for IS service: {0}
Explanation

Application Platform was unable to produce Java POJO service wrappers for the selected IS service(s).

Action

Verify that the IS service is properly defined and retry the code generation step.


PLDISWE0002 An Application Platform IS facet is not installed on this project.
Explanation

The project is not configured to use the custom Application Platform facet for Integration Server extensions.

Action

Enable the Application Platform IS facet on the project's properties page.


PLDISWI0003 IS services from IS product packages are not supported. Do not use this in a production setting.
Explanation

The checkbox for selecting all IS services is provided only for demonstration purposes.

Action

Create new services to be used with the Application Platform.


PLDMSPE0000 Error creating the list of Eclipse jobs for creating the project jar. Details: {0}
Explanation

Eclipse reported an error in response to Application Platform querying metadata on the project.

Action

The project may be corrupted or Eclipse may require a restart. Review the CoreException error in the Eclipse workspace log file and take appropriate action.


PLDNAVE0000 {0} model class is missing its identifier.
Explanation

Every graph node in the Visual Navigator must have a unique identifier, which is provided by the model node provider implementation.

Action

Check if the class type is produced by a custom model node provider implementation and try to resolve the problem.


PLDNAVE0002 Exception creating model node for object type {0}. Details: {1}
Explanation

An error occurred while creating the model content for a graph node.

Action

Check if this is a custom implementation and try to resolve the problem.


PLDNAVE0003 A class type is required when creating a category for a model object. Category name: {0}
Explanation

You must provide a class type for all categories that you create for model node providers.

Action

Check if this is a custom implementation and try to resolve the problem.


PLDNAVE0004 Exception creating list of package fragments from {0}. Details: {1}
Explanation

An error occurred while the Visual Navigator was rendering a graph for the class dimension.

Action

Verify that there are no compilation errors in your projects and try again.


PLDNAVE0005 Exception loading method {0}'s references. Details: {1}
Explanation

The Method dimension in the navigator view could not find a reference to the method in Designer when rendering the graph view.

Action

Check the details of the exception and try to resolve the problem.


PLDNAVE0006 Exception creating model nodes for class type {0} from native object {1}. Details: {2}
Explanation

The Visual Navigator uses the currently selected object as input when it switches from one dimension to another. An error occurred while extracting the model from this input for the next dimension graph.

Action

Check the details of the exception and try to resolve the problem.


PLDNAVE0007 Exception loading projects {0}'s references. Details: {1}
Explanation

The Project dimension in the navigator view could not find a reference to the project in Designer when rendering the graph view.

Action

Check the details of the exception and try to resolve the problem.


PLDNAVE0008 Exception loading resource {0}'s references. Details: {1}
Explanation

The Resource dimension in the navigator view could not find a reference to the resource in Designer when rendering the graph view.

Action

Check the details of the exception and try to resolve the problem.


PLDNAVE0010 Error executing model node providers for dimension {0} in the navigator view. Details: {1}
Explanation

The Visual Navigator encountered an error while building the object model for its graph view.

Action

Check the details of the exception and try to resolve the problem.


PLDNAVE0013 Universe with id {0} does not exist.
Explanation

You can register universes containing unique IDs through the Visual Navigator API. However, the specified ID does not match any registered universe.

Action

Contact Software AG Global Support.


PLDNAVE0014 Model node classname is required when creating an instance key.
Explanation

Every graph node, created in the Visual Navigator must have a unique ID, which includes the model node class name.

Action

Contact Software AG Global Support.


PLDNAVW0009 Unable to load annotation provider {0} for the navigator view. Details: {1}
Explanation

The Visual Navigator failed to load the annotation provider, which is required for extending the content added to the graph view.

Action

Check the details of the exception and try to resolve the problem.


PLDUTLE0000 An error occurred while updating Application Platform {0} project classpath. Cause: {1}
Explanation

The project classpath failed to updated. The project classpath is updated when Application Platform project facets are installed or removed.

Action

Manually update the project classpath in Designer.


PLDUTLE0001 Unable to resolve OSGi service: {0}
Explanation

Designer could not resolve the OSGi service. This suggests that the OSGi service interface has no implementations in the service registry. A possible reason is that the bundle contributing an implementation did not activate as expected or is missing from the container.

Action

Restart Designer and retry.


PLDWSE0000 An error occurred while adding Application Platform classpath containers to the {0} project. Cause: {1}
Explanation

Adding Application Platform classpath containers failed with an error. When Application Platform project facets are added to a project, additional classpath containers are also added to the project. This error can be caused by a corrupt Java project.

Action

Delete the Java project and create it again. While creating the project, make sure that you do not delete project contents.


PLDWSE0001 An invalid number format was found for Application Platform server configuration key: {0}. Value: {1}
Explanation

The Application Platform server configuration key has an invalid number format. A numeric value is required.

Action

Verify that the server configuration value is non-null and numeric.


PLDWSE0002 An attempt was made to register an Application Platform WST server instance with no server name.
Explanation

A registration attempt was made for an Application Platform WST server instance with no server name. A server name is required.

Action

Verify that the server configuration has a server name and restart the server instance.


PLDWSE0003 An error occurred while removing Application Platform classpath containers from the {0} project. Cause: {1}
Explanation

Removing Application Platform classpath containers from the project faield with an error. When Application Platform project facets are removed from a project, additional classpath containers are also removed from the project. This error can be caused by a corrupt Java project.

Action

Delete the Java project and create it again. While creating the project, make sure that you do not delete project contents.


ProfilesPageContentProvider_0 Cannot resolve the server profiles from the base directory: {0}.
Explanation

An error occured while resolving the server profiles using the base installation directory.

Action

Check if the ECLIPSE_HOME classpath variable for Designer points to the correct location. The default location is SAG_INSTALL_DIR/Designer/eclipse.