Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
syed_17 Super Contributor.
Super Contributor.
2101 views

Access Manager Appliance installation Issues

I have downloaded and deployed the eval copy of NAM4.4 available online. I followed the instructions in the documentation related to installation. The installation goes smoothly but he Access Gateway on the Dashboard shows no AG-Cluster and appears to be blank. I understood from the documentation that the AccessManager appliance.iso contains all the components integrated in it including Access Gateway default with reverse proxy. Hope I am correct in my understanding. However, it shows only IDP cluster but not the Access Gateway cluster!!!!

I need to know if the file I am picking is the right one or any other file I need to install for getting Access Gateway also running!!!! If I am correct, then what could be the issue??? Can I verify somehow, if my installation is correct or bad??

Any helpful ideas are highly appreciated.
0 Likes
19 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Access Manager Appliance installation Issues

On 10-01-2019 4:04 AM, squadri wrote:
>
> I have downloaded and deployed the eval copy of NAM4.4 available online.
> I followed the instructions in the documentation related to
> installation. The installation goes smoothly but he Access Gateway on
> the Dashboard shows no AG-Cluster and appears to be blank. I understood
> from the documentation that the AccessManager appliance.iso contains all
> the components integrated in it including Access Gateway default with
> reverse proxy. Hope I am correct in my understanding. However, it shows
> only IDP cluster but not the Access Gateway cluster!!!!
>
> I need to know if the file I am picking is the right one or any other
> file I need to install for getting Access Gateway also running!!!! If I
> am correct, then what could be the issue??? Can I verify somehow, if my
> installation is correct or bad??


This can happen if you don't allocate sufficient memory to the virtual machine (i'm assuming you are using virtual hardware). Tomcat doesn't want to
start due to lack of memory which then has a cascading effect that the installer can't create the AG cluster. How much memory have you allocated to
the VM?

Any errors that shown during the installation as well?




--
Cheers,
Edward
0 Likes
syed_17 Super Contributor.
Super Contributor.

Re: Access Manager Appliance installation Issues

Yes it’s a virtual machine with 8GB memory. It does not show errors on installation. I noted seeing the messages “installing the access Gateway “ . But like you mentioned, will again reinstall with added memory and check. How can I check if tomcat or other services/processes for access Gateway are running or not?
0 Likes
ScorpionSting Absent Member.
Absent Member.

Re: Access Manager Appliance installation Issues

squadri;2493348 wrote:
Yes it’s a virtual machine with 8GB memory. It does not show errors on installation. I noted seeing the messages “installing the access Gateway “ . But like you mentioned, will again reinstall with added memory and check. How can I check if tomcat or other services/processes for access Gateway are running or not?



/etc/init.d/novell-appliance status

Visit my Website for links to Cool Solution articles.
syed_17 Super Contributor.
Super Contributor.

Re: Access Manager Appliance installation Issues

ScorpionSting;2493349 wrote:

/etc/init.d/novell-appliance status


It only has /start/stop/restart but no status option with /etc/init.d/novell-appliance /start/stop/restart
0 Likes
ScorpionSting Absent Member.
Absent Member.

Re: Access Manager Appliance installation Issues

squadri;2493356 wrote:
It only has /start/stop/restart but no status option with /etc/init.d/novell-appliance /start/stop/restart


If you double-tab on /etc/init.d/novell- then you'll get a list of the services, each service does have a status option

Visit my Website for links to Cool Solution articles.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Access Manager Appliance installation Issues

On 10-01-2019 7:46 AM, squadri wrote:
>
> Yes it�s a virtual machine with 8GB memory. It does not show errors on
> installation. I noted seeing the messages �installing the access Gateway
> � . But like you mentioned, will again reinstall with added memory and
> check. How can I check if tomcat or other services/processes for access
> Gateway are running or not?
>
>

8 GB is more than sufficient. With 4GB the install works fine (obviously not suited for production load tho). Can you check if you can see a file
called /tmp/novell_access_manager/configure_cluster_<date>.log and post the output here? It should contain the output of the cluster creation and if
there were any errors.

--
Cheers,
Edward
syed_17 Super Contributor.
Super Contributor.

Re: Access Manager Appliance installation Issues

edmaa;2493357 wrote:
On 10-01-2019 7:46 AM, squadri wrote:
>
> Yes it�s a virtual machine with 8GB memory. It does not show errors on
> installation. I noted seeing the messages �installing the access Gateway
> � . But like you mentioned, will again reinstall with added memory and
> check. How can I check if tomcat or other services/processes for access
> Gateway are running or not?
>
>

8 GB is more than sufficient. With 4GB the install works fine (obviously not suited for production load tho). Can you check if you can see a file
called /tmp/novell_access_manager/configure_cluster_<date>.log and post the output here? It should contain the output of the cluster creation and if
there were any errors.

--
Cheers,
Edward


Hello Edward,
As mentioned earlier, I once again installed NAM appliance ,this time with 12 GB RAM , the problem still appears to be the same. Here is the output of configure_cluster log copied from your mentioned path :
Creating clusters...
Creating the Identity Server cluster...
/opt/novell/java/bin/java -classpath "/opt/novell/nam/adminconsole/webapps/roma/WEB-INF/lib/*" com.volera.roma.app.handler.AutoConfigHandlerWrapper configureIdpCluster nam.almabani.com.sa almabani.com.sa 192.168.1.25 192.168.1.25 cn=admin,o=novell XXXXX
Invoking IDP cluster creation URL : https://192.168.1.25:8443/nps/rest/clusterconfig/idpcluster?ClusterName=IDPCluster&eDirReplicaIPAddress=192.168.1.25&dnsName=nam.almabani.com.sa&AdminName=cn=admin,o=novell&AdminPassword=xxxx
Response: 200

Creating the Access Gateway cluster...
/opt/novell/java/bin/java -classpath "/opt/novell/nam/adminconsole/webapps/roma/WEB-INF/lib/*" com.volera.roma.app.handler.AutoConfigHandlerWrapper configureAGCluster nam.almabani.com.sa almabani.com.sa 192.168.1.25 192.168.1.25 cn=admin,o=novell XXXXX ag-4A2FD1247EC91A6C
Invoking Access Gateway cluster creation URL : https://192.168.1.25:8443/roma/autoconfig/cntl?handler=group_create&actionCmd=SaveNameAndDesc&groupCluster_check=on&groupName=AG-Cluster&groupPrimaryServer=ag-4A2FD1247EC91A6C&groupUrl=192.168.1.25&ag-4A2FD1247EC91A6C_checkbox_vcp=ag-4A2FD1247EC91A6C
Response code:302

Importing the default policies...
/opt/novell/java/bin/java -classpath "/opt/novell/nam/adminconsole/webapps/roma/WEB-INF/lib/*" com.volera.roma.app.handler.AutoConfigHandlerWrapper configurePolicies nam.almabani.com.sa almabani.com.sa 192.168.1.25 192.168.1.25 cn=admin,o=novell XXXXX
Invoking URL: https://192.168.1.25:8443/roma/autoconfig/cntl?handler=group_create&actionCmd=ImportDefaultPolicies&policycollectionid=xpemlPEP&prevstep=savepolicy&containerid=mastercdn
Response code:200

Enabling role based policies for the Identity Server cluster...
/opt/novell/java/bin/java -classpath "/opt/novell/nam/adminconsole/webapps/roma/WEB-INF/lib/*" com.volera.roma.app.handler.AutoConfigHandlerWrapper enableIDPRoles nam.almabani.com.sa almabani.com.sa 192.168.1.25 192.168.1.25 cn=admin,o=novell XXXXX
Invoking URL: https://192.168.1.25:8443/nps/rest/clusterconfig/configureservices?dm.sessionSynchronization.idpRoles=%3Cxpeml%3APolicyEnforcementList%20xmlns%3Axpeml%3D%22urn%3Anovell%3Aschema%3Axpeml%3A2.0%3Apolicy%22%20RuleCombiningAlgorithm%3D%22DenyOverridesWithPriority%22%20IncludedPolicyCategories%3D%22%22%20schemaVersion%3D%222.0%22%20LastModified%3D%224294967295%22%20LastModifiedBy%3D%22String%22%3E%3Cxp...
Response code:200



Its noticed that Response code for creating Access Gateway cluster appears to be code:302 unlike others where it shows Response code:200 . Does that mean an error?? If yes, please guide how to fix it.
0 Likes
syed_17 Super Contributor.
Super Contributor.

Re: Access Manager Appliance installation Issues

btw, while creating vmware Virtual Machine , I had taken the Network Adapter as E1000 for Esxi Host 6.5. ref to documentation : Using a Network Adapter for VMWare ESX#
Use the E1000 network adapter for Access Manager Appliance installation on VMWare ESX.
ref: https://www.netiq.com/documentation/access-manager-44-appliance/install_upgrade/data/b139b2nx.html from Virtual Machine requirements. is that correct or we are supposed to take VMXNet3 adapter???
0 Likes
Highlighted
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Access Manager Appliance installation Issues

On 10-01-2019 7:36 PM, squadri wrote:
>
> btw, while creating vmware Virtual Machine , I had taken the Network
> Adapter as E1000 for Esxi Host 6.5. ref to documentation : -Using a
> Network Adapter for VMWare ESX#
> Use the E1000 network adapter for Access Manager Appliance installation
> on VMWare ESX.- ref:
> https://www.netiq.com/documentation/access-manager-44-appliance/install_upgrade/data/b139b2nx.html
> from Virtual Machine requirements. is that correct or we are supposed to
> take VMXNet3 adapter???


I dont think that particularly matters to be honest. My VM here in my lab also uses the e1000 driver.


--
Cheers,
Edward
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Access Manager Appliance installation Issues

On 10-01-2019 6:44 PM, squadri wrote:
>
> edmaa;2493357 Wrote:
>> On 10-01-2019 7:46 AM, squadri wrote:
>>>
>>> Yes it�s a virtual machine with 8GB memory. It does not show errors

>> on
>>> installation. I noted seeing the messages �installing the access

>> Gateway
>>> � . But like you mentioned, will again reinstall with added memory

>> and
>>> check. How can I check if tomcat or other services/processes for

>> access
>>> Gateway are running or not?
>>>
>>>

>> 8 GB is more than sufficient. With 4GB the install works fine (obviously
>> not suited for production load tho). Can you check if you can see a file
>> called /tmp/novell_access_manager/configure_cluster_<date>.log and post
>> the output here? It should contain the output of the cluster creation
>> and if
>> there were any errors.
>>
>> --
>> Cheers,
>> Edward

>
> Hello Edward,
> As mentioned earlier, I once again installed NAM appliance ,this time
> with 12 GB RAM , the problem still appears to be the same. Here is the
> output of configure_cluster log copied from your mentioned path :
> -Creating clusters...
> Creating the Identity Server cluster...
> /opt/novell/java/bin/java -classpath
> "/opt/novell/nam/adminconsole/webapps/roma/WEB-INF/lib/*"
> com.volera.roma.app.handler.AutoConfigHandlerWrapper configureIdpCluster
> nam.almabani.com.sa almabani.com.sa 192.168.1.25 192.168.1.25
> cn=admin,o=novell XXXXX
> Invoking IDP cluster creation URL :
> https://192.168.1.25:8443/nps/rest/clusterconfig/idpcluster?ClusterName=IDPCluster&eDirReplicaIPAddress=192.168.1.25&dnsName=nam.almabani.com.sa&AdminName=cn=admin,o=novell&AdminPassword=xxxx
> Response: 200
>
> Creating the Access Gateway cluster...
> /opt/novell/java/bin/java -classpath
> "/opt/novell/nam/adminconsole/webapps/roma/WEB-INF/lib/*"
> com.volera.roma.app.handler.AutoConfigHandlerWrapper configureAGCluster
> nam.almabani.com.sa almabani.com.sa 192.168.1.25 192.168.1.25
> cn=admin,o=novell XXXXX ag-4A2FD1247EC91A6C
> Invoking Access Gateway cluster creation URL :
> https://192.168.1.25:8443/roma/autoconfig/cntl?handler=group_create&actionCmd=SaveNameAndDesc&groupCluster_check=on&groupName=AG-Cluster&groupPrimaryServer=ag-4A2FD1247EC91A6C&groupUrl=192.168.1.25&ag-4A2FD1247EC91A6C_checkbox_vcp=ag-4A2FD1247EC91A6C
> *Response code:302*
>
> Importing the default policies...
> /opt/novell/java/bin/java -classpath
> "/opt/novell/nam/adminconsole/webapps/roma/WEB-INF/lib/*"
> com.volera.roma.app.handler.AutoConfigHandlerWrapper configurePolicies
> nam.almabani.com.sa almabani.com.sa 192.168.1.25 192.168.1.25
> cn=admin,o=novell XXXXX
> Invoking URL:
> https://192.168.1.25:8443/roma/autoconfig/cntl?handler=group_create&actionCmd=ImportDefaultPolicies&policycollectionid=xpemlPEP&prevstep=savepolicy&containerid=mastercdn
> Response code:200
>
> Enabling role based policies for the Identity Server cluster...
> /opt/novell/java/bin/java -classpath
> "/opt/novell/nam/adminconsole/webapps/roma/WEB-INF/lib/*"
> com.volera.roma.app.handler.AutoConfigHandlerWrapper enableIDPRoles
> nam.almabani.com.sa almabani.com.sa 192.168.1.25 192.168.1.25
> cn=admin,o=novell XXXXX
> Invoking URL: http://tinyurl.com/y74q4wae
> Response code:200-
>
>
> Its noticed that Response code for creating Access Gateway cluster
> appears to be code:302 unlike others where it shows Response code:200 .
> Does that mean an error?? If yes, please guide how to fix it.
>
>

I'm also seeing a 302 response code here in my lab when it creates the AG cluster. Can you check if the ESP has actually started?

cat /opt/novell/nam/mag/logs/catalina.out



--
Cheers,
Edward
0 Likes
syed_17 Super Contributor.
Super Contributor.

Re: Access Manager Appliance installation Issues

edmaa;2493369 wrote:
On 10-01-2019 6:44 PM, squadri wrote:
>
> edmaa;2493357 Wrote:
>> On 10-01-2019 7:46 AM, squadri wrote:
>>>
>>> Yes it�s a virtual machine with 8GB memory. It does not show errors

>> on
>>> installation. I noted seeing the messages �installing the access

>> Gateway
>>> � . But like you mentioned, will again reinstall with added memory

>> and
>>> check. How can I check if tomcat or other services/processes for

>> access
>>> Gateway are running or not?
>>>
>>>

>> 8 GB is more than sufficient. With 4GB the install works fine (obviously
>> not suited for production load tho). Can you check if you can see a file
>> called /tmp/novell_access_manager/configure_cluster_<date>.log and post
>> the output here? It should contain the output of the cluster creation
>> and if
>> there were any errors.
>>
>> --
>> Cheers,
>> Edward

>
> Hello Edward,
> As mentioned earlier, I once again installed NAM appliance ,this time
> with 12 GB RAM , the problem still appears to be the same. Here is the
> output of configure_cluster log copied from your mentioned path :
> -Creating clusters...
> Creating the Identity Server cluster...
> /opt/novell/java/bin/java -classpath
> "/opt/novell/nam/adminconsole/webapps/roma/WEB-INF/lib/*"
> com.volera.roma.app.handler.AutoConfigHandlerWrapper configureIdpCluster
> nam.almabani.com.sa almabani.com.sa 192.168.1.25 192.168.1.25
> cn=admin,o=novell XXXXX
> Invoking IDP cluster creation URL :
> https://192.168.1.25:8443/nps/rest/clusterconfig/idpcluster?ClusterName=IDPCluster&eDirReplicaIPAddress=192.168.1.25&dnsName=nam.almabani.com.sa&AdminName=cn=admin,o=novell&AdminPassword=xxxx
> Response: 200
>
> Creating the Access Gateway cluster...
> /opt/novell/java/bin/java -classpath
> "/opt/novell/nam/adminconsole/webapps/roma/WEB-INF/lib/*"
> com.volera.roma.app.handler.AutoConfigHandlerWrapper configureAGCluster
> nam.almabani.com.sa almabani.com.sa 192.168.1.25 192.168.1.25
> cn=admin,o=novell XXXXX ag-4A2FD1247EC91A6C
> Invoking Access Gateway cluster creation URL :
> https://192.168.1.25:8443/roma/autoconfig/cntl?handler=group_create&actionCmd=SaveNameAndDesc&groupCluster_check=on&groupName=AG-Cluster&groupPrimaryServer=ag-4A2FD1247EC91A6C&groupUrl=192.168.1.25&ag-4A2FD1247EC91A6C_checkbox_vcp=ag-4A2FD1247EC91A6C
> *Response code:302*
>
> Importing the default policies...
> /opt/novell/java/bin/java -classpath
> "/opt/novell/nam/adminconsole/webapps/roma/WEB-INF/lib/*"
> com.volera.roma.app.handler.AutoConfigHandlerWrapper configurePolicies
> nam.almabani.com.sa almabani.com.sa 192.168.1.25 192.168.1.25
> cn=admin,o=novell XXXXX
> Invoking URL:
> https://192.168.1.25:8443/roma/autoconfig/cntl?handler=group_create&actionCmd=ImportDefaultPolicies&policycollectionid=xpemlPEP&prevstep=savepolicy&containerid=mastercdn
> Response code:200
>
> Enabling role based policies for the Identity Server cluster...
> /opt/novell/java/bin/java -classpath
> "/opt/novell/nam/adminconsole/webapps/roma/WEB-INF/lib/*"
> com.volera.roma.app.handler.AutoConfigHandlerWrapper enableIDPRoles
> nam.almabani.com.sa almabani.com.sa 192.168.1.25 192.168.1.25
> cn=admin,o=novell XXXXX
> Invoking URL: http://tinyurl.com/y74q4wae
> Response code:200-
>
>
> Its noticed that Response code for creating Access Gateway cluster
> appears to be code:302 unlike others where it shows Response code:200 .
> Does that mean an error?? If yes, please guide how to fix it.
>
>

I'm also seeing a 302 response code here in my lab when it creates the AG cluster. Can you check if the ESP has actually started?

cat /opt/novell/nam/mag/logs/catalina.out



--
Cheers,
Edward


here is catalina.out output:

Jan 10, 2019 10:17:10 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'xmlValidation' to 'false' did not find a matching property.
Jan 10, 2019 10:17:10 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'xmlNamespaceAware' to 'false' did not find a matching property.
Jan 10, 2019 10:17:10 AM org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib64:/opt/novell/eDirectory/lib64:/opt/novell/lib64
Jan 10, 2019 10:17:10 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-nio-127.0.0.1-9009"]
Jan 10, 2019 10:17:10 AM org.apache.tomcat.util.net.NioSelectorPool getSharedSelector
INFO: Using a shared selector for servlet write/read
Jan 10, 2019 10:17:10 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 746 ms
Jan 10, 2019 10:17:10 AM org.apache.catalina.users.MemoryUserDatabase open
SEVERE: The specified user database [conf/tomcat-users.xml] could not be found
Jan 10, 2019 10:17:10 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Jan 10, 2019 10:17:10 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat
Jan 10, 2019 10:17:10 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /opt/novell/nam/mag/webapps/agm
Jan 10, 2019 10:17:10 AM org.apache.catalina.startup.SetContextPropertiesRule begin
WARNING: [SetContextPropertiesRule]{Context} Setting property 'debug' to '0' did not find a matching property.
Jan 10, 2019 10:17:12 AM org.apache.jasper.servlet.TldScanner scanJars
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
AMLoggingInit.<static initializer block>, configuring log4j, configPath=/etc/opt/novell/amlogging/config/log4j.xml
log4j:WARN Continuable parsing error 41 and column 17
log4j:WARN The content of element type "appender" must match "(errorHandler?,param*,rollingPolicy?,triggeringPolicy?,connectionSource?,layout?,filter*,appender-ref*)".
Creating ActiveMQ Connection...
Creating ActiveMQ Connection...
Confirm Queue: queue://AMLoggingMonitor-local-confirm
Consuming queue: AMLoggingMonitor-local-indicate
indicateSession: ActiveMQSession {id=ID:nam.almabani.com.sa-49433-1547104632563-0:0:3,started=false}
respondSession: ActiveMQSession {id=ID:nam.almabani.com.sa-49433-1547104632563-0:0:4,started=false}
log4j:WARN No such property [host] in com.novell.nacm.logging.audit.AMSyslogAppender.
log4j:WARN No such property [port] in com.novell.nacm.logging.audit.AMSyslogAppender.
log4j:WARN No such property [protocol] in com.novell.nacm.logging.audit.AMSyslogAppender.
log4j:WARN No such property [cacheenabled] in com.novell.nacm.logging.audit.AMSyslogAppender.
log4j:WARN No such property [cachedir] in com.novell.nacm.logging.audit.AMSyslogAppender.
log4j:WARN No such property [cachemaxfilesize] in com.novell.nacm.logging.audit.AMSyslogAppender.
initiateStartup() called.
initiateStartup(), CONFIGURATION FILE /opt/novell/nam/mag/webapps/agm/WEB-INF/config/current/config.xml NOT FOUND!!! Using factory defaults.
initateStartup(), Setting management IP as 192.168.1.25
initateStartup(), Setting device ID as ag-4A2FD1247EC91A6C
Creating ActiveMQ Connection...
Creating ActiveMQ Connection...
Confirm Queue: queue://GatewayManager-local-confirm
Consuming queue: GatewayManager-local-indicate
indicateSession: ActiveMQSession {id=ID:nam.almabani.com.sa-49433-1547104632563-0:1:3,started=false}
respondSession: ActiveMQSession {id=ID:nam.almabani.com.sa-49433-1547104632563-0:1:4,started=false}
log4j:WARN Continuable parsing error 41 and column 17
log4j:WARN The content of element type "appender" must match "(errorHandler?,param*,rollingPolicy?,triggeringPolicy?,connectionSource?,layout?,filter*,appender-ref*)".
[]
Starting to add global filter settings
High Volume Events initializaed
final custom extension string
done with global filter settings
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: ag-maga, tomcat restart command is: null
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: ag, tomcat restart command is: null
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: ag-lag, tomcat restart command is: null
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: ag-mag, tomcat restart command is: null
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: ag-mag, tomcat restart command is: /bin/bash -c "/etc/init.d/novell-mag restart"
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: idp-idp, tomcat restart command is: null
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: idp-idp, tomcat restart command is: /bin/bash -c "/etc/init.d/novell-idp restart"
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: idp-esp, tomcat restart command is: null
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: agent-agent, tomcat restart command is: null
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: jccserver, tomcat restart command is: null
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: system, tomcat restart command is: null
Jan 10, 2019 10:17:13 AM com.novell.jcc.JCCServiceType <init>
INFO: ar, tomcat restart command is: null
Jan 10, 2019 10:17:13 AM com.novell.jcc.client.JCCClientImpl <init>
INFO: Starting client 4A2FD1247EC91A6C of type ag
Jan 10, 2019 10:17:13 AM com.novell.jcc.client.JCCClientImpl$_B run
INFO: server connection thread started
Jan 10, 2019 10:17:13 AM com.novell.jcc.util.JCCSettings A
INFO: Current settings
rmiPort: 1197
localMgmtPort: 1443
localMgmtIP: 192.168.1.25
remoteMgmtPort: 8444
remoteMgmtIP: [192.168.1.25]
jccProxyPort: 2483
agProxyPort: 444
sslvpnProxyPort: 3423
healthFreq: 300
statsFreq: 300
remoteMgmtIPFreq: 3600
externTomcatDir: /opt/novell/nam/mag
secure: true

Jan 10, 2019 10:17:14 AM com.novell.jcc.client.JCCClientImpl$_B D
INFO: attempting to contact RMI server on 127.0.0.1:1197
Jan 10, 2019 10:17:15 AM com.novell.jcc.client.JCCClientImpl queueAlert
INFO: queuing alert: Severe: Failure in Audit, local syslog is offline. at Thu Jan 10 10:17:15 AST 2019 for ag-4A2FD1247EC91A6C
initiateStartup() completed
Jan 10, 2019 10:17:15 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /opt/novell/nam/mag/webapps/agm has finished in 5,405 ms
Jan 10, 2019 10:17:15 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /opt/novell/nam/mag/webapps/nesp
Jan 10, 2019 10:17:15 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Context/Manager} Setting property 'saveOnRestart' to 'false' did not find a matching property.
log4j:ERROR No appender named [AMAuditSyslogAuditAppender] could be found.
Jan 10, 2019 10:17:23 AM org.apache.jasper.servlet.TldScanner scanJars
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Jan 10, 2019 10:17:24 AM com.sun.xml.ws.server.MonitorBase createRoot
INFO: Metro monitoring rootname successfully set to: com.sun.metro:pp=/,type=WSEndpoint,name=/nesp-provider
Jan 10, 2019 10:17:25 AM com.sun.xml.ws.server.MonitorBase createRoot
INFO: Metro monitoring rootname successfully set to: com.sun.metro:pp=/,type=WSEndpoint,name=/nesp-SecurityTokenService-STS_Port
Jan 10, 2019 10:17:25 AM com.sun.xml.ws.server.MonitorBase createRoot
INFO: Metro monitoring rootname successfully set to: com.sun.metro:pp=/,type=WSEndpoint,name=/nesp-SecurityTokenService-STS_Port_saml
Jan 10, 2019 10:17:25 AM com.sun.xml.ws.server.MonitorBase createRoot
INFO: Metro monitoring rootname successfully set to: com.sun.metro:pp=/,type=WSEndpoint,name=/nesp-SecurityTokenService-STS_Port_active12
Jan 10, 2019 10:17:25 AM com.sun.xml.ws.transport.http.servlet.WSServletDelegate <init>
INFO: WSSERVLET14: JAX-WS servlet initializing
Jan 10, 2019 10:17:25 AM org.glassfish.jersey.servlet.init.JerseyServletContainerInitializer addServletWithApplication
SEVERE: Mapping conflict. A Servlet registration exists with same mapping as the Jersey servlet application, named net.microfocus.impersonation.service.v1.application.ImpersonationApplication, at the servlet mapping, /impersonation/*. The Jersey servlet is not deployed.
Jan 10, 2019 10:17:25 AM org.glassfish.jersey.servlet.init.JerseyServletContainerInitializer addServletWithApplication
INFO: Registering the Jersey servlet application, named net.microfocus.mobileaccess.service.v1.application.MobileAccessApplication, at the servlet mapping /mobileaccess/*, with the Application class of the same name.
Jan 10, 2019 10:17:25 AM org.glassfish.jersey.servlet.init.JerseyServletContainerInitializer addServletWithApplication
INFO: Registering the Jersey servlet application, named net.microfocus.basicsso.service.v1.application.BasicSSOApplication, at the servlet mapping /basicsso/*, with the Application class of the same name.
Jan 10, 2019 10:17:25 AM org.glassfish.jersey.servlet.init.JerseyServletContainerInitializer addServletWithApplication
INFO: Registering the Jersey servlet application, named com.novell.nam.nidp.risk.RiskRESTApplication, at the servlet mapping /risk/*, with the Application class of the same name.
Jan 10, 2019 10:17:25 AM org.glassfish.jersey.servlet.init.JerseyServletContainerInitializer addServletWithApplication
INFO: Registering the Jersey servlet application, named com.novell.nidp.rest.NIDSRestApplication, at the servlet mapping /rest/*, with the Application class of the same name.
A critical error has occurred during startup. {0}Evaluation code has been disabled as of Fri, Nov 30, 2018.
Jan 10, 2019 10:17:25 AM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
INFO: WSSERVLET12: JAX-WS context listener initializing
Jan 10, 2019 10:17:25 AM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
INFO: WSSERVLET12: JAX-WS context listener initializing
Filter initialized! 'SameOriginFilter'
Filter initialized! 'ClusterRequestFilter'
Jan 10, 2019 10:17:26 AM org.glassfish.jersey.server.ApplicationHandler initialize
INFO: Initiating Jersey application, version Jersey: 2.10.1 2014-06-30 13:53:32...
Jan 10, 2019 10:17:26 AM com.novell.nam.nidp.oauth.core.TokenServiceImpl <init>
INFO: TokenServiceImpl created
Jan 10, 2019 10:17:26 AM org.apache.catalina.core.StandardContext filterStart
SEVERE: Exception starting filter OAuthApplicationJspMvcFilter
MultiException stack 1 of 3
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Access Manager Appliance installation Issues

On 11-01-2019 6:26 PM, squadri wrote:

> INFO: TokenServiceImpl created
> Jan 10, 2019 10:17:26 AM org.apache.catalina.core.StandardContext
> filterStart
> SEVERE: Exception starting filter OAuthApplicationJspMvcFilter
> MultiException stack 1 of 3
>
>


That doesn't look right at all. The ESP isn't starting properly which probably stops the cluster from being created successfully. Can you validate the
md5 or sha checksum of the ISO by any chance?

--
Cheers,
Edward
0 Likes
syed_17 Super Contributor.
Super Contributor.

Re: Access Manager Appliance installation Issues

edmaa;2493454 wrote:
On 11-01-2019 6:26 PM, squadri wrote:

> INFO: TokenServiceImpl created
> Jan 10, 2019 10:17:26 AM org.apache.catalina.core.StandardContext
> filterStart
> SEVERE: Exception starting filter OAuthApplicationJspMvcFilter
> MultiException stack 1 of 3
>
>


That doesn't look right at all. The ESP isn't starting properly which probably stops the cluster from being created successfully. Can you validate the
md5 or sha checksum of the ISO by any chance?

--
Cheers,
Edward


You nailed it perfectly my friend. Its horrifying to know that the checksum didnt match and I had not focussed on that one possibility. However, did a fresh download and proceeded with fresh deployment of appliance after verifying checksum this time :pp . It shows both the clusters(IDP and Access Gateway) created.
Appreciate your wonderful supporting ideas.

Now moving to the next step. Our main objective is to protect our web based application with NAM. To begin with, we need to implement this solution to Groupwise WebAccess and SSPR for our eDirectory Users. Can you suggest the best possible and easy approach to do so?
Please note that this is our first deployment of NAM4.4.
0 Likes
ScorpionSting Absent Member.
Absent Member.

Re: Access Manager Appliance installation Issues

squadri;2493461 wrote:
You nailed it perfectly my friend. Its horrifying to know that the checksum didnt match and I had not focussed on that one possibility. However, did a fresh download and proceeded with fresh deployment of appliance after verifying checksum this time :pp . It shows both the clusters(IDP and Access Gateway) created.
Appreciate your wonderful supporting ideas.

Now moving to the next step. Our main objective is to protect our web based application with NAM. To begin with, we need to implement this solution to Groupwise WebAccess and SSPR for our eDirectory Users. Can you suggest the best possible and easy approach to do so?
Please note that this is our first deployment of NAM4.4.


Groupwise: https://support.microfocus.com/kb/doc.php?id=7022808
SSPR has a list of Protected and Public resources under Administration -> More Options -> URL Reference

Visit my Website for links to Cool Solution articles.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.