Setup Middleware as a Service using EM12c

Transcription

1 Setup Middleware as a Service using EM12c Date: 20/11/12 Author: Rob Zoeteweij This paper will guide you through the steps necessary to allow your users to use Middleware as a Service using EM12c Cloud Control and show an example of using the Self Service Portal to request for a new Middleware Service. When setting up MWaaS we need to have a Service Template that we will make available to users of the Self Service Portal. For this we will connect to the Cloud Console as user CLOUD_ADMIN, this user has got the role EM_CLOUD_ADMINISTRATOR assigned and looks like this: From the Enterprise Menu navigate Provisioning and Patching Middleware Provisioning

2 When in the Middleware Provisioning page, we notice 3 out of the box WLS profiles that have been downloaded and deployed to the Software Library. A WLS Domain Provisioning Profile is made out of a Middleware Home, the domain configuration and binary files. After a WLS domain Provisioning Profile has been created, it can be stored in the EM Software Library. From here the Profile can be used to provision new WebLogic Domains. By this enforcing standardized and consistent configured Domains. Next we select the Provisioning Middleware Deployment Procedure and press [Launch] In the Source Page we will select a WebLogic Domain Provisioning Profile. In our example we selected the Small_LWS_1036 Profile and press [Next]

3 When in the Destinations Page we will save this Procedure and exit from this Launch by pressing [Save]. After entering a Name and Description for our Procedure we again press [Save] to close the dialog box, after which we will return to the Middleware Provisioning Page. As you can see, Deployment Procedure Create Middleware Small Heap now shows up in the Page. We now have created a Customized Deployment Procedure that we will use in the Middleware Cloud setup, what will be the next step to proceed with. We will disconnect from the Cloud Console. The Setup of the Middleware Cloud For the administrative steps to do the MWaaS setup, I have created an Administrator called MWAAS_ADMIN. This Administrator has granted the role EM_SSA_ADMINISTRATOR that allows him to define quotas and constraints for self service users and grant them access privileges. Next we connect to the EM12c Console as the MWAAS_ADMIN administrator.

4 From the Setup Menu we navigate Cloud Middleware In this Page we need to complete the Setup of the Middleware Cloud. A Middleware Pool contains a set of Resources that can be used to provision a service instance somewhere in a PaaS Infrastructure Zone. Press [Create] to create the Middleware Pool Here we will enter a Name and Description of the Pool. We also enter the maximum number of Java Servers (WebLogic Server instances) per host, 1 in our example. Press [Next]

5 In this page we need to add the Targets that will be in the Software Pool. Notice that you can actually only select WLS Oracle Homes here, meaning each Target (Server / Host) that become a member of the Software Pool need to have a valid FMW Oracle Home installed. Press [Submit] to complete the Pool. Next we need to setup the Request Settings where we need to specify: Future Reservation: how many days in advance can a user make a request? Request Archive Retention: Maximum duration after which archived requests will be automatically deleted from the system. Request Duration: How long should the requested Service be available? Next we need to create Quota for the Roles that will be authorized to file requests for Middleware Services.

6 After selecting the Role you want to create the Quota for, specify the Quota by means of Memory in GB and number of Java severs (WebLogic Server instances). Press [OK] Next we need to specify a Service Template that will be made available to users of the Self Service Portal. Press [Create] After entering a Name and Description you need to select the Deployment Procedure that will be submitted when a Self Service Portal user files a request based on this Service Template. In our example this is the Procedure we have created as user CLOUD_ADMIN.

7 Press [Next] In the Configuration Page we can enter values for the following properties: WebLogic Username: Administration User to be used WebLogic Password: The password for the Administration User Port Range Start: From what port should the provisioning try to find a free port Port Range End: Up to what port should the provisioning try to find a free port Expected Memory Consumption: As we have selected a Deployment Procedure that is based on a 512MB Heap Size WLS Profile we enter 0.5 in this example Expected CPU Utilization: CPU required by each addition instance in percentage These vales will be used to provision Weblogic Server Instances. Leaving any of the values empty will result in using default values. Press [Next] In the PaaS Infrastructure Zone Page we need to add the Infrastructure Zones you allow this Service Template to be used to provision Middleware Instances. Press [Next] In the Roles Page we need to enter those Roles that need to be authorized to access this Service Template.

8 Press [Next] The Review Page allows you to check that you have entered the proper values. If not you can navigate backwards to make corrections, if all entered values are correct you press [Submit] to complete this Service Template creation. Press [Submit] Next we will disconnect from he Cloud Console as we have finished the Middleware Cloud Setup. Accessing the Self Service Portal and request for a new Middleware Instance We will know connect to the Cloud Control Console as user DEVELOPER_FINANCE1 that is an Administrator with the EM_SSA_USER Role assigned. The assignment of the EM_SSA_USER Roles automatically results in access to the Self Service Portal.

9 From the Self Service Portal Homepage we will navigate to My Middleware Next we press [Request Service]

10 In the New Service Request Page we can enter a name for the Service, select from what Date the Service need to be created and what Date the Service is not needed anymore. Optionally you can select a Java EE application component from the Software Library to be deployed in the new WLS Domain that will be created. Press [Submit] Next connect to the Cloud Console as CLOUD_ADMIN and navigate from the Enterprise Menu: Provisioning and Patching Procedure Activity

11 The Procedure Activity Page shows us the running Provisioning Procedure. In this page we also notice the presence of the MWAAS- DELETE- #182 Job that has been scheduled to do the deletion of the Middleware Instance on 2/17/2013. Select link MWAAS- CREATE- #181 to show the Procedure progress

12 This Page shows a detailed progress overview of the Provisioning Procedure. After 28 minutes (in our example) the Procedure finished successfully. We now reconnect to the Cloud Console as End- user DEVELOPER_FINANCE1 and notice the newly created Middleware Service. The left side of the Page shows you the Quota that is left for future requests.

13 Now we select the MyCorpdomainService link that will bring us to the Middleware Service Homepage. We will now reconnect to the Cloud Console as CLOUD_ADMIN to check the newly created Middleware Instance. From the Targets Menu navigate Middleware

14 Notice the Oracle Fusion Middleware Farm mwaas_mycorpdomainservice_ _developer_finance1 that was created from the Self Service Portal