This question may sound silly for some of you, but I would be grateful if you could advise if it is possible to publish apex app into www?
Let's say I am going to run my testing environment under apex.oracle.... url, however I would like my production environment to be running under for example www.MyWebSite.com
Many thanks in advance for any tips.
If you want to host your own production environment, you have two stages: setting up your server, and deploying your application.
For server setup, you've got two main options:
Sign up with a specialized APEX hosting company who will do all the server setup and administration for you.
Do it yourself. You'll need to register your domain name and sign up with a hosting company. Then you'll install and configure Oracle Database, as well as a web application server (like Weblogic or Tomcat). Then install and configure Oracle Rest Data Services (ORDS), which will act as the listener for APEX.
Now, once your server is ready, look at the documentation on Deploying Your Application. The basic steps are that you want to export your application from your test workspace, and import it into your production environment.
Related
I can not access the web interfaces of obiee. Any suggestions or solutions?
"www".localhost:7001 should just be localhost:7001.
Also, OBIEE runs on the /analytics deoloyment. /console is the WebLogic administration console.
You must use the correct URL:
Use this URL:
http://localhost:7001/analytics
instead of:
http://www.localhost.com:7001/console
Please check whether your URL is apt or not.
Because what I think it should be localhost:7001/em or localhost:7001/console which is Enterprise Manager and Weblogic Console respectively.
And for OBIEE web page, we use analytics that is nothing but localhost:9704/analytics or localhost:9502/analytics
Solely depends on your OBIEE configuration.
Hope it would be helpful.
Based on your screenshot it appears as if you are attempting to access weblogic console. I would make sure that node manager and Admin Server are both started and running. On Windows os, click on the start menu and type NodeManager/Start Weblogic and it will give you the shortcut icons.
Once those two have been started you should be able to login to weblogic console and to ensure that admin/managed servers are both running.
If you did an enterprise installation of OBIEE11g, the default port for analytics should be 9704 unless you manually configured to use a different port number.
I am pretty new to Windows Azure, I want to migrate existing web application that connects to remote Oracle server and run it as a cloud service web role how can I accomplish this while windows azure has no Oracle client installed by default ? or in other words how can I connect from within .net application to a 64Bit Oracle database server without installing oracle client ?
I have worked with Oracle client long time back so some of things below may not be right. But here are some of your options:
You could make use of Oracle client for .Net provided by Microsoft and add those assemblies references in your project. When you publish the project, make sure that Copy Local attribute on those assemblies are marked as true so that those DLLs get packaged along with the rest of your application.
If you're using Oracle provided client for .Net, I remember we had to install that application on our web server. In that case, you could make use of something called Startup Tasks in your webrole and install the package when your role starts. You could either include the installer as part of your package and then install the software using a startup task.
I'd like to have my Scala application server find out if it's running inside Heroku or CloudBees or Cloud Foundry or something else. Is there some standard way of finding out which Java hosting provider is currently in use? (if any)
Perhaps the hosting provider's firewall/load-balancer/whatever adds some standard HTTP header that the app server could check? Or perhaps it's possible to do hosting provider specific checks somehow, for the most popular hosting providers?
Background: The app server could then show helpful tips to the server admin that tells him/her how to view the server's log files. This would be useful during the initial setup of the server + database, because then the admin needs to find a certain magic password in the log file, which s/he then uses to get access to the admin interface web pages the very first time (before any admin user exists in the database, see this security question). — The installation would be more user-friendly, if the server could tell the admin exactly how to view the log files (which varies from hosting provider to hosting provider).
In the case of cloudbees there are several ways, none of which are guaranteed to be future proof (given changing containers).
Perhaps what is needed is a standard environment variable to make this doable.
We have TeamCity running on a server and our Production site (ASP.NET) running on another Web server. What would be the best way to deploy from TeamCity to the Production server, so that we don't have to install much on the Production server and deployments are fast & secure?
Would Web Deploy (http://www.iis.net/download/webdeploy) be the ideal solution?
Ideally you could have your build script FTP the output of your build to your production server if it's got an FTP daemon running. SSH would give you more security still. It's up to you as to how far you want to take it security wise. I don't use SSH with my blog, for example. If someone wants to jack with my blog, so be it.
I am working with a team of 5 developers at a small company. There are 3 who work here and 2 work remotely. Currently, we are using Assembla with Trac for source control. We are working on a ASP.NET MVC web site. We are not hosting our production environment right now. I am setting up a BuildServer with Teamcity!! I have it working right now on my locally on my laptop. Should we host our own buildserver or pay some else?
TeamCity is pretty good for small shops such as yours. Hosting your own really shouldn't be bad in terms of setup and cost. As long as your remote colleagues can access it without issue and it fulfills your requirements, go for it.
I'd recommend hosting it closer to your version control server so that it can obtain the sources and perform builds faster. If you host your own version control server, either install TeamCity on the same machine (if the hardware allows it) or put it in the same network. You will also need to install build agent(s) somewhere and a database server (as the internal database may lack the performance and reliability). In a small shop a standalone server would handle all of it (TeamCity Server + Build Agent + MySQL database). In a long term buying a server and hosting it by yourself would be much cheaper than paying some hosting provider each month for a virtual or dedicated server with limited resources. It would also simplify upgrading if it becomes necessary.
TeamCity server by itself is a web application hosted on the Tomcat server. It's accessed via the web interface from the browser. If you have an external IP address on the server, just configure the Tomcat to listen on that address and TeamCity will become accessible from all over the world (don't forget to configure the security).