1
votes

It's in a pre-production installation, with Windows Server 2008 and WAS Liberty. In the Liberty is deployed IBM MobileFirst Platform 7.0, Analytics, a MobileFirst runtime, an application and an adapter. In the Operational Analytics there are not data/applications/servers/... There are not data/applications

The server.xml file contains:

<application location="analytics.ear" name="analytics-ear" type="ear">
      <application-bnd>
        ...
       </application-bnd>
    </application>

<jndiEntry jndiName="wl.analytics.url" value='http://maquinalocal.dominio.local:9080/analytics-service/data'/>
    <jndiEntry jndiName="wl.analytics.console.url" value='http://maquinalocal.dominio.local:9080/analytics/console'/>
    <jndiEntry jndiName="wl.analytics.queues" value='"1"'/>
    <jndiEntry jndiName="wl.analytics.queue.size" value='"0"'/>
    <jndiEntry jndiName="wl.analytics.logs.forward" value='true'/>

The messages.log is: https://drive.google.com/file/d/0BxAEyIioPI2YSTByRFF2eWdkQ2c/view?usp=sharing

2
Have you tried by setting the wl.analytics.queue.size = 1 ?dhineshsundar
Did it work before? Is this really a live production environment or a pre-production environment?Idan Adar
Are your MobileFirst Console Server and MobileFirst Analytics Server being hosted on the same physical server?Chevy Hungerford
it's a preproductión enviromentMiguel Ángel Hernández Castro

2 Answers

1
votes

I had faced a similar issue on a WASND production server environtment, but that was for the client side logs not being displayed in the analytics console. In a production server environment for the client logs to be seen in the analytics console along with setting up analytics console I had to also create a log profile in MobileFirst operations console.

  • In the MobileFirst console open the Client Log Profiles tab.
  • Click on the Add Profile tab here
  • Select different filters from the list that comes up and finish the profile creation.

Restarted the server once the log profile is created. After this I was able to view the client side logs in the analytics console when they were generated.

0
votes

I also had the same issue. Following configuration worked for me.

    <application location="analytics.ear" name="analytics-ear"  type="ear" context-root="analytics">
      <application-bnd>
        <security-role name="worklightadmin">
           <user name="username"/>
        </security-role>
        <security-role name="worklightdeployer">
        </security-role>
        <security-role name="worklightmonitor">
        </security-role>
        <security-role name="worklightoperator">
        </security-role>
       </application-bnd>
        <classloader delegation="parentLast">
        </classloader>
    </application>

    <jndiEntry jndiName="wl.analytics.url" value="http://<domain>:<port>/analytics-service/data"/>
    <jndiEntry jndiName="wl.analytics.console.url" value='http://<domain>:<port>/analytics/console'/>
    <jndiEntry jndiName="wl.analytics.queues" value="1"/>
    <jndiEntry jndiName="wl.analytics.queue.size" value="1"/>
    <jndiEntry jndiName="wl.analytics.logs.forward" value="true"/>
    <jndiEntry jndiName="wl.analytics.username" value="username"/>
    <jndiEntry jndiName="wl.analytics.password" value="password"/>

Also, I noticed that you have provided values like value='"1"' instead of value="1" which could be the issue(not sure about it though).