CODEWITHSUNDEEP
consoleibm-mobilefirstanalytics
raj prabhu
raj prabhu

Reputation: 11

IBM Mobile First V 7.0

I have an issue working in IBM Mobile First v7.0 Analytics console. In analytics console the data was not loaded from mobile first server.but all data are stored in Worklight database...

The following configuration i did for my application and deployed in production server...

Worklight.proerties file enable JNDI proerties

wl.analytics.url=http://192.168.1.3:9080/analytics-service/data wl.analytics.console.url=http://192.168.1.3:9080/analytics/console

Keep the analytics.ear file in my application foler... C:\IBM\WebSphere\Liberty\usr\servers\testserver\apps

Server.xml

<feature>jndi-1.0</feature>

</featureManager>


    <application location="analytics.ear"
    name="analytics-ear"
    type="ear">
  <application-bnd>
    <security-role name="worklightadmin">
       <user name="admin"/>
    </security-role>
    <security-role name="worklightdeployer">
       <user name="deployer"/>
    </security-role>
    <security-role name="worklightmonitor">
       <user name="monitor"/>
    </security-role>
    <security-role name="worklightoperator">
       <user name="operator"/>
    </security-role>
   </application-bnd>
     </application>

If I did any mistake, kindly anyone help me

Upvotes: 0

Views: 133

Answers (1)

Chevy Hungerford
Chevy Hungerford

Reputation: 1167

Since you are using security roles on your analytics console you need to send data with a username and password. Inside your server.xml for your Operations Console, you can set these username and password with the following JNDI properties:

<jndiEntry jndiName="AppName/wl.analytics.username" value="admin"/>

<jndiEntry jndiName="AppName/wl.analytics.password" value="admin"/>

Also, make sure that your security roles an constraints match your server.xml to the WEB.xml in your analytics-service.war. Default is the security configuration below:

<security-constraint>
<security-role>
  <role-name>worklightadmin</role-name>
</security-role>
<security-constraint>
<web-resource-collection>
  <web-resource-name>allAccess</web-resource-name>
  <url-pattern>/data/*</url-pattern>
</web-resource-collection>
<auth-constraint>
  <role-name>worklightadmin</role-name>
  <role-name>worklightdeployer</role-name>
  <role-name>worklightmonitor</role-name>
  <role-name>worklightoperator</role-name>
</auth-constraint>
<user-data-constraint>
  <transport-guarantee>NONE</transport-guarantee>
</user-data-constraint>
</security-constraint>

The role-names will need to match the names that you use in your basic registry.

Upvotes: 1

Related Questions