noxvita

[noxvita]

Tutorial on connecting an Oracle utilities

Hello and welcome to this tutorial on connecting an Oracle utilities, enterprise SAS environment, to the object, storage that you're, using in order for the application environment to be able to write and read files from object storage. So this applies to customer cloud service. Meter solution, cloud service, work and asset cloud service, we'll start with an overview of quick overview of the instructions, and this scenario it will be demo and it will assume that you are fairly familiar with the concepts of object, storage and familiar with [ Music ], navigating Through customer clouds bad service or that any oh, you AF based application, Oracle utilities application framework. 

So if we take a look at the steps, essentially, what we do here is gather some information from your Oracle cloud infrastructure or your object, storage, part of the system, and that includes getting some OC, IDs and namespace values and we'll copy those in I'll show you How you get those we create one new object there. The scenario here is that we have a new application environment and we'll call it a CCS dev, o2 environment. So we're gon na create an application user in for object, storage that map's to that new environment and will capture the OC ID. For that, then we'll do a couple things in the application environment itself, including creating a keyring and grabbing the public key from that keyring and then finally, using the information that we grabbed in steps. 

One and two to complete extendible look at look EPS that are the mapping in the application back to object, storage to particular compartments; okay. So, let's start out by gathering information from the Oracle cloud infrastructure, starting with the tenancy information. So I'm going to switch over to my Firefox and just have gone into the OCI object storage area. To get the data we need we're gon na have to go down first to administration, tendancy details; okay, here's the tenancy details; this happens to be an internal environment, but yours will look very similar, but at the top ocid we're gon na copy the tenancy information from That ocid and it will look something like that. Long unreadable string and that's part first thing we need second thing is: we need the object, storage, namespace so grab that and I'll slap it into that document. Okay, then we need for the appropriate compartments. 

We need the OCAD of those compartments, so I'm gon na go back in and now I'm gon na switch over to the identity section for compartments. Remember that we create the shared compartment for use by all the environments, and then we separated out by production and non production in our basic set up. You may have a different. You may have split these in a different way and that's fine. The concept remains the same that you'll want to grab go into the compartment. You want to map to the high-level compartment and grab an OC ID from it. So I went into the in this case. Ccs shared I'm going to copy the OSI ID from that shared compartment. I am back to my doc and slap in the shared, Miss Eid and then, in this case it's a demo to scenario so we're going to get the non production compartment go back to that area. 

I'M gon na go back to compartments. I want non production this time, I'm gon na copy the ocid from that and put that into my document. Okay - and that completes the first step that we need to do, then we're gon na create this application user correspond to devote to environment. So CCS demo to when I go back in I'm gon na go, do that from identity, create users we already have in this case dev and prod and test application users I'm going to create one for dev o2. So it looked very similar to this dev user. Just no actually copy this, so I have it handy when I say create user. That user will be CCS. Deb o2 description would be that we won't use an email because of never be a direct login. This will be through an API key and no tags are necessary, so let's say create that creates our dev o2. Now, let's grab the ID post Eid from dev, o2 or new user record, we'll copy that and put it in our file, and we need to link that user to the appropriate group. So it has access to some compartments. Okay, and so we do that by going to groups, we find the group that is the appropriate one for this user. 

It'S an application user and it's non prod access. So it's this group, I'm going to click on that group and I'm going to say, add user to group and I'm gon na add debo to dev and test are already there and add a vote. Okay and that for now completes what we need to do on the object storage side. Now I'm going to go into an application environment, we'll say that this is our dev o2 environment and we need to do a couple things here. First, off and I'll go back to my instructions briefly, we're now in step 3 in the SAS environment, create a keyring called OS, OS API keys and then we'll generate a key. So I'm going to go and back into that environment navigate to keyring. We can check first, if there's anything there in a new environment that we will not find any records here. So, I'm going to say, add the keyring. 

You brings up a ad dialog and it's the OS API keys. I'Ll just call give it the same description and say saved: it creates a keyring next we need to on a while. On this same record, we need to generate a key that creates a private key and will be able to also then you get a public key for it, so I'm going to generate key that creates this record down below that. We see here notice that it's shown as today's date last day of 2019, it's inactive right now we're going to activate it you and get a warning on that singing. It then we're gon na view the public key that gives us a pop up and what we want to do is copy that entire public key and you know, cancel what we're gon na do with that. Public key is put it back into object, storage for our user, so I'm going to click on that user and notice for a and a pyro. This is our dev o2 user that we just created, I'm gon na add a public key and that's a public key. We just got for that in that environment, let's say, add Meg and that stores the public key, so they're now linked together and we now get our last step. So we we copy the Pope key and we say we did step 4 and then in step 5. We create and update some extendable lookups under the file storage description, so I'm gon na go back to our environment and do a navigation over to extendable. Look up there. 

I'M gon na search for file - and I will find this is the one I'm after is F. 1 file, storage and click on that. What you'll find in a new environment is that we've proceeded one extendable, lookup value for the shared compartment, because we assume that every environment will need to be able to kind of connect to the shared compartment in object storage. But if you broadcast on that value, we'll see that a number of the fields are not filled in and in order to fill them in. We had to do with earlier steps in this demo, but now we're in a position where we can fill these in. For the shared compartment, so I will edit this record and now I can fill in some of these values. So now it's looking for a user - and these are OC IDs, that it's looking for so first the user and I'm going to copy these back from the from the document we used. So this is our user CCS DeVoe we'll put that in the first box. 

Next, we need the tenancy ocid and we'll get that from the top one. Here, it's a tendency, then we need the shared compartment ocid for shared. That'S this one copy that then it's looking for the namespace, which we also got it's this value here when the last two are dropped, dance and we should find our OS API keys of it created. That'S a reference to the keyring, and then your region is dependent on where your object storage is located in the US that would be in Ashburn in other parts of the world. It might be a different region, pick the appropriate region for your object, storage and you hit save okay. Now, that's all filled in the final step that you would do is that gives us a mapping to our shared compartment in object, storage. What we need to do, then, is add one more record which, by default, we call the OS app a storage lookup, and so it's where the application rights in general writes its files that are not to be shared and [ Music ]. It'S an object, storage file, adapter, that's going to use and notice. It has the same fields that we just filled in, so everything would be the same in filling this out, except for the only difference would be that you'd pick up your non prod here. 

As your compartment mapping you'd pick up that value instead and fill it in on the compartment, all the rest would be the same values that we filled in on the other another one, and that would give you a mapping to OS for your application. So you have. Oh s, app and OS shared and of course you use those that I won't save that one, but because I didn't fill it all in, but once you have those two values you can use our shared analyst app in things like your batch parameters to indicate where A batch job should write a file or read a file, for example. So that concludes the steps of setting up connectivity between an environment in the you, gbu enterprise, SAS world local utilities, application framework based customer cloud service. In this case - and I and your object - storage and you can modify that as needed if you have a different compartment, setup and so forth, but this step should be all all similar. So, thank you for your attention and this one and good luck on setting up your environments. Thanks