String Conversion

One of the best functionalities of this plugin is string conversion. You can run it using shortcuts, or after selecting a string in the editor, you can use Convert from the editor context menu (Figure 5-3) to select the action you want to do.

I use To Upper Case, To Lower Case, and Chars to Html Entities the most, but the all the others can be useful as well.

When you are using the newest NetWeaver version, you can use the Capitalize function or you can choose to keep CamelCase formatting on such backends.

Sorting

The next function that comes with the AnyEdit Tools is sorting selected text. You may wonder what you need such a function for, but when you are preparing mockups, it can be very handy. Additionally, when you deal with old code and the assignment of the structure values is spread through dozens of lines, you can sort them case-insensitively for easier readability. I use this feature often when I am dealing with old code that uses the ALV field catalog preparation.

To call sorting, you have to select lines in your editor and then use the Sort context menu option. There are a few sorting functions available there, as you can see in Figure 5-4. None of them needs a deeper explanation.

Comparison

Normally you use the Compare With editor context menu to compare current code with the code available on another SAP system, revision, or local history. But AnyEdit Tools introduces another four possibilities: Clipboard, Workspace File, External File, and Opened Editor. In ABAP development, I use the comparison with other opened editor (Figure 5-5).

There are two scenarios in which I use this option. First, when I am dealing with one of the dozens of versions of print programs, which are in fact copies of standard SAP print programs with some adaptations. If I want to combine some of them, I use this comparison to see the places in which they differ.

The second scenario is when I am asked to do some performance improvements in legacy program. I create a copy of the existing program with the new name, then start the adaptations. When I do a lot of refactoring, I sometimes need to check what I have changed in order to be sure that I have done things correctly. Comparing two programs opened in two different tabs is very useful at that moment.

Save Console Output

The next nice function that comes with this plugin is a new button in the Console view—the Save to File button (Figure 5-6). It allows you to quickly store the output of the console in a .log or .txt file. It is most useful for ABAP cloud developers, as they use the console output a lot.

You may also want to go to Preferences ➤ General ➤ Editors ➤ AnyEdit Tools in order to look at the additional settings that come with this plugin.

Clipboard History

Having a clipboard that keeps a long history can be a huge timesaver. When you do not have such a tool installed on your OS, you can use the one from PDE Tools. It only works inside Eclipse, but isn’t that where you spend most of your time?

To call the extended clipboard, you have to use Ctrl+Shift+V. When you do so, the list of previous clipboard entries will appear (Figure 5-8). By default, the first five lines of copied text are shown in the preview. To look at the full content of the clipboard, you need to select an entry using the arrow key and look at the right popup, which will show you not only the full contents of the clipboard, but also indicate where it was captured.

You can use a link found in the source of the capture to navigate to the code if it was copied from the Eclipse editor. The nice thing here is that the code is copied with its formatting, so it is easy to read.

Besides the key shortcut, which you can use to call the clipboard history, you can also open a view called Clipboard (Figure 5-9). It contains the same data.

If you want to change the default number of clipboards kept, or the number of lines in the preview of the clipboard, go to Preferences ➤ PDE-Tools ➤ Clipboard in order to adapt the preferences of this plugin function.

Theme

If you have chosen to use one of the DevStyles themes, you will see the difference on each of the views. First of all, most of the icons are different. You can see this on the toolbar (Figure 5-15) and in any other view (Figure 5-16). You may find it difficult to use at first, especially if you use the mouse for navigation in Eclipse, but you will get used to the new look quite fast.

I found these new icons more readable and clearer, but of course this is only my personal opinion. What is more important for me is that whenever I want to switch between the dark and the light themes, I do not need to set the colors of the ABAP Editor again to fit the new theme settings. DevStyle makes the changes automatically, so it saves lots of time.

Just to explain myself, since I claim to be an ambassador of using dark themes, I have to switch from time to time to a light theme. In most cases, it is due to presentations done on projectors in the conferences rooms with bad lightning. In such cases, the light theme is a better option.

Icon Designer

You can adjust and create the new icons that come with the DevStyle yourself. In the past, I made a lot of adaptations to the ADT icons, but you can always adapt the icons so that they fit your preferences.

To do so, you need to call the Icon Designer view. Each time you run it, it will check your Eclipse installation and gather all the used icons. They will be listed in a table (Figure 5-17), where besides the name, origin, and preview, you will see if the icon has been replaced by the DevStyle icon (column Replacement) and if the icon is official DevStyle (status live). If you create your own icons, the status will change to custom.

To create or edit an icon, simply double-click to open the Icon Editor (Figure 5-18). You will not be able to manually draw an icon, but you can select one from the list of icons and characters. You can also use two icons at the same time, by setting the icon layout to overlay. For each icon, you can also choose a primary color, scale, and fill color.

If you are happy with your changes, you can share the icon with the Genuitec team by using the Sync option in the Icon Designer view. When you click the Sync button, you need to pass your credentials to the Genuitec account or create a new one. Once you are logged in, your changes are sent to the Genuitec team and checked by them. If will spread the icon as a default icon to other users if they like it. I synchronized my adaptations to the icons in the past and I am glad that now, many ABAP developers are using them.

Inline Search

Inline Search is a small yet useful function that replaces the standard find/replace dialog of Eclipse (Figure 5-20). It is activated by default on installation of Darkest Dark. If you have worked with other IDEs, such as Visual Studio, you will be really happy with it.

Besides the minimal view of the inline search (Figure 5-21), it also adds the hits counter, highlights all of the results in the editor, and adds markers to the vertical and overview rulers.

CodeTogether

In the initial versions of Darkest Dark, CodeTogether was not available. When it was published I gave it a try, as I like to discover new software. I was pleasantly surprised with the ease of code sharing with other people around the globe.

Unfortunately, in the first releases, I was not able to share the ABAP code, but for Java files it worked perfectly. I kept it in my Eclipse installation, hoping that someday I would be able to share my ABAP code. And now it is possible, allowing developers to do pair programming or solving issues with other developers without sitting next to each other.

To start or join a session, you need to open CodeTogether view (Figure 5-22) and use the links.

When you choose to start a session, you will be asked to set up the parameters of that session (Figure 5-23). You can choose how you want to allow participants to join, who can lead the navigation through the code, and who can edit.

After starting the session, you will be able to copy the invite URL from the CodeTogether view (Figure 5-24). This URL can be then used in other Eclipse versions, IntelliJ, or VS Code with CodeTogether installed. The session link can also be used in any modern browser.

If the people you invited to the session want to join from Eclipse, they need to paste the invite URL and their name into the Join Session window, which is called by clicking the Join Remote Session button of the CodeTogether view.

Once this is done, you as a host will receive an authorization request with the name of participant (Figure 5-26).

If your peers want to join using a web browser, they will be asked not only for their name, but also for the IDE theme and key bindings that they want to use in the remote editor (Figure 5-27).

After starting the session in Eclipse, you will notice a green frame around the editor that is shared and an information if you are driving or following others (Figure 5-28). If you are driving, each step you take will be replicated in the remote editor for the other participants.

The participant view is a bit different than the host view. This is because ABAP syntax highlighting is not yet available in CodeTogether. For problem solving, this should not be an issue, but I am waiting for the day when ABAP syntax highlighting is available. As you can see in Figure 5-29, besides the shared code, the participant will have access to the Project Explorer of the host. With ABAP projects, which are virtual folders, only previously opened objects will be available, but it is still something.

As I wrote before, all changes are synchronized between the host and participants, as well as the Problems view, selection of code, and cursor position (Figure 5-30). It is easy to see who is changing the code and where, as the full name or initials of the person who is editing the code is displayed next to the cursor position.

Code completion is not synchronized on-screen, but you can still use it on the remote editor and get the code completion results that are calculated in the session host IDE.

You can achieve the same using any online meeting software. But this works very fast, much faster than screen sharing, as you are exchanging code, not images. This could be extremely useful when working remotely and when the network connection is not fast.

abapGit Repositories

If you are already using abapGit in your backend using the ZABAPGIT transaction, all your repositories will be listed in this view (Figure 5-32), but you will not have all the functionality of the GUI transaction yet.

These sets of functions are suitable for the basic actions with the Git repositories. Especially when you are only installing the repositories of others, you will not have to switch to a GUI transaction anymore. With ABAP in the cloud, you will not have GUI, so this plugin is the only way to bring ABAP repositories to your system.

Let’s now go through the process of linking a new abapGit repository to your system. First of all, you need to select the repository you want to bring into your system and copy its clone URL. If you do not have a project in mind, but you would like to try the plugin, simply go to https://dotabap.org (Figure 5-33). This is a list of ABAP open source projects with short descriptions and clone URLs.

When you have the clone URL, you need to click the Link New abapGit Repository button from the view. On the first screen, you need to paste in the clone URL, just like I did in Figure 5-34.

The second step is to select the branch and package (Figure 5-35). The changes of the linked branch are not possible in the Eclipse plugin, so pay attention to which branch you are linking your package to. If you make a mistake, you will need to unlink and recreate the link to the package. During this step, you can also decide if pulling (installing) the repository should happen directly after creating the link.

The next screen that will appear is the Transport Request Selection dialog, which you should have seen a dozen times. When you click the Finish button, you should see the linked repository on your list, just like in Figure 5-36.

Note in Figure 5-36 that there were some warnings during the installation of the repository in the backend system. You can double-click the Status column to get the details. For example, in my case, it was a message that programs are not allowed in the cloud environment, that is why they were not imported. The rest of the objects were imported and are available in the selected package.

abapGit Staging

When you want to contribute to the open source projects or create your own versions, abapGit Staging view can be useful. It is a very simple view that shows which local objects differ from the one stored in the remote repository. It allows you to commit and push the changes into a remote repository.

Despite the project type (your own or a community one), it is recommended to have your own branch for any adaptations. If you want to contribute to somebody else’s project, first fork it to your own Git repository, then link to your backend using abapGit and start the changes in code.

To commit and push the changes, you need to jump to abapGit Staging view and select the repository to check using the Switch Repository button on the view toolbar (Figure 5-37).

If there are any changes, you will see them as Unstaged Changes (Figure 5-38). Now you have to select the object you want to stage. You can do that by selecting the objects on the list and using the Stage button or choosing Stage Objects from the context menu. They will be moved to the Staged Changes tree. The last fields you need to fill in are Commit Message, Author, and Committer. At that stage, the Commit and Push button will became active.

When you commit your changes, you will be asked for the remote repository credentials. Your changes will then appear in the remote repository. There is also one additional function available here. When you use the context menu on staged or unstaged objects, you can run a comparison of the local object version with the one in the remote repository.

Coloring Projects

After installing the ABAP CI and restarting Eclipse, you will see the first of the popup windows that comes with the plugin. It’s a screen with the color assignment selection for the project (Figure 5-40). Color changing may be useful for quick recognition of the development, integration, or production systems. You can of course decide not to color the project. On this screen, you can also decide if it should appear when you switch to the project.

The basic settings are set to update the status color only, as it is presented in Figure 5-41, but you can make more adaptations. My personal feeling is that when you decide to color the project, status coloring is enough.

All assigned coloring projects will be listed on the ABAP Colored Projects view (Figure 5-42). From that view, you can add, edit, or delete the assignments using either the view toolbar or the context menu.

Continuous Integration

When you activate the first object after the installation of ABAP CI, you will see another screen from that plugin (Figure 5-43). This time it will be configuration of CI jobs for the package containing the object you just activated. CI jobs are done in the background after objects are activated, when you select from this screen that the package should be included in the automatic Unit Test run or the automatic ATC run.

Once you set up the package to be included in the CI jobs, you will see this package listed in the ABAP Continuous Integration view together with the last state of the Unit Tests and ATC run (Figure 5-44). From the view toolbar and context menu, you will also be able to add new packages to the list, or edit or delete the package from the CI jobs. You can also call Unit Tests and ATC Check on demand from here.

The ABAP Continuous Integration view is helpful if you are activating objects from several packages, as in other case you will be also notified about the result of the last CI run in the status bar. The widget shown in the bottom-left corner of Eclipse will show you the status of the CI job, the number tests passed and failed, and the number of the ATC results (Figure 5-45). By default, when the job is be successful, the color of the widget will remain white. With failed Unit Tests, it changes to pink. With ATC issues, it becomes purple.

If you have some ATC results, they will also be listed when you hover over the widget. A sample list can be found in Figure 5-46. It can be used to look quickly at any errors you made.

When you do not want to use the status bar widget to display the last CI job details, you can deactivate this in the plugin’s preferences. In this case, you can still follow the last calls of the job using the ABAP CI Dashboard view (Figure 5-47), which displays the same information as the status bar widget.

You may want to you want omit some classes from the CI jobs, but still want to check the other contents of the package. In such cases, you can use the ABAP CI Suppressions view (Figure 5-48) to exclude classes from the CI jobs run. Of course, at any stage, you can clear the list or add new objects to it using the view toolbar buttons.

Preferences

You should be used to the fact that not everything is available directly, but after making changes in the preferences, you can get much more. The same is true with the ABAP CI plugin. When you go to Window ➤ Preferences ➤ ABAP Development ➤ Continuous Integration, you will notice that there are some nice functionalities available and you can also adjust the ones I have described.

First of all, you can choose to run a Unit Test not for whole package, but only for activated object. This should speed up the visibility of the results on the status bar widget.

You can also set up a variant for ATC. It does not need to correspond to the default variant available in your system.

The third group of settings is the visualization of the source code state in the UI, where in addition to the color customization for failed Unit Tests and ATC results, you can decide if the widget for the source code state should be shown in the status bar. Additionally, you can decide if the popup for the unconfigured CI jobs packages should appear.

If you are using the TDD approach, you may like also to activate the Show TDD Labels for Source Code State Output option (Figure 5-49). Choosing this option, instead of the test results, means the status bar widget will guide you if you should now write test, write code, or refactor. The last step appears when your unit tests pass the checks and ATC has no result. Once you achieve that, the refactor state will remain visible for the time specified in the Minimal Time The TDD Cycle Will Remain in the Refactor State option.

The next nice possibility of the ABAP CI configuration is to allow automatic source code formatting when you activate or save an object. By default, the mandatory prefix in the source code is set to #autoformat. You would need to put this in each object you are changing in the first line in order for this function to be triggered. I guess this is something most of us would not do, but instead if you fill the mandatory prefix with <NO_FILTER> (Figure 5-50), each activated or saved object will be automatically formatted. You can also decide to clean up unused variables.

Search Tools

You can use it directly, using two new buttons on the Eclipse toolbar (Figure 5-55), or you can just run a standard Eclipse search (Ctrl+H) and switch the tab to ABAP Objects Search+.

The standard ADT ABAP Object Search is very limited. It only allows you to search the objects by name. ABAP Object Search+ brings the searching functionality to another level. It is limited to CDS Views, Database tables and views, classes and interfaces. It covers most of the needs of the developers. This is because it contains search filters that you will love to use.

You should remember search filters from many other ADT places, such as from the ABAP Repository Trees or the Open ABAP Development Object dialog (Ctrl+Shift+A). There are quite a few more of them in this plugin (Figure 5-56).

A great feature of some of the search filters is code completion. For example, for Anno or From (Figure 5-57). A few of them allow you not only to select the filter criteria, but also to enter a strict value of the filter criteria. For example, CDS View search filter anno: accesscontrol.authorizationcheck=#NOT_ALLOWED will search for only CDS Views with the annotation @Accesscontrol.authorizationCheck set to #NOT_ALLOWED.

You can put several search filters together and use more than one value for each filter. By default, when you put several values into one filter, they work as if they were part of an OR clause. If you want to change that behavior, click the Use “AND” instead of “OR” during search checkbox; the search results will then be more accurate. In Figure 5-58 there is an example of search of CDS Views that are having SELECTs from MARA AND MARC tables and the field called MATNR.

So far, it has been all about search criteria. Now it is time to look at the results of the search (Figure 5-59). They will be visible in standard Eclipse Search view and they will contain different details for different searched object types. Ludwig has focused mostly on the CDS Views, which is why you can get a lot of details about the CDS Views.

You can also mark the search as a favorite. To do that, just use the Favorite button on the Search view toolbar and select Create Favorite from Current Query (Figure 5-60). With repeatable searches, this can save you some time. Of course, this comes mostly in hand when you search for the same objects, as the standard history also saves your queries.

Besides creating favorites, from the context menu of ABAP Object Search + results, you can also call the favorites organizer, the data preview, and the analysis tools that are the second part of this plugin.

Analysis Tools

In each of these places, you can choose one of four possible analyses: CDS Top-Down, Used Entities, Where-Used in CDS, or Field Analysis. The first two analyses are available only for CDS Views, the other two work with database tables and views.

CDS Top-Down Analysis (Figure 5-61) shows you which other CDS Views, database tables, or views are used in the currently selected CDS. It drills down the usage to the last level, so you can see all types of CDS Views and the database tables used at each CDS level. This analysis can be extremely helpful when you’re working with complex, multilevel CDS Views. In the view menu, you can also enable the display of used associations.

Used Entities Analysis (Figure 5-62) gives you an aggregated view of the data from the Dependency Analyzer and usage information of the CDS View. This view can be useful to determine if you need to reduce the number of used entities or transform the CDS. This view can also give you an overview about the importance of the CDS View.

Where-used in CDS Views analysis can show you if the analyzed object is used in a SELECT or the association part of CDS Views (Figure 5-63). Using the view menu, you can choose to see only usage in CDS Views for whom the API state is set to Released. Viewing only locally defined associations can also be set in the same place.

The last of the analysis tools is Field Analysis (Figure 5-64). It is very useful for quickly checking the origin of a CDS View field. The view for this analysis is split into two parts: Field list and Field details. The Field detail area has two modes. The Field origin mode uses a top-down approach to display the origin of field down to the database layer. It also shows the name of the field at each level in the field hierarchy. The other mode is Usages in Fields and it will show the usages of a field in other CDS Views.

CDS Analyzer also collects the history of the analysis. Using the Show Previous Analyses button, you can return to the cached results of the previous analysis (Figure 5-65). Its behavior is exactly the same as the history on the Search view.

Tags

In order to tag the objects in ADT, you need to create them inside the Tags view (Figure 5-67). You can create user and global tags. As you can foresee, user tags are visible only for you and global tags are visible for every developer, that is using your system. Each of the tags is stored in the backend, so they are system specific.

Tags view enables you to create a tags hierarchy with multilevel tags. This can be used for example to create development project specific tags.

After creating the tags, you can start to assign them to the objects. You can do that from the Assign Tags To Object button that is found on the Eclipse toolbar, or using the context menu of the Project Explorer and ABAP Editor. You can do this also from the Tag Explorer view. In each case, a wizard for adding tags to your object is displayed (Figure 5-68). If you try to assign a sub-tag, you will also have to select the parent object of the tag. The parent object is one of the objects that is assigned to the parent tag. Using my example, if I want to assign an object to the Demo tag of the FALV node, then the FALV tag would need to be assigned to any of the objects.

You can find several uses for the tags. They can be useful for onboarding new developers, describing the tasks that need to be done with the object or for highlighting of the object’s purpose.

Tag Explorer

The second view that is installed with the ABAP Tags plugin is Tag Explorer (Figure 5-69). By default, it is linked with the active editor and shows all the tags that are assigned to edited objects. You can also manually select other objects to be used by clicking the Other Object button on the view toolbar. You can also assign new tags or delete linked tags from this view.

ABAP Tags Search

If you like to list all the objects with a specific tag, you need to use the search functionality of Eclipse (Ctrl+H) and switch the tab to ABAP Tags Search (Figure 5-70).

You can select one or more tags here and then choose if the search should only consider objects that match all the SELECT tags. After you click the Search button, the result will appear in the standard Search view. If the object is a parent of other objects, the list of liked sub-tags and the objects assigned to them will be visible after you expand the object node, as shown in Figure 5-71.

The maximum number of results is set to 50 by default, but you can use the ABAP Tags preferences (Window ➤ Preferences ➤ ABAP Tags ➤ Search) to adjust this value to your needs. You will be able to adapt a few more minor options as well.

Favorites

The Favorites view is universal (Figure 5-76). It can contain both standard and Development Objects folders. Both types of folders can contain different object types and act a bit differently.

Standard folders work exactly like the user favorites menu from SAP GUI, which means when you store a program or transaction, you can double-click it to run it.

The Development Objects folders work similarly to the Favorites Objects ABAP Repository Tree that I described in previous chapters. So when you double-click one of the favorite objects, it will open in the editor. Additionally, Development Objects folders have a different icon than the standard one, for faster recognition.

In order to assign an object to favorites, you first need to create a folder using the view toolbar or its context menu. When you create a folder (Figure 5-78), besides the name and descriptions, you can choose if the folder is project independent and the folder type. Using proper names and descriptions can help you filter the view entries.

Project independent folders are always visible on the view, while project dependent ones by default are shown only when the active editor is linked to the same project. Additionally, when you double-click the object that is linked to a specific project, it will be always opened in that project, regardless of which one is currently active. This behavior can be helpful when you work with several customer systems and they have totally different sets of transactions or when you work with different types of ABAP systems (CRM, HR, etc.) that have their own specific transaction codes. Currently there is no way to manually select the linked project; it is always currently the active project.

After creating the folder, you can start assigning objects to it. The basic option to do this is to use the context menu on the created folder and choose the selected type of object to create. After that, you will see a favorite object creation window (Figure 5-79). In all cases, besides URLs and ADT links, the name used should correspond to the real object name. For the two other kinds of objects, the name can be anything, as there is another input field to enter the whole URL or ADT link.

The second way to add objects to favorites is by using the Project Explorer’s or editor’s context menu. After selecting an object, simply choose Add To Favorites. The folder selection dialog will appear, just like in Figure 5-80.

Once you have your favorite object list, you can also open or run the elements in each of the projects that are available in your workspace. To do this, use the context menu on the object and choose Open in Project. The second possibility is to press the Ctrl button while double-clicking the object. In such cases, you will get a popup window, where you can select the project to which the objects should be opened. This functionality was added by Ludwig Stockbauer-Muhr and it is extremely helpful when you have a long list of projects in your workspace.

If you create the object in the wrong folder, you can drag and drop the favorite to the correct place.

Favorites Dev Objects

The second view of the plugin is Favorites Dev Objects (Figure 5-81). It has the same behavior as the Favorites, but with one difference—you can only create Development Objects folders here. This split for two different views was done to enable developers to choose their own way, with one view containing both types of folders or using two views with separation of the folder types. Personally, I use the second approach.

Preferences

For flexibility of usage, I’ve created a preferences page for Favorites. It can be found in ABAP Development ➤ Favorites (Figure 5-82) and consists of five settings so far.

The Hide Project Dependent Folders option is set by default, but when you deselect it, your project-dependent folders will be always visible in the views. However, when you double-click, it will open or run the object in the linked object.

The Save state of folder expansion setting is deselected by default, but if you select it, the expansion of the Favorites tree will be saved when Eclipse is closed and restored during the next start.

The Navigate to Eclipse for Supported Development object is also set by default. When you deselect it, instead of the Eclipse editor, the development objects will be opened in the SAP GUI transactions.

The last two radio buttons groups are responsible for the behavior of double-click and double-click with the Ctrl key pressed. You can decide which behaviors should be the defaults.

Project Settings

When you create an ABAP project in Eclipse, you are not able to change the client, language, or user. That is the standard behavior of the ADT. If you install ABAP ADT Extensions, you can however update each of these preferences using the Project Explorer’s context menu (Figure 5-84).

When you choose a change action, a proper window will appear, where you can enter a new value for the changed parameter. So far there is no completion of the possible entries, so you need to be sure you are entering them correctly.

To change the settings, all currently opened objects from the changed project will be closed. So make sure that you have saved your work before adopting those settings.

Personally, I like the Change of Language option the best, and sometimes I also change the user on the integration systems. This is because I do not like to have several systems as different projects in Eclipse. I keep one project for one system and adjust the logon settings when necessary.

Automatic Logon

When your company does not have single sign-on (SSO) enabled for your SAP systems, starting Eclipse might be boring. Especially if you have dozens of systems to which you need to log in, or maybe you have to remember the passwords to many customer systems. In such cases, I think you will like this part of the ABAP ADT Extensions plugin.

You can now use the Passwords view (Figure 5-86) to store the passwords of each of your projects. When you install the plugin, it will read the workspace’s configuration and add all the projects, clients, and users to the Passwords view.

You can then find the system, client, and user for which you want to use automatic logon. You double-click the username and enter a password (Figure 5-87). If your instance is not the developer edition of SAP with the default password for the DEVELOPER user, I recommend you use the Encrypt Password option. That way, no one will be able to read it.

The passwords are stored in Secure Storage. You can check this by going to Window ➤ Preferences ➤ General ➤ Security ➤ Secure Storage. Under the storage called com.abapblog.adt.extension.passwords, you will find all your projects and assigned clients and users (Figure 5-88).

Now each time you start your Eclipse workspace, you will automatically be logged in to these systems. All the logon is happening in the background job, so you might have to wait a bit if you have dozens of system to log on, to. This behavior is visible if you have a slow connection to the backend systems.

This standard behavior of this plugin can be configured using the preference page of Automatic Logon, which can be found in the ABAP Development preferences node (Figure 5-89). You can resign from automatic logon at start or by raising a save password popup for each new created ABAP project. You can also decide if you want to log on to all ABAP systems, not only to those for which you have a password saved. In such a case, if the plugin finds a system that has no password stored, it will raise the standard ADT logon widget.

The Logon Automatically For All Stored Users setting can be useful if you want to restrict the automatic logon at start for only some of the systemclientuser combinations. In this case, the checkboxes found on the Passwords view will tell the plugin which systemclientuser it should log on to automatically.

When you disable automatic logon at the start of Eclipse, I suggest you keep the Logon Automatically at Expand of the Project Setting enabled. In this case, whenever you need to log on to a system and save your credentials, it is enough to expand the project folder on Project Explorer. The other option for logging on is to use the same context menu as for project settings, but then select the Logon with Secure Storage (logon only to selected system) or Logon to All SAP Systems option.