Sunday, January 16, 2011

Freckle In Mouth Inside Cheek

Fusion Middleware patchset 3 (PS3) available

The portfolio manager can search the repository for new requests to Web services. is searched for this type 'Request for Service' and Registration Status 'Unregistered'. On the right, then found the request for the web for information about vacation days will be displayed. If selected, the service in the hit list with the mouse, appears below the plain text of the request. The portfolio manager finds here the purpose of the required web services and can now check whether there is already an existing service to meet that purpose.


Before he opens the Asset Editor and accepts the request with the Accept button). Even the request for service is now in the status of 'Registered' converted so that it further in the repository is available. could now be searched for as search string 'holiday' and type 'Service'

  • Now the search is of course the previously created web service that required by the Return parameters name, surname and remaining vacation days at least the first two returns. Our portfolio manager decides not to pursue further development of the existing web service, a new version, which returns the needed vacation days.
  • The entire process until the new Service Manuals available, can be also supported by the repository. For example, initially the new service could now be defined in the repository, with development status. Then he could be assigned to a developer, later tests could be documented in the repository. For this workshop there will be sufficient, but if the service is easily created and placed in the repository.



The Generic Project is sufficient.

It will restore the selected Web service technology that Java in its wake. The project then gets the name HRService2. The next step then close the dialog.
is now created in the new project HRSerivce2 another PL / SQL web service. The steps for creating the Web services are essentially the same as in Chapter service creation with the following changes:


The service gets a new name, here 'HrInfoService2'




This time, the procedure uses GETHRINFO2. The rest of the Wizards simply by clicking with the defaults.

For your safety, the new web service will be tested shortly in JDeveloper. This new version now gives back next and last name and the remaining vacation days.
It works out of the test is successful, the Web may be just as previous to the WLS will be deployed, as in
'deploy Web services' chapter already described.

After that, the new web service under the old HRService in the Weblogic Console appear under deployment.



too well the WLS web service should be tested shortly.
Next, over the new service on the harvester in the repository.


is given in the HarvesterSettings1.xml (~ / app/Middleware/repository111/harvester /), the entry remote query be modified so that now Hrservice-HRservice 2-context-root is queried. The file is then stored under a new name, eg HarvesterSettings2.xml. is now back to the harvesters, 'take over the Enterprise Web repository' as already described in the chapter in the series. So again call with



. / harvest.sh-settings HarvesterSettings2.xml






Continue asset editor as admin. There may be performed on the 'Advanced Search' button at the top left of the 'Search' button an advanced search by type 'Service'.

The service can now be described in more detail in the repository. The version is 2.0, he will get a description and the project is assigned.
on the Administration can go through the service rush through the steps for registration, list web service to the Enterprise Repository as described in Chapter .

Other attributes can be set, eg on the support page, the check mark for 'Supported', or according to 'Management Review'. These are for a potential service consumers important information, it is again typically use more of a service that is supported.
On the Taxnomy yet the connections are at the very bottom add 'Relationships' on the 'Add'.


The HrInfoService2 gets the relation 'Previous version is' to HrInfoService. The inverse relationship 'Next version is' is automatically set. With OK, the dialog is closed. The second does one 'Implements' relation to the application 'web service for information on days off'.

Thus, the relations to the request and the previous version are stored in the repository.
Now that the new service is deployed and registered can be run, the process developers use it. In addition it can in the OER for example, after hrservice look and now finds both versions.

Called the new service in the Navigator, it now displays all relationships. Both automatically collected by the harvester, and the manually nachgetragenen connections to the previous version and the request.
This is the process of new service now available and can be integrated accordingly.

0 comments:

Post a Comment