Basic Tutorial/Sample Release Notes

URN Mapping

The sample LoanProcessService orchestration collaborates with other services, which have been provided in separate BPR files. The services are located by the sample orchestration using URNs. Upon deployment these URNs need to be mapped to the actual endpoints of the deployed services using the URN Mapping capability of the Administration console.

All of the partner service URNs relating to the loan approval example can be mapped with a single mapping entry:

urn:x-vos:loancompany                                http://localhost:8080/active-bpel/services/${urn.4}          


This maps all URNs fitting this pattern to a generic URL pattern, replacing specific entries for each service, e.g.
  
urn:x-vos:loancompany:RiskAssessmentService			(RiskAssessmentService) (default is http://localhost:8080/active-bpel/services/RiskAssessmentService)
urn:x-vos:loancompany:LoanApprovalService			(LoanApprovalService)  (default is http://localhost:8080/active-bpel/services/LoanApprovalService)

See the Admin and Configuration guide for more information on URN mapping.
