This chapter includes the following sections:
The ECSF application must include the searchable objects before you deploy it to the application server.
Searchable objects and their dependencies must be deployed as part of the ECSF application's data model and user interface projects (Model
and ViewController
respectively) to make the searchable objects available for search. To deploy searchable objects, you must complete the following tasks:
Deploy the ECSF shared library to Oracle WebLogic Server.
Create an application.
If desired, change the application name and context root of the view-controller project.
Modify the run configuration of the view-controller project.
Add the ECSF Runtime Server library and the required Java archive (JAR) files to Model
and ViewController
.
The ECSF shared library eliminates the need for ECSF libraries to be packaged into each application. Instead, applications that depend on ECSF libraries can reference the ECSF shared library that is deployed to the Oracle WebLogic Server. The ECSF shared library contains the following Java archive (JAR) files:
ecsf.jar
search_admin_wsclient.jar
search_client.jar
ses_admin_ows_proxy.jar
soap.jar
The ECSF extension in JDeveloper controls the reference to the ECSF shared library that is deployed to Oracle WebLogic Server. When you add the ECSF Runtime Server or ECSF Client library to a project, the reference to the ECSF shared library, shown in Example 32-1, is automatically added to the WebLogic deployment descriptor file (weblogic-application.xml
).
The ECSF shared library is oracle.ecsf
.
If the weblogic-application.xml
file does not exist, one is created and updated with the reference to the ECSF shared library.
In addition, when you deploy an application to a Oracle WebLogic Server instance and the project contains ECSF libraries, the code checks the descriptor for the ECSF shared library reference. If no ECSF shared library reference is detected in the descriptor, one is added. The WebLogic deployment descriptor also contains a list of library dependencies for the application to be deployed to the Oracle WebLogic Server instance.
The ECSF shared library is automatically deployed to the Integrated WebLogic Server instance by the ECSF extension in JDeveloper through the JDeveloper Application Development Runtime Service (ADRS). However, you must manually deploy the ECSF shared library to the standalone WebLogic Server.
Example 32-1 Reference to the ECSF Shared Library
<library-ref> <library-name>oracle.ecsf</library-name> </library-ref>
The ECSF shared library is automatically deployed to the Integrated WebLogic Server instance by the ECSF extension in JDeveloper through the JDeveloper Application Development Runtime Service (ADRS). When the Integrated WebLogic Server instance is first started and the ECSF shared library is automatically deployed to it, the ECSF shared library creates a SearchDB data source in the Oracle WebLogic Server domain. The data source initially contains placeholder database connection information. You must manually update the data source after the Integrated WebLogic Server instance is started to include the correct connection information.
To update the SearchDB data source, do the following:
You must manually deploy the ECSF shared library to the standalone WebLogic Server instance. The ECSF shared library creates a SearchDB data source in the Oracle WebLogic Server domain. During the process of deploying the ECSF shared library, you must provide the database connection information for the SearchDB data source, which is deployed with the shared library.
To deploy the ECSF shared library, do the following:
Extend the Oracle WebLogic Server domain by using the Oracle Fusion Middleware Configuration Wizard.
For a Linux OS, execute:
$WL_HOME/common/bin/config.sh
For a Windows OS, execute:
%WL_HOME%\common\bin\config.bat
Select the ECSF Shared Library Extension template (oracle.ecsf_11.1.1_template.jar
), which is located in oracle/jdeveloper/common/templates/applications
.
Configure the SearchDB data source by providing valid values for the following fields:
DBMS Host
DBMS Port
SID
Username
User Password
When a new version of the ECSF shared library is available, you must redeploy it.
Remove the old oracle.ecsf
library.
Install the library enterprise archive (EAR) file (oracle/jdeveloper/ecsf/modules/oracle.ecsf_11.1.1/oracle.ecsf.ear
) with the name set as oracle.ecsf
.
Note:
You can also redeploy the ECSF shared library by using the Oracle Fusion Middleware Configuration Wizard.
Creating the application creates Model
and ViewController
, which must include the searchable objects and their dependencies.
To create a new application, do the following:
If desired, change the application name and context root of the view-controller project by modifying the Java EE application settings.
To change the Java EE application settings, do the following:
Modify the run configuration of the view-controller project to run ECSF in debug mode.
To modify the run configuration, do the following:
You must add the ECSF Runtime Server library and one of the following sets of required Java archive (JAR) files to both the Model and view-controller projects:
For using ECSF for crawling and querying
oracle/jdeveloper/soa/modules/oracle.soa.fabric_11.1.1/fabric-runtime.jar
oracle/wlserver_10.3/server/lib/wls-api.jar
For using ECSF for querying only
oracle/jdeveloper/webservices/lib/soap.jar
Caution:
Make sure that cwallet.sso
and jazn-data.xml
are part of your application before adding the Java archive (JAR) files. You can do so through the Application Navigator by navigating to Application Resources, then Descriptors, then META-INF. The cwallet.sso
file is created when you create a database connection. To create jazn-data.xml
, right-click the META-INF folder select New Oracle Deployment Descriptor, select jazn-data.xml
, and click Finish.
You do not need to add the Java archive (JAR) files that are included in a library that you have already added.
After you update the Model and view-controller projects to include the searchable objects and dependencies, you must deploy the ECSF application. For information, see Setting Up Your JDeveloper Application Workspace and Projects .