3 Configuring the Environment

This chapter describes the steps required to configure ACS.

Configuration File

Many ACS tools and processes depend on a shared configuration file. This file acs.conf is located in the $ACS_ROOT/etc directory. The configuration file consists of several sections named for the processable they control. Each section contains a name value pair representing a single configuration option.

If the operator changes the acs.conf file, the corresponding service needs to be restarted, so that the configuration file is reread and the changes take effect.

Final Configuration

It is important to complete the final configuration of ACS after this chapter. See ACS User's Guide - Setting up ACS for the First Time.

Setting the ACS Root Directory

The ACS installation depends on a single environment variable to determine the location of the configuration and other support files.

If the software is not installed in the default location, the UNIX system accounts used to run the service logic and ancillary tools must have this environment variable defined.

The ACS_ROOT variable will only need to be modified if you intend to manually configure two ACS installations side-by-side on the same machine.

Note:

This should only be done in consultation with a qualified Oracle engineer.

If you are not required to manually configure two ACS installations, side-by-side, on the same machine the ACS_ROOT variable does not need to be set.

Table 3-1 ACS_ROOT

Variable Default Description
ACS_ROOT /IN/service_packages/ACS ACS installation base directory

Table 3-2 ACS_ROOT

Description The ACS installation base directory
Type String
Optionality Optional (default used if not set)
Default /IN/service_packages/ACS

Oracle Variables

The ACS account (acs_oper) requires the standard ORACLE environment variables to be present.

Oracle usr/pwd String

While it is possible to specify the usr/pwd string a process uses to connect to Oracle, it is recommended to use the defaults.

Most ACS processes are run by the UNIX user acs_oper. The OPS$ACS_OPER Oracle operator account corresponds to acs_oper. This allows acs_oper to log on to oracle as OPS$ACS_OPER without specifying a user name or password (that is, the process uses the default of "/"). A separate Oracle password is not needed for OPS$ACS_OPER because it is, in Oracle terms, identified externally.

Configuration File

ACS is configured by the following components:

Table 3-3 Configuration of ACS Components

Components Locations Description Further Information
acs.conf all SMSs and VWSs in the $(ACS_ROOT)/etc directory This file consists of several sections named for the ACS processable they control. There are different configuration options in the acs.conf on the SMS to the configuration options in the acs.conf on the SLC. Configuring the acs.conf
SLEE.cfg all SLCs This file sets up SLEE interfaces and applications. SLEE Technical Guide
eserv.config all SMSs and VWSs ACS has some additional configuration in the ACS section of eserv.config. eserv.config Configuration

Defining the Screen Language

The default language file sets the language that the Java administration screens start in. The user can change to another language after logging in.

The default language can be changed by the system administrator.

By default, the language is set to English. If English is your preferred language, you can skip this step and proceed to the next configuration task, Defining the Help Screen Language

Default.lang

When ACS is installed, a file called Default.lang is created in the application's language directory in the screens module. This contains a soft-link to the language file that defines the language that will be used by the ACS UI.

If a Default.lang file is:

  • Not present, the English.lang file will be used
  • Present, a user must explicitly set their language to their required language in the Tools screen or the default language will be used

The ACS Default.lang file is located in the /IN/html/Acs_Service/language/ directory.

Example Screen Language

If Dutch is the language you want to set as the default, create a soft-link from the Default.lang file to the Dutch.lang file.

Follow these steps to set the default language for your ACS user interface (UI):
  1. Go to the /IN/html/Acs_Service/language directory.
    Example command:
     cd /IN/html/Acs_Service/language
  2. Ensure the Default.lang file exists in this directory.
  3. If the required file does not exist, create an empty file called Default.lang.
  4. Ensure that the language file for your language exists in this directory. The file should be in the format:language.lang

    Where:

    language is your language.

    Example:

    Spanish.lang

  5. If the required language file does not exist, perform one of the following actions:
    • Create a new one with your language preferences
    • Contact Oracle support.
    To create a language file, you will need a list of the phrases and words used in the screens. These should appear in a list with the translated phrase in the following format:
    original phrase=translated phrase

    Any existing language file should have the full set of phrases. If you do not have an existing file to work from, contact Oracle support.

  6. Create a soft link between the Default.lang file, and the language file you want to use as the default language for the SMS UI.
    Example command:
    ln -s Dutch.lang Default.lang

Defining the Help Screen Language

The default Helpset file sets the language that the help system for the Java Administration screens start in. The user can change to another language after logging in.

The default language can be changed by the system administrator. By default, the language is set to English.

Default_Acs_Service.hs

When ACS is installed, a file called Default_Acs_Service.hs is created in the application's language directory in the screens module. This contains a soft-link to the language file which defines the language that will be used by the ACS UI.

If a Default_Acs_Service.hs file is:

  • Not present, the English_Acs_Service.hs file will be used.
  • Present, a user must explicitly set their language to their required language in the Tools screen or the default language will be used.

The Default_Acs_Service.hs file is located in the /IN/html/Acs_Service/helptext/ directory.

Example Helpset Language

If Dutch is the language you want to set as the default, create a soft-link from the Default_Acs_Service.hs file to the Dutch_Acs_Service.hs file.

Procedure

Follow these steps to set the default language for your ACS user interface (UI):

  1. Go to the /IN/html/Acs_Service/language directory.
    Example command:
    cd /IN/html/Acs_Service/helptext
  2. Ensure the Default_Acs_Service.hs file exists in this directory.
  3. If the required file does not exist, create an empty file called Default_Acs_Service.hs.
  4. Check if the language file for your language exists in this directory. The file should be in the format:language.Acs_Service.hs

    Where:

    language is your language.

    Example:

    Dutch_Acs_Service.hs

  5. If the required language file does not exist, perform one of the following actions:
    • Create a new one with your language preferences
    • Contact Oracle support.
    To create a language file, you will need a list of the phrases and words used in the screens. These should appear in a list with the translated phrase in the following format:
    original phrase=translated phrase

    Any existing language file should have the full set of phrases. If you do not have an existing file to work from, contact Oracle support.

  6. Create a soft link between the Default_Acs_Service.hs file, and the language file you want to use as the default language for the SMS UI.
    Example command:
    ln -s Dutch_Acs_Service.hs Default_Acs_Service.hs

Setting up the Screens

Accessing ACS

To use the Graphical user interface, you will need to do the following:

  • Ensure the Java SE Runtime Environment version 21 is installed on your computer.
  • If required, obtain, and install the trusted certificate for the database connection into your keystore.
  • Obtain the application zip file containing jars and executable. (acsGui.bat or acsGui.sh)
    • In Windows: Run acsGui.bat to start the application.
    • In other machines:
      • Change the permission of smsGui.sh by using "chmod 755 acsGui.sh"
      • Run the application by using "bash acsGui.sh" command.
      • Where SMS_hostname is the hostname of an SMS in the IN.
      • For more information about the ACS UI, see ACS User's Guide.

About Customizing the ACS UI

You can customize the ACS UI by setting Java application properties in the following files located in the /IN/html/ directory:
  • acsGui.bat/acsGui.sh
  • smsGui.bat/acsGui.sh
  • You use the following syntax to set a Java application property in the smsGui.bat/acsGui.sh or the smsGui.bat/acsGui.sh file:
    -Dproperty="value"
    Where:
    • property is the name of the Java application property.
    • value is the value to which that property is set.

    Note:

    Some Java application properties may be set in both the acsGui.bat/acsGui.sh file and in the smsGui.bat/acsGui.sh file. You must specify the same value in both files.

Java Application Properties

The following application properties are available to customize the UI:

jnlp.acs.ACSDefaultCustomerIsPrepaid

Syntax: -Djnlp.acs.ACSDefaultCustomerIsPrepaid="value"
Description: Specifies whether the ACS New Customer screen has the Prepaid Charging Customer check box selected by default.
Type: String
Optionality: Optional
Allowed:
  • True
  • t(rue)
  • Yes
  • y(es)
  • 1

All other values are considered to be false.
Default:  
Notes: If set to:
  • True – The Prepaid Charging Customer check box is selected by default.
  • False – The Prepaid Charging Customer check box is cleared by default.
Example: -Djnlp.acs.ACSDefaultCustomerIsPrepaid="value"

jnlp.acs.ACSStartScreenVersion

Syntax: jnlp.acs.allowRefInCustCombo
Description: Specifies whether users can perform searches in the ACS UI by using the customer reference number rather than the customer name.
Type: String
Optionality: Optional
Allowed:
  • True
  • t(rue)
  • Yes
  • y(es)
  • 1

All other values are considered to be false
Default: False
Notes:

If set to:

  • True – Allows searches using the customer reference number only.
  • False – Requires searches to include a customer name along with a customer reference number.
Example: -Djnlp.acs.allowRefInCustCombo = "t"

jnlp.acs.allowCallPlanSchedulingInPast

Syntax: -Djnlp.acs.allowCallPlanSchedulingInPast = "value"
Description: Specifies whether control plans can be scheduled to start in the past.
Type: String
Optionality: Optional
Allowed:
  • True
  • t(rue)
  • Yes
  • y(es)
  • 1

All other values are considered to be false
Default: False
Notes:

If set to:

  • True – Control plans can be scheduled to start in the past.
  • False – Control plans cannot be scheduled to start in the past.
Example: -Djnlp.acs.jnlp.acs.allowCallPlanSchedulingInPast = "t"

jnlp.acs.allowRefInCustCombo

Syntax: -Djnlp.acs.allowRefInCustCombo = "value"
Description: Specifies whether users can perform searches in the ACS UI by using the customer reference number rather than the customer name.
Type: String
Optionality: Optional
Allowed:
  • True
  • t(rue)
  • Yes
  • y(es)
  • 1

All other values are considered to be false
Default: False
Notes:

If set to:

  • True – Allows searches using the customer reference number only.
  • False – Requires searches to include a customer name along with a customer reference number.
Example: -Djnlp.acs.allowRefInCustCombo = "t"

jnlp.acs.autoCloseCompileDialog

Syntax: -Djnlp.acs.autoCloseCompileDialog = "value"
Description: Specifies whether the CPE compiler report closes automatically after a control plan compiles successfully.
Type: String
Optionality: Optional
Allowed:
  • True
  • t(rue)
  • Yes
  • y(es)
  • 1

All other values are considered to be false
Default: False
Notes:

If set to:

  • True – The CPE compiler report closes automatically after a control plan compiles successfully.
  • False – The CPE compiler report remains open after a control plan compiles successfully.
Example: -Djnlp.acs.autoCloseCompileDialog = "t"

jnlp.acs.autoCloseCPE

Syntax: -Djnlp.acs.autoCloseCPE = "value”
Description: Specifies whether the Control Plan Editor closes automatically after a control plan compiles successfully.
Type: String
Optionality: Optional
Allowed:
  • True
  • t(rue)
  • Yes
  • y(es)
  • 1

All other values are considered to be false
Default: False
Notes:

If set to:

  • True – The CPE closes automatically after a control plan compiles successfully.
  • False – The CPE remains open after a control plan compiles successfully.
Example: -Djnlp.acs.autoCloseCPE = “t"

jnlp.sms.clusterDatabaseHost

Syntax: -Djnlp.sms.clusterDatabaseHost = "(DESCRIPTION= (LOAD_BALANCE=YES)(FAILOVER=ON)(ENABLE=BROKEN) (ADDRESS_LIST=(ADDRESS=(PROTOCOL=type)(HOST=name)(PORT=port)) (ADDRESS=(PROTOCOL=type)(HOST=name)(PORT=port))) (CONNECT_DATA=(SERVICE_NAME=SMF)(FAILOVER_MODE=(TYPE=SESSION) (METHOD=BASIC)(RETRIES=5)(DELAY=3))))"
Description: Specifies the connection string (including a host and an alternative host address, in case the first IP address is unavailable) for non-SSL cluster-aware connection to the database.

To use non-SSL connections to the database, set the jnlp.sms.EncryptedSSLConnection property to false.

Type: String
Optionality: Optional
Allowed:  
Default: By default, port is set to 1521.
Notes: If present, this property is used instead of the jnlp.sms.databaseID property.
Example: -Djnlp.sms.clusterDatabaseHost = "(DESCRIPTION= (LOAD_BALANCE=YES)(FAILOVER=ON)(ENABLE=BROKEN) (ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=smsphysnode1) (PORT=1521)) (ADDRESS=(PROTOCOL=TCP)(HOST=smsphysnode2)(PORT=1521))) (CONNECT_DATA=(SERVICE_NAME=SMF)(FAILOVER_MODE=(TYPE=SESSION) (METHOD=BASIC)(RETRIES=5)(DELAY=3))))"

jnlp.acs.connectionsDialog

Syntax: -Djnlp.acs.connectionsDialog = "value"
Description: Specifies whether the Control Plan Editor displays the Manage Node Exits dialog box when you hold down the Shift key while dragging the mouse to connect a feature node exit to a feature node entry.
Type: String
Optionality: Optional. (default used if not set)
Allowed:
  • shown – CPE displays the Manage Node Exits dialog box.
  • hidden – CPE does not display the Manage Node Exits dialog box.
Default: shown
Notes:  
Example: -Djnlp.acs.connectionsDialog = "hidden"

jnlp.acs.cpeLineDrawingMechanism

Syntax: -Djnlp.acs.cpeLineDrawingMechanism = "connection_type"
Description:

Specifies the type of connector lines that the Control Plan Editor displays. You use connector lines to connect feature nodes in control plans.

Connector lines can be angled or straight lines:

  • Angled connector lines bend around feature nodes where possible instead of crossing over them. Angled connector lines are colored when highlighted.
  • HV connector lines use a combination of horizontal and vertical lines to connect feature nodes and may cross over other feature nodes. HV connector lines can be black or colored when highlighted.
Type: String
Optionality: Optional
Allowed:
  • ColouredNodeConnectionDrawer – The CPE displays connectors as angled lines that are colored when highlighted.
  • HVNodeConnectionDrawer – The CPE displays connectors as horizontal and vertical lines that are black.
  • ColouredHVNodeConnectionDrawer – The CPE displays horizontal and vertical lines that are colored when highlighted.
Default: ColouredNodeConnectionDrawer
Notes:  
Example: -Djnlp.acs.cpeLineDrawingMechanism = "HVNodeConnectionDrawer"

jnlp.sms.database

Syntax: -Djnlp.sms.database = "SMF"
Description: Specifies the Oracle SID for the SMF database.
Type: String
Optionality: Optional (default used if not set)
Allowed:  
Default: SMF
Notes: Set at installation
Example: -Djnlp.sms.database = "SMF"

jnlp.sms.databaseHost

Syntax: -Djnlp.sms.databaseHost = "ip:port:sid"
Description: Sets the IP address and port to use for non-SSL connections to the SMF database, and the database SID.
  • To use non-SSL connections to the database, set port to 1524 and the jnlp.sms.EncryptedSSLConnection property to false.
  • To use SSL connections to the database, set the jnlp.sms.EncryptedSSLConnection property to true and set either the jnlp.sms.secureConnectionDatabaseHost property or the jnlp.sms.secureConnectionClusterDatatbaseHost property appropriately. When the jnlp.sms.EncryptedSSLConnection property is set to true or is undefined, jnlp.sms.databaseHost is ignored.
Type: String
Optionality: Optional
Allowed:  
Default: Not set. Secure SSL connection is enabled at installation by default.
Notes: Internet Protocol version 6 (IPv6) addresses must be enclosed in square brackets []; for Example: [2001:db8 :n:n:n:n:n:n] where n is a group of 4 hexadecimal digits. The industry standard for omitting zeros is also allowed when specifying IP addresses.
Example: -Djnlp.sms.databaseHost = "192.0.2.1:2484:SMF"-Djnlp.sms.databaseHost = "[2001:db8:0000:1050:0005:0600:300c:326b]:2484:SMF"-Djnlp.sms.databaseHost = "[2001:db8:0:0:0:500:300a:326f]:2484:SMF" -Djnlp.sms.databaseHost = "[2001:db8::c3]:2484:SMF"

jnlp.sms.databaseID

Syntax: -Djnlp.sms.databaseID = "port:sid"
Description: Specifies the SQL*Net port for connecting to the database, and the database SID.
Type: String
Optionality: Required
Allowed:  
Default: 1521:SMF
Notes:
  • To use non-SSL connections to the database, set port to 1521 and the jnlp.sms.EncryptedSSLConnection property to false.
  • To use SSL connections to the database, set the jnlp.sms.EncryptedSSLConnection property to true and set either the jnlp.sms.secureConnectionDatabaseHost property or the jnlp.sms.secureConnectionClusterDatatbaseHost property appropriately. When the jnlp.sms.EncryptedSSLConnection property is set to true or is undefined, jnlp.sms.databaseHost is ignored.
Example: -Djnlp.sms.databaseID = "1521:SMF"

jnlp.sms.dbPassword

Syntax: -Djnlp.sms.dbPassword = "password"
Description: Specifies the database password. This password is for a special database user that the ACS Logon screen uses before the user logs in. This property is set during installation and is then not changed
Type: String
Optionality: Optional (default used if not set)
Allowed:  
Default: acs_public
Notes: Do not change this value.
Example: -Djnlp.sms.dbPassword = "acs_public"

jnlp.sms.dBUser

Syntax: -Djnlp.sms.dBUser = "user"
Description: Specifies the database user name. This is a special database user that the ACS Logon screen uses before the user logs in. This property is set during installation and is then not changed.
Type: String
Optionality: Optional (default used if not set)
Allowed:
Default: acs_public
Notes: Do not change this value.
Example: -Djnlp.sms.dBUser = "acs_public"

jnlp.acs.defaultTelcoManaged

Syntax: -Djnlp.acs.defaultTelcoManaged = "value"
Description:

Specifies whether new ACS customer accounts are marked as being managed by a Telecommunications Operator (telco) by default. Telco-managed customers are customers that never log into ACS but are managed explicitly (and without resource limits) by the telco.

This property controls whether the Managed Customer check box is selected in the ACS New Customer Details dialog box by default.
Type: String
Optionality: Optional
Allowed:
  • True
  • t(rue)
  • Yes
  • y(es)
  • 1

All other values are considered to be false.
Default: True
Notes:

If set to:

  • True – The Managed Customer check box is selected by default.
  • False – The Managed Customer check box is clear by default.
Example: -Djnlp.acs.defaultTelcoManaged = "f"

jnlp.sms.EncryptedSSLConnection

Syntax: -Djnlp.sms.EncryptedSSLConnection = "value"
Description: Specifies whether connections to the client UI use encrypted SSL.
Type: Boolean
Optionality: Optional (default used if not set)
Allowed:

true – Use encrypted SSL connections to access the client UI.

false – Use non-SSL connections to access the client UI.
Default: true
Notes:
  • To use SSL connections to the database, set the jnlp.sms.EncryptedSSLConnection property to true and set either the jnlp.sms.secureConnectionDatabaseHost property or the jnlp.sms.secureConnectionClusterDatatbaseHost property appropriately.
  • To use non-SSL connections to the database, set the jnlp.sms.EncryptedSSLConnection property to false.
Example: -Djnlp.sms.EncryptedSSLConnection = "true"

jnlp.sms.host

Syntax: -Djnlp.sms.host = "IPaddress"
Description: Specifies the Internet Protocol (IP) address for the SMS host machine that is set at installation.
Type: String
Optionality: Required
Allowed:
  • IP version 4 (IPv4) addresses
  • IP version 6 (IPv6) addresses
Default: No default
Notes: You can use the industry standard for omitting zeros when specifying IP addresses.
Example: 
-Djnlp.sms.host = "192.0.2.0"
-Djnlp.sms.host"
value="2001:db8:0000:1050:0005:0600:300c:326b" 
-Djnlp.sms.host = "2001:db8:0:0:0:500:300a:326f"
-Djnlp.sms.host = "2001:db8::c3"

jnlp.acs.issuePCClockWarning

Syntax: -Djnlp.acs.issuePCClockWarning = "value"
Description: Specifies whether a warning is raised when the user's PC clock time is more than two minutes faster or slower than the SMS platform's clock time.
Type: String
Optionality: Optional
Allowed:
  • True
  • t(rue)
  • Yes
  • y(es)
  • 1

All other values are considered to be false.
Default: True
Notes:

If set to:

  • True – A warning is raised.
  • False – A warning is not raised.
Example: -Djnlp.acs.issuePCClockWarning = "t"

jnlp.sms.logo

Syntax: -Djnlp.sms.logo = "file"
Description:

Specifies the logo displayed on the splash screen immediately before the ACS Logon screen appears.

At installation, the property is set to an Oracle logo GIF file.
Type: String
Optionality: Optional
Allowed: A valid network path and filename.
Default: None
Notes:
Example: -Djnlp.sms.logo = "SMS/images/oracle.gif"

jnlp.acs.MAX_CONTROL_PLANS_DISPLAYED

Syntax: -Djnlp.acs.MAX_CONTROL_PLANS_DISPLAYED = "num"
Description: Specifies the maximum number of control plans that can be displayed in the search results section of an ACS UI dialog box.
Type: String
Optionality: Optional
Allowed: 1 through 999
Default: 200
Notes:
Example: -Djnlp.acs.MAX_CONTROL_PLANS_DISPLAYED = "200"

jnlp.acs.maximiseAcsScreens

Syntax: -Djnlp.acs.maximiseAcsScreens="value"
Description: Specifies whether the windows in the ACS UI are opened at maximum size or optimum size.
Type: String
Optionality: Optional
Allowed:
  • True
  • t(rue)
  • Yes
  • y(es)
  • 1

All other values are considered to be false.
Default: False
Notes:

If set to:

  • True – The windows in the ACS UI are opened at maximum size.
  • False – The windows in the ACS UI are opened at optimum size.
Example: -Djnlp.acs.maximiseAcsScreens = "t"

jnlp.acs.paletteStyle

Syntax: -Djnlp.acs.paletteStyle = "value"
Description:

Specifies the style used to display the feature palette in the Control Plan Editor window. There are two possible feature palette styles:

  • The floating panel style feature palette displays feature group names in a list, and the feature nodes within a selected group in a floating panel. The floating panel style enables you to quickly locate a feature node in the palette by using the Search Palette feature to filter the available feature nodes.
  • The static panel style feature palette displays an expandable list of feature node groups from which you select individual feature nodes in a static panel. The Search Palette feature is not available with this style.
Type: String
Optionality: Optional
Allowed:
  • old – Sets the feature palette to the static panel style.
  • Not set – Sets the feature palette to the floating panel style.
Default: Floating panel style
Notes: To enable the jnlp.acs.paletteStyle property, clear the Java cache and the client browser cache before restarting the Control Plan Editor.
Example: -Djnlp.acs.paletteStyle = "old"

jnlp.sms.port

Syntax: -Djnlp.sms.port = "num"
Description: Specifies the SQL*Net port for connecting to the SMS host machine.
Type: Integer
Optionality: Optional (default used if not set)
Allowed:
Default: 1521
Notes: Set at installation
Example: -Djnlp.sms.port = "num"

jnlp.acs.ProfileN

Syntax: -Djnlp.acs.Profilenumber = "new_name" smsGui.bat/smsGui.sh
Description: Specifies to suppress or change the name of any of the 20 profile blocks.
Type: String
Optionality: Optional
Allowed:

1 £ number £ 20

new_name is one of the following:

  • – (dash): The profile block is not displayed in screens.
  • String comprising any printable characters.
Default:

The following table lists default profile block names in the order in which they appear in feature node drop-down lists.

Profile1 - VPN Network Profile

Profile2 - VPNStation Profile

Profile3 - Customer Profile

Profile4 - Control Plan Profile

Profile5 - Global Profile

Profile6 - CLI Subscriber Profile

Profile7 - Service Number Profile

Profile8 - App Specific 1

Profile9 - App Specific 2

Profile10 - App Specific 3

Profile11 - App Specific 4

Profile12 - App Specific 5

Profile13 - App Specific 6

Profile14 - App Specific 7

Profile15 - App Specific 8

Profile16 - Any Valid Profile

Profile17 - Temporary Storage

Profile18 - Call Context

Profile19 - Outgoing Extensions

Profile20 - Incoming Extensions
Notes:
  • If VPN is not installed, Profile1 and Profile2 are suppressed by default.
  • If Charging Control Services is installed, profile block names associated with Profile8 through Profile15 are changed automatically. For more information, see CCS Technical Guide.
  • If RCA is not installed, Profile19 and Profile20 are suppressed by default. You can make them available by installing RCA or by appending them to the smsGui.bat/smsGui.sh file.
  • Feature nodes with writable fields cannot write into Profile16.
Example: 
-Djnlp.acs.Profile1 = "–" 
-Djnlp.acs.Profile6 = "Originating CLI"

jnlp.acs.requireCustomerReference

Syntax: -Djnlp.acs.requireCustomerReference = "value"
Description: Specifies whether a customer reference number is mandatory for each ACS customer that is created.
Type: String
Optionality: Optional
Allowed:
  • True
  • t(rue)
  • Yes
  • y(es)
  • 1

All other values are considered to be false.
Default: True
Notes:

If set to:

  • True – Customer reference numbers are mandatory for newly created ACS customers.
  • False – Customer reference numbers are optional for newly created ACS customers.
Example: -Djnlp.acs.requireCustomerReference = "f"

jnlp.acs.scfs

Syntax: -Djnlp.acs.scfs = "scfn"
Description:

Lists the network entities that are available for handover.

The names listed in this section are used by the following feature nodes:

  • TCAP Handover (as the SCP Name list)
  • RIMS MAP Query and IS41 Query (as the Return Address for mapping the SCCP Calling Party Address)
Type: String
Optionality: Optional. However, the TCAP Handover feature node must have at least one scf to work.
Allowed: Any scf name configured in the acs.conf file. See acsChassis SSF Configuration (SLC) for more information.
Default: None
Notes: For every jnlp.acs.scfs property in the JNLP file, you must create a matching scf entry in the acs.conf file on each SLC defining the address associated with this entry.
Example: -Djnlp.acs.scfs = "SCF_Name1,SCF_Name2"

jnlp.acs.SDRfastTimeoutDefault

Syntax: -Djnlp.acs.SDRfastTimeoutDefault = "secs"
Description: Specifies the default fast timeout period, in seconds, for the Selection Dependent Routing feature node. If the specified timeout period expires before a customer enters a digit on their telephone keypad, the feature node exits. You can use this feature, for example, to connect calls directly to the operator after timing out.
Type: Integer
Optionality: Optional (default used if not set)
Allowed: Any positive integer
Default: 10
Notes:
Example: -Djnlp.acs.SDRfastTimeoutDefault = "5"

jnlp.sms.secureConnectionDatabaseHost

Syntax: 
-Djnlp.sms.secureConnectionDatabaseHost = "(DESCRIPTION=
(ADDRESS_LIST=(ADDRESS=(PROTOCOL=type)(HOST=IPaddress)
 (PORT=port))))(CONNECT_DATA=(SERVICE_NAME=servicename)))"
Description:

Specifies the connection string (including host address and port) for encrypted SSL connections to the SMF database on a non-clustered system.

To use SSL connections to the database, set port to 2484 and set the jnlp.sms.EncryptedSSLConnection property to true.

Type: String
Optionality: Optional (default used if not set)
Allowed:
Default:
Notes: If present, this property is used instead of the jnlp.sms.databaseID property.
Example: 
-Djnlp.sms.secureConnectionDatabaseHost = "(DESCRIPTION=
(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCPS)(HOST=192.0.1.1)
 (PORT=2484))))(CONNECT_DATA=(SERVICE_NAME=SMF)))"

jnlp.sms.secureConnectionClusterDatabaseHost

Syntax: 
-Djnlp.sms.secureConnectionClusterDatabaseHost = "(DESCRIPTION=
(ADDRESS_LIST=(ADDRESS=(PROTOCOL=type)(HOST=IPaddress)
(PORT=port))
(ADDRESS=(PROTOCOL=type)(HOST=IPaddress)(PORT=port)))
(CONNECT_DATA=(SERVICE_NAME=servicename)))"
Description:

Specifies the connection string (including host address and port) for encrypted SSL connections to the SMF database on a clustered system.

To enable secure SSL connections to the database, set port to 2484 and set the jnlp.sms.EncryptedSSLConnection property to true.

Type: String
Optionality: Optional (default used if not set)
Allowed:
Default:
Notes: If present, this property is used instead of the jnlp.sms.secureConnectionDatabaseHost property.
Example: 
-Djnlp.sms.secureConnectionClusterDatabaseHost = "(DESCRIPTION=
(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCPS)(HOST=192.0.1.1)
(PORT=2484))
(ADDRESS=(PROTOCOL=TCP)(HOST=192.0.2.1)(PORT=2484)))
(CONNECT_DATA=(SERVICE_NAME=SMF)))"

jnlp.acs.showAnnouncementSource

Syntax: -Djnlp.acs.showAnnouncementSource = "value"
Description: Specifies whether announcement sources (i.e., the resource name and resource ID) are displayed next to announcement names in ACS UI windows.
Type: String
Optionality: Optional
Allowed:
  • TRUE
  • true
  • YES
  • yes
  • Y
  • y

All other values are considered to be false.
Default: True
Notes:

If set to:

  • True – Announcement sources are displayed.
  • False – Announcement sources are not displayed.
Example: -Djnlp.acs.showAnnouncementSource = "f"

jnlp.acs.showCallPlanCopy

Syntax: -Djnlp.acs.showCallPlanCopy = "value"
Description: Specifies whether the Copy button is enabled on the ACS Numbers screen.
Type: String
Optionality: Optional
Allowed:
  • True
  • t(rue)
  • Yes
  • y(es)
  • 1

All other values are considered to be false.
Default: True
Notes:

If set to:

  • True – The Copy button is enabled.
  • False – The Copy button is disabled.
Example: -Djnlp.acs.showCallPlanCopy" = "f"

jnlp.acs.showNetwork

Syntax: -Djnlp.acs.showNetwork = "value"
Description: Specifies whether the Network field is displayed in the ACS New Customer dialog box.
Type: String
Optionality: Optional
Allowed:
  • True
  • t(rue)
  • Yes
  • y(es)
  • 1

All other values are considered to be false.
Default: True
Notes:

If set to:

  • True – The Network field is displayed.
  • False – The Network field is not displayed.
Example: -Djnlp.acs.showNetwork = "f"

jnlp.acs.ssfs

Syntax: -Djnlp.acs.ssfs = "ssf1,ssf2,...,ssfn"
Description:

Lists the switches that are available in the IN network.

The switches listed in this section are used by the Call Initiation feature node (as the switch name list).
Type: String
Optionality: Optional. However, the Call Initiation feature node must have at least one scf to work.
Allowed: Any ssf name configured in the acs.conf file. See acsChassis SSF Configuration (SLC) for more information.
Default: None
Notes:
Example: -Djnlp.acs.ssfs = "SSF_Name1,SSF_Name2"

jnlp.sms.sslCipherSuites

Syntax: -Djnlp.sms.sslCipherSuites = "(TLS_RSA_WITH_AES_128_CBC_SHA)"
Description: Specifies the cipher suites to use for SSL encryption. You must set this property if you are using encrypted SSL for connecting to the SMS database.
Type: String
Optionality: Optional (default used if not set)
Allowed: (TLS_RSA_WITH_AES_128_CBC_SHA)
Default: (TLS_RSA_WITH_AES_128_CBC_SHA)
Notes: You must also set the SSL_CIPHER_SUITES property to (TLS_RSA_WITH_AES_128_CBC_SHA) in the listener.ora and sqlnet.ora files.
Example: -Djnlp.sms.sslCipherSuites = "(TLS_RSA_WITH_AES_128_CBC_SHA)"

jnlp.acs.suppressedSDRDigits

Syntax: -Djnlp.acs.suppressedSDRDigits = "digits"
Description:

The Selection Dependent Routing feature node allows you to route calls based on the number, letter, or special character entered on the caller's telephone keypad.

You use the jnlp.acs.suppressedSDRDigits property to prevent users from assigning specified digits to a calling route and to exclude those digits from the Configure Selection Dependent Routing dialog box of the ACS Control Plan Editor.
Type: String
Optionality: Optional
Allowed:
  • Numbers ranging from 0 (zero) through 9
  • Letters ranging from A through F
  • Special characters * and #
Default: None
Notes:
Example: -Djnlp.acs.suppressedSDRDigits = "12ab"

jnlp.acs.SuppressTagID

Syntax: -Djnlp.acs.SuppressTagID = "value"
Description:

Specifies to not include the profile tag value when displaying a profile field name in the ACS Control Plan Editor.

For example, when jnlp.acs.SuppressTagID is set to:

  • true – The profile tag 196613 displays the name "PIN Prefix"
  • false – The profile tag 196613 displays the name "PIN Prefix (196613)"
Type: Boolean
Optionality: Optional
Allowed:
  • True
  • t(rue)
  • Yes
  • y(es)
  • 1

All other values are considered to be false
Default: True
Notes:

If set to:

  • True – Only the profile field name is displayed.
  • False – Both the profile field name and the profile field value is displayed.
Example: -Djnlp.acs.SuppressTagID = "True"

jnlp.trace

Syntax: -Djnlp.trace = "value"
Description: Specifies whether to enable tracing for the Control Plan Editor. The output is displayed in the Java Console.
Type: Boolean
Optionality: Optional (default used if not set)
Allowed: on | off, true | false, yes | no, 1 | 0, enabled | disabled
Default: Off
Notes:
Example: -Djnlp.trace = "on"

jnlp.sms.TZ

Syntax: Djnlp.sms.TZ = "timezone"
Description: Specifies the time zone used for all time and date values displayed in Convergent Charging Controller UI windows.
Type: String
Optionality: Optional (default used if not set)
Allowed: Any Java supported time zone.
Default: GMT
Notes: For a full list of Java supported time zones, see Time Zones for more information.
Example: -Djnlp.sms.TZ = "GMT"

jnlp.acs.updateCPReferences

Syntax: -Djnlp.acs.updateCPReferences = "value"
Description: When you update a control plan, the Control Plan Editor creates a new version of the control plan. If any customers are scheduled to use the older version of the control plan, the customers' service numbers or CLIs remain attached to the older version by default. This property specifies whether you can attach customers' service numbers or CLIs to the new control plan version.
Type: String
Optionality: Optional
Allowed:
  • True
  • t(rue)
  • Yes
  • y(es)
  • 1

All other values are considered to be false.
Default: None
Notes:

If set to:

  • True – After an updated control plan compiles successfully, the Control Plan Editor prompts you to select the service numbers or CLIs to attach to the new control plan version.
  • False – The existing service numbers or CLIs remain attached to the older version of the content plan.
Example: -Djnlp.acs.updateCPReferences = "t"

jnlp.ccs.UseAnnouncements

Syntax: -Djnlp.ccs.UseAnnouncements = "value"
Description: Specifies whether to play announcements.
Type: String
Optionality: Optional
Allowed:
  • True
  • t(rue)
  • Yes
  • y(es)
  • 1

All other values are considered to be false.
Default: False
Notes:
Example: -Djnlp.ccs.UseAnnouncements = "Yes"

jnlp.acs.useTNForNodeName

Syntax: -Djnlp.acs.useTNForNodeName = "value" value="value" />
Description:

Specifies whether the feature node name displayed in the Control Plan Editor window is the Termination Number (TN). This applies to the following feature nodes only:

  • Attempt Termination (AT)
  • Unconditional Termination (UT)

The TN is displayed for any UT or AT feature node in the CPE window, without requiring you to save each feature node to update the stored control plan data.

Type: Boolean
Optionality: Optional (default used if not set)
Allowed:
  • True
  • t(rue)
  • Yes
  • y(es)
  • 1

All other values are considered to be false.
Default: False
Notes:

If set to:

  • True – The feature node name is displayed as the TN in the CPE window.
  • False – The feature node name is displayed as the stored feature node name in the CPE window.

You can update the TN for these feature nodes in a control plan by using the ACS Numbers screen. See the discussion about Editing Termination Numbers in ACS User's Guide for more information.

Example: -Djnlp.acs.useTNForNodeName = "true"

jnlp.acs.warnAboutUnfilledExits

Syntax: -Djnlp.acs.warnAboutUnfilledExits = "True"
Description:

Specifies whether a control plan passes validation if any of its feature nodes are missing exits.

This property has a dependency on the endUnlinkedExits parameter. For more information, see endUnlinkedExits
Type: String
Optionality: Optional
Allowed:
  • True
  • t(rue)
  • Yes
  • y(es)
  • 1

All other values are considered to be false.
Default: False
Notes:

If set to:

  • True – Control plans that are missing feature node exits will pass validation. To work, you must also set the endUnlinkedExits parameter to 1.
  • False – Control plans that are missing node exits will fail during validation.
Example: -Djnlp.acs.warnAboutUnfilledExits = "True"

Example GUI Script Application Properties

Here is an example acsGui.bat/acsGui.sh file showing the application property settings at installation.

acsGui.bat 

@echo off
REM Copyright (c) 2025 Oracle. All rights reserved.
REMREM This material is the confidential property of Oracle Corporation or its
REM licensors and may be used, reproduced, stored or transmitted only in
REM accordance with a valid Oracle license or sublicense agreement.
REM
REM
REM acsGui.bat: runs the ACS application
REM Run: execute acsGui.bat
 
REM Set JAR_PATH to the current directory
set JAR_PATH=%~dp0

REM Enable delayed expansion
setlocal enabledelayedexpansion

REM Set classpath
set
CLASSPATH=%JAR_PATH%;%JAR_PATH%sms.jar.sig;%JAR_PATH%acs.jar.sig;%JAR_PATH%common.jar
.sig;%JAR_PATH%ojdbc11.jar.sig;%JAR_PATH%oraclepki.jar.sig;%JAR_PATH%ohj.jar.sig;%JAR
_PATH%help-
share.jar.sig;%JAR_PATH%oracle_ice.jar.sig;%JAR_PATH%jewt.jar.sig;%JAR_PATH%share.jar
.sig;%JAR_PATH%osd.jar.sig;%JAR_PATH%rims.jar.sig;%JAR_PATH%xms.jar.sig;%JAR_PATH%ses
.jar.sig;

REM Starting GUI....
java ^
     -Djava.util.Arrays.useLegacyMergeSort=true ^
     -Djava.util.Arrays.useLegacyMergeSort=true ^     
     -Djnlp.sms.TZ=GMT ^
     -Djnlp.sms.host=OUI_HOSTNAME ^ 
     -Djnlp.sms.port=LPORT ^ 
     -Djnlp.sms.database=OUI_ORACLE_SID ^   
     -Djnlp.sms.databaseHost=NCC_DBHOST:LPORT:OUI_ORACLE_SID ^
     -Djnlp.sms.secureConnectionDatabaseHost="(DESCRIPTION= (ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCPS)(HOST=NCC_DBHOST)(PORT=SECPORT))) (CONNECT_DATA=
(SERVICE_NAME=OUI_ORACLE_SID)))" ^
        -Djnlp.sms.EncryptedSSLConnection=true ^    
        -Djnlp.sms.sslCipherSuites="(TLS_RSA_WITH_AES_128_CBC_SHA)" ^
        -Djnlp.vpn.INProtocol=IN_PROTOCOL ^
        -Djnlp.acs.SuppressTagID=TRUE ^
        -Djnlp.acs.Profile8="Account Reference Profile" ^
        -Djnlp.acs.Profile9="Product Type Profile" ^
        -Djnlp.acs.Profile10="Control Plan Profile (App 3)" ^
        -Djnlp.acs.Profile12="CCS Global Profile" ^
        -Djnlp.acs.Profile13="CCS Temporary Profile (App 6)" ^
        -Djnlp.acs.Profile14="CCS Temporary Profile (App 7)" ^
        -Djnlp.acs.Profile15="CCS Temporary Profile (App 8)" ^
        -Djnlp.acs.ACSDefaultCustomerIsPrepaid=false ^
        -Djnlp.ccs.UseAnnouncements=YES ^
        -cp "%CLASSPATH%" ^
com.g8labs.acs.coreScreens.Application 

REM End delayed expansion
endlocal
acsGui.sh
#!/bin/bash

###############################################################################
#
# Copyright (c) 2025  Oracle. All rights reserved.
#
# This material is the confidential property of Oracle Corporation or its
# licensors and may be used, reproduced, stored or transmitted only in
# accordance with a valid Oracle license or sublicense agreement.
#
#
# acsGui.sh : runs the ACS application
# Run: bash acsGui.sh
#
###############################################################################

JAR_PATH=$(pwd)

CLASSPATH=$JAR_PATH/:$JAR_PATH/sms.jar.sig:\
$JAR_PATH/acs.jar.sig:\
$JAR_PATH/common.jar.sig:\
$JAR_PATH/ojdbc11.jar.sig:\
$JAR_PATH/oraclepki.jar.sig:\
$JAR_PATH/ohj.jar.sig:\
$JAR_PATH/help-share.jar.sig:\
$JAR_PATH/oracle_ice.jar.sig:\
$JAR_PATH/jewt.jar.sig:\
$JAR_PATH/share.jar.sig:\
$JAR_PATH/osd.jar.sig:\
$JAR_PATH/rims.jar.sig:\
$JAR_PATH/xms.jar.sig:\
$JAR_PATH/ses.jar.sig:


echo "Starting GUI...."
exec ${JAVA_HOME}/bin/java \
    -Djava.util.Arrays.useLegacyMergeSort=true \
    -Djnlp.sms.TZ=GMT \
    -Djnlp.sms.host=OUI_HOSTNAME \
    -Djnlp.sms.port=LPORT \
    -Djnlp.sms.database=OUI_ORACLE_SID \
    -Djnlp.sms.databaseHost=NCC_DBHOST:LPORT:OUI_ORACLE_SID \
    -Djnlp.sms.secureConnectionDatabaseHost="(DESCRIPTION= (ADDRESS_LIST=

(ADDRESS=(PROTOCOL=TCPS)(HOST=NCC_DBHOST)(PORT=SECPORT))) (CONNECT_DATA=
(SERVICE_NAME=OUI_ORACLE_SID)))" \    
      -Djnlp.sms.EncryptedSSLConnection=true \
      -Djnlp.sms.sslCipherSuites="(TLS_RSA_WITH_AES_128_CBC_SHA)" \
      -Djnlp.vpn.INProtocol=IN_PROTOCOL \
      -Djnlp.acs.SuppressTagID=TRUE \
      -Djnlp.acs.Profile8="Account Reference Profile" \
      -Djnlp.acs.Profile9="Product Type Profile" \
      -Djnlp.acs.Profile10="Control Plan Profile (App 3)" \
      -Djnlp.acs.Profile12="CCS Global Profile" \
      -Djnlp.acs.Profile13="CCS Temporary Profile (App 6)" \
      -Djnlp.acs.Profile14="CCS Temporary Profile (App 7)" \
      -Djnlp.acs.Profile15="CCS Temporary Profile (App 8)" \
      -Djnlp.acs.ACSDefaultCustomerIsPrepaid=false \
      -Djnlp.ccs.UseAnnouncements=YES \
      -cp "$CLASSPATH" \
com.g8labs.acs.coreScreens.Application