All the NetStore Administration functions are maintained in the Administration application.
NetStore Administration
Administration is an application to handle system administration tasks foremost to NetStore. It is also of help for the programmer during development. Administration application does not use all NetStore frontend features since it is an internally used system that is utilised by very few users. It therefore does not, for example, need the same kind of flexibility and performance thinking as the NetStore frontend.
Note: If several administration sessions are active and one system administrator, for instance, closes NetStore it is possible from another administrator session to reopen NetStore again.
Mandatory Administration property file:
- Adm.Config.properties
- Contains NetStore Administration configuration attributes overriding.
Menu options
The following menu options are described in this section:
- Preload
- Update of session tracker cleanup
- Close/Shutdown NetStore
- Work with NetStore site cache
- Work with pools
- Show configuration
- Session tracking
- Work with users
Preload
The preload function is used to load data to the NetStore Backoffice files. Different modes, files and mandatory fields can be preloaded.
Caution: The use of the preload function should be restricted when the customer installation is done. The restriction is made using the setting type ValidNSAdminFunction. If the preload function is used after the customer installation and if all NetStore Backoffice files have been updated, all values will be set to default again.
The preload function is always used during installation of NetStore if the NetStore Backoffice files are empty.
Panel image
During the installation you must complete the following mandatory fields in the Preload selection (You do not have to access the Backoffice application to change these fields):
- Preload mode
- Select a preload mode to be used when you load data to the NetStore Backoffice files.
- Note: This field is not shown during the installation.
- File
- Select the files to which you want to load data.
- Note: This field is not shown during the installation.
- Primary language
- The primary language is the system language to which the preload constants will be translated.
- Secondary language
- The secondary language is the second language to which the preload constants will be translated. However, we have just made an example of a translated secondary language constant. The secondary language that you choose will be added to the supported language vector in NetStore automatically. This will indicate for NetStore that this language also should be supported.
- Note: You must translate the Preload_language code (e.g. for Sweden Preload_SV) to the secondary language in order for this to work. You must also translate the NSNLS_language code (e.g. for Sweden NSNLS_SV). The NSNLS_language code is used when language sensitive text on JSP’s and BAP constants/message should be translated. All text in NetStore will then be translated.
- Handler
- Enter the default order handler. We recommend that you use order handler NETSTORE. This must be added to the Enterprise/DC1 Signature table.
- Lost sales reason
- Select the lost sales reason from the list.
- Address category
- Select the default category from the list.
- Order type
- Enter the sales order type to be used for NetStore orders. The recommended sales order type is value IO.
- Request initial status
- Enter the request status code. The recommended value is NSN. This value is added in the Enterprise/DC1 Request status table.
- From/To date
- Enter default from/to dates to be used in the system.
- Note: To add new preload data into the Backoffice files you need to develop your own preload data in class: se.ibs.ns.adm.NSDataPreloader
Update of session tracker cleanup
Panel image
The session tracker keeps track of all the sessions currently active within NetStore and Administration. All new sessions should be registered on the session tracker. Session tracker’s main task is to get all active session ids and check if a specific session id is active. The maximum inactive time is configurable. The inactive time is set in a static variable on the Session Tracker during site cache initialisation. In session tracker you can manipulate the session tracker cleanup methods.
The session tracker cleanup functions are responsible for removing inactive sessions in NetStore and Administration. The session tracker cleanup thread or session tracker single cleanup function removes invalid sessions. The cleanup interval for the cleanup thread is configurable by Backoffice.
The session tracker cleanup thread will be initialised the first time a user uses either NetStore or Administration after the server has been started. If the system has been set up to have no automatic cleanup (Session tracker cleanup interval = 0) the cleanup thread will not start automatic and inactive sessions will not be removed. But you can start the session tracker single cleanup function.
The session tracker single cleanup function will execute the cleanup function at once and not in a thread. This is good to use when the web site has been visited by many users and the session tracker cleanup thread has not been run.
The system administrator can also see the maximum inactive time and the cleanup interval for a session in NetStore.
Close/Shutdown NetStore
Panel image
Shutdown of NetStore is a function for closing or shutting down NetStore so no client can enter the web site. This function may be used when NetStore, for instance, has a comprehensive web site update.
Actions handled on this page
If the Do not allow new user is ticked, NetStore will be closed for new clients. Clients that have already entered the web site can still add orders or, e.g., search on quotation.
If the Notify active users that NetStore is to be shutdown in __ minutes has been ticked a message will be sent to active users that have already entered NetStore and notify them about the shutdown. If no minutes have been added a message will be sent to NetStore users that system will be shutdown soon.
When Close is clicked, the system administrator can choose to cancel close or to do a complete shutdown.
Prompted with this window:
Panel image
Actions handled on this page
If the Close pool is ticked the system will close the pool. Closing a pool will also expire (close) all resources managed by the pool. This will happen instantly without waiting for clients that might currently be using the resources in the pool. When Shutdown is clicked the PoolCleaner and PoolObjectReclaimer threads are stopped.
If the Clear of site cache is ticked the system will reset preloaded and additional site cache data when you click Shutdown.
After clicking Shutdown the following page will appear:
Panel image
When clicking on Open the system administrator will open NetStore for clients. First client that visits the web site will initialise NetStore environment.
Work with NetStore site cache
Panel image
Using the Work with NetStore site cache function you can refresh additional preloaded data in the site cache data, clear the site cache or view the NetStore site cache. This function can be used during customer development to refresh/clear or view the site cache without closing the web server.
Caution: If you click Clear or Refresh when NetStore is up and running this will cause problems for the users that are visiting the web site. If the web site is up and running for a customer, you should use the Close/shutdown function instead. If you clear the NetStore site cache data while web users are placing orders they might not be able to close their orders.
Below are some situations when work with NetStore site cache function makes it easier for the system administrator or developer to work:
- When something on the site cache needs to be updated, for example, the product catalogue that is cached on the site cache.
- To know what is actually up on the site cache.
- During development.
Work with pools
Panel image
Connection pooling is a technique used for sharing server resources among requesting clients. A connection pool is a named group of identical JDBC connections to a database that is created when the connection pool is registered. The connection properties for a start-up connection pool are defined in the ConnectionPool.xml file.
In the Administration application the system administrator can choose to work with Monitor or Close a pool.
Monitor pools
Panel image
Page for monitoring the database connection pools in NetStore and Administration applications. In Monitor pool page it is possible to see statistics and configuration data for the selected pool.
Note: For a developer it can be useful information to see if any resources that remain locked in the pool exists.
Close pools
Panel image
If you click Close the system will close the pool. Closing a pool will also expire (close) all resources managed by the pool. This will happen instantly without waiting for clients that might currently be using the resources in the pool. The PoolCleaner and PoolObjectReclaimer threads are stopped.
Show configuration
Panel image
This function can be used to view the property files for the system. This function should primarily be used by the developer during development to quickly see what the property files holds and test different property data. However, the function can also be used for run time environment.
The Netstore configuration panel displays the database connection, the static connection, the Administration configuration, and the NetStore configuration files. If any extended property files exist, these are also displayed on this panel.
- The files CCF.DBConnection.properties and CCF.StaticConnection.properties contain all connection and start up related properties.
- CCF.DBConnection.properties contains database connection configuration attributes. The property file has been set up to have NetStore Front-end running in a connection pool and NetStore Administration using static database connection.
- CCF.StaticConnection.properties is used instead of the ConnectionPool.xml when applications are using static database connection.
- The NS.Config.properties file contains NetStore configuration attributes.
- The Adm.Config.properties file contains NetStore administration specific configuration.
Session tracking
Panel image
In Session Administration page it is possible to track what sessions are up and running, inactivate sessions, and send messages to all users or selected users. It is not possible to inactivate your own administration session or to send messages to it. By clicking Start search you will see all active sessions and be able to work with individual or several sessions.
Work with users
User and customer accounts that are not created directly must be approved before they can be used. With this function the administrator can disable or enable user accounts, approve or reject requests for new accounts. When a request is approved or rejected an e-mail is sent to the user with necessary information, such as password etc.
Panel image
Note: Internal NetStore users and administrators cannot be handled in this tool.
The following tasks are handled in this tool.
- Approving new customers or users
When a customer or user is approved an e-mail is sent to the user with password, user id and customer number. The mail text can be entered or a standard text can be used. When a customer is approved the new customer number must be entered. - Rejecting customer or user requests
Rejections are handled similar to approvals, but with another standard text. - Enabling or disabling users
No e-mail is sent when users are enabled or disabled. - Sending e-mails to users
The mail subject and message text has to be entered.