Stephen Weblog

Once we login HFM and click on open application it will error out for authentication issues. To solve this we need to add the below line in %hyperion_home%\deployments\WebLogic9\config\config.xml file

   <node-manager-username>hyperionnode-manager-username>
<node-manager-password-encrypted>{3DES}weLFQ0l+HvCXqB36mIQZDQ==node-manager-password-encrypted>
  <enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials>

 Recycle the weblogic and hfm services.

Wanted to change admin console port on Weblogic, it was fairly straight forward. Just login admin console and click servers and change port and activate changes. But we had lot of hyperion components deployed on weblogic admin server, for no reason all the hyperion components were showing status SHUTDOWN. Steps done to resolve this issue are as below:

– Node manager was running on a different port, make sure it runs on 5556 port.
– There were lots of 7001 reference for all components on windows registry, check for the variable JVMOption4 and replace 7001 with custom port number.

Then startup all hyperion components, things will be fine.

We normally provision hyperion instance to customers with virtual URL configuration. With OAS deployment of hyperion components were as oc4j’s, which runs of common port and the url for different components will be as below in OAS

https://hyperionprod.com/interop
https://hyperionprod.com/workspace

But when we came to Weblogic all components were running on individual ports and there were no common port mapping so URL were as below

https://hostname:58080/interop
https://hostname:32000/workspace

It was a challenge to coverup the host name and port number, to overcome this situation we need to use a reverse proxy mechanism with apache.

Steps to implement common apache port and make mappings to all components using Apache
————————————————————————————————————-

As a high level plan we wanted to have a apache server which runs on top of weblogic and routs the request from client to weblogic.

– When we install Weblogic we need to select custom option and select the Weblogic plugin as well, by which we can get the different web server plugins to weblogic.
– Once we have installed weblogic along with the plugin, we now need to do a standalone install of Apache 2.0

Note - Apache 2.2 is not compatible to load the .so files provided by Weblogic 9.2 so its mandatory to have Apache 2.0, if we have workspace installed on the node then we do not require to do a
standalone install of Apache. As workspace will come with Apache install as well, and its made available under %hyperion_home%/common/

– Copy the file mod_wl_20.so, into %apache_home%/modules folder
– Load this module in the %apache_home%/conf/httpd.conf file

LoadModule weblogic_module modules/mod_wl_20.so

– Add the below to your %apache_home%/conf/httpd.conf file

<IfModule mod_weblogic.c>
WebLogicHost myweblogic.server.com
WebLogicPort 7001
MatchExpression *.jsp
</IfModule>

<Location /console>
SetHandler weblogic-handler
WebLogicCluster localhost:7001
</Location>

– Bounce your Apache http server, now you have access the weblogic console via Apache mapping

http://hostname:80/console

– Once you are done with this changes you are all set to pile up individual components into httpd.conf file, for shared services its as below

<Location /interop>
SetHandler weblogic-handler
WebLogicCluster localhost:58080
</Location>

Whenever we edit httpd.conf file Apache http server need to be bounced to reflect the mapping, now access shared services using as shown below

http://localhost:80/interop

– We were able to eliminate the individual port requests from browser, with all the port mappings are taken care by Mr. Apache which made my life simple.

Will have to work this setup with multiple instance and have it posted here in a while.

Was into a project on deployment of hyperion components on Weblogic 9.2, but Weblogic was something new for me. We are suppose to learn new technologies on the fly and start working on it right away….  After struggling with the manual deployment of Hyperion components on OAS in came a simple solution of Weblogic wherein we have automatic deployment. Its fairly straight forward but few bugs we found here and there, but believe me life is so simple with hyperion we weblogic. Expected to post few things in days to come.

If you have installed planning and EAS on a separate node, we will have to install adm drivers alone on the node where EAS is installed. If not ESSCMD might not work.

Even the Admin user needs to be provisioned to have Business Rules access, or you won’t be able to access them and you’ll get errors, including the following error in the “Get Detail” button:

“Detail:Error authenticating user in UserServerManager.”

So do the following:
1. Provision your Admin user with “Business Rules” permissions.
2. Log into AAS & try using Business Rules again.

Steps to disable proxy on Linux:

1. vi /etc/profile.d/proxy.sh
2. comment the proxy setting in that file
3. recycle the network configuration or else reboot the server

Hmm.. been a while since I had a outing, so had to do a quick plan for the long weekend on Ugadi. I had just booked a cab and did not make any other plan for the trip. Just called Bangalore help line and  asked for lodging details near kadur, and called some lodge and blocked 2 rooms. We packed up our stuffs and started midnight at 12. We were 4 of us along with cab driver, it was a memorable journey in night for we lost the route and went in a marooned road.  We were sure that we were on a wrong side, and saw a police station there and asked for the appropriate route and marched forward. Stepped out for T around 2:30 and had a small jinx with the T shop owner. In a sleepy mood I had given 50Rs note, but somehow I remembered that I had given 100Rs note. In a while I realized mistake was on my side, and without making any more fuss we moved ahead

Reached Kadur around 5 am, banged into the lodge and slept off. Woke up at 9 had breakfast and started out roaming, we first went to Kalkathri falls 30 kms from Kadur, where we did lot of stunts like sliding on the rocks and bit of trekking as well. From there we moved ahead to kemmangundi where we did good trekking and climate was pity good. Finished our late lunch there and headed back to our lodge at kadur. Took rest and bells started ringing for dinner, we roamed entire kadur and believe me there were no hotels opened here at 8 pm. People going to kadur beware of this, we then had to take our car and went to Bipur which is 5 kms from kadur. We were lucky enough to locate a road side dosa shop, we ate like aliens and the bill amount was just 150 Rs, we were really surprised !!!.

Time to take some rest, shutter are down and our eyes rolled down, all tiered and down. We woke up at 4:30 morning checkout room at 5 and started to Shimoga!!! We were able to get into Ghajanur dam and one elephant camp house, then went ahead to Jog falls. It was a terrific experience there, if you people want to do rock climbing go in summer for the level of water is pity low. But its still risky business getting near the water fall, it was amazing experience, we did not take carry any money while getting down to the falls and we all were tired while getting up… there are few shops where we can get lime juice, so people plase carry some money while getting down jog falls. We were almost dehydrated under the sun, but somehow managed to get over. Had lunch in the near by restaurant, we will  only get veggie foods so please don’t have high expectations on food near jog falls. Our trip ended there, and we started our journey back. Wait still a bit of excitement is pending, while our way back car tier got punctured, and luckily we were able to locate one puncher shop. Lost nearly 2 hrs on the process, and reached back Bangalore at early morning 3am.

Over all its a zero plan trip but came out very well….