FMW Composer is a client application that provides a graphical user interface for describing the elements of a Fusion Middleware topology, such as the hosts, Oracle homes, domains, servers, and so on.
With FMW Composer, you can create a topology from scratch, as well as make edits and updates to an existing topology. Once you finish creating or updating a topology, you can save your topology to a topology file, which can be a XML or JSON file. You can use this file as input with the Oracle Lifecycle Management (LCM) Tools to configure and manage your Fusion Middleware environment. To learn more about what you can do with the LCM Tools, see About the Lifecycle Management Tools in Oracle Fusion Middleware Configuring Oracle Fusion Middleware Using Lifecycle Management Tools.
The following help topics provide information on using the menus, toolbar, panels, and other features in Composer:
The File menu includes commands for creating a file, opening a file, saving a file, displaying the Settings page, and quitting FMW Composer.
Command | Description |
---|---|
New |
Creates a new, empty file. The following file types are available:
Shortcut: |
Open File... |
Opens an existing file. Shortcut: |
Save |
Saves the current page to a file. If the current page is already associated with a file, the page will be saved to that file. If the current page is not associated with a file, you will be prompted to specify a directory location on your system. The file name is automatically generated using the Shortcut: |
Save As... |
Saves the current page to a file. You can save the file either as a XML file or JSON file. You will be prompted to specify a directory location on your system. The file name is automatically generated using the Shortcut: |
Settings |
Displays the Settings page. Use the Settings page to display and set Composer settings, such as the directory path of the Oracle home and the wallet file for environment credentials. On the Settings page, you can:
|
Exit |
Exits Composer. Any unsaved changes will be discarded. |
The Edit menu includes commands for adding, assigning, removing, and deleting elements. This menu is context sensitive (the menu options that you can choose from are related to the selected element on the screen).
You can invoke these commands using one of the following methods:
From the Edit menu itself.
From the right-click (context) menu.
Note that this menu will only list the actions that you can perform on the selected element.
Use the Help menu to get help using the various features of the Oracle Lifecycle Management (LCM) Tools. You can also use this menu to obtain and verify the version number for FMW Composer.
Command | Description |
---|---|
About the Life Cycle Tools |
Provides an introduction to the Oracle LCM Tools. |
Getting Started |
Provides information on how to get started using the LCM Tools, such as locating the LCM Tools in an Oracle home, using the LCM Tools tutorial, and getting help with Composer. |
Tutorial |
Displays a tutorial that shows you step-by-step how to use the LCM Tools to configure a sample Oracle SOA Suite topology. |
About |
Displays the version number and build information for Composer. |
The FMW Composer toolbar appears at the top of the window. You can use the toolbar to create a new file, save a file, add an element to the topology, delete an element, and more.
Some of the toolbar buttons might appear grayed out. These options are context sensitive and become enabled only after you select an element on the current page. For example, if you select a host, then only the buttons related to that host are enabled.
Button | Description | Menu Location |
---|---|---|
Creates a new, empty file. The following file types are available:
|
Select File and then New |
|
Opens an existing file. |
Select File and then Open... |
|
Saves the current page to a file. If the current page is already associated with a file, the page will be saved to that file. If the current page is not associated with a file, you will be prompted to specify a directory location on your system. The file name is automatically generated using the |
Select File and then Save |
|
Adds a new element (host, Oracle home, etc.) to the active file. This button is only available for the Topology and Domain Profile file types. This button is context-sensitive (the elements you can choose from are related to the selected element on the screen). |
Edit |
|
Assigns or maps an existing element to another element. For example, you might use this button to assign an Oracle home to a host. This button is context-sensitive (the elements you can assign are related to the selected element on the screen). |
Edit |
|
Removes or unassigns an existing element from another element. For example, you might use this button to remove an Oracle home from an assigned host. You must select the element you want to remove. |
Edit |
|
Deletes an existing element from the active file. This button is only available for the Topology and Domain Profile file types. You must select the element you want to delete. |
Edit |
|
Use this option to get help for an element on the screen. After you click this button, select an element (for example, a host) on the screen to open the online help for that element. |
N/A |
The Topology Properties panel allows you to specify information about the topology file you are editing, such as the name and version of the file.
Property | Description |
---|---|
ID |
A unique name for the topology file used to identify this file from other files. |
Version |
The version number of this topology file. For example, If you need to make an update to the topology, this property allows you to create multiple versions of the file and distinguish them from one another. |
FMW Version Range |
This field identifies the minimum or exact Fusion Middleware version of the file. For example, |
Variables |
Use this field to define any variables you want to use when setting values in the topology file. A variable represents an actual value in your environment. A variable includes two parts:
|
Directories |
To add a LDAP directory component to the topology, click . A dialog box will appear where you can specify information about a directory. To remove a directory component from the topology, select the name of the directory and click . To edit the information for an existing directory component, select the name of the directory and click . |
Miscellaneous Properties |
Use this field to add additional property settings for a topology.
|
The Directory panel contains fields that you can use to specify information (or attributes) for a LDAP directory.
Attribute | Description |
---|---|
ID |
A unique name used to identify the directory. The default ID is dir. |
Type |
Use the drop-down list to specify the directory type of the LDAP server. Valid types include:
|
Port |
The port number of the LDAP server. |
RCU Connect String |
The connect string used by RCU to connect to the database: db_host:db_port:service_name Where db_host is the host name of the machine on which the database resides, db_port is the listener port of the database, and service_name is the service name identified for the database. |
Credential |
The password used to connect to the LDAP server. Click select to select the password from the wallet or to add the password to the wallet. When you click select, a dialog box will appear with a list of credentials to choose from only if you have provided the path to a wallet on the Composer Settings page (located in the File menu).
|
Search Base |
The search base for the LDAP server in DN format. |
User Search Base |
The user search base for the LDAP server in DN format. |
Group Search Base |
The group or enterprise search base for the LDAP server in DN format. |
LBR URL |
Load balancer URL |
Miscellaneous Config |
Use this field to add additional configuration property settings for a directory.
|
A blueprint file lists and defines the configuration templates required to create a domain.
Attributes Tab
Use the Attributes tab to specify information about the blueprint file.
Attribute | Description |
---|---|
ID |
A unique name for the blueprint used to identify this blueprint file from other files. |
Version |
The version number of this blueprint. For example, If you need to make an update to the blueprint, this property allows you to create multiple versions of the file and distinguish them from one another. |
FMW Version Range |
This field identifies the minimum or exact Fusion Middleware version of the file. For example, |
Referenced Blueprints |
Use this field to add a blueprint to the current file, edit an existing blueprint, or remove a blueprint. |
Templates Tab
Use the Templates tab to add or remove domain templates from the blueprint.
You can use the domain profile file type to specify information about a domain, such as server, cluster, template, and server group information.
Attributes Tab
Use the Attributes tab to specify information about the file.
Attributes | Description |
---|---|
ID |
A unique name for the domain profile file used identify this domain profile from other files. |
Version |
The version number of this file. For example, If you need to make an update to the file, this property allows you to create multiple versions of the file and distinguish them from one another. |
FMW Version Range |
This field identifies the minimum or exact Fusion Middleware version of the file. For example, |
External Profile |
Use this field to add a domain profile to the current file. |
Blueprints Tab
Use the Blueprints tab to define the blueprints for the domain.
Click to add a blueprint to the domain.
If you have not provided the path to the Oracle home directory on the Composer Settings page (located in the File menu), you will be prompted to specify the path to the Oracle home.
To edit a blueprint, select the blueprint from the list and click .
This will open the blueprint file in a new tab.
To remove a blueprint from the domain, select the blueprint from the list and click .
Server Groups Tab
The Server Groups tab displays a list of server groups only if at least one of the templates in a selected blueprint defines a server group. You can assign a server group to a server or cluster.
You can use FMW Composer to create, define, and edit the elements of your topology. Specifically, FMW Composer has a context-sensitive panel located on the right side of the screen with fields where you can specify information about each element.
You can access a panel by selecting an element on the screen.
For more information about each element panel, see the following topics:
The Host panel contains fields that you can use to specify information (or attributes) for a host in the topology.
Attribute | Description |
---|---|
ID |
A unique name for the host used to identify this host from other elements. When you add a new host, the default ID is host1. If host1 is already used in the topology, FMW Composer will default to host2, then host3, and so on. |
Address |
The primary IP address or DNS name of the host. |
Credential |
The credential from the wallet that will be used to connect to the host. Click select to select the credential for the host from the wallet or add the credential to the wallet. When you click select, a dialog box will appear with a list of credentials to choose from only if you have provided the path to a wallet on the Composer Settings page (located in the File menu).
|
LCM Listen Port |
The port that the LCM Agent on this host is listening for REST requests on. |
Directory |
Use this field to add a directory to this host. Click change to select a directory for the host. A dialog box will appear with a list of directories only if you added and defined at least one directory on the Topology Properties panel. After you add a directory to this host, you can click edit to edit the information for that directory. |
Additional Addresses |
Use this field to specify additional IP addresses or DNS names for a host. |
The Oracle Home panel contains fields that you can use to specify information (or attributes) for an Oracle home in the topology.
Attribute | Description |
---|---|
ID |
A unique name for the Oracle home used to identify the Oracle home from other elements. When you add a new Oracle home, the default ID is home1. If home1 is already used in the topology, FMW Composer will default to home2, then home3, and so on. |
Type |
Indicates whether the Oracle home is on a local file system (and disk) or on a shared file system (and disk). Valid values are local or shared. |
Path |
The full path to a directory on the file system. This is the path to the directory where the Oracle home is (or will be) installed on your system. |
Java Home |
The full path to a directory on the file system. This is the path to a directory where a JDK is installed on your system. For example, |
Inventory Location |
The location where you want to create your central inventory. This field is required if you are installing any Oracle product for the first time on a host that is running UNIX or Linux system software. For more information, see About the Oracle Central Inventory in Oracle Fusion Middleware Installing Software with the Oracle Universal Installer. |
Installations |
Installation data required to create an Oracle home and install a product.
|
Patches |
List of patches to be applied to the Oracle home.
|
The Domain panel contains an Attributes tab that you can use to specify information (or attributes) for a domain in the topology. The Blueprints and Server Groups tabs allow you to add domain templates and server groups, respectively.
Attributes Tab
Attribute | Description |
---|---|
ID |
A unique name for the domain used to identify this domain from other elements. When you add a new domain, the default ID is domain1. If domain1 is already used in the topology, FMW Composer will default to domain2, then domain3, and so on. |
Name |
The name of the domain. |
Type |
Indicates whether the domain directory is on a local file system (and disk) or on a shared file system (and disk). Valid values are local or shared. |
Path |
The full path to a directory on the file system. This is the directory where the domain is (or will be) located on your system. |
Application Path |
The full path to a directory on the file system. This is the directory where selected applications related to the domains you configure will be created. |
Admin Credential |
The administrative credential from the wallet that will be used to access the domain’s WebLogic Administration Server. Click select to select the credential from the wallet or add the credential to the wallet. When you click select, a dialog box will appear with a list of credentials to choose from only if you have provided the path to a wallet on the Composer Settings page (located in the File menu).
|
Admin Server Url |
The URL used to connect to the domain’s Administration Server in the following format: http://adminserver_host:adminserver_port Where:
|
External Profile |
Use this field to select a domain profile for the domain. |
defaultCoherencePort |
The port of the Coherence cluster. |
Tuning Parameter Variables |
Use this field to define any variables you want to use when setting values for tuning parameters. A variable represents an actual value in your environment. A variable includes two parts:
The following reserved variables are fixed and cannot be changed:
|
Tuning Parameter Imports |
Use this field to import tuning parameter settings from a separate tuning parameter XML or JSON file. |
Tuning Parameter Settings |
Composer provides a predefined list of tuning parameter settings that you can apply to a domain.
|
Tuning Parameter External Settings |
Use this field to add, remove, or edit an external tuning parameter setting (either MBean or WLST).
|
Blueprints Tab
Use the Blueprints tab to define the blueprints for the domain.
Click to add a blueprint to the domain.
If you have not provided the path to the Oracle home directory on the Composer Settings page (located in the File menu), you will be prompted to specify the path to the Oracle home.
To edit a blueprint, select the blueprint from the list and click .
This will open the blueprint file in a new tab.
To remove a blueprint from the domain, select the blueprint from the list and click .
Server Groups Tab
The Server Groups tab displays a list of server groups only if at least one of the templates in a selected blueprint defines a server group. You can assign a server group to a server or cluster in this domain.
The Server panel contains an Attributes tab that you can use to specify information (or attributes) for a server in the topology. The Server Groups tab allows you to select and assign server groups to the selected server.
Attributes Tab
Attribute | Description |
---|---|
ID |
A unique name for the server used to identify this server from other elements in a domain. When you add a new server to a domain, the default ID is server1. If server1 is already used in the domain, FMW Composer will default to server2, then server3, and so on. |
Is Admin Server |
Select this option if this server is the Administration Server. |
Name |
Name of the server. |
Listen Address |
The IP address or DNS name this server uses to listen for incoming connections. |
Listen Port |
The port that this server uses to listen for regular (non-SSL) incoming connections. |
SSL Listen Port |
The port that this server uses to listen for SSL incoming connections. |
Tuning Parameter Variables |
Use this field to define any variables you want to use when setting values for tuning parameters. A variable represents an actual value in your environment. A variable includes two parts:
The following reserved variables are fixed and cannot be changed:
|
Tuning Parameter Imports |
Use this field to import tuning parameter settings from a separate tuning parameter XML or JSON file. |
Tuning Parameter Settings |
Composer provides a predefined list of tuning parameter settings that you can apply to a server.
|
Server Groups Tab
The Server Groups tab displays the server groups assigned to the server.
Click to select server group(s) to assign to the server. A dialog box will appear with a list of server groups only if at least one of the templates in a selected blueprint defines a server group.
Click to remove or unassign the selected server groups from the server.
The Node Manager panel contains fields that you can use to specify information (or attributes) for a Node Manager in the topology.
Attribute | Description |
---|---|
ID |
A unique name for the Node Manager used to identify this Node Manager from other elements. When you add a new Node Manager, the default ID is nm1. If nm1 is already used in the topology, FMW Composer will default to nm2, then nm3, and so on. |
Name |
Name of the Node Manager. |
Credential |
The credential from the wallet that will be used to connect to the Node Manager. Click select to select the credential from the wallet or add the credential to the wallet. When you click select, a dialog box will appear with a list of credentials to choose from only if you have provided the path to a wallet on the Composer Settings page (located in the File menu).
|
Tuning Parameter Variables |
Use this field to define any variables you want to use when setting values for tuning parameters. A variable represents an actual value in your environment. A variable includes two parts:
The following reserved variable is fixed and cannot be changed:
|
Tuning Parameter Imports |
Use this field to import tuning parameter settings from a separate tuning parameter XML or JSON file. |
Tuning Parameter Settings |
Composer provides a predefined list of tuning parameter settings that you can apply to a Node Manager, such as the Node Manager port.
|
Tuning Parameter External Settings |
Use this field to add, remove, or edit an external tuning parameter setting (either MBean or WLST).
|
The Cluster panel contains an Attributes tab that you can use to specify information (or attributes) for a cluster in the topology. The Server Groups tab allows you to select and assign server groups to the selected cluster.
Attributes Tab
Attribute | Description |
---|---|
ID |
A unique name for the cluster used to identify this cluster from other elements in a domain. When you add a new cluster to a domain, the default ID is cluster1. If cluster1 is already used in the domain, FMW Composer will default to cluster2, then cluster3, and so on. |
Name |
The name of the cluster. |
Tuning Parameter Variables |
Use this field to define any variables you want to use when setting values for tuning parameters. A variable represents an actual value in your environment. A variable includes two parts:
The following reserved variables are fixed and cannot be changed:
|
Tuning Parameter Imports |
Use this field to import tuning parameter settings from a separate tuning parameter XML or JSON file. |
Tuning Parameter Settings |
Composer provides a predefined list of tuning parameter settings that you can apply to a cluster, such as the cluster address.
|
Tuning Parameter External Settings |
Use this field to add, remove, or edit an external tuning parameter setting (either MBean or WLST).
|
Server Groups Tab
The Server Groups tab displays the server groups assigned to the cluster.
Click to select server group(s) to assign to the cluster. A dialog box will appear with a list of server groups only if at least one of the templates in a selected blueprint defines a server group.
Click to remove or unassign the selected server groups from the cluster.
The Database panel contains fields that you can use to specify information (or attributes) for a database associated with the topology.
Attribute | Description |
---|---|
ID |
A unique name for the database used to identify the database from other elements. When you add a new database, the default ID is database1. If database1 is already used in the topology, FMW Composer will default to database2, then database3, and so on. |
Vendor |
The type of database server. Valid values are ORACLE, EBR, SQLSERVER, IBMDB2, or MYSQL. |
Driver Class |
The fully qualified Java class name of the non-XA JDBC driver. |
XA Driver Class |
The fully qualified Java class name of the XA JDBC driver. |
RCU Connect String |
The connect string used by RCU to connect to the database: db_host:db_port/service_name Where db_host is the host name of the machine on which the database resides, db_port is the listener port of the database, and service_name is the service name identified for the database. |
DBA Credential |
The credential from the wallet that will be used for actions that require DBA privileges. Click select to select the credential from the wallet or add the credential to the wallet. When you click select, a dialog box will appear with a list of credentials to choose from only if you have provided the path to a wallet on the Composer Settings page (located in the File menu).
|
DBA Role |
Select the database user role from the drop-down list:
|
The Node panel contains fields that you can use to specify information (or attributes) for a node assigned to a database.
Attribute | Description |
---|---|
ID |
A unique name for the node element used to identify the node from other elements. When you add a new node to a database, the default ID is node1. If node1 is already used within a database, FMW Composer will default to node2, then node3, and so on. |
Connect String |
The JDBC URL that is used to connect to the database repository. For example, for Oracle databases: jdbc:oracle:thin:@db_host:db_port/service_name Where db_host is the host name of the machine on which the database resides, db_port is the listener port of the database, and service_name is the service name identified for the database. |
The Data Source panel contains fields that you can use to specify information (or attributes) for a data source.
Attribute | Description |
---|---|
Type |
The data source type. Valid types include:
|
XA |
Specifies whether an XA driver must be used for the data source. |
Tuning Parameter Variables |
Use this field to define any variables you want to use when setting values for tuning parameters. A variable represents an actual value in your environment. A variable includes two parts:
The following reserved variables are fixed and cannot be changed:
|
Tuning Parameter Imports |
Use this field to import tuning parameter settings from a separate tuning parameter XML or JSON file. |
Tuning Parameter Settings |
Composer provides a predefined list of tuning parameter settings that you can apply to a data source, such as a timeout on a data source.
|
Tuning Parameter External Settings |
Use this field to add, remove, or edit an external tuning parameter setting (either MBean or WLST).
|
The Schema panel contains fields that you can use to specify information (or attributes) for a schema.
Attribute | Description |
---|---|
Shared |
Use the drop-down list to specify whether the schema is shared with other domains. Valid values are No, Primary, or Yes.
|
Credential |
The password for the schema. Click select to select the password from the wallet or add the password to the wallet. When you click select, a dialog box will appear with a list of credentials to choose from only if you have provided the path to a wallet on the Composer Settings page (located in the File menu).
|
Prefix |
Prefix for your schema. |
Component Info |
Full path to the location of the |
Storage Location |
Full path to the location of the |
Tablespace |
Tablespace name of the component. |
Temp Tablespace |
TEMP tablespace name of the component. |
Auxiliary Schema Credentials |
The schema passwords for auxiliary schemas. |
The Web Tier panel contains fields that you can use to specify information (or attributes) for a web tier component within the topology.
Attribute | Description |
---|---|
ID |
A unique name used for the web tier component. When you add a new web tier, the default ID is tier1. If tier1 is already used in the topology, FMW Composer will default to tier2, then tier3, and so on. |
Name |
Name of the web tier component. |
Type |
Use the drop-down list to specify the component type:
|
Address |
The listen address to use for this component. |
Admin Credential |
Click select to select the password from the wallet or add the password to the wallet. When you click select, a dialog box will appear with a list of credentials to choose from only if you have provided the path to a wallet on the Composer Settings page (located in the File menu).
|
The Virtual Host panel contains fields that you can use to specify information (or attributes) for a virtual host.
Attribute | Description |
---|---|
ID |
A unique name used for the virtual host. When you add a new virtual host to a web tier component, the default ID is host1. If host1 is already used within a web tier, FMW Composer will default to host2, then host3, and so on. |
Name |
Name of the virtual host. |
Server Address |
The server address for this virtual host. |
Server Admin |
The email address for the server administrator. This is displayed on error pages to help the user contact technical support. |
Protocol |
The protocol to use (HTTP or HTTPS). |
Attribute | Description |
---|---|
ID |
A unique name for the Location element. When you add a new location element to a virtual host, the default ID is loc1. If loc1 is already used within a virtual host element, FMW Composer will default to loc2, then loc3, and so on. |
WebLogic Host |
The host name for the Administration Server. |
WebLogic Port |
The port for the Administration Server. |
WebLogic Cluster |
List of Oracle WebLogic clusters that can be used for load balancing. |
Handler |
weblogic-handler |
WL Proxy SSL |
Valid values are ON or OFF. |
WL Proxy SSL Pass Through |
Valid values are ON or OFF. |
Tuning parameters allow you to customize or tune additional configuration settings for various elements.
FMW Composer provides a predefined list of parameters that you can edit for the following elements:
Domain
Server
Cluster
Node Manager
Data Source
To add a tuning parameter for an element, select that element on the current page. Then, in the Attributes panel, click under Tuning Parameter Settings. This will display a dialog box with a drop-down menu of available tuning parameters you can set.
The validation panel allows you to quickly see and correct any errors that occur while you are editing a topology, blueprint, or domain profile.
To locate an error in FMW Composer, select the error message from the list, and then click . You can also double-click the error message to go straight to the panel that contains the error.
After you correct the errors, click to refresh the list and verify that the errors have been resolved.