Installation and Configuration Guide - Wizards

×
Menu

Automatically Import your Connection Instance List into Wizards

 
Note - Only Wizards with Common Code version 201.7 and above contain the functionality to automatically import your URL connections from an “ini” file stored in your roaming profile, if no URL’s are currently saved in the Wizard.
 
To use this functionality a More4apps directory and INI file needs to be added to your roaming directory.  Instructions on how to do this is held in the Installation Instructions below.
 
When logging in it checks if there are already Oracle EBS login URLs saved in the workbook, if none are found, and a configuration settings file (More4apps\More4apps.ini) is found in the client’s standard roaming directory, the Wizard will display a prompt as per the image below:
 
 
If “Yes” is selected:
 
        The ‘Instance’ Listbox is populated with URLs from the INI file.
        The message box closes.
 
 
If “No” is selected:
 
        The message box closes and the Wizard Login form remains open.
 
Note:  The automatic importing of URL connections co-exists with current functionality and is not intended as a replacement.  Connection URLs can still be entered manually from the Login screen and imported from other workbooks using the setup ribbon options.
 
Installation Requirements for Network Administrators
Windows uses the Roaming folder for application specific data, such as custom dictionaries, which are machine independent and should roam with the user profile.  The AppData\Roaming folder in Windows Vista, 7 and 8 is the same as the Documents and ‘Settings\username\Application Data’ folder in Windows XP.
 
Common Locations of Application Roaming Directories
 
Please check the location of your roaming profile with your Network Administrator
 
Windows OS
Profile Location
 
Windows 10
 
Users\username\AppData\Roaming
 
 
Windows 8
 
Users\username\AppData\Roaming
 
 
Windows 7
 
Users\username\AppData\Roaming
 
 
Windows Vista
 
Users\username\AppData\Roaming
 
 
Windows XP
 
Documents and Settings\username\Application Data
 
 
Note: These directories are typically hidden.
 
The Wizards will attempt to locate the URL connections file in a “More4apps” directory in the roaming profile directory.
 
Create More4apps Directory and File
 
 
Step 1     Add a sub folder to the Roaming directory named “More4apps”.
 
Step 2     Using Notepad create your own text file named “More4apps.ini” in this directory, containing the following information in the top two lines of the file:
[INSTANCE_LIST]
Example,https://machine.domain.com:8000/pls/finprod
 
Step 3    Add your own URL connection lines to the file after the above data, as per the examples below where the text before the comma is an alias for the server and the text after the comma is the URL from the appropriate Oracle EBS profile:
My Oracle EBS R11i,https://myR11server.mybusiness.com:8000/pls/vis1
My Oracle EBS R12.1.3,https:// myR12server.mybusiness.com:8000/OA_HTML
 
Step 4      Check the file contains data similar to the example below:
[INSTANCE_LIST]
Example,https://machine.domain.com:8000/pls/finprod
My Oracle EBS R11i,https://myR11server.mybusiness.com:8000/pls/vis1
My Oracle EBS R12.1.3,https:// myR12server.mybusiness.com:8000/OA_HTML
 
Step 5      Windows XP - Save the file to this location:
Documents and Settings\username\Application Data\More4apps\More4apps.ini
Windows Vista, 7, 8 - Save the file to this location:
Users\ username \AppData\Roaming\More4apps\More4apps.ini
 
Important Notes:
 
     The “[INSTANCE_LIST]” heading row is required in the file.
 
     The first line under “[INSTANCE_LIST]” is an example and cannot be connected too so must be replaced.
 
     The Wizard will only display and use the first nine URLs in the INI file.
 
     Only one comma per line in the file should exist as this separates the name of the Instance from the connection URL.
 
     List each instance on a separate line.
 
     Ensure when creating and amending the file, the filename remains as “More4apps.ini” and doesn’t get a “txt” extension or the file will not be found.
 
     Information from this file will be imported and not checked for accuracy. More4apps accepts no responsibility for the data entered in the More4apps.ini file.
 
     If the More4apps.ini file contains unexpected data this will be imported into the URL form and the user will need to manually correct it.
 
     To remove an entry from the More4apps.ini file, either delete the line, ensuring no blank lines remain in the file, or prefix the line with a semi-colon to effectively ignore the record.
 
 
Example INI file:
 
 
[INSTANCE_LIST]
 
Example,https://machine.domain.com:8000/pls/finprod
Punga VIS2 11.5.10, https://punga.mycompany.com:8001/pls/vis2
Rimu VIS1 12.0.6, https://rimu.mycompany.com:8000/OA_HTML
Pohutukawa VIS6 12.1.1,https://pohutukawa.mycompany.com:8000/OA_HTML
Titoki VIS7 115.10, https://titoki.mycompany.com:8000/pls/vis7
Matai VIS1 11.5.9, https://matai.mycompany.com:8000/pls/vis1
Kahikatea VIS8 12.1.3, https://kahikatea.mycompany.com:8000/OA_HTML
Kauri 11i, https://kauri.mycompany.com:8000/pls/vis1
Rata VIS9 12.1.3, https://rata.mycompany.com:8000/OA_HTML
Totara VIS3 11.5.10, https://totara.mycompany.com:8000/pls/vis3
 
Note:  Instance names and URLs can be copied from the “Set your HTTP Addresses” form into your INI file using standard copy/paste functionality (per field).
 
Refer to section:  Enter Instance(s) Manually
Refer to section:  Enter the Licence Key
Refer to section:  Add Named Users