If during installation your code "knows" what namespace is used, then you can get the associated resources as described in my previous post.

If you don't know the namespace, then...game over, no way.

Maybe you can run a setup script after install that add to your role the required resources?

Yes, it's normal, Web Applications are local configuration on each mirror member.

If/when you create a new Web Application you need to create it in all mirror members. Personally I prefer to create the application using a script (a class method) that is deployed and run (typically along with code etc.) in all members nodes.

In addition to Web Applications note that also all security related configuration (Users, Roles, Resources, SQL privileges etc.) are local to each mirror member.

It's my understanding that InterSystems is working on enhancing the mirror to include security configuration synchronization (Web Applications are part of the Security) between mirror member.

To address similar cases some time ago I developed a little utility to export to a %DynamicArray the output from an SQL query.
In my case I had to export existing classes that did not extend %JSON.Adaptor (I'm not even sure %JSON.Adaptor existed at that time).
 

Class Community.SQL2JSON
{

/// Execute am SQL query and returns a %DynamicArray containing the rows (as %DynamocObject) returned by the query
/// RetDynArray is the returned %DynamicArray containing the results
/// Parameters used by the query must be included in the query using placeholders (?) e passed By Reference in the local variable array ParamArray
/// where the root node contains the number of parameters, ie:
/// ParamArray = 1
/// ParamArray(1) = 123
ClassMethod QueryToJSON(ByRef SQLQuery As %String, Output RetDynArray As %DynamicArray, ByRef ParamArray As %String) As %Status
{
	Set sc=$$$OK
	Try {
		Set stSql=##class(%SQL.Statement).%New()
		Set stSql.%ObjectSelectMode=0
		Set rsSql=##class(%SQL.Statement).%ExecDirect(.stSql, .SQLQuery,ParamArray...)
		If rsSql.%SQLCODE < 0 {
			Set sc = $$$ERROR($$$GeneralError,"%SQLCODE="_rsSql.%SQLCODE_", %Message="_rsSql.%Message)
			Quit
		}
		If '$IsObject($g(RetDynArray)) Set RetDynArray = []
		While rsSql.%Next(.sc) {
			If $$$ISERR(sc) Quit
			Set RowDynObj={}

			Set sc=..RowToDynObj(stSql,rsSql,.RowDynObj)
			If $$$ISERR(sc) Quit
			Do RetDynArray.%Push(RowDynObj)
		}
	} Catch CatchError {
		#dim CatchError as %Exception.SystemException
		Set sc=CatchError.AsStatus()
	}
	Quit sc
}

/// Convert a recordset in a %DynamicObject with property name equal to the column name
/// If RowDynObj is passed, then adds the properties are added to it, otherwise creates and returns a new dynamic object
ClassMethod RowToDynObj(StSql As %SQL.Statement, RsSql As %SQL.StatementResult, ByRef RowDynObj As %DynamicObject) As %Status
{
	Set sc=$$$OK
	Try {
		If '$IsObject($g(RowDynObj)) Set RowDynObj= {}
		
		For col=1:1:StSql.%Metadata.columnCount {
			Set ColumnName=StSql.%Metadata.columns.GetAt(col).colName
			Set ColumnValue=$Property(RsSql,ColumnName)
			Do RowDynObj.%Set(ColumnName,ColumnValue)
		}
	} Catch CatchError {
		#dim CatchError as %Exception.SystemException
		Set sc=CatchError.AsStatus()
	}
	Quit sc
}

}

Using it is very simple:

EPTEST>Set SQLQuery="select Name, DOB as ""Birth Date"", Home_City as City from Sample.Person where Home_City=?"
 
EPTEST>Set ParamArray=1
 
EPTEST>Set ParamArray(1)="Newton"
 
EPTEST>Set sc=##class(Community.SQL2JSON).QueryToJSON(SQLQuery,.RetDynArray,.ParamArray)
 
EPTEST>Do RetDynArray.%ToJSON()
[{"Name":"Uhles,Susan D.","Birth Date":31836,"City":"Newton"},{"Name":"Ubertini,Debby N.","Birth Date":42513,"City":"Newton"},{"Name":"Harrison,Rob E.","Birth Date":62265,"City":"Newton"},{"Name":"Adams,Robert E.","Birth Date":62769,"City":"Newton"}]
EPTEST>

Hi @Benjamin De Boe 😊

In general I agree 100%, BUT, if you need to add a favorite now, then the "right thing to do" would be:

• Open a WRC and explain the issue...may take some time depending on your luck...
• WRC open an issue, wait for developers to look at it and fix it
• Wait for patch/ad-hoc, how long? Probably 2~3 weeks for this not so critical issue
• Install the ad-hoc and...finally you get your favorite in Management Portal!

Another option is to fix it yourself, the problem is due to the property Data in %SYS.Portal.Users class that is defined as %List but in fact is used by the portal code as a string.
The "misuse" of Data property went unnoticed until version 2025 that implements/introduce %IsValid() method for %List datatype and that's why the %AddFavorite() method does not work anymore. Note that if you call %AddFavorite() passing (correctly) a %List ($list), then the method works, the favorite does not, because the portal code that read the Data property treat it as a String, not a $List!
Fixing this is simple, just edit %SYS.Portal.Users class (after modifying IRISLIB db to R/W and back when you are done...) and change Data datatype from %List to %String.

OR....just set the damn global, enjoy your favorite and go back to business! 😁

Anyone willing to report this to WRC? ...not me 😉

In these cases I use Ens.InboudAdapter with a very high call interval so it runs only once when the BS is enabled (START action in schedule definition)

While the suggested method should still work (haven't tested), I'd advise using the official method $system.SQL.Schema.ExportDDL()

See Class Reference for documentation details  and samples.

It the issue of this question/post the "?wsdl" not working or that the SOAP pass-through does not work?

To get "?wsdl" to work you need an HTTP pass-through, technically it's not a SOAP call.
In fact the "?wsdl" parameter is interpreted by IRIS and you get the "wsdl" returned by EnsLib.SOAP.GenericService. 

I created the production and tested the call to the SOAP service (I'm using 2024.1 but I don't thin is relevant) and it works.
I'm using SOAP UI to call the service through the IRIS production and I get the correct result.

Apart from the "?wsdl" call, have you tried calling the actual SOAP service?

For simple cases I found that often using a HTTP pass-through instead of SOAP pass-through makes thing easier.

Never concatenate parameters to query text, use placeholders ("?").

What's the status (SC) returned by the called methods?

In your code after each "SET SC=....:" add the line:

$$$LOGSTATUS(SC)

What's the status logged?

%ResultSet in deprecated, use %SQL.Statement instead.
Never concatenate parameters to query text, use placeholders ("?").

Set sql = "SELECT COUNT(*) FROM "_tableName_" WHERE "_fieldName_">=? AND "_fieldName_"<=?"
Set resultset = ##class(%SQL.Statement).%ExecDirect(,sql,fromDate,currentDate)
Do tResult.%Display()

And in every method you call that returns a status code, check it!😊

I came across this old question and I was (almost) shocked by the answers because we are considering using System Default Settings for a project and one of the settings value we need to customize per system is Pool Size!

Fortunately things have changed since this was posted an now Pool Size can be defined/configured in System Default Settings and this is also documented:

Settings That Can Act As System Overrides

I'm not sure when this has changed,I believe this has been implemented in 2024.1, the version I tested and it works.

The behavior of this default setting a a little different then others (cannot be modified/overridden from within the production settings) but, IMHO, that's fine or even better!

I'm writing this to warn anyone using a recent product version looking/reading this question that now, from 2024.1 Pool Size can indeed be configured in System Default Settings.

Hi @Aya Heshmat , please consider adding the host Pool Size in the Production Configuration page as it once was.

For details on this topic see my post/discussion:

Display Pool Size in Production Configuration page

and related Idea:

Add pool size in production configuration page

For us is REALLY important, at the moment (where we can) we have hacked/changed the Prod. Config. Portal page, in the future with the new modernized page this change may be difficult to implement/hack.

It's difficult to tell if the bad value is in the passed parameter or in the returned value.

Just as curiosity, what's the value of pRequest.Warehouse and what's the datatype of Warehouse column in the prod.stocks table?

In the code you posted that's not true for all SetValueAt().

Does any call returns an error? If so, what's the error?

You keep not checking the status returned by SetValueAt() calls, that would probably gives clues/hints on the problem.

I suggest to change all calls with:
Set tSC=xxxx.SetValueAt(...)
$$$LOGSTATUS(tSC)