•
Note:
1. Log in to Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.
2.
3. From the Oracle Cloud menu, select Setup -> Getting Started. Click the Setup link next to Tuxedo in the left panel.From the Getting Started: Tuxedo page, you need to complete the the following required setup steps. Click on a tab in the left to show the related setup page in the right side detail pane.
1.
2. In the Create PaaS Infrastructure Zone: General page, enter the target name, name, and description for the zone. Click Next.
3. Click Add to add one or more host members to the zone. The hosts that you select cannot be present in more than one PaaS Infrastructure Zone. Click Next.
4. In the Create PaaS Infrastructure Zone: Credentials page, specify the host credentials that are to be used for provisioning all targets in this zone. The credentials provided should be of global credential type (valid across the members in the zone) and owned by the current user. Click Next.
• Maximum CPU Utilization: The average CPU utilization percentage for the past 7 days.
• Maximum Memory Allocation: The average memory allocation for the past 7 days.
6. Click Next. In the Create PaaS Infrastructure Zone: Characteristics page, specify the target properties such as cost center, lifecycle status, location, and so on.
7. Click Next. The Create PaaS Infrastructure Zone: Roles page appears. A PaaS Infrastructure Zone can be made available to a restricted set of self service users with the EM_SSA_USER role. Click Add to add and select the roles that can access this PaaS Infrastructure Zone.
8. Click Next. The Create PaaS Infrastructure Zone: Review page appears. Review the details of the zone being created and click Submit to create the zone.
1.
2. Click Create. The Create Tuxedo Pool: General page appears. Enter a name and description for the Tuxedo Pool. Select the PaaS Infrastructure Zone in which the Tuxedo pool is to be created. Click Next.
3. In the Members page, select the platform of the hosts you are going to add. The Host table filters all the hosts running on the selected platform.
4.
Note: For the existing domain, if IsHostExclusive of the domain package was configured to true, you can choose to keep all primary directory structure and deploy to the same directories on the target host.
7. In the Target Properties region, specify the characteristics that will be used to tag and identify the target properties. Click Next.The Tuxedo profile uses the Tuxedo domain package to provision service instances. Before creating a Tuxedo profile, you must have created the desired domain package. You can create it from scratch or from an existing domain using the introspection feature in the Enterprise Manager Console. For more information, refer to Introspecting an Existing Domain.
1.
4. Click Add and select the product you want to add.Oracle Tuxedo, Oracle Tuxedo Application Runtimes, Oracle Tuxedo Patch, and Other Products can be configured in the profile. Default installation scripts (Perl script) is provided for installing these products. You can specify the default scripts for special installation purpose. When configuring other products, installation location and environment variables are required to tell provisioning procedure where the product to be installed and what runtime environment variables should be exported to applications. PROD_DIR,ORA_HOME, and BASE_DIR can be used as the marco in runtime variables. The macro format is ${macro name}.
Note: ${ORA_HOME} is used as the default home name in Oracle inventory. it must not be used before.
5. (Optional) If you want to deploy the Tuxedo domain, add a domain package to the profile and click Next. Currently, only one domain package can be configured.
6. Review the information and click Submit to create the Tuxedo profile.
1.
1.
2. Click Create. Enter a name and description for the service template.
Note: If you want to create a new template with similar configuration settings of an existing service template, you can get a quick start by selecting that service template in the list and click Create Link to launch the creating wizard with all configured parameters loaded.
3.
4. Click Next. In the Characteristics page, specify the characteristics that will be used to tag and identify the target properties. Service instances created from the template will have the characteristics.
5. Click Next. In the Resource Providers page, Click Add to select the Tuxedo Pool into which the service instances are to be provisioned.
6. Click Next. In the Configuration page, specify the parameters that will be used to provision service instances according to onscreen descriptions.
7. Click Next. In the Roles page, click Add to select the self service user roles to which this service template will be available. All users belonging to the selected role can use this service template.
8. Click Next. Review the information entered so far and click Submit.
1.
3. Click Apply.
Note: Before using Chargeback, it is assumed that you have read Chargeback Administration in Enterprise Manager Cloud Administration Guide. Make sure that you have deployed Oracle Consolidation Planning and Chargeback plugin. If Oracle Consolidation Planning and Chargeback is absent, deploy it following Managing Plug-Ins in Enterprise Manager Cloud Administration Guide.
2. Click Create drop down list, select Plan to create a new Tuxedo chargeback plan.
3. Click Add under Entity Types. In the Add Entity Types window, make sure Oracle Tuxedo Machine is selected.
4. In the Oracle Tuxedo Machine page, click Add to add Chargeback items.
5. Click Configure Cost Center to configure cost center. For more information, see Chargeback Administration in Enterprise Manager Cloud Administration Guide.
6. Click Configure Targets to assign the Chargeback plan to an existing Tuxedo Machine.
Note: Before using the Tuxedo self service portal, the EM_SSA_USER role must have been configured in the Paas Infrastructure Zone, Quotas, and Service Templates definition.To view the Tuxedo Self Service Portal, log in to Enterprise Manager as a user with EM_SSA_USER role. Select Enterprise -> Cloud -> Self Service Portal, and click Tuxedo Cloud Services.Select columns from the View menu to view more details about the request. You can select a scheduled request and click Reschedule to reschedule the request. To delete a request, select the request and click Delete.
•
1. Click Create Instance in the Home page of the Tuxedo Cloud Self Service Portal.
2. The Service Catalog - Create Instance window appears. A list of service templates available to the self service user is displayed. Choose a service template and click Select to launch the Create Instance wizard.
4. In the Instance Duration region, specify the schedule for the instance.
5. Click Next. The Characteristics page appears.
7. Click Next. The Configuration page appears.
9. Review the information entered so far and click Submit to create the service request.The Chargeback page displays charge information for Tuxedo machines in login SSA user. Only the Tuxedo Machine target instances associated with predefined Tuxedo Charge Plan are monitored here. For more information, see Configuring Chargeback.
1. Click the Policies tab in the Tuxedo Self Service Portal.
2.
6.
7. Click OK to create the policy. You will return to the Policies page where the policy you have defined will appear in the Policies table. To apply these policy for a target, click Add in the Associations region and select a target with which this policy must be associated.
1. Click the Policies tab in the Tuxedo Self Service Portal.
2.
4. In the Create Performance Policy: Rule page, select a metric from the right panel and click Add to Definition. Specify the condition, value, and number of occurences.When these conditions are met, the policy is executed.Click Next.
5.
6. Review the policy details and click Save and return to the Policies page.
7. In the Associations region, click Add and select one or more targets to be associated with this policy. The associated targets are listed in the Associations region.Click on the target link to view a list of policies associated with the target. Once the targets have been associated, the policy is activated. Click View History to view the policy action history.
a. From the Enterprise Manager Console menu, click Targets > Middleware at the top.
b.
c. In the Oracle Tuxedo Summary page, click Introspect.
d. Click New to create a new introspection project and select one of the domains monitored by Enterprise Manager from the list.
e. Click OK to retrieve the tuxedo domain UBB configurations.
2. Click Package >Introspect to invoke the introspecting process. When the process completes successfully, the Confirmation window with the result and domain package file name is displayed.
3.
4. (Optional) Click Save to export the newly created introspection project parameters to the local computer. The file is exported as XML format without a user password. The file can be used to introspect the domain under the command line mode as well.
5. (Optional) Click Open to upload a local project file saved before.A property file template InputParamsTemplate.xml is created under the location where java command invoked.Listing 9‑1 Property File TemplateListing 9‑2 Property File ExampleA binary package zip file is created during introspection process for each of machine configured in the Tuxedo domain. This package includes all the applications, libraries, and all third party products that the domain needs. The file is named [lmid].zip and is configured in the Tuxedo domain package configuration file. For example, when introspecting the machine "LMID1" on a host, its binary package in the configuration file may looks like Listing 9‑3:Listing 9‑3 Binary Package in Configuration FileWhen introspecting an existing domain running on the different machine with OMS, the machines configured in the domain can not post message in the .bashrc configuration file. This causes SFTP connection faliure.Placeholders are used to replace old values in configuration files. These placeholders can be treated as "Variables" which will be filled with the real value at deployment time. All the placeholders are defined in the package configuration file. Listing 9‑4 shows the definitions.Listing 9‑4 Placeholders DefinitionListing 9‑5 Placeholders ExampleUBB, DM, SALT, and Oracle TNS configuration files are parsed during introspectiong, and replaced with placeholders at deployment time automatically. Listing 9‑6 lists the well-known placeholder types:Listing 9‑6 Well-known Placeholder TypesThe placeholders assigned with the type of UBB_MACHINE_NAME, UBB_NET_ADDR, UBB_NLS_PORT, UBB_NA_PORT, JMX_PORT, JMX_ADDRESS, DM_LOCAL_ADDRESS, DM_LOCAL_PORT are handled automatically. That is, their values are filled by provisioning procedure. For those placeholders assigned with the type of "GLOBAL_VAR", the value can be embedded with other placeholders. See the example shown in Listing 9‑7.Listing 9‑7 Placeholders with GLOBAL_VARlmid is the logical name of the machine configured in UBB.For those automatically handled placeholders, for example, ${SITE1-machine-name} is filled with a real host name at provisioning time without any input from end users. But in the case that there is no proper value to replace the placeholder, you need to input the values. For example, ${GWDOMAIN3-remote-port} in DM CONF will be filled with proper value to the best extent possible. If no proper value can be determined automatically, you need to input the value. Here is an example that shows the process of how to handle such placeholders.Listing 9‑8 Domain 1 DM configuration-dm1.confListing 9‑9 Domain 2 DM configuration-dm2.confWhen handling dm1.conf at provisioning time, the assembly procedure attempts to find the host in Domain 2 UBB configuration (find it by access point) by comparing original net address value. If the host is successfully found, the new address will be filled ${GWDOMAIN2-remote-addr}, but if domain 2 is not included in the profile or such host can not be found in domain 2 UBB, then you need to provide this value before submitting the provisioning procedure, for example, provide the value for ${GWDOMAIN3-remote-addr}.
•
•