SAP Portal doesn't work!!!!
Hello, this is the 3rd time that we tried to install a support package in our productive SAP Enterprise Portal, and fails again.
We started on Friday 7th at 9:00 PM, the J2ee, Portal Platform and KM patch finished on the cluster server on Saturday at 6:00 PM (too long), then we continue with the other servers (for load balancing) one of them takes 12 hrs and the other 20 hrs (too long also). Why takes this time to run the support package? with Windows doesn't take more than 1 hr.
On monday 10th, at 9:00 AM the latest server finished and we start to test all the solution, but doesn't work, for some reason the servers goes down and never started again.
We decide to restore the backup on monday at 10:00 PM, because SAP doesn't have solution for our problem. The restore finished on tuesday at 5:00 AM, but after restart de servers there wasn't portal.
We have SUN 15k machines, in cluster, with SAP EP 6.0 SP09. SUN people says that SAP software doesn't work on SUN cluster, but in the documentation and the SAP consultants involved in our implementation recomended this solution.
The idea to implement SAPPortal in our company was the "Lower TCO" and for having a
"general portal solution" for all our applications, this never happened, with Windows IIS we have really lower TCO that SUN and JAVA.
Now we are working in migrate to ASP.net 2.0 (with Membership and Profiling services), we finished the core services for user and content management, we are only wating for a final decision of our managers.
We have an OSS with SAP support but the can't solve the problem.
I can't understand why takes too much time to implement a Support Package, why doesn't work with SUN cluster (recomended by SAP consultants), why we spent more time in monitoring and solve problems with this solution than with other web servers.
Some one have answers to this questions?...
Hello, this is the 3rd time that we tried to install a support package in our productive SAP Enterprise Portal, and fails again.
We started on Friday 7th at 9:00 PM, the J2ee, Portal Platform and KM patch finished on the cluster server on Saturday at 6:00 PM (too long), then we continue with the other servers (for load balancing) one of them takes 12 hrs and the other 20 hrs (too long also). Why takes this time to run the support package? with Windows doesn't take more than 1 hr.
On monday 10th, at 9:00 AM the latest server finished and we start to test all the solution, but doesn't work, for some reason the servers goes down and never started again.
We decide to restore the backup on monday at 10:00 PM, because SAP doesn't have solution for our problem. The restore finished on tuesday at 5:00 AM, but after restart de servers there wasn't portal.
We have SUN 15k machines, in cluster, with SAP EP 6.0 SP09. SUN people says that SAP software doesn't work on SUN cluster, but in the documentation and the SAP consultants involved in our implementation recomended this solution.
The idea to implement SAPPortal in our company was the "Lower TCO" and for having a
"general portal solution" for all our applications, this never happened, with Windows IIS we have really lower TCO that SUN and JAVA.
Now we are working in migrate to ASP.net 2.0 (with Membership and Profiling services), we finished the core services for user and content management, we are only wating for a final decision of our managers.
We have an OSS with SAP support but the can't solve the problem.
I can't understand why takes too much time to implement a Support Package, why doesn't work with SUN cluster (recomended by SAP consultants), why we spent more time in monitoring and solve problems with this solution than with other web servers.
Some one have answers to this questions?...
