Database Reference
In-Depth Information
Now, with another few quick steps, we will proceed with the creation of Proxy Service
from our EJB Business Service. Go to the
Proxy Services
subfolder and start the
Proxy
Service
wizard.
Tip
By the way, you can have any folder's structure according to your preferences, but we ad-
vise you to look closely at the structure presented in step one in the previous figure. It
seems to be a minor thing, but it has considerable impact on team collaboration, bundle
deployment, and Governance in general. The presented structure is strongly conducted to
a Solid Foundation for Service Inventory
for brevity—the
Optimal Flexible Architecture
(
OFA
). The role of this standard is really hard to overestimate and DB architects and
DBAs know it really well. For OSB/SCA, in terms of the Adapter framework, the purpose
of this standard is to identify the location of OSB and JDeveloper artifacts. For some, as
we mentioned earlier, two developer tools around one framework seems too many and
you can find the examples where the structure of the JDev SCA/JCA projects is embedded
into the Eclipse OSB folders structure. Although we can see the reason for that, we still
advise you to keep these structures separate and use the Continuous Integration and deliv-
ery bundling tools for the final assembly. Also remember that OFA principles are ex-
tremely important for the FTP/FSO TP folders hierarchy.
Name your Proxy service suitably and set it as
Transport Type Service
(the
General
tab). Transport shall be JEJB, similar to the Business service. Set an endpoint URI as you
want or leave it as proposed. JEJB properties are the same as for Business Service in step
4, please choose the same Clients jar. Leave all values in other tabs as proposed by de-
fault. Now we are ready to implement the Message Flow around this EJB. Refer to the
following screenshot:
Search WWH ::
Custom Search