Siebel Composer Developer Preview Guide > Setting up Siebel Composer > Adding the Virtual Directory for Siebel Composer >

Editing the new_virdirs Script


You edit the new_virdirs script to specify the virtual directory name that Siebel Composer (the Siebel Web Tools application) requires. The virtual directory name is also used for the application section in the eapps.cfg file. You can run an edited script on additional Web servers, as necessary.

To edit the new_virdirs script

  1. Stop the Web server.
  2. Back up the eapps.cfg file, the eapps_sia.cfg file, and the Web server configuration file, such as obj.conf, http.conf, or magnus.conf, as appropriate for your browser.
  3. Navigate to SWSE_HOME/config.

    In this directory, SWSE_HOME is the SWSE installation location.

    (Use the backslash for Microsoft Windows; use the forward slash for UNIX or Linux.)

  4. Back up the existing new_virdirs script as follows:
    • On Microsoft Windows, the name of the script is new_virdirs.bat.
    • On UNIX or Linux, the name of the script is new_virdirs.sh.
  5. Using an appropriate text editor, such as Notepad on Microsoft Windows, open new_virdirs.bat or new_virdirs.sh.

    NOTE:  When you edit the script, do not enter any special characters, such as tabs.

  6. Add the elements for the Siebel Web Tools application to an existing entry in this file as follows so the file creates a new virtual directory and new eapps.cfg file section for the application:

    %JAVA_HOME%\java -jar %ORACLE_HOME%\config\new_virdirs.jar

    {webtools} {SWToolsObjMgr} %LANG

    In this entry:

    • webtools is the name of the virtual directory
    • SWToolsObjMgr is the name of the corresponding Application Object Manager without the corresponding language code. (The language-specific items are created when you run the script.)
  7. Save the new_virdirs script.

    Next, run the new_virdirs script to add the virtual directory for the specified language. For more information, see Running the new_virdirs Script.

Siebel Composer Developer Preview Guide Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices.