4.3 Access Manager Configuration Files and Folders

IMPORTANT:From Access Manager 5.0, modifying a configuration file directly on a device is not supported. Any modification made directly on a device is replaced when modifications made through Administration Console are applied. You must customize a configuration file using Advanced File Configurator on Administration Console.

You can add or fetch your files in the following folders:

You can manage the following files through Advanced File Configurator:

NOTE:Advanced File Configurator does not support managing system files, such as /etc/init.d/novell-apache2 and /etc/rsyslog.conf.

bcsLogin.conf

For information about how to modify a file, see Modifying Configurations.

Device

 

Restart after Modification

Identity Server

/opt/novell/java/jre/lib/security/

Yes. On the Identity Servers page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Identity Server service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Identity Server pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-identity-server-pod> -- sh command.

  3. Run the /etc/init.d/novell-idp restart or rcnovell-idp restart command.

server.xml

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Administration Console

/opt/novell/nam/adminconsole/conf/

Yes. Restart Tomcat by running the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Administration Console pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-administration-console-pod> -c am-ac -- sh command.

  3. Run the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

Identity Server

/opt/novell/nids/lib/webapp/WEB-INF/

Yes. On the Identity Servers page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Identity Server service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Identity Server pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-identity-server-pod> -- sh command.

  3. Run the /etc/init.d/novell-idp restart or rcnovell-idp restart command.

Access Gateway

/opt/novell/nam/mag/conf/

Yes. On the Access Gateways page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Access Gateway service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Access Gateway pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-access-gateway-pod> -- sh command.

  3. Run the /etc/init.d/novell-mag restart or rcnovell-mag restart command.

web.xml

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Administration Console

/opt/novell/nam/adminconsole/conf/

Yes. Restart Tomcat by running the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Administration Console pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-administration-console-pod> -c am-ac -- sh command.

  3. Run the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

Identity Server

/opt/novell/nids/lib/webapp/WEB-INF/

Yes. On the Identity Servers page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Identity Server service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Identity Server pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-identity-server-pod> -- sh command.

  3. Run the /etc/init.d/novell-idp restart or rcnovell-idp restart command.

Risk Service

/opt/novell/nam/idp/webapps/rba-core/WEB-INF/

Yes. On the Identity Servers page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Identity Server service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Identity Server pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-identity-server-pod> -- sh command.

  3. Run the /etc/init.d/novell-idp restart or rcnovell-idp restart command.

Access Gateway

/opt/novell/nam/mag/conf/

Yes. On the Access Gateways page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Access Gateway service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Access Gateway pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-access-gateway-pod> -- sh command.

  3. Run the /etc/init.d/novell-mag restart or rcnovell-mag restart command.

Embedded Service Provider

/opt/novell/nesp/lib/webapp/WEB-INF/

Yes. On the Access Gateways page, click Actions > Service Provider > Restart Service Provider > OK.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Access Gateway pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-access-gateway-pod> -- sh command.

  3. Run the /etc/init.d/novell-mag restart or rcnovell-mag restart command.

kerb.properties

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/WEB-INF/classes

Yes. On the Identity Servers page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Identity Server service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Identity Server pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-identity-server-pod> -- sh command.

  3. Run the /etc/init.d/novell-idp restart or rcnovell-idp restart command.

context.xml

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Administration Console

/opt/novell/nam/adminconsole/conf/

Yes. Restart Tomcat by running the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Administration Console pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-administration-console-pod> -c am-ac -- sh command.

  3. Run the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

Identity Server

/opt/novell/nids/lib/webapp/META-INF/

Yes. On the Identity Servers page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Identity Server service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Identity Server pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-identity-server-pod> -- sh command.

  3. Run the /etc/init.d/novell-idp restart or rcnovell-idp restart command.

tomcat.conf

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Administration Console

/opt/novell/nam/adminconsole/conf/tomcat8.conf

Yes. Restart Tomcat by running the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Administration Console pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-administration-console-pod> -c am-ac -- sh command.

  3. Run the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

Identity Server

/opt/novell/nam/idp/conf/tomcat.conf

Yes. On the Identity Servers page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Identity Server service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Identity Server pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-identity-server-pod> -- sh command.

  3. Run the /etc/init.d/novell-idp restart or rcnovell-idp restart command.

Access Gateway

/opt/novell/nam/mag/conf/tomcat.conf

Yes. On the Access Gateways page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Access Gateway service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Access Gateway pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-access-gateway-pod> -- sh command.

  3. Run the /etc/init.d/novell-mag restart or rcnovell-mag restart command.

cic_linux.txt

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nam/idp/webapps/nidp/classUtils/

Yes. On the Identity Servers page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Identity Server service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Identity Server pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-identity-server-pod> -- sh command.

  3. Run the /etc/init.d/novell-idp restart or rcnovell-idp restart command.

nidpmonitor.txt

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nam/idp/webapps/nidp/WEB-INF/

Yes. On the Identity Servers page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Identity Server service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Identity Server pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-identity-server-pod> -- sh command.

  3. Run the /etc/init.d/novell-idp restart or rcnovell-idp restart command.

Access Gateway

/opt/novell/nam/mag/webapps/nesp/WEB-INF/

Yes. On the Access Gateways page, click Actions > Service Provider > Restart Service Provider > OK.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Access Gateway pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-access-gateway-pod> -- sh command.

  3. Run the /etc/init.d/novell-mag restart or rcnovell-mag restart command.

sun-jaxws.xml

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nam/idp/webapps/nidp/WEB-INF/

Yes. On the Identity Servers page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Identity Server service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Identity Server pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-identity-server-pod> -- sh command.

  3. Run the /etc/init.d/novell-idp restart or rcnovell-idp restart command.

main.jsp

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/jsp/

No

nidp.jsp

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/jsp/

No

content.jsp

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/jsp/

No

nidp_latest.jsp

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/jsp/

No

login.jsp

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/jsp/

No

login_latest.jsp

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/jsp

No

logout.jsp

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/jsp/

No

Access Gateway

/opt/novell/nesp/lib/webapp/jsp

No

logoutSuccess.jsp

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/jsp/

No

Access Gateway

/opt/novell/nesp/lib/webapp/jsp

No

logoutSuccess_latest.jsp

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/jsp

No

Access Gateway

/opt/novell/nesp/lib/webapp/jsp

No

logoutSuccess_legacy.jsp

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/jsp

No

Access Gateway

/opt/novell/nesp/lib/webapp/jsp

No

err.jsp

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/jsp/

No

Access Gateway

/opt/novell/nesp/lib/webapp/jsp

No

err_latest.jsp

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/jsp

No

Access Gateway

/opt/novell/nesp/lib/webapp/jsp

No

err_legacy.jsp

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/jsp

No

socialauth_icons.jsp

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/jsp/

No

oauth2UserConsent.jsp

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/jsp/

No

oauth2LogoutConsent.jsp

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/jsp/

No

impersonator.jsp

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/jsp/

No

impersonatee.jsp

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/jsp/

No

ux_access.css

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/css

No

httpd.conf

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Access Gateway

/etc/opt/novell/apache2/conf/

Yes. Restart Apache by running the following command:

/etc/init.d/novell-apache2 restart OR rcnovell-apache2 restart

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Access Gateway pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-access-gateway-pod> -- sh command.

  3. Run the /etc/init.d/novell-mag restart or rcnovell-mag restart command.

vcdn.conf

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Administration Console

/opt/novell/devman/share/conf

Yes. Restart Tomcat by running the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Administration Console pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-administration-console-pod> -c am-ac -- sh command.

  3. Run the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

ErrorPagesConfig.xml

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Access Gateway

/opt/novell/nam/mag/webapps/agm/WEB-INF/config/current/

Yes. On the Access Gateways page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Access Gateway service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Access Gateway pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-access-gateway-pod> -- sh command.

  3. Run the /etc/init.d/novell-mag restart or rcnovell-mag restart command.

ErrorMessages.xml.<lang>

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Access Gateway

/opt/novell/nam/mag/webapps/agm/WEB-INF/config/current/

Yes. On the Access Gateways page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Access Gateway service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Access Gateway pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-access-gateway-pod> -- sh command.

  3. Run the /etc/init.d/novell-mag restart or rcnovell-mag restart command.

NovellAgSettings.conf

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Access Gateway

/etc/opt/novell/apache2/conf/

Yes. Restart Apache by running the following command:

/etc/init.d/novell-apache2 restart OR rcnovell-apache2 restart

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Access Gateway pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-access-gateway-pod> -- sh command.

  3. Run the /etc/init.d/novell-mag restart or rcnovell-mag restart command.

httpd-mpm.conf

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Access Gateway

/etc/opt/novell/apache2/conf/extra/

Yes. Restart Apache by running the following command:

/etc/init.d/novell-apache2 restart OR rcnovell-apache2 restart

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Access Gateway pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-access-gateway-pod> -- sh command.

  3. Run the /etc/init.d/novell-mag restart or rcnovell-mag restart command.

httpd-multilang-errordoc.conf

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Access Gateway

/etc/opt/novell/apache2/conf/extra/

Yes. Restart Apache by running the following command:

/etc/init.d/novell-apache2 restart OR rcnovell-apache2 restart

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Access Gateway pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-access-gateway-pod> -- sh command.

  3. Run the /etc/init.d/novell-mag restart or rcnovell-mag restart command.

agm.properties

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Access Gateway

/opt/novell/nam/mag/webapps/agm/WEB-INF/

Yes. On the Access Gateways page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Access Gateway service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Access Gateway pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-access-gateway-pod> -- sh command.

  3. Run the /etc/init.d/novell-mag restart or rcnovell-mag restart command.

top.html

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Access Gateway

/opt/novell/apache2/share/apache2/error/include/

Yes. Restart Apache by running the following command:

/etc/init.d/novell-apache2 restart OR rcnovell-apache2 restart

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Access Gateway pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-access-gateway-pod> -- sh command.

  3. Run the /etc/init.d/novell-mag restart or rcnovell-mag restart command.

bottom.html

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Access Gateway

/opt/novell/apache2/share/apache2/error/include/

Yes. Restart Apache by running the following command:

/etc/init.d/novell-apache2 restart OR rcnovell-apache2 restart

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Access Gateway pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-access-gateway-pod> -- sh command.

  3. Run the /etc/init.d/novell-mag restart or rcnovell-mag restart command.

rest_nps_web.xml

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Administration Console

/var/opt/novell/iManager/nps/WEB-INF/

Yes. Restart Tomcat by running the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Administration Console pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-administration-console-pod> -c am-ac -- sh command.

  3. Run the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

config.xml

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Administration Console

/var/opt/novell/iManager/nps/WEB-INF/

Yes. Restart Tomcat by running the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Administration Console pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-administration-console-pod> -c am-ac -- sh command.

  3. Run the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

Advanced Authentication Plug-in

/opt/novell/nam/idp/plugins/aa/

Yes. On the Identity Servers page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Identity Server service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Identity Server pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-identity-server-pod> -- sh command.

  3. Run the /etc/init.d/novell-idp restart or rcnovell-idp restart command.

Access Gateway

/opt/novell/nam/mag/webapps/agm/WEB-INF/config/current

Yes. On the Access Gateways page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Access Gateway service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Access Gateway pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-access-gateway-pod> -- sh command.

  3. Run the /etc/init.d/novell-mag restart or rcnovell-mag restart command.

listen.conf

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Access Gateway

/etc/opt/novell/apache2/conf/

Yes. Restart Apache by running the following command:

/etc/init.d/novell-apache2 restart OR rcnovell-apache2 restart

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Access Gateway pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-access-gateway-pod> -- sh command.

  3. Run the /etc/init.d/novell-mag restart or rcnovell-mag restart command.

config.properties

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Administration Console

/var/opt/novell/iManager/nps/WEB-INF/

Yes. Restart Tomcat by running the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Administration Console pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-administration-console-pod> -c am-ac -- sh command.

  3. Run the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

configiman.properties

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Administration Console

/var/opt/novell/iManager/nps/WEB-INF/

Yes. Restart Tomcat by running the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Administration Console pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-administration-console-pod> -c am-ac -- sh command.

  3. Run the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

jsp_resources_en_US.properties

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nam/idp/webapps/nidp/WEB-INF/classes/properties

Yes. On the Identity Servers page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Identity Server service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Identity Server pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-identity-server-pod> -- sh command.

  3. Run the /etc/init.d/novell-idp restart or rcnovell-idp restart command.

nidp.jar

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/WEB-INF/lib

Yes. On the Identity Servers page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Identity Server service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Identity Server pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-identity-server-pod> -- sh command.

  3. Run the /etc/init.d/novell-idp restart or rcnovell-idp restart command.

Access Gateway

/opt/novell/nam/mag/webapps/nesp/WEB-INF/lib

Yes. On the Access Gateways page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Access Gateway service automatically.

NAMCommon.jar

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nids/lib/webapp/WEB-INF/lib

Yes. On the Identity Servers page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Identity Server service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Identity Server pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-identity-server-pod> -- sh command.

  3. Run the /etc/init.d/novell-idp restart or rcnovell-idp restart command.

Access Gateway

/opt/novell/nam/mag/webapps/nesp/WEB-INF/lib

Yes. On the Access Gateways page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Access Gateway service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Access Gateway pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-access-gateway-pod> -- sh command.

  3. Run the /etc/init.d/novell-mag restart or rcnovell-mag restart command.

sc.conf

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/devman/share/conf

Yes. On the Identity Servers page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Identity Server service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Identity Server pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-identity-server-pod> -- sh command.

  3. Run the /etc/init.d/novell-idp restart or rcnovell-idp restart command.

nam.conf

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Administration Console

/opt/novell/syslog/rsyslog.d/

Yes. Restart Tomcat by running the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Administration Console pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-administration-console-pod> -c am-ac -- sh command.

  3. Run the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

namMultiTarget.conf

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Administration Console

/opt/novell/syslog/rsyslog.d/

Yes. Restart Tomcat by running the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Administration Console pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-administration-console-pod> -c am-ac -- sh command.

  3. Run the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

Auditlogging.cfg

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Administration Console

/opt/novell/syslog/

Yes. Restart Administration Console by running the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

For the Docker deployment, perform the following steps to restart Administration Console:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Administration Console pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-administration-console-pod> -c am-ac -- sh command.

  3. Run the /etc/init.d/novell-ac restart or rcnovell-ac restart command.

Restart syslog by running the following commands:

  • SLES 12, SLES 15: rcsyslog restart OR systemctl restart rsyslog

  • RHEL 6.9: service rsyslog restart

  • RHEL 7.6: systemctl restart rsyslog.service

  • Docker environment, execute this script: /opt/novell/nam/docker/restart_rsyslog.sh

limits.conf

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/etc/security/

Yes. On the Identity Servers page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Identity Server service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Identity Server pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-identity-server-pod> -- sh command.

  3. Run the /etc/init.d/novell-idp restart or rcnovell-idp restart command.

logging.properties

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nam/idp/conf/

Yes. On the Identity Servers page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Identity Server service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Identity Server pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-identity-server-pod> -- sh command.

  3. Run the /etc/init.d/novell-idp restart or rcnovell-idp restart command.

externKeystore.properties

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/nam/idp/webapps/nidp/WEB-INF/classes/

Yes. On the Identity Servers page, click Update All. By default, Custom Files Configuration is selected. This action restarts the Identity Server service automatically.

For the Docker deployment, perform the following steps:

  1. Run the kubectl get pods command to view the Access Manager pods.

  2. Go to the Identity Server pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-identity-server-pod> -- sh command.

  3. Run the /etc/init.d/novell-idp restart or rcnovell-idp restart command.

dtomcat9

For information about how to modify a file, see Modifying Configurations.

Device

Path

Restart after Modification

Identity Server

/opt/novell/tomcat9/bin/

No

Access Manager Configuration Folders

The following tables list the folders that are available by default when you install Access Manager:

Table 4-1 Administration Console Default Folder

/var/opt/novell/iManager/nps/portal/modules

/opt/novell/devman/share/conf

Table 4-2 Identity Server Default Folder

/opt/novell/nam/idp/webapps/nidp/images/

/opt/novell/nam/idp/webapps/nidp/WEB-INF/classes/

/opt/novell/nids/lib/webapp/jsp

/opt/novell/nam/idp/webapps/nidp/css/

/opt/novell/nam/idp/webapps/nidp/javascript

Table 4-3 Access Gateway Default Folder

/opt/novell/nam/mag/webapps/nesp/images/

/opt/novell/nesp/lib/webapp/jsp/

/opt/novell/nesp/lib/webapp/css/

/opt/novell/nesp/lib/webapp/javascript/

/opt/novell/nesp/lib/webapp/html/

/opt/novell/nesp/lib/webapp/images/

/opt/novell/nesp/lib/webapp/config/

/opt/novell/nesp/lib/webapp/WEB-INF/classes/

/etc/opt/novell/apache2/conf/extra/

/opt/novell/apache2/share/apache2/error/

/opt/novell/nam/mag/webapps/agm/WEB-INF/config/current/

/opt/novell/nam/mag/webapps/agm/WEB-INF/config/apache2/