Greetings,
I had a great time at ODTUG Kscope13 in New Orleans and good to see some of my friends and ADF audience which is growing year by year. I attended few sessions from ADF, APEX and Database and learned lot. Next year ODTUG kscope is going to be in Seattle and i am excited to be a part of it. I have already start thinking about my new abstracts.
Thank you ODTUG for providing me this opportunity to share my knowledge.
Following are the slides from my Kscope13 presentation.
Cheers,
Zeeshan Baig
@baigsorcl
Thursday, June 27, 2013
Monday, May 20, 2013
How to Reset Weblogic Server Administrator Password
Hi,
Sometimes there is a possibility that you forget Weblogic server administrator password or you are in the environment where nobody knows the password.
In this post i will show the steps how to reset weblogic server administrator password
Cheers,
Zeeshan Baig
Sometimes there is a possibility that you forget Weblogic server administrator password or you are in the environment where nobody knows the password.
In this post i will show the steps how to reset weblogic server administrator password
What you need?
- Access to the server where weblogic is installed.
- Location where weblogic domain is created default is <fmw-home>/user_projects/domains/<domain-home>
Steps to do:
- Stop the AdminServer including all managed servers.
- Rename the LDAP folder of AdminServer and other managed servers. Location would be like <WLS_DOMAIN>/servers/<server-name>/data/ldap
- Run the setDomainEnv.sh or .cmd command to setup the environment i.e. <wls-domain>/bin/
- Go to security directory in the domain i.e. <domain-home>/security
- Run the following command (Make sure include DOT at the end) java weblogic.security.utils.AdminAccount weblogic welcome1 .
- Delete the 'DefaultAuthenticatormyrealmInit.initialized' file from ldap folder in the AdminServer <domain-home>/servers/AdminServer/data/ldap
- edit the boot.properties file in <domain-name>/servers/<server-name>/security for all managed servers with your new password
- Start the weblogic server
Cheers,
Zeeshan Baig
Tuesday, April 9, 2013
Slides from my Sessions at Collaborate 2013
Greetings,
I presented 2 sessions at Collaborate 2013 in Denver. Following are slides from it.
Enjoy,
Zeeshan Baig
I presented 2 sessions at Collaborate 2013 in Denver. Following are slides from it.
Enjoy,
Zeeshan Baig
Labels:
ADF,
Collaborate,
Developer,
Java,
Sessions,
SOA,
Webservices
Monday, March 4, 2013
My Sessions at Collaborate 2013 in Denver
Hi,
This year i am going to speak in 2 sessions at IOUG Collaborate Conference in Denver. I will be sharing some my experience and best practices in these quick tips sessions. Please mark your calendars and come to say Hello.
Click on the link for more info
Click here for more info
See you in Denver,
Zeeshan Baig
@baigsorcl
This year i am going to speak in 2 sessions at IOUG Collaborate Conference in Denver. I will be sharing some my experience and best practices in these quick tips sessions. Please mark your calendars and come to say Hello.
Click on the link for more info
Click here for more info
See you in Denver,
Zeeshan Baig
@baigsorcl
Wednesday, February 20, 2013
Setting up WebLogic server for REST Web Services
Hi,
REST web services are getting popular with the time. They are programmer friendly and easy to develop.
By default weblogic server ships with all required shared libraries for REST but there is one step we need to do in order to activate it which is to deploy those libraries on domain.
The step is simple. All we need to do is to deploy required libraries from
$WLS_HOME/common/deployable-libraries to weblogic domain
In my case i had following libraries used in my application
1. Go to weblogic console http://server:port/console
2. Go to Deployment link (click Lock & Edit if in production mode)
3. Click install and choose libraries as shown in the slide
4. Follow wizard and active.
Reference http://docs.oracle.com/cd/E17904_01/web.1111/e13734/rest.htm#WSADV572
Cheers,
Zeeshan Baig
Follow me on twitter @baigsorcl
REST web services are getting popular with the time. They are programmer friendly and easy to develop.
By default weblogic server ships with all required shared libraries for REST but there is one step we need to do in order to activate it which is to deploy those libraries on domain.
The step is simple. All we need to do is to deploy required libraries from
$WLS_HOME/common/deployable-libraries to weblogic domain
In my case i had following libraries used in my application
- jersey-bundle 1.1.5.1
- jsr311-api-1.1.1
1. Go to weblogic console http://server:port/console
2. Go to Deployment link (click Lock & Edit if in production mode)
3. Click install and choose libraries as shown in the slide
4. Follow wizard and active.
Reference http://docs.oracle.com/cd/E17904_01/web.1111/e13734/rest.htm#WSADV572
Cheers,
Zeeshan Baig
Follow me on twitter @baigsorcl
Tuesday, February 12, 2013
How to enable System.out.println messages in Weblogic server
Hi,
Using System.out.println is common practice to debug issues in Java applications. However, in ADF applications using ADF logger is common and best practice. But if we have some web services/ java apps deployed on weblogic server mostly it will use System.out.println
By default Weblogic server does not display the standard System.out.println messages. To enable those go to weblogic console http://<server-name>:port/console
Click Domain Name > Environments > Servers > <Server-name> > Logging and check the following options under Advanced option
Restart the specific managed server and now the System.out.println messages will be visible on the ServerName.log file which is commonly under domain_directory/servers/<server-name>/logs
Cheers,
Zeeshan Baig
Using System.out.println is common practice to debug issues in Java applications. However, in ADF applications using ADF logger is common and best practice. But if we have some web services/ java apps deployed on weblogic server mostly it will use System.out.println
By default Weblogic server does not display the standard System.out.println messages. To enable those go to weblogic console http://<server-name>:port/console
Click Domain Name > Environments > Servers > <Server-name> > Logging and check the following options under Advanced option
Restart the specific managed server and now the System.out.println messages will be visible on the ServerName.log file which is commonly under domain_directory/servers/<server-name>/logs
Cheers,
Zeeshan Baig
Subscribe to:
Posts (Atom)