|
|
This chapter describes using the various IDEs to interact with Oracle Enterprise Repository. This chapter provides an overview of the production and consumption processes, and encompasses the development environment use cases. It contains the following topics:
The Oracle JDeveloper development environment use cases are as follows:
Through Oracle JDeveloper, you can select files to submit to Oracle Enterprise Repository. The files are bundled into a .zip format for submission. You can submit single and/or compound-payload assets to Oracle Enterprise Repository.
Oracle Enterprise Repository can harvest BPEL, WSDL, XSD, and XSLT files and file directories. After harvesting, Oracle Enterprise Repository automatically creates assets, populates asset metadata, and generates relationship links based on the information in the artifact files. The harvesting function is available from the command line, and can be integrated into Oracle JDeveloper or into the build process.
| Note: | The Harvester is not restricted to Oracle products, it can be used to harvest standards-based artifacts generated from any tooling. |
You can access the assets and artifacts available in the Oracle Enterprise Repository through Oracle JDeveloper. Through Oracle JDeveloper, you can search for assets matching various criteria or view assets that may be of interest to a development project.
For selected assets, you can view asset details such as description, usage history, expected savings, and relationships. Within the asset metadata, links to the supporting documentation, user guides, test cases are provided to better enable you to reuse the existing functionality.
You can download an asset’s artifacts (i.e., payload) into your project. Typically an asset payload is the functionality that you need to use a service (such as a WSDL file) or incorporate into your code base (usually a binary).
Through the Oracle Enterprise Repository, analysts, architects, technical leads, and others who are involved in the design stages of a project can create a list of assets that fulfills a project’s requirements. The list of assets are captured in compliance templates in the repository and the compliance templates are associated with an Oracle Enterprise Repository project.
From within the Oracle JDeveloper, you can view a list of assets appearing in all of the Compliance Templates assigned to your project. You can see which of the assets have been used and/or other project members. For more information on compliance templates, see Oracle Enterprise Repository Compliance Templates Guide.
Oracle Enterprise Repository can automatically detect asset reuse within Oracle JDeveloper. This allows development teams to ensure that they get asset reuse credit, regardless of whether the assets have been downloaded through Oracle Enterprise Repository or pulled from another source such as the developer’s desktop.
The Oracle Enterprise Repository plug-in for Eclipse development environment use cases are as follows:
The Oracle Enterprise Repository plug-in for Eclipse allows you to select files to submit to the Oracle Enterprise Repository. It packages the files into a .zip format for archive submission. The Archive Submission Wizard allows you to submit single and/or compound-payload assets to Oracle Enterprise Repository via an archive ZIP file.
Oracle Enterprise Repository can harvest BPEL, WSDL, XSD, and XSLT files and file directories. After harvesting, Oracle Enterprise Repository automatically creates assets, populates asset metadata, and generates relationship links based on the information in the artifact files. The harvesting function is available from the command line, and can be integrated into Eclipse or into the build process.
You can access the assets and artifacts available in the Oracle Enterprise Repository through the Oracle Enterprise Repository plug-in for Eclipse. Through Eclipse, you can search for assets matching various criteria or view assets that may be of interest to a development project.
For selected assets, you can view asset details such as description, usage history, expected savings, and relationships. Within the asset metadata, links to the supporting documentation, user guides, test cases are provided to better enable you to reuse the existing functionality.
You can download an asset’s artifacts (i.e., payload) into your project. Typically an asset payload is the functionality that you need to use a service (such as a WSDL file) or incorporate into your code base (usually a binary).
Through the Oracle Enterprise Repository, analysts, architects, technical leads, and others who are involved in the design stages of a project can create a list of assets that fulfills a project’s requirements. The list of assets are captured in compliance templates in the repository and the compliance templates are associated with an Oracle Enterprise Repository project.
From within the Oracle Enterprise Repository plug-in for Eclipse, you can view a list of assets appearing in all of the Compliance Templates assigned to your project. You can see which of the assets have been used and/or other project members. For more information on compliance templates, see Oracle Enterprise Repository Compliance Templates Guide.
Oracle Enterprise Repository can automatically detect asset reuse within the development environment. This allows development teams to ensure that they get asset reuse credit, regardless of whether the assets have been downloaded through Oracle Enterprise Repository or pulled from another source, such as the developer’s desktop. Automated Usage Detection relies on a fingerprinting process, called Software File Identification (SFID), which tags selected files within an asset with a unique ID. This SFID is then used to detect when and where an asset is used, even if the asset was acquired through means other than the Oracle Enterprise Repository Use - Download process. An instance of usage is recorded by Oracle Enterprise Repository when tagged files within the asset are brought into the Oracle Enterprise Repository plug-in for Eclipse, and a new build or build clean occurs. For more information, see Oracle Enterprise Repository Software File Identification Guide.
The Oracle Enterprise Repository plug-in for VS .NET development environment use cases are as follows:
The Oracle Enterprise Repository plug-in for VS .NET allows you to select files to submit to the Oracle Enterprise Repository. It packages the files into a .zip format for archive submission. The Archive Submission Wizard allows you to submit single and/or compound-payload assets to Oracle Enterprise Repository via an archive ZIP file.
Oracle Enterprise Repository can harvest BPEL, WSDL, XSD, and XSLT files and file directories. After harvesting, Oracle Enterprise Repository automatically creates assets, populates asset metadata, and generates relationship links based on the information in the artifact files. The harvesting function is available from the command line, and can be integrated into VS .NET or into the build process.
You can access the assets and artifacts available in the Oracle Enterprise Repository through the Oracle Enterprise Repository plug-in for VS .NET. Through VS .NET, you can search for assets matching various criteria or view assets that may be of interest to a development project.
For selected assets, you can view asset details such as description, usage history, expected savings, and relationships. Within the asset metadata, links to the supporting documentation, user guides, test cases are provided to better enable you to reuse the existing functionality.
You can download an asset’s artifacts (i.e., payload) into your project. Typically an asset payload is the functionality that you need to use a service (such as a WSDL file) or incorporate into your code base (usually a binary).
Through the Oracle Enterprise Repository, analysts, architects, technical leads, and others who are involved in the design stages of a project can create a list of assets that fulfills a project’s requirements. The list of assets are captured in compliance templates in the repository and the compliance templates are associated with an Oracle Enterprise Repository project.
From within the Oracle Enterprise Repository plug-in for VS .NET, you can view a list of assets appearing in all of the Compliance Templates assigned to your project. You can see which of the assets have been used and/or other project members. For more information on compliance templates, see Oracle Enterprise Repository Compliance Templates Guide.
Oracle Enterprise Repository can automatically detect asset reuse within the development environment. This allows development teams to ensure that they get asset reuse credit, regardless of whether the assets have been downloaded through Oracle Enterprise Repository or pulled from another source, such as the developer’s desktop. Automated Usage Detection relies on a fingerprinting process, called Software File Identification (SFID), which tags selected files within an asset with a unique ID. This SFID is then used to detect when and where an asset is used, even if the asset was acquired through means other than the Oracle Enterprise Repository Use - Download process. An instance of usage is recorded by Oracle Enterprise Repository when tagged files within the asset are brought into the Oracle Enterprise Repository plug-in for VS .NET, and a new build or build clean occurs. For more information, see Oracle Enterprise Repository Software File Identification Guide.
|