Integration with Eclipse Using Oracle Workshop for WebLogic

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Administrative Prerequisites and Establishing the Oracle Enterprise Repository Connection

This section contains information on the following subjects:

 

Configuring the Oracle Enterprise Repository Plug-ins for Repository Access in Workshop for WebLogic

For instructions on installing the Oracle Enterprise Repository plug-ins for repository access within the Eclipse-based Oracle Workshop for WebLogic IDE, see the Oracle Enterprise Repository Installation Guide.

Uninstalling the Oracle Enterprise Repository Plug-ins

When uninstalling the Oracle Enterprise Repository plug-ins, Oracle Workshop for WebLogic will also be removed if it was installed by the Oracle Enterprise Repository installer. This may not be desirable if other plug-ins were since added to Oracle Workshop for WebLogic. To avoid uninstalling additional Oracle Workshop for WebLogic plug-ins, deselect the Oracle Enterprise Repository plug-ins for Eclipse option from the list of components to uninstall.

Installing Products After Installing Oracle Enterprise Repository

If Oracle Service Bus applications are installed after the Oracle Enterprise Repository plug-in is installed, then Eclipse must be launched using the -clean flag.

 

Prerequisites for Using the Oracle Enterprise Repository Plug-ins with Workshop for WebLogic

You should complete the prerequisites described in this section before using the Oracle Enterprise Repository plug-ins for Oracle Workshop for WebLogic.

Installing the Eclipse Solution Pack

In order to be able to submit Oracle Service Bus projects as assembly models to the repository, you must first import the Eclipse Solution Pack that is bundled with your installation into Oracle Enterprise Repository.

  1. Start the Oracle Enterprise Repository Import/Export tool, as described in the Oracle Enterprise Repository Import/Export Guide.
  2. Select the Import tab.
  3. Navigate to the BEA_HOME\repository103\core\tools\solutions folder.
  4. Select the OER103-Eclipse-Solution-Pack.zip as the target file to import into Oracle Enterprise Repository.
  5. Click Next, and then click Next again to start the import process.
  6. Click Finish to complete the process.
  7. After importing the Eclipse Solution Pack, you must reestablish connectivity to the Oracle Enterprise Repository plug-ins by using the Eclipse Preferences page, as described in Configuring the Oracle Enterprise Repository Connection.

Once connectivity is established, then the Oracle Enterprise Repository plug-in imports all the necessary asset types, taxonomy, relationships, and other entities for application integration to Oracle Enterprise Repository. Once these entities are imported, they will be available whenever you connect the Oracle Enterprise Repository plug-in to the enterprise repository.

Assign Users to an Oracle Enterprise Repository Project

In order to download assets from the repository, users must be assigned to at least one Oracle Enterprise Repository project. An Oracle Enterprise Repository project administrator can assign users to projects using the Oracle Enterprise Repository Projects page.

Obtain the Eclipse integration path from the Oracle Enterprise Repository administrator. (For example, http://appserver.example.com/aler-web/eclipse).

Enabling the Assets-in-Progress Properties

Two system settings must be enabled in order to activate Assets-in-Progress when using Oracle Workshop for WebLogic with Oracle Enterprise Repository.

This procedure is performed on the Oracle Enterprise Repository Admin screen.

  1. Click System Settings.
  2. Click General Settings in the System Settings section.
  3. Enter the property cmee.asset.in-progress in the Enable New System Setting box and click Enable to reveal this hidden property.
  4. Make sure the Asset in Progress property is set to True.
  5. Click Save.
  6. Enter the property cmee.asset.in-progress.visible in the Enable New System Setting box and click Enable to reveal this hidden property.
  7. Make sure the Asset in Progress property is set to True.
  8. Click Save.

The Registration Status drop-down menu will now appear in the Search section on the AquaLogic Enterprise Repository Assets screen. For more information about Assets-in-Progress, see the Oracle Enterprise Repository Registrar Guide.

Enabling Assembly Model Submission Properties

In order to be able to submit Oracle Service Bus projects as assembly models to the repository, this capability must be enabled in the Oracle Enterprise Repository System Settings. You can also enable the logging of asset submissions from external endpoints.

  1. Click System Settings in the sidebar on the Oracle Enterprise Repository Admin page.
  2. Enter the property cmee.tooling.submission.enabled in the Enable New System Setting box and click Enable to reveal this hidden property.
  3. Set the Asset Submission from Integrated Endpoint property to True to enable asset submissions generated through integrations with external endpoints.
  4. Click Save.
  5. Enter the property cmee.tooling.submission.logging in the Enable New System Setting box and click Enable to reveal this hidden property.
  6. Set the Submission Logging of Integrated Endpoint property to True to enable the logging of import/export jobs controlling asset submissions through integrations with external endpoints.
  7. Click Save.

For more information about System Settings, see the Oracle Enterprise Repository Administration Guide.

SiteMinder

If Oracle Enterprise Repository is or will be configured to be secured by Siteminder, the policy server must be configured to ignore (or unprotect) the following URL: 

  http://appserver.example.com/aler-web/eclipse/

Java JDK

The Java Cryptography Extension (JCE) is required. It is provided in JDK v1.4, and is available as an optional package in JDK 1.2.x through 1.5.x. Note that Oracle Enterprise Repository plug-ins for use with Eclipse 3.x require JDK v 1.5.x or later.

XML Parsing

Since Editor and Viewer metadata is represented as CDATA-escaped XML, some XML parsers may exceed their entity expansion limit when communicating with Oracle Enterprise Repository. For example, if you have defined a large number of Asset Types in Oracle Enterprise Repository, then you may need to increase the Entity Expansion Limit of your XML parser.

On some popular parsers, the default entity expansion limit is set to 64,000. This limit can be increased on JAXP-compliant processors by passing a command-line parameter called entityExpansionLimit. The entityExpansionLimit can be increased by passing a VM argument on the Eclipse command-line (modify the Eclipse desktop shortcut). For example, set the target of the shortcut to the following: 

  c:\eclipse\eclipse.exe -debug -consolelog -vmargs -DentityExpansionLimit=1048576

 

Configuring the Oracle Enterprise Repository Connection

When you invoke an action on a repository, such as querying or publishing assets, before repository connectivity has been established, then the Connect to Enterprise Repository wizard will either be automatically displayed (in the case of querying the repository), or will be launched by an explicit user gesture.

Note: If credential information had been specified in a previous session, the wizard will display this persisted information when it is launched.
  1. In the Credentials area, enter the server location and login credentials, as follows:
    • Repository URL – the URL of the repository server. The URL must include the host, port, and Oracle Enterprise Repository server name. For example, http://localhost:7001/oer.
    • User Name – user name to gain access to the repository.
    • Password – password to gain access to the repository.
      • Figure 2-1 Establish Enterprise Repository Connection


      Establish Enterprise Repository Connection

  2. Click the Establish Connection button to ensure enterprise repository connectivity.

    3. If a connection cannot be established, an appropriate error message will be displayed.

  3. Once connectivity is established, you can either:
    • Click Finish to exit.
    • Click Next to select your workspace preferences (skip to Step 4).
      • Figure 2-2 Specify Workspace Preferences


      Specify Workspace Preferences

  4. Once connectivity is established, you can specify your workspace preferences:
    • Enter a Model Namespace to use as a default for your all of your projects. The Namespace provides a means to organize your models, with the Namespace pre-pended to the names of all the assets in the model in the repository. However, you can change the Namespace on a project-by-project basis (such as when submitting assets), and the new Namespace will only be saved for that project, but will not affect the Workspace Preference name.
    • Select a Repository project in Oracle Enterprise Repository that the submitted model will be associated with. Asset usage is tracked in the repository and attributed to repository projects, which typically represent software development programs, business initiatives, etc.
    • Enable usage detection – If you selected an Oracle Enterprise Repository project as the workspace default, usage detection will be enabled for the default Oracle Enterprise Repository project. For more information about workspace preferences, see Setting Eclipse Preferences for Oracle Enterprise Repository.
  5. The Artifact Store area displays the name of a preconfigured Artifact Store that the submitted assets will be associated with. Artifact Stores are Oracle Enterprise Repository’s representation of Software Configuration Management (SCM) systems. SCMs contain the master artifacts, which are referenced by URLs in Artifact Assets and in asset FileInfos. Only those Artifact Stores that have been defined by an Oracle Enterprise Repository administrator will appear in the Name list. If an SCM does not appear in the Name list, an administrator must add it to the Oracle Enterprise Repository instance. The Details box may also display some additional information about the Artifact Store.
  6. Click Finish to exit.

  Back to Top       Previous  Next