20-30 Developers Guide for Oracle Application Integration Architecture Foundation Pack
Figure 20–7 Systems page 2 of 2
3. Enter your search criteria and click Search to execute a search for a particular
participating application system.
4.
Use the page elements listed in Table 20–5
to define participating application system registry entries.
Table 20–5 Systems Page Elements
Page Element Description
Delete Select a system row and click Delete to execute the deletion.
Create Click to add a system row that you can use to add a
participating application to the system registry.
Save Click to save all entries on the page.
Internal Id System instance name assigned by an implementer, for example
ORCL 01. This value would be used in transformation and domain value map column names to indicate a system instance.
For example, the value can be used in transformations to identify the requester or provider system.
System Code This is a required value. This value populated to the Enterprise
Business Message EBM header.
System Description Long description of the requester or provider system instance
identified in the System Code field. This value populated to the EBM header.
IP Address IP address of the participating application by which one can
access the participating application endpoint. This value is populated to the EBM Header.
URL This is the hostname and port combination specified in the URL
format by which one can access the participating application. Typically, this is in the form of http:hostname:port. This
value is populated to the EBM Header. This URL is not used by process integrations to access the participating applications web
services, but rather this value is stored for informational purposes. Process integration developers determine which URL
to use as the entry point for a participating application.
Building AIA Integration Flows 20-31
20.4.5.2.3 How to Manage the System Registry Using the SystemRegistration.xml Configuration
File Goal:
Create a systemRegistration.xml configuration file for a Project Lifecycle Workbench process integration project. Create one systemRegistration.xml file per project. The
systemRegistration.xml file is used by the Deployment Plan Generator and AIA Deployment Driver to populate the participating applications used by the process
integration to the Oracle AIA system registry.
This is a progammatic approach to completing the same task that can be completed using the Systems page.
For more information about the Systems page, see Section 20.4.5.2.2, How to Manage
the System Registry Using the Systems Page .
Figure 20–8 illustrates how the values defined in systemRegistration.xml files for each
process integration are used to populate the Oracle AIA system registry.
System Type Provides the system type. For example, Oracle EBIZ. This is a
required value.
Application Type Application being run within the specified system. For example,
a system type of Oracle EBIZ may have an application type value of FMS. This value populated to the EBM header.
Version Provides the version of the application being run by the system.
This value populated to the EBM header.
Contact Name Provides the name of the contact responsible for the system. This
value populated to the EBM header.
Contact Phone Provides the phone number of the contact responsible for the
system. This value populated to the EBM header
Contact E-Mail Provides the email address of the contact responsible for the
system. This value is populated to the EBM header.
Table 20–5 Cont. Systems Page Elements
Page Element Description
20-32 Developers Guide for Oracle Application Integration Architecture Foundation Pack
Figure 20–8 Flow of System Registration Data
Role: Integration developer
To manage your Oracle AIA system registry using the SystemRegistration.xml configuration file:
1.
Create a systemRegistration.xml file for your process integration project.
2.
To add participating application values to the system registry, use the create element provided in the sample XML structure shown in
Example 20–1 .
Example 20–1 AIASystemRegistration.xml
AIASystemRegistration create
MERGE INTO AIA_SYSTEMS sysreg USING dual on dual.dummy is not null and sysreg.SYSTEM_CODE=SampleSEBLDPT003 WHEN NOT
MATCHED THEN INSERT SYSTEM_ID,SYSTEM_INTERNAL_ID,SYSTEM_CODE, SYSTEM_DESC,SYSTEM_IP_ADDR,SYSTEM_URL,SYSTEM_TYPE,APPLICATION_
TYPE,APPLICATION_VERSION,CONTACT_NAME,CONTACT_PHONE,CONTACT_ EMAIL VALUES AIA_SYSTEMS_S.nextval,SampleSEBLDPT003,SampleSEBLDPT003,
Sample Siebel Instance01,10.0.0.1,http: {participatingapplications.SampleSiebel.server.
soaserverhostname}:{participatingapplications.SampleSiebel. server.soaserverport}
ecommunications_enu ,Sample SIEBEL,CRM,{pips.BaseSample.version}
,Siebel contact,1234567891,aiasamples_contactaia.com MERGE INTO AIA_SYSTEMS sysreg USING dual on dual.dummy is
not null and sysreg.SYSTEM_CODE=SamplePortalDPT003 WHEN NOT MATCHED THEN INSERT SYSTEM_ID,SYSTEM_INTERNAL_
Building AIA Integration Flows 20-33
ID,SYSTEM_CODE,SYSTEM_DESC,SYSTEM_IP_ADDR,SYSTEM_URL,SYSTEM_ TYPE,APPLICATION_TYPE,APPLICATION_VERSION,CONTACT_NAME,CONTACT_
PHONE,CONTACT_EMAIL VALUES AIA_SYSTEMSS.nextval, SamplePortalDPT003,SamplePortalDPT003,
Sample Portal Instance 01,10.0.0.1, http:{participatingapplications.SamplePortal.server.
soaserverhostname}:{participatingapplications.SamplePortal.
server.soaserverport} ,Sample Portal,BILLING,{pips.BaseSample.version}
,Portal contact,1234567892,aiasamples_contactaia.com create
AIASystemRegistration
The tokens you create in the create element should be based on the structure of the AIAInstallProperties.xml file.
For example, the following token, {participatingapplications.SamplePortal.server.soaserverhost
name}, was derived from the structure in the AIAInstallProperties.xml file shown in
Example 20–2 :
Example 20–2 AIAInstallProperties.xml
properties participatingapplications
SamplePortal server
soaserverhostnameadc2180948.us.oracle.com soaserverhostname
server ...
participatingapplications properties
Actual values for the tokens in bold are derived from AIA_ INSTANCEconfigAIAInstallProperties.xml during process integration
installation using a deployment plan.
3.
To delete participating application values from the system registry, use the delete element provided in the sample XML structure shown in
Example 20–3 and replace the system code values in bold with the system codes of the
participating applications you want to remove from the AIA application registry.
Example 20–3 delete element in AIASystemRegistration.xml
AIASystemRegistration delete
delete from AIA_SYSTEMS where SYSTEM_CODE=SampleSEBLDPT005 delete from AIA_SYSTEMS where SYSTEM_CODE=SamplePortalDPT005
delete AIASystemRegistration
4.
Save the systemRegistration.xml file to AIA_ HOMEpipsprojectCodeDatabaseObjects.
20-34 Developers Guide for Oracle Application Integration Architecture Foundation Pack
If you are using the Project Lifecycle Workbench in your development methodology, the projectCode folder name is the project code value assigned
to your project in Project Lifecycle Workbench.
If you are not using the Project Lifecycle Workbench, you can assign your own project code value to the folder name.
The Deployment Plan Generator always generates the system registration task in the deployment plan. The system registration task extracts configuration information from
systemRegistration.xml, replaces tokens with actual values from AIAInstallProperties.xml, and executes an SQL statement to populate the
system registry.
If no systemRegistration.xml file is present for the Deployment Plan Generator to leverage, you must manually remove the system registration task from the
deployment plan, or the deployment will fail.
Example 20–4 shows a generated deployment plan that includes the system
registration task to register systems for projectCode ABCProcessInt:
Example 20–4 System Registration Task in Generated Deployment Plan
DeploymentPlan Configurations
... SystemRegistration database=fp.db.aia resourceFileName=AIA_
HOMEpipsABCProcessIntDatabaseObjectssystemRegistration.xml delimiter=
action=create ...
Configurations DeploymentPlan
The AIA Deployment Driver reads the deployment plan, replaces the tokens from the systemRegistration.xml with actual values from
AIAInstallProperties.xml, and executes the system registration SQL statement to populate the system registry.
Example 20–5 shows the SQL content extracted by the AIA Deployment Driver:
Example 20–5 SQL Content Extracted by AIA Deployment Driver
MERGE INTO AIA_SYSTEMS sysreg USING dual
on dual.dummy is not null and sysreg.SYSTEM_CODE=SampleSEBL WHEN NOT MATCHED THEN INSERT
SYSTEM_ID,SYSTEM_INTERNAL_ID,SYSTEM_CODE,SYSTEM_DESC,SYSTEM_IP_ADDR,SYSTEM_ URL,SYSTEM_TYPE,APPLICATION_TYPE,APPLICATION_VERSION,CONTACT_NAME,CONTACT_
PHONE,CONTACT_EMAIL VALUES AIA_SYSTEMS_S.nextval,Siebel,SampleSEBL,Sample Siebel Instance
01,10.0.0.1,http:siebel.us.oracle.com:7001ecommunications_enu, SIEBEL,CRM,1.0, Siebel contact,1234567891,SiebelcontactSiebel.com
Ensure that if you are deploying multiple Project Lifecycle Workbench process integration projects and therefore have multiple systemRegistration.xml files,
that participating applications being added to the system registry entries are checked for existence before being added. Duplicate requests cause an SQL exception due to
primary key and unique value constraints enabled on the system registry table.
Building AIA Integration Flows 20-35
You can perform this check by including the text in bold in the SQL content above. If a participating application value is found to be a duplicate, it will not be created. If it is
unique, it will be created.
The AIA Deployment Driver extracted this example SQL content based on replacing tokens from systemRegistration.xml with
Example 20–6 data provided in AIA_
INSTANCEconfigAIAInstallProperties.xml:
Example 20–6 Sample SQL Content Extracted by AIA Deployment Driver
?xml version=1.0 encoding=UTF-8? properties
participatingapplications siebel
http hostsiebel.us.oracle.comhost
port7001port http
internal idSiebelid
internal version1.0version
siebel ...
participatingapplications properties
20.4.6 Identifying and Creating the EBF
