You create EIS import and export components with the enterprise service discovery wizard. You create business objects from data structures with the enterprise data discovery wizard. These wizards are discussed in this section.
Using
the enterprise service discovery wizard is similar no matter what resource
adapter you use and EIS system you access. When you launch the wizard, you
first select the resource adapter you will use. If the resource adapter is
not in the list, you can import a resource adapter at that time.
Once
you have the resource adapter, you select it and proceed to use the enterprise
service discovery wizard.
You begin by configuring
the connection settings. In this PeopleSoft example, for instance, you would
specify the component interface JAR for the resource adapter, the userid and
password for the server, the server name and its port number. Were you working
with another resource adapter that complied with the Enterprise Metadata Discovery
specification, you would of course have different connection properties.
You next run a query to find
the metadata on an EIS system. The query returns the objects it finds. From
this set of objects, you build the business object that will end up in your
component. You may be prompted for whether you want lower level information
available to you. You may also use a filter as you work with the metadata..
In the next page, you make a decision that will determine if
you create an import or an export component. An outbound service type, the
default, results in an import component. Inbound results in an export component.
Other fields determine the namespace to be used and the functions on the EIS
server your component will invoke. In the example that follows, there are
functions like create, update delete and so on.
You
are ready to create your component. In the following page, you can change
the module or define a new one for your component. You can add a folder to
contain your generated service files. You provide a name for your service
and make a choice if you wish to deploy the resource adapter with the module. Deploying or not deploying the resource adapter in the module discusses why you
might want to deploy your resource adapter. You can choose between two types
of managed connections. The differences are discussed in Using connection properties specified on a server or using the discovered ones.
You may also add the J2C Authentication Data (the JAAS alias name) if one
is specified at the server.
You may also edit
the operation names. These names map to the functions at the EIS server. You
might edit them for the same reason that you named the service you will create
with your component; the names that appear are picked from the names found
at the server and may not be relevant to your service. For example, you might
rename createPSOFTPoCompInterface to simply create.
Your service is created and added to the module.
If you select your business object, the relationship of this business object
to others appears in the references view. Opening the business object shows
the business object you created in the business object editor. You can also
see the interface, which the enterprise discovery wizard also created for
you. Opening the service you created in the assembly editor shows the icon
representing an EIS component. In the example that follows, it is an import
component.
Selecting this component opens lower
level details in the properties view of the assembly editor such as the list
of operations, the interface name and the binding information. These details
are explained in more depth in the task help, which shows the construction
of several EIS import and export components using the enterprise service discovery
wizard.
The
enterprise data discovery wizard lets you create business objects for your
services based on applications available locally. You begin by launching the
wizard and selecting the map you want from the data source to the business
object. In the case of the example shown, it is a map between a COBOL program
and a business object. You then browse to the source file.
In the next
page, the data structure of the source is shown. You select the platform and
code page required and make a selection of the particular data structure you
want represented in your business object. For example, you may only need a
subset of what you see in the enterprise data discovery wizard. When you click
Apply, you get the data structure you have selected from the source file.
The final page opens and you specify the names, styles and
folder for the properties. Note that you can choose to change or create a
new module at this point. Remember, at this point nothing has been generated.
The name will be the selected data structure name if you do not change it.
For our example, we changed it to DeptPersonnelInfo. Specifying a folder is
recommended since otherwise all generated files will be put in the root module
folder. Generation style lets you specify a variation of generated names.
Clicking Finish completes the generation of your business object.
Selecting the business object the enterprise data discovery
wizard has produced, you can open it in the business object editor to see
it or edit it.