Application 1 reopens the cursor.
应用程序1再次打开游标。
Developing Application 1: myfirstproject.
开发应用程序1：myfirstproject。
Application 1 (A1) selects rows from a single table in a cursor.
应用程序1 (A 1)在一个游标内从单独一个表选择行。
Documents for Application 1. Resume 2. Passport 3. Certificates.
申请所需材料1。个人简历2。护照扫描件3。毕业证书。
Table 1 shows the configuration of data sources for Application 1.
表1展示为应用1进行的数据源配置。
Application 1: Consider UML for the role of common enterprise notation.
应用1：要为企业提供通用的符号，可以考虑uml。
Table 2 shows the settings for the pureQuery properties files for Application 1.
表2展示为应用1 进行的pureQuery属性文件配置。
Assume you have discovered that you need to run incremental capture on Application 1.
假设您需要对应用1进行增量捕获。
Table 4 shows the various files that are created when capturing SQL for Application 1.
表4展示了为应用1捕获SQL时所创建的各种文件。
As shown in Figure 5, Application 1 and Application 2 are installed on a cluster that has four members.
如图5中所示，应用1和应用2装入有4个成员的集群中。
Application 1 use all three data sources (DS1, DS2, and DS3), while Application 2 USES only one data source (DS3).
应用1使用全部3个数据源(DS 1、DS2、以及ds3)，然而应用2仅使用一个数据源(ds3)。
For example, tenant 1 might sign up for SaaS application 1 and 2, while tenant 2 signed up for SaaS application 2 and 3.
例如，租户1可能签订了应用程序1和2，而租户2则签订了应用程序2和3。
Application 1 will execute the export operation and Application 2 will get a lock snapshot while Application 1 is running.
Application 1将执行导出操作，Application2将在Application 1运行的同时获得一个锁快照。
That means application 1 may use INDEX 1, while application 2 uses INDEX 2, but concurrent use of INDEX 1 in both applications is not allowed.
这意味着，应用程序1可能使用索引 1，同时应用程序2使用索引 2，但是不允许两个应用程序中同时使用索引 1 。
For example, in Figure 3, there are two applications; application 1 access is via HTTP port 8081 and application 2 access is through HTTP port 8082.
例如，在图3中有两个应用程序；应用程序1通过HTTP端口8081进行访问，应用程序2通过HTTP端口8082进行访问。
The deadline for applying to his favorite college was Nov.1, and by early October he had yet to fill out the application.
申请他最喜欢的大学截止日期是11月1日，到十月初他还没有填好申请表。
See " Deploy and run the application" from Part 1 for a refresher on this.
有关内容请参考第 1 部分的 “部署和运行应用程序”一节。
Note that the architecture discussed below builds on the sample application developed in Part 1.
注意，下面讨论的架构基于 第 1部分中开发的示例应用程序。
These interactions are among the major design elements of the sample application illustrated in Figure 1.
这些交互包含在图1展示的示例应用程序的主要设计元素之中。
A screenshot of the running application is shown in Figure 1.
图1中显示了该应用程序正在运行时的抓屏。
At the end of the last article, our Explorer application looked like Figure 1.
上一篇文章结束时，我们的资源管理器应用程序如图1所示。
This application pattern is illustrated in Figure 1.
图1说明了这个应用程序模式。
The application supports the actions in Figure 1.
该应用程序支持图1中的操作。
Figure 1 shows an application scenario used throughout this article.
图1显示了本文通篇使用的应用程序场景。
Figure 1 shows the application main page.
图1显示了应用程序的主页面。
If an application takes 1 second to respond to a request, then the number of requests per second must be 1 for the load to be in equilibrium.
如果一个应用程序需要1秒的时间来响应请求，那么每秒的请求数必须是1，负载才能均衡。
Let's assume an enterprise legacy application (see Figure 1) is divided into modular components of business processes.
假设企业以前的应用程序(参见图1)被分成业务流程的模块化组件。
Figure 1 shows this application structure.
图1显示了这个应用程序结构。
Let's look at the main layout file for our application, shown in Listing 1.
我们来看看本文中的应用程序的主要布局文件，如清单1所示。
Figure 1 shows the application design.
图1显示了该应用程序的设计。
应用推荐