Genuitec » All Posts Sat, 17 Feb 2018 17:15:55 +0000 en-US <![CDATA[[WebLogic] Defining a WebLogic 12 Runtime]]> Thu, 12 Oct 2017 08:09:59 +0000 support-tony Some users have understandably been confused about the folders that need to be specified when creating a new WebLogic runtime (either directly or through the new Server wizard). This FAQ hopefully clarifies the locations to specify.

For the “BEA home directory“, specify the folder containing the domain-registry.xml file. This will also include the folder in which the actual WebLogic server is installed and may contain other software that is common to a number of BEA products (“BEA” is the name of the company that previously owned the WebLogic product now owned by Oracle). For example, on my Linux machine, for example, this folder is /home/tony/dev/servers/weblogic12/wls12210, though the key folder here is wls12210.

For the “WebLogic installation directory“, specify the folder containing the server folder, which itself contains the main server executable code, though the parent folder will contain other server code. The parent folder is typically named wlserver, and is a child of the BEA home directory. On my Linux machine, for example, the WebLogic installation directory is /home/tony/dev/servers/weblogic12/wls12210/wlserver. Note that will see an error message at the top of the wizard page for specifying most runtime details about an invalid WebLogic installation directory, until it is specified correctly; once you select the correct location, you may continue to see an error message but it will be concerning a invalid domain directory, so ensure you select that from the browse button against that text field.

]]> <![CDATA[Changes to Application Server Connectors After Release 2014]]> Mon, 08 Jun 2015 08:21:32 +0000 support-tony Changes to Application Server Connectors Between 2014 and 2015

From release 2015, the user interface to the application server connectors has changed somewhat. Their essential functions are unchanged but there are differences in how they are created and configured and in how applications are deployed to servers. From our delivery log:

With 2015, we’re merging our connector framework with the Web Tools server framework, giving you the best server tooling across both camps. All the servers we have ever shipped are still supported, but they now offer additional control and configurability.

This FAQ summarizes the differences.

Note that, with the 2017 releases, the organization of the GUI has been better integrated with eclipse, so the location of many preferences and options may be in a slightly different place from those mentioned here and related pages. Refer to this article for more information.

For a description of the application server connectors, as they are now, you should refer to the learning center article found here:
MyEclipse Application Server Connectors.
There are also other articles in the Learning Center that deal with the connectors. Please refer to this section for more information.

Migrating connector settings from earlier releases

The easiest way to move your server definitions from earlier releases is to open the workspace, used with the earlier release, with MyEclipse 2015 (or later). This will automatically migrate the settings.

Creating and configuring connectors

Prior to the 2015 release, server connectors were enabled and configured from the MyEclipse/Servers preferences pages, with custom launches being created via run configurations.

With 2015, server connectors are based on a <i>runtime</i> or <i>runtime environments</i>. A runtime environment defines the location of the installed server. Multiple servers can then be defined to use that runtime, though often only one server is sufficient. In addition, it’s possible to define multiple runtime environments for the same server installation.

A runtime environment can be defined either in the MyEclipse/Servers/Runtime Environments preferences page or when a new server is defined in the Servers view. Conversely, servers may be created as part of the process of defining a new runtime environment or directly in the Servers view.

Whilst runtime environments are configured in the preferences pages, servers are configured using a special editor, once they are created in the wizard. The editor is opened by double clicking on the server in the servers view. Different server families will be associated with different editors, though there are common features. Note that the launch configuration is reached by clicking on the link shown in the General Information section of the editor.

For some servers, configuration information may be held in the workspace, in a special project, or in other places specified by the user. The Tomcat server acts this way. Refer to the learning center article mentioned above for more information on saving Tomcat configuration information in the workspace. Note that this doesn’t apply to the built-in MyEclipse Tomcat server connector. Note also that for some changes to be made, there must be no projects deployed to the server; take note of the information in the server configuration editor about this.

Deploying Applications

Deploying applications is essentially a two step process. After deployment, the application is synchronized to ensure that the latest code and resources are available on the server. Synchronizing is accomplished by publishing. Publishing is normally automatic, both at deployment time and when code or resources change in the workspace. Publishing is controlled by a configuration setting. A server may need to be started to publish but this also is done automatically.

A project may be deployed by dragging it from an explorer view to the server in the Servers view.

However, for fuller control over deployment, use the deployment manager by right clicking on a server, in the Servers view, and selecting “Add/Remove Deployments”. In this wizard, the projects that can be deployed to the selected server are shown in the left hand pane and the deployed projects are shown in the right hand pane. Select projects and use the Add button to move them from the left pane to the right pane. You can select the deployment mode (packaged or exploded) against the projects in the right pane.

Another route to deployments can be seen by right clicking in the MyEclipse Explorer or Package Explorer view and selecting MyEclipse->Add/Remove Project Deployments. With this, select the project (“Module”) to be deployed from the dropdown list and click the Add button. From there, you will be given a list of servers to which the selected project can be deployed. Note that only servers on which the project can run will be shown. If no servers appear, then the project cannot be run on any server.

Adding Server Connectors

Though MyEclipse has server connectors for most releases of most commonly used servers, others may be available from third party developers. These additional connectors may also be added to the suite of connectors. To see what other connectors are available, go to the Servers view, right click and select New->Server. In this dialog, click on the link “Download additional server adapters”, near the top right of the dialog. Wait for the list to be populated.

Running Servers

The Run/Start/Stop MyEclipse Server toolbar action () is no longer available and, hence, there is no default launch mode for servers (debug/run). The Run toolbar action now includes configured servers, as does the Debug toolbar action ().

The launch mode has to be chosen explicitly by using the Debug or Run action, from the main toolbar, from the Servers view toolbar or from the Servers view context menu. Of course, as before, you can choose to run or debug a project on a server, by choosing the appropriate action from the project’s context menu.

You must be logged in to view attached files.
]]> <![CDATA[Missing Icons and Images With Remote Phonegap Builds]]> Wed, 25 Mar 2015 03:16:20 +0000 support-tony If you are developing mobile applications with images (icons and splash screens), using the remote PhoneGap build, and the images don’t appear in your application, please read on.

Note that this affects remote builds for both Android and IOS applications, with PhoneGap 3.6 or later, and is due to a bug in the remote build.

The workaround is to move the config.xml file into the www folder and reselect all images so that their paths are relative to www and not the project root (and this can also be done by reselecting the images in the config.xml editor, after it is moved into www).

Even with this workaround, local builds will also continue to work fine.

For a discussion on the bug, with another potential workaround, check out this issue on the PhoneGap forum at GitHub.

]]> <![CDATA[Troubleshooting performance issues in MyEclipse 2015]]> Wed, 04 Mar 2015 00:19:10 +0000 support-tony If you are using MyEclipse 2014 or earlier versions, please see this document.

If you have noticed long running jobs labeled “Synchronizing script resources with Tern server”, or errors with “Calculating completion proposals” where the IDE goes into a non-responsive state, these situations are caused by performance issues in our JavaScript tooling, read on.

In MyEclipse 2015, we switched to Tern, for content assist, from Eclipse’s JSDT solution. This has lead to better analysis of JavaScript code and a higher quality of content assist proposals as well as added functionality for modern frameworks like Angular JS.

We have noticed that with large JavaScript code bases, the Tern server is overloaded leading to a non-responsive IDE as described above.

For users on the MyEclipse 2015 CI stream, this issue was addressed in MyEclipse 2015 CI 12. This update is more efficient with JavaScript performance from the get go, but it has further performance options as well. Users on the CI stream are urged to update to CI 12 or later; for users on the Stable stream, please update to Stable 2.0 or later.

MyEclipse 2015 CI 12 and Following

In 2015 CI 12, if MyEclipse notices a performance issue with your project, you will be warned and given the option to take corrective action. Options include:

  1. Increase the performance setting either for your project or globally.
  2. Change the scope to work only on a single file (as opposed to the entire project) or turn Tern off entirely:
  3. Modify the JavaScript source path, as described in the section below.

MyEclipse 2015 CI 11 or earlier

  1. Right click on your project and choose Properties.
  2. Select the MyEclipse > JavaScript Resources node and the Source tab.
  3. Click the Excluded node and click Edit.

  4. Click “Add Multiple …” and select folders containing JavaScript that you do not actively work and/or folders with a large number of JavaScript resources. You can also exclude individual files.

  5. Click OK to persist these changes.
  6. In case MyEclipse has already processed this server, you may need to restart MyEclipse for these changes to take effect.


  • When JavaScript code is excluded from source folders, you will not get content assist proposals covering JavaScript entities defined in these files.
  • Often you have a large number of JavaScript resources in your project but are only actively working with a small subset of these resources – if you are facing performance issues, consider excluding resources you are not working with.
  • Check the technologies page for source that you have in your project. You can exclude the source files from the source folder and enable the corresponding Tern module on this page instead for improved performance and content assist.

]]> <![CDATA[[DB] Problems accessing Oracle database]]> Wed, 05 Mar 2014 02:50:15 +0000 support-tony From time to time we have users report problems when dealing with Oracle databases either with using the DB Explorer, reverse engineering or some other function. The issue almost always stems from the fact that they are using the old driver and not the newer ojdbc14.jar driver (JDBC for java 1.4/5.0). The newer driver is much more robust and will work with Oracle DB versioned 8.1.7 or greater and can be downloaded from here.

Additionally there is a known problem when using the Oracle 9 or 10 JDBC driver in an international environment that will result in a stack trace like:

java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-12705: Cannot access NLS data files or invalid environment specified

The fix is to upgrade your JDBC driver to the latest version, available here.

]]> <![CDATA[[DB] How do I install and connect to Apache Derby?]]> Wed, 05 Mar 2014 02:34:13 +0000 support-tony Note: MyEclipse comes with Derby included as an integrated test database. There is no need to do anything to configure this sandbox version, though there are associated preferences. If you want a simple database on which to test, use this embedded version of Derby (there is a Derby Database Server Tutorial, in the workbench help). Otherwise, you may install an external version and follow this guide.

Apache Derby is a great Java-based multi-use database, along with HSQLDB. Both of these databases can be set to run in-memory (embedded) or as a service like a more typical DBMS install. This tip will cover how to install and run Derby in-memory.

This is extremely helpful when testing an application and you need a temporary DB to run all your tests against.

Installing Apache Derby

    1) Go here for the latest stable Derby release and download the BIN ZIP file.
    2) After downloading it, unzip the file to some location (it will create a db-derby-<VERSION>-bin subdirectory)

Believe it or not, now we are done with the installation. Since the DB is going to run in-memory, just making “connect” calls via the embedded JDBC driver will actually create the DB for us, we don’t need to do any more installing or initialization.

Connecting to Apache Derby
These instructions look long, but they are very straight forward and most of them you only need to do once…

  1. In MyEclipse, switch to the “MyEclipse Database Explorer” perspective:

  2. Click the “New” menu item in the DB Browser view:

  3. Fill in the fields as shown in the screenshot below
  4. In the “Driver JARs” panel, click “Add JARs…”
  5. Find your derby.jar file in the /lib directory under the derby directory we unzipped from the section above.
  6. Use the “Driver classname” drop-down box to select the org.apache.derby.jdbc.EmbeddedDriver class:

  7. Hit Finish

Now you can select the Embedded Derby connection and hit the “Open Connection” button to connect to your Derby DB.

Note:Any created database will be created as a folder with the same name in the MyEclipse installation folder (for the example above, this would be “derbyDB”). To setup Derby as a normal server service, please see the Derby Documentation.

]]> <![CDATA[[AppServer] My app needs a JAR or DLL file to run]]> Wed, 05 Mar 2014 01:09:29 +0000 support-tony Some applications will require external resources to be available to the application server during runtime like a JDBC driver or a DLL that contains a native library that the app needs. When this happens what you need to do is double-click on your server in the Servers view then click the “Open launch configuration” link in the server’s configuration editor. On the Classpath tab you can add jars and reorder them. For DLLs, on the Arguments tab, modify the VM Arguments panel to add or change the java.library.path property.

]]> <![CDATA[[DB] Can I use Windows Auth wth the DB Explorer?]]> Mon, 03 Mar 2014 03:38:46 +0000 support-tony If you are connecting to a Microsoft SQL Server database and want to use Windows authentication, follow these steps:

1) Download the Microsoft JDBC Driver

2) Install it and place sqljdbc_auth.dll into the jre/bin folder under the MyEclipse JDK , which is in the binary directory of the MyEclipse installation directory.

3) Configure the Microsoft SQL Server Driver in MyEclipse using the downloaded sqljdbc.jar (or sqljdbc4.jar) in a new connection from the Database Explorer view.

4) Set the driver profile connection URL to be of the following format:


Where you replace “servername” with the proper name of your server and “instance” with the proper instance name of a running server.

]]> <![CDATA[[AppServer] How do I connect the debugger?]]> Mon, 03 Mar 2014 02:41:14 +0000 support-tony This is a common misconception that you need to connect the Eclipse debugger to a running application server once it is started. Part of the job of the MyEclipse connectors when starting up the application servers is to hook the debugger directly into the application server, so all you need to do after the server is started is start setting break points then exercising your application to hit them. This is all covered in our online or in-product help here:

]]> <![CDATA[[Troubleshoot] Getting OutOfMemoryExceptions]]> Mon, 03 Mar 2014 02:33:16 +0000 support-tony 9/10 OutOfMemoryExceptions are caused by 1 of 2 things:

  • Your VM has run out of heap space, default heap size is 64mb
  • Your VM has run out of permSpace

As Eclipse based products get larger, the memory requirements go up. MyEclipse is no exception here. The fastest way to work around this issue and also provide some additional boost in performance, we suggest the following command line or ini file arguments:


If you are running a 64 bit version of MyEclipse, the following settings are recommended:


In the past it was sufficient to merely use the -Xmx512m setting, but we have noticed increasingly so with larger Eclipse-based products that running out of permSpace can occur and give OutOfMemoryExceptions as well, which is why we are now suggesting users increase that setting too.

On Windows and Linux it is fairly straight forward to update your shortcut or startup script/launcher/shortcut respectively to include these arguments. On Mac it’s a little more confusing. For details on how to find the locations of the ini files, look at this FAQ.

]]> <![CDATA[Disabling/Enabling Validators on OS X, with MyEclipse 2014]]> Thu, 19 Dec 2013 01:45:58 +0000 support-tony Note that this only applies to users running under Apple Mac OS X operating system.

There is a bug in eclipse Kepler, which will be fixed in a future eclipse release. The bug causes MyEclipse 2014 to hang if the user attempts to disable/enable a validator by clicking on the validator on the validation preference page.

A workaround to the problem is to right click on the validator and use the context menu to enable or disable the validator, as seen in this screenshot:

Note that it is still possible to use the other buttons and checkboxes on the page – so you can still enable/disable or suspend all validators together.

This is fixed in our 2015 releases.

]]> <![CDATA[[MyEclipse Tomcat] Enable logging for Integrated Tomcat]]> Thu, 05 Apr 2012 01:30:27 +0000 support-swapna To enable logging for the Integrated Tomcat server you have to add the following property definitions to the integrated MyEclipse Tomcat 6 configuration. Double click the “MyEclipse Tomcat V7.0” server in the Servers view, to bring up the configuration editor. Then click the “Open launch configuratoin” link in the “General Information” pane. Select the Arguments tab and go to the “VM arguments” section. Copy/paste the following property definitions to the end of the existing arguments:

-Djava.util.logging.config.file=”<your workspace folder>\.metadata\.me_tcat7\conf\”

Remember to substitute your workspace folder path, as appropriate (you can copy and paste it from other arguments that are already there).

Start the server and now you can see the log messages at <workspace dir>\.metadata\.me_tcat7\logs\catalina<date>.txt

Note: For releases earlier than 2015, you will find the VM arguments via the MyEclipse preferences. Go to Window -> Preferences -> MyEclipse -> Servers -> Integrated Sandbox -> MyEclipse Tomcat6 -> JDK. Copy/paste the property definitions into the Optional Java VM arguments (don’t forget to substitute your workspace folder path as appropriate) and save the changes. The logging config file should be created at the following location with the .metadata folder: .plugins\com.genuitec.eclipse.easie.tomcat.myeclipse\tomcat\conf\, instead of the location mentioned above.

]]> <![CDATA[[Troubleshoot] MyEclipse Menu & Ubuntu Global Menu Bar]]> Fri, 17 Jun 2011 06:29:18 +0000 support-tony With versions of Ubuntu that have the Unity desktop (e.g. 11.04 up), certain applications (including MyEclipse) have problems integrating their menu bars with the Unity global menu bar, which is always present at the top of the screen, displaying the menu bar of the currently active window.

This problem exists in eclipse, also (see this bug). There are two ways to address this issue, currently:

  1. Log in with the Ubuntu classic desktop or another desktop environment which isn’t the default Ubuntu desktop. This will affect all application windows and the desktop, which will operate in the classic desktop way.
  2. Start MyEclipse from a launcher or terminal, using the following command:
    UBUNTU_MENUPROXY= <MyEclipse installation directory>/myeclipse
    Note that there must be a space between the “=” and the myeclipse invocation string. The executable name may be different depending on the MyEclipse version that you’ve installed. When setting up a launcher, you’ll need to have the command as a parameter of a sh invocation:

    sh -c "UBUNTU_MENUPROXY= <MyEclipse installation directory>/myeclipse"

    If there are spaces in the path to the MyEclipse executable, precede each with a backslash.

    This works with the bash and dash shells but may not work with other shells. Note that Basically, you have to set UBUNTU_MENUPROXY to null before starting MyEclipse. There are other ways to do this, such as setting the entry in your .profile file

    This will allow you to use the Unity desktop (the default desktop in Ubuntu 11.04) though the MyEclipse menu will appear in the MyEclipse window, not on the global menu bar.

]]> <![CDATA[[Troubleshooting] Memory & performance issues]]> Wed, 04 May 2011 13:37:16 +0000 Brian Fernandes If you are having performance issues in MyEclipse 2015, please click here for more information that might help.

1) myeclipse.ini settings
If you are using a 64-bit installation of MyEclipse, you may want to increase the memory settings in myeclipse.ini; 64-bit software really does consume more memory and our tests have shown that the increase can be as high as 30 to 40%. You may need more memory even on a 32-bit install, if you have a large workspace.

The myeclipse.ini file can be found in the same folder as your MyEclipse executable. Open it in any text editor and change the values based on the size of your workspace. For instance, the following settings may be preferable to the defaults.


2) JavaScript issues with MyEclipse 9 and above
MyEclipse 9.1 and later
In MyEclipse 9.1, we have introduced several JavaScript code analysis modes to allow you to tailor the JavaScript feature set to suit your specific needs. While the Active mode is feature rich, in very large workspaces it can lead to memory and performance issues; a problem further compounded if you do not actively work with JavaScript. The Passive mode is a good mix of necessary JavaScript features and performance, this is the default mode for MyEclipse 9.1.
To change your JavaScript code analysis mode, go to Window > Preferences > MyEclipse > Files and Editors > JavaScript

MyEclipse 9.0
In case you are not interested in global JavaScript analysis, you can remove folders from the JavaScript indexer by performing the following steps. Note that JavaScript validation and auto-completion within a single file will still work, however it will be disabled across projects and while you will see squiggly lines indicating errors, actual problem markers will be disabled so errors will not appear in the problems view or the ruler.
You may want to do this if you have a lot of generated JavaScript code in your projects or entire JavaScript frameworks (such as YUI or DOJO) which you deploy with your projects but do not directly use or actively work with.

Go to Project Properties > MyEclipse > JavaScript > Include Path and the Source tab. Expand any entry and then select the Excluded node and click Edit. In the resulting dialog, click Add in the Exclusion patterns section and type in “WebRoot/**” (you will need to change this if your WebRoot folder is differently named). This will prevent the JavaScript indexer from running for all resources under your project’s WebRoot folder. Based on how your project is structured, you may want to exclude different folders and can use wildcards as required.

Note that these steps are not required with MyEclipse 9.1 and above, simply switch to the Passive JavaScript mode as directed in the MyEclipse 9.1 section above.

Some background information:
In MyEclipse 8.6.1 we had custom JS solution that was highly efficient in terms of memory consumed. Unfortunately, this solution had to be withdrawn due to several other issues surrounding compatibility with third party plugins and we have moved back to an integrated JSDT solution. We have brought several of our custom JS enhancements to JSDT, but the memory issues remain unresolved and far from trivial to fix.

3) MyEclipse Configuration Center
Depending on your actions, the MyEclipse Configuration Center could consume a significant amount of memory. Though most users will not leave the configuration center open when closing the workspace, if you do so, it will reopen when you next start MyEclipse. You do not need to wait for the configuration center to open each time MyEclipse starts and can close it before it opens by pressing Ctrl + F8 or simply clicking the “Close” link.

I apologize for any inconvenience caused; our focus this year is on performance and efficiency so you should be seeing improvements constantly being made in this area over the next few releases

]]> <![CDATA[[Troubleshoot] Using the -clean command line argument]]> Wed, 04 May 2011 00:55:30 +0000 support-tony Using the -clean command line argument when starting up MyEclipse can help with problems related to stale plugin cache information (usually shown in the log as problems loading bundles). The way it is used is as an argument to the MyEclipse executable; on Windows that is myeclipse.exe, on Linux or OS X it is myeclipse:

myeclipse.exe -clean

On OS X, the path to the executable is complex, so this may be an easier way to start MyEclipse from the command line (assuming it was installed into Applications):

open /Applications/MyEclipse\ Professional/MyEclipse\ --args -clean

Alternatively, add the following line to the myeclipse.ini file, near the top (after the first line would be a good place):


Refer to the FAQ here for how to locate the ini file.

[If you have installed MyEclipse as a plug-in to a classic eclipse installation, the corresponding executable is eclipse.exe and the ini file is eclipse.ini.]

This option tells eclipse/MyEclipse to erase and rebuild its plugin cache to avoid conflicts with incorrect plugin information. This is very important to use when upgrading between major releases or trying to fix a strange behavior in your workspace. After you have used -clean once, you are free to remove it from your command line arguments. Indeed, it’s recommended to remove it, since startup takes noticeably longer with -clean.

An explanation of what the clean option does may be found here.