Posts tagged 11g
Run it with $WL_HOME/ common/bin/wlst.sh -loadPropertiesÂ <property_file> <script_name>Â Â ($WL_HOME is the location of your WebLogic server directory, like /opt/oracle/Middleware/wlserver_10.3)
Property file(properties.py): admin_server=<name adminserver> admin_server_port= wluser=weblogic wlpassword=<password> clustername=[name] domain=<domain_name> Â
#Definition to print a running servers state def printState(AdminServer): connect(wluser, wlpassword, ‘t3://’+ admin_server + ‘:’ + admin_server_port) serverConfig() state(“AdminServer”) state(“[name of managed server1]“) state(“[name_of managed_server2]“)
#Definition to disconnect from a server def disconnectFromServer(): disconnect() exit()
#Calling connectToServer definition with no arguments #connectToServer()
#Calling printstateDetails with arguments printState(‘AdminServer’)
#Calling disconnectFromServer definition with no arguments #disconnectFromServer()
De system directory is where JDeveloper stores the user specific settings, configurations and also (for 11g) the default domain of the embedded weblogic server. It uses the JDEV_USER_HOME environment variable to dettermine the location. If it’s not set is uses a default directory, for 11g on windows XP that’s <user dir>\Application Data\JDeveloper\systemXXX (XXX stands for the exact IDE version, e.g. system22.214.171.124.37.56.60 for 11gPS2, 126.96.36.199.0) and for 10g that’s <JDev install dir>\jdev\system (no version included). Note that the Application Data directory contains a space. And although this doesn’t prevent JDeveloper and the embedded weblogic from proper functioning, it may sometimes leads to an issue, e.g. that diagnostics (adrs) cannot create an image.
To change this directory, just add the JDEV_USER_HOME environment variable and set it to the required directory, that must not contain a space in the name and when you restart JDeveloper it will use that directory. However, you’ll notice that JDeveloper will now consider itself an almost new installation, without your custom configuration and no default weblogic domain but with installed extensions. It should be able to copy More >
Although JDeveloper provides loads of libraries out-of-the-box, you often need other libraries in your application. You can easily add these libraries via the project properties. This provides two options: ‘Add Library’ and ‘Add Jar / Directory’. We normally us the Add Library option because it allows to include the JavaDoc and the source code. However make sure that you check the ‘Deployed by Default’ checkbox or else the library will not be included on the classpath and the application will fail with a java.lang.ClassNotFoundException. By the way, we never use Tools -> Manage Libraries because we only use project libraries and never the user or system libraries, because they introduce local dependencies that need to be maintained at every workstation seperately.
Subversion is a great source control system. One of the great features is it’s branching and merging support. Although many developers avoid it, branching is very powerful and useful and should not be something to be afraid off but something to be familiar with. And for the stable and controlled development is it almost a necessity to master it.
In general we can identify two types of branches: product and feature branches.
- The product branch is normally to support maintenance on a released version while development of the next version continues.
- A feature branch is normally a temporary branch to work on a (complex) change without interfering with the stability of the main development line (trunk) and in the end is incorporated back into the main line again.
Now, while you can work on isolation on the feature branch, there will come a time that you’ll have to integrate (merge) the changes with the trunk. And although subversion does provide extensive merge support, this might get messy with big changes. So it’s a real good idea to keep the feature branch in sync with the trunk and have the changes in the trunk regularly applied to the feature branch too. Actually, this is not so More >
In this post I introduce to you one of the new ADF Rich Client components and one way to use it: The Carousel. You can display a set of images through a carousel, an animation effect that switches the emphasis successively between images as the user moves the mouse across them.
You can also have the carousel invoke and respond to partial triggers and display data in master detail relationships. (more…)
Starting WebLogic managed servers without providing username and password manually – SOA Suite 11g tip
After installing the Oracle SOA suite 11g, you will notice that you have to enter username and password for each managed server during startup and shutdown. This in contrary to the administration server where you don't need to enter username and password at startup. I was wondering if there was an easy way of skipping this manual step for the managed servers as well.
And yes, there is an easy and elegant way to prevent entering credentials every startup and shutdown. Just follow these steps:
1 Create a boot.properties file.
Create a plain text file called
boot.properties with the following content:
2 Place the boot.properties file in the security directory.
Save or copy this file in the
security directory under the managed server root directory. This directory was not created at installation time, so I had to create it myself. The server root directory is located at
3 Start the managed server.
The server will read the credentials from the
boot.properties file and in case of plain text username and More >