Quick guide:
Managed instance and managed server
| Managed Instance | Example | Managed Server | Recommendation |
| The is the server manager name, used in all SM screens and server manager directories | PY910_9006_WEB02 | This is the J2EE container name on your webserver. Not really used in JDE that much | PY910_9006 |
Domain name
Call it something to do with the machine and purpose of the domain. Potentially the release of weblogic also. Remember that you can have multiple domains on a single server (which is nice). A domain will always be part of WLS (but you can upgrade a domain, so release might not be too good?).
I like to see the servername and purpose in the domain name:
web02_jdehtml
web02_jdeAIS
web02_jdeovr
Examples and boring stuff
I always have this issue, when creating new JAS instances or enterprise server instances in server manager, what do I name them so that it makes sense. I think we need a definitive guide!
Above is an example of the server manager screen defining the weblogic domain – in my case e1_apps
So my weblogic domain is called e1_apps. Should that have a component of the machine name – I think yes – that makes sense.
The domain name is listed on a number of screens and it’s good to know what machine is belongs to.
Also see when you have a cluster, some other naming options
So you have 2 managed servers, but a single name for the managed instance.
What does this look like in WLS?
You can see that weblogic also defines by domain.
if we look under server manager, we see:
drwxr-xr-x. 7 oracle oinstall 4096 Apr 30 2015 DV910AIS
drwxrwxr-x. 3 oracle oinstall 4096 Apr 30 2015 E1ENT_DNT_Ent
drwxrwxr-x. 3 oracle oinstall 4096 Jul 16 2013 E1ENT-DNT_WLS
drwxr-xr-x. 8 oracle oinstall 4096 May 29 2015 JAS_JPY910_9085
drwxrwxr-x. 8 oracle oinstall 4096 Aug 31 2015 JDE91_PY
drwxrwxr-x. 2 oracle oinstall 4096 Jul 15 2013 ocm
drwxr-xr-x. 7 oracle oinstall 4096 May 29 2015 PY910_9087_AIS
-rwxrwxr-x. 1 oracle oinstall 2235 Aug 31 2015 targets.xml
[root@E1ENT-DNT targets]# pwd
/u01/app/oracle/jde_home_1/SCFHA/targets
Note, that these are the
So the server manager name is “Related managed instance” – for example JAS_JPY910_9085
EnterpriseOne HTML Server: JAS_JPY910_9085
but, when you create the container in SM, that is what it’s going to be called in WLS
J2EE Server JPY910_9085
See the directory structure below: under domains –> domain name –> servers, you have your container name. The J2EE server
/u01/app/oracle/Middleware/user_projects/domains/dnt_domain/servers
[root@E1ENT-DNT servers]# ls -l
total 28
drwxrwxr-x. 7 oracle oinstall 4096 Jul 16 2013 AdminServer
drwxrwxr-x. 3 oracle oinstall 4096 Aug 31 2015 domain_bak
drwxr-x---. 8 oracle oinstall 4096 Feb 26 2015 DV910AIS
drwxrwxr-x. 8 oracle oinstall 4096 Jul 16 2013 JPY910
drwxr-xr-x. 8 oracle oinstall 4096 May 25 2015 JPY910_9085
And so then it get’s a bit fruity, as the final location of your JDE JAS files have both names in the path:
/u01/app/oracle/Middleware/user_projects/domains/dnt_domain/servers/JPY910_9085/stage
[root@E1ENT-DNT stage]# ls -l
total 4
drwxr-x---. 3 oracle oinstall 4096 May 29 2015 JAS_JPY910_9085
/u01/app/oracle/Middleware/user_projects/domains/dnt_domain/servers/JPY910_9085/stage/JAS_JPY910_9085/app/webclient.war/WEB-INF/classes
The final location of jas.ini etc (for runtime) is above, note the combination of the two names managed server (WLS name) and managed instance (JDE NAME)
When you look at the “servers by type”, you get the screen below:
See that this uses the instance name – which is the JDE name. So what would be handy here? port, machine, lifecycle – all of this would be good
Also if looking “by group”, it also uses the instance name – what we call in in JDE – not WLS world.
Therefore, when creating a new JAS server (for example),
Which creates:
This is not really known to SM yet – it’s a WLS concept
Now, to create in SM
This is the name that is going to go everywhere in SM – so machine, port and lifecycle is important
No comments:
Post a Comment