How Can We Help?

Search for answers or browse our knowledge base.

Documentation | Demos | Support

< All Topics
Print

Web ViewPoint Enterprise Configuration Parameters

This screen allows you to edit and configure parameters. It is simple, easy to use and dynamic. You can now configure parameters on the fly with one touch filter for dynamic and static parameters. Parameter table list is also color graded to differentiate between dynamic and static parameters.

Dynamic parameters:

Parameters that can be edited while the product is running. Respective rows are white color graded.

Static Parameters:

Parameters that require the product to be stopped before editing. Respective rows are grey color graded.

There are 40 Params configured when you install and setup Web ViewPoint Enterprise. They are as follows:

1.  ACTION-COLLECTOR

Name of the EMS collector to which alerts sent to Enterprise Manager via JSON are logged.

Default: $0

2. ANALYZER-COLLECTION-TIME

Time at which the collection should run by Event & Storage Analyzer modules. The data collection for both Storage and Event Analyzer modules takes place once every day.

Valid Range: 00:00 to 23:59

Default: 00:05

The changed settings do not come into effect until after the next run of the collector. In other words, the WVP E’s SA/EA modules reads the configuration file after it has finished collecting for that day and it only runs once every day. So, if the user changes the run time the following are possible scenarios:

Collector run scenarios
Original Run time New Run time Has run today?  

Effect on Collection

 

1:00 pm 8:00 pm (later than the original schedule)  

No (i.e., current time is prior to 1pm)

 

Collector will run at 1:00 pm today and will run at 8:00 pm from the next day onward.
1:00 pm 8:00 pm (later than the original schedule)  

Yes

 

 

Collector will run at 1:00 pm the next day ,read the new settings and run at 8:00 pm from the next day onward. Note that it will not run again today.

1:00 pm  

10:00 am (before the original schedule)

 

No Collector will run at 1:00 pm today and will run at 10:00 am from the next day onward.
1:00 pm 10:00 am (before the original schedule) Yes Collector will run at 1:00 pm today, read the new settings and run at 10:00 am from the next day onward.
3. ANALYZER-DATA-RETAIN

Maximum number of days to retain Event Analyzer & Storage Analyzer data collection. This works as the cleanup logic for the newly created store subvolumes.

Valid Range: 1 – 180

Default: 90

4. ANALYZER-STORE-VOL

Guardian Volume where EA & SA files are stored. Storage volume is the name of Volume where Event Analyzer should store its files. One file is created daily, named EAACT, and is stored in a subvolume named ‘EAyymmdd’, where ‘yymmdd’ represents the day on which the action events were generated.

Default: $DSMSCM

5. AUTOLICENSE

Whether at 60 days before License expiration date, should WVP E check for new License via internet.

Default: Yes

6. CCMOPER-AUTHENCACHE

Period (in seconds) for which MFA token will be cached.

Default: 300

7. CCMOPER-TIMEOUT

Period (in seconds) CCMOPER stays alive with the recent user’s access id.

Default: 600

8. CONFIG

Guardian Volume.Subvolume location where the SSLCONF file is located.

Default: SSLCONF

9. EA-COLLECTORS

Collectors whose log files are scanned daily by Event Analyzer module. Multiple collectors can be added whose log files should be scanned daily. You can specify up to 25 collectors in total.

Default: $0

10. EA-CPU-THROTTLE

Maximum CPU busy(%) Event Analyzer should use during its nightly work.

Default: 5

11. EMSLINK-BUSY-MAX

Maximum CPU Busy % the EMS query module may use when querying for a search string.

Valid Range: 5 – 80

Default: 5

12. EMSLINKTIMEOUT

The amount of time after which Events Query module should timeout when it does not receive a request from the user.

Valid Range: 5 – 80

Default: 5

13. ENFORCE-SECURITY

Option to enable the user permissions and access control feature. If this feature is enforced then it allows only the users who have permissions to Web ViewPoint Enterprise to logon.

Default: No

14. EVENTS-PAGE-SIZE

Number of Events which should be displayed on a browser page, before older events are removed.

Valid Range: 100 – 1000

Default: 1000

15. EVENT_LOG_COLLECTOR

EMS collector WVP E should write its messages to.

Default: $0

16. EXECUTION-LOG

This is a runtime requirement for WVPPREF and UMPGATE.

17. FILTERFILE-LOCATION

Where you keep your EMS Filter files ($VOL.SUBVOL). This list of filter files is displayed on the Events settings screen of Web ViewPoint Enterprise.

18. HIDEACKS

Hides the acknowledged EMS Events from the Events View.

Default: No

19. LISTENER-PORT

Port number used by Listener Process.

Valid Range: 1025 – 65535 or 443

Default: 8787

20. LISTENER-PROCESS

Process name used by the Listener Process.

Default: $WVLST

21. LITEAUTH

Indicates whether the light version of Web ViewPoint Enterprise, requires Logon.

Default: No

22. MAXPROCESS

The maximum number of UMPGATE processes that can run at the same time.

Default: 20

23. MULTILANGSUPPORT

Character set, text portions of EMS Events should support. This specifies whether multi-language character support is required for displaying of EMS messages in Events.

Default: English

24. NUMSTATIC

The maximum number of static UMPGATE processes that can be active.

Default: 10

25. OSSPPD-PROCESS

Name of the SNMP process, if SNMP is to be used.

Default: $USNMP

26. OSSSYSLOG-PROCESS

Name of the SYSLOG process, if SYSLOG is to be used.

Default: $UMPSL

27. OUT-TCP-PROCESS

TCP Process Web ViewPoint Enterprise uses to send out Alerts.

Default: $ZTC0

28. PATHWAY-01

Location ($VOL.SUBVOL.FILENAME) where you have your PATHMON programs in.

Default: $SYSTEM.SYSTEM.PATHMON

29. RDF-LOCATION

Where your RDF environment ($vol.subvol) is present. This is used by WVP E’s alert module to monitor & report on RDF metrics.

Default: $SYSTEM.RDF

30. SA-OLDFILES

The value for this field is used to determine what files will be included in the old file count in Storage Analyzer (i.e. those files that do not have a used date within the number of days specified, thus being considered “old”). Files meeting this criteria will show as “Old files” in Event Analyzer.

Valid Range: 1 – 1000

Default: 365

31. SA-RELOAD

The files whose index levels are greater than or equal to the specified value will only be selected for collection. The value for this field is used to calculate the number of reloadable files for disks.

Valid Range: 1-255

Default: 3

32. SAVEEVENTS

This specifies the EMSLINK whether to show the Save Events to Log option on the settings screens. If SAVEEVENTS is NO, the Save Events to Log feature is disabled and the option does not appear on the Events Settings screen.

Default: No

33. SCROLL-DELAY

Controls the speed at which the events are displayed on the Events screen.

Valid Range: 0 – 100

Default: 0

34. SEND-RESET

Specifies whether the mail server requires RESET during mail delivery handshake.

Default: Yes

35. SEND-SMS-DIRECT

Indicates if you want to send SMS alerts directly via SMS server instead of Phone Carriers.

Default: No

36. SMTP-PORT

SMTP Port to be used for alert Email/SMS delivery notifications. Set the SMTP port to 25 for non-secure SMTP servers.

Valid Range: 1 – 65535

Default: 587

37. SMTP-TIMEOUT

This allows the user to specify the amount of time (in milli seconds) after which UMPDRNE should timeout when it does not receive a request from the SMTP server.

Default: 500

38. SNMP-VERSION

Indicates the version of SNMP, if it is to be used.

Default: v2

39. TCP-PROCESS

TCP Process used by Web ViewPoint Enterprise.

Default: $ZTC0

40. WEBLOCATION

The OSS Directory where Product’s UI library files should be stored in.

Default: /usr/tandem/wvpe

Was this article helpful?
0 out of 5 stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
5
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Table of Contents
Skip to content