There are multiple tenants and sites running under single instance of Sitecore 10.1. When we try to create a site programmatically, the entire Sitecore instance restarts.
Is there any options to stop this behavior of sitecore instance restarts during new site creation programmatically
Related
I want to increase the maximum web service requests for my application in Oracle APEX earlier version of APEX 18.2 has an option to this in manage workspace section. But now this option is not found in APEX 19.2. Any idea how to achieve this?APEX 18.2
I'm not sure if the UI has moved or stripped out, but you should be able to set it via the APEX_INSTANCE_ADMIN.SET_PARAMETER procedure.
https://docs.oracle.com/en/database/oracle/application-express/19.2/aeapi/SET_PARAMETER-Procedure.html#GUID-A6D8CA93-798D-4582-97B9-C7D3ED709AC5
The setting is MAX_WEBSERVICE_REQUESTS, which is in this list:
https://docs.oracle.com/en/database/oracle/application-express/19.2/aeapi/Available-Parameter-Values.html#GUID-75DCF658-5A76-4E81-B12D-04E254A3D80A
As stated in the doc:
APEX_INSTANCE_ADMIN can be executed by the SYS or SYSTEM database
users and any database user granted the role APEX_ADMINISTRATOR_ROLE.
I read from this guide http://docs.cloudfoundry.org/devguide/deploy-apps/blue-green.html that this deployment is supported through CLI.
Can I use my Pivotal Web Services web interface to do that ?
Does the Green instance connect to the production DB ?
Any guide is greatly appreached
Yes,you can use the web interface to map and unmap routes. When you go to the detail app of your app, you can see at the bottom a tab panel. One of the tabs says 'Routes'. There you can map and unmap routes.
Yes, both instances should be connected to the same db. During a time, when both instances are live (the production route is mapped to both of them), you will have users using the old and the new version. If a user is using the old version, you want his/her edits to be stored and present when he/she is switched over to the new version. Note: That means you should make sure that all your database migrations are backwards compatible.
I have download the umbraco accelerator to try get an azure based CMS up and running, I have managed to change the configuration file and the command prompt log upon running the .bat files does not generate any errors.
I have created the storage and azure database and hosted service but when I look at the hosted service there is no way for me to connect into this as the connect button has been disabled. Has anyone else went through the setup and if so have you encoutnered this issue? The URL displayed in azure http://appname.cloudapp.net/umbraco/default.aspx does not work
Which Umbraco version are you deploying? AFAIK the accelerator is deprecated, but I could be wrong if you're doing something in particular, or something I haven't heard of (could be lots!) with web/hosted services.
I've deployed Umbraco 4-6 CMS through WebMatrix 2-3 to azure as a website with relative ease. I didn't need it to be a hosted service/cloudapp.
Is that url not a generic placeholder, do you have a Domain registered to point at it?
Y'know, the more I type, the more I realise I have only a shaky grasp of what you're talking about. Are you sure you need a cloudapp, will an azure website not do?
I am planning a Sitecore deployment, I was reading a "Separating Authoring from Delivery" http://www.awareweb.com/AwareBlog/ArchConsideration.aspx.
Do I need to install and configure Sitecore in both envioronments. In that case users can access Delivery/Sitecore and Authoring/Sitecore.
How can I actually seperate two websites? I am bit confused. Please help!
Dhanuka777, as mentioned by techphoria, you'll really have to start reading up on a lot of things before you'll be able to get more direct help.
That being said, this is the basics of what you're trying to achieve:
Delivery: This is a website running the sitecore web application, but it does not allow users to login to the Sitecore editing interface. It can only serve up the content to your extranet users.
Authoring: This is a website running the sitecore web application, but it allows users to login to the Sitecore editing interface. Extranet users cannot access it. This usually means it's running on a VM or server behind a firewall.
You will also need to look at how you want deploy your databases to support these two sites.
What is the difference between Sitecore's core, master, and web databases?
Master: Contains all versions of all items. This is the database that content authors interact with, and is the default database used by the Sitecore Content Ediitor.
Web: This contains only the current versions of items. This is the database that supports the live website.
Core: This database has two purposes:
It contains definitions for the Sitecore user interface (Content Editor, Page Editor, etc.). This is where you would go to add, for example, a new Right-click option to the Content Editor or a new ribbon button to the Page Editor.
It contains the ASP.NET membership tables that drive authentication and security.
I recommend you look at the Launch Sitecore site to understand more about the CMS.
From the page on Sitecore Architecture:
Master
The Master database is the authoring database - it contains all versions of any content or assets.
Core
The Core database is all Sitecore settings, as well as the tables containing the .Net membership provider (i.e. users/roles contained in the Sitecore repository)
Web
The Web database is only the latest published version, and the content that is driving the live web site. Therefore it is a subset of the master database, optimised for size and speed. When content is published, or goes through the publishing task of a workflow, the latest content version is copied from the master to web database.
Of course, in an Enterprise deployment, you may have multiple Sitecore instances, which may share DBs (or not)
Some great answers here but it's worth a clear note that the Web database is the default publishing target and is not set in stone. You can rename it to whatever you wish as well as have multiple publishing targets similar to 'Web'.
e.g. We have a Sitecore instance with two websites (website and intranet), thusly the Master database contains all the items for both sites. For publishing we have two targets 'Website' and 'Intranet' that are hosted by different SQL servers.
Ultimately our connections include: Core; Master; Website; Intranet (the latter two being copies of the original 'Web' database of course)