Hi Ramon,
the solution has two elements to it. The bypass of the system selection is the personalisation flag "hide system selection on start up" set in your personalisation settings. This, combined with the last system you logged into successfully means that you are taken to the login screen for the last system you were in, in your case development.
The default settings are stored in your local profile in the NwbcOptions.xml file, which usually sits here:
C:\Users\d<user ID>\AppData\Roaming\SAP\NWBC
Trick for new players, the AppData is nearly always a hidden system file, so just paste in the directory to get past it.
The settings are stored in the single options section of the xml file, and are as follows:
<NwbcOptions>
<SingleOptions>
<ShowSystemInfo>False</ShowSystemInfo>
<ActiveConnectionGuid>f5050d00-2d3a-4acc-8bc1-ece0b4df62f2</ActiveConnectionGuid>
</SingleOptions>
</NwbcOptions>
The "Active Connection GUID is found in the system connection entry xml file SAPUILandscape.xml or SAPUILandscapeGlobal.xml files, usually found here:
C:\Users\<user ID>\AppData\Roaming\SAP\Common, in the service section, which has all the connection entries defined. You're after one service type "NWBC" and you want to take the UUID of the entry you want to default, e.g. of your production system.
Another piece of advice, this overwrites as soon as a user changes the system they log into, so you will want to think about how you define/rollout the default files, if you will let an end user change this. (Its always a good idea to let them do it if they change from your default). Forcing the overwrite of these files means any update the user makes that updates those files will be lost whenever they get refreshed.
Best of luck,
Di
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.