In TKU February 2009 we added code to prevent the Software Instance attribute, 'oc4j_instance', being added to _tw_meta_data_attrs twice.
In TKU March 2009 the way the patterns create the model of Oracle Application Server was re-worked to make it more accurate. Oracle Application Server is a collection of Oracle OC4J (J2EE Container) instances, and this is now reflected by the patterns that model the product.
The original Application Server pattern has been broken out into two patterns, with a first-order SI pattern for Oracle Application Server OC4J instance being used as a building block for second-order Oracle Application Server pattern
In addition to this, we added code to ensure all optional additional attributes were displayed in the Software Instance when they were populated
In TKU July 2009 we added the ebs_suite attribute to the Oracle Application Server SI. This attribute is key in modeling a speific Relationship correctly, as it allows the Oracle E-Business Suite pattern to model a Relationship with the right Oracle Application Server SI.
As a result of the new Oracle Internet Application Server Pattern, we removed a few known versions from the Oracle Application Server Pattern, as these are now fully supported by the Oracle Internet Application Server Pattern.
In TKU August 2010 we enhanced three regular expressions in order to parse the contents of the readme.txt file correctly.
In TKU May 2012 some slight changes were made to the way product version is reported
For the ApplicationServerOC4J pattern, two new attributes, inst_top and oracle_config_home, are now added to the Software Instance. In addition, the server_name attribute is now unset if oracleas_instance_name has no value.
These two attributes, inst_top and oracle_config_home, are now inherited by an Oracle Application Server Software Instance. In addition, code to destroy an aged out Oracle Application Server SI has been added.
In TKU May 2013 Oracle Application Server pattern module patterns were updated to improve identification of very early releases of the product. Path versioning method was also improved.
Finally, version mapping from full version to marketing version (product_version) was improved.
In TKU August 2013 Oracle Web Cache and Oracle Process Manager patterns were migrated to separate modules as they are components of Oracle Fusion Middleware and their evolution is not tied to Oracle Application Server. In the Oracle Application Server module, path versioning mapping table was updated. Furthermore, code performing versioning in OC4J pattern was tidied up, and finally, the relationship Oracle Application Server OC4J Instance SI and Oracle Process Manager was changed from dependency to management (Oracle Application Server OC4J Instance SI managed by Oracle Process Manager) to more accurately reflect the relationship of these entities.
In TKU June 2016 the pattern was updated with the following changes:
In TKU April 2017 the pattern was updated with the following changes: