Last updated on OCTOBER 04, 2016
Applies to:Oracle WebLogic Server - Version 22.214.171.124.0 and later
Oracle Web Services Manager - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Using the Fusion Middleware 12.2.1 provisioning framework, which is heavily based on WLST code, to automate the domain generation process. The following documentation is being used as a guide for this:
The chapter being followed is "3.2 Creating and Updating a WebLogic Domain".
This chapter currently shows an example "3-3 Creating a Domain From Multiple Templates", which illustrates an approach to be taken for the creation of a domain.
According to this documentation, what this framework does is start the WLST interpreter in offline mode, load various WLS and FMW templates (e.g. OWSM), create data sources, managed server instances, cluster and node manager settings, assign resources, and finally write the new domain configuration to the file system, just as the Config Wizard would do.
The WebLogic Server instances of such a newly created domain start up fine, but the wsm-pm service endpoints are not published to the service table, thus rendering the wsm-agent > wsm-pm interaction non-functional (auto-discovery / cross-component-wiring fails) until the endpoints are published manually via the EM console.
If using this approach to roll out hundreds of domains, this is not practical. Why is the initial publishing not functional?
Is there a way to manually setup the cross component wiring as is possible through the EM console?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms