The configurations required to connect eclipse to external weblogic server 11g on a VM
Before we begin...
- I am using an OSx 10.9 mac and connecting externally to my weblogic 10.3.6, which resides on my RHEL 6.x virtual machine, which is currently installed on my mac
- You must however determine which weblogic version you're using
In order to integrate your eclipse IDE with an external weblogic server, you MUST first install the WLS Zip Distribution on your local computer. This is a bite-size version of the WLS domain deployment, which contains all to goodies to develop and test on WLS server. You also need to ensure that you're downloading the specific WLS version as described above
Download it, unzip it, then place the folder an a permanent location (Mine is in my home directory)
Then you need to then download the plugin repository from the Oracle website
http://download.oracle.com/otn_software/oepe/12.1.3.3.1/luna/repository/
After that, open up a terminal window and run the following commands. You may need to alter based on your current locations
export JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home
export MW_HOME=/Users/danielredfern/wls1036_dev
export USER_MEM_ARGS="-Xmx512m -XX:PermSize=128m"
After that and within the same terminal, perform the following commands:
cd $MW_HOME ./configure.sh
Once performed, you'll see a BUILD SUCCESSFUL if all is... well, successful
You then need to run the following command and receive a response saying, Your environment has been set
. $MW_HOME/wlserver/server/bin/setWLSEnv.sh
You then need to create a new WLS domain and start WLS. It is also recommended that you create the domains outside the MW_HOME
mkdir /Users/danielredfern/devDomain
cd /home/myhome/mydomain
$JAVA_HOME/bin/java -Xmx1024m -XX:MaxPermSize=256m weblogic.Server
Note: you may be asked that that config.xml was found and 'Would you like the server to create a default configuration and boot? (y/n):', click yes
After the WLS server is up and running within the WLS server, you can then jump back into eclipse and within the server window, right click and select 'new server'. You can see this within the window, show view, server.
You should then select the weblogic home as well as the java home. These are the parameters you used before.
Once you've done that, select the WLS version and enter in teh server name. This is only the name and not specifically a configuration setting
After that, click on the remote server button and enter in the setting of your remote instance. Assuming that it's up and running, you should get a successful test connection
Then any current resources can be moved over
once that's all been done, you could then setup your initial context configuration to access your remote WLS connections
About the author
Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles
Comments
Other Posts
AS I was migrating my environment into an S3 environment, I wanted to leverage off the SES services that AWS provide, more specifically, to leverage the off the SMTP functionality by sending an email via PHP
Read More...
The WeMos D1 is a ESP8266 WiFi based board is an extension to the current out-of-the-box library that comes with the Arduino installation. Because of this, you need to import in the libraries as well as acknowledging the specific board. This process is highly confusion with a number of different individuals talking about a number of different ways to integrate.
Read More...
NameID element must be present as part of the Subject in the Response message, please enable it in the IDP configuration.
Read More...
For what I see, there's not too many supportive documentations out there that will demonstrate how provision AD group membership with the ICF connector using OpenIDM. The use of the special ldapGroups attribute is not explained anywhere in the Integrators guides to to the date of this blog. This quick blog identifies the tasks required to provision AD group membership from OpenIDM to AD using the LDAP ICF connector. However this doesn't really explain what ldapGroups actually does and there's no real worked example of how to go from an Assignment to ldapGroups to an assigned group in AD. I wrote up a wiki article for my own reference: AD group memberships automatically to users This is just my view, others may disagree, but I think the implementation experience could be improved with some more documentation and a more detailed example here.
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...