Using Natural Business Services, you can create all the components of a business service, including Natural object subprograms that perform maintenance and browse functions and GUI dialogs or web pages that communicate with the object subprograms. Communication between server and client components of an application is performed by a combination of EntireX and Natural RPC (or EntireX configured to use TCP/IP), as well as Natural Business Services middleware components. The middleware components encapsulate calls to EntireX on the client and server. The following diagram shows the architecture of character-based Natural applications and business service components:
This section describes these components according to the platforms on which the components run.
This section describes the server components for Natural Business Services. The following topics are covered:
The following table lists the components required for development purposes:
|Subprograms written in
Natural that do not contain user interface code (for
example, WRITE, DISPLAY, PRINT, INPUT, and REINPUT statements) or navigation
code (for example, PF-key processing). They can be existing
Natural subprograms or they can be wizard-generated
in NaturalONE. Existing subprograms can be wrapped
together so one server subprogram accesses more than one subprogram. The
Business Service wizard can wrap the subprograms it generates, as well as use
Natural Construct models internally to generate
subprograms that perform maintenance and browse functions on the server. The
wizard chooses the appropriate model based on criteria the user has selected.
These models are: Object-Browse-Subp, Object-Maint-Subp,
Object-Browse-Select-Subp, and Object-Generic-Subp.
The same set of business objects can be accessed from character-based Natural applications, client/server applications, and web applications. This ensures that the integrity of business data is preserved, independent of the presentation layer, and existing code can be preserved.
|Character user interface (optional; only used at sites that access the business service from a 3270 client)
|Non-distributed Natural applications created with Natural Construct accessing subprograms directly (for example, subprograms generated by the Object-Maint-Dialog model).
The following table lists the components required for runtime purposes:
|Business Service Administration subsystem
|Server subsystem that allows system
administrators, application administrators, and developers to set up and manage
system and application environments.
|Runtime component that transfers
messages between Windows or the web server and the
EntireX can be configured to use either native
TCP/IP or Entire Net-Work as the transport layer.
EntireX performs the following runtime functions:
|Natural RPC server
|Server that provides a common interface
and EntireX services for
Natural subprograms in the application. The main
functions of the Natural RPC server are to:
|Business Service repository
|Directory structure containing the business service metadata, such as domains, descriptions, methods, method descriptions, as well as security access to these services and methods.
You can create business services with NaturalONE's Service Development plug-in. The plug-in links to Natural Business Services from NaturalONE. Using the plug-in, you can configure the business service connections, search for business services, and invoke the wizards.
|Business Services menu
|Menu used to perform tasks such as the
|Natural Server view
|Tree view of the business repository. You
can perform tasks such as the following:
|You can define preferences such as:
|Business Service wizard
|Creates new business service definitions in the local workspace.
|Domain and Steplib wizards
|Creates domain and steplib definitions in the local workspace.
|Creates Java classes to access your business service from the client.
|Web Service wizard
|Creates Java classes and Web services definitions.
|Used to inspect and update NBS security definitions.