Offline access using the OSGi framework of SmartCloud entry

The SmartCloud Entry supports the user in selecting a Derby database to bring with them, or using the DB2 database. The purpose of this article is to show you how to access the system's own Derby database, because DB2 itself provides accessible clients, so it is not covered in this article.

Environmental preparedness

Derby Introduction

The Derby database is a purely Java-implemented memory database that belongs to an open source project in Apache. Because it is implemented in Java, it can be run on any platform, and another feature is small, installation-free, requiring only a few small Jar packs to run.

The Derby engine can be embedded in the application. When working in embedded mode, application access to the database is direct and proprietary. This means that other applications cannot access the database at the same time.

Offline access to the database

The Derby database used by SmartCloud Entry is working in embedded mode, so in general, we can only access the offline database, which requires you to stop SmartCloud Entry instance before we can continue.

The SmartCloud Entry database will be stored in different configurations, with the default configuration stored in the. Skc/database under the current user directory, and there are many tools available to access the Derby database, where we mainly use the Eclipse's own data Source Explore.

First, let's Open the Data Source Explore first. In Eclipse, select Menu Window/show view/other, select Data Source Explore, as shown below

Figure 1. Select Data Source Explore

After the confirmation, the effect is as follows

Figure 2. Data Source Explore Default view

Now let's add a connection that connects to the Derby database. We can right-click on "Database 50x15" and choose New.

Figure 3. New Derby Connection

We chose database Derby and specified names, such as "SmartCloud Entry database", next.