Data Infrastructure Management Software Discussions

Highlighted

Re: How to create an own data source

You will need to enable remote MySQL connections and use the default wfa user - wfa/Wfa123

  1. Stop the WFA Database Service
  2. Edit 'C:\Program Files\NetApp\WFA\mysql\my.ini'
  3. Comment the last line - "bind-address=localhost" to "#bind-address=localhost"
  4. Save the file and close
  5. Start the WFA Database Service

Now you can access the database remotely and verify the row counts.  However, the comment about 9,999 row count sparked a memory.  The default results returned in a filter are limited to a 9,999 results and is hard coded.  Take a look at the previous communities post where we discussed this situation.

https://communities.netapp.com/thread/24521

Jeremy Goodrum, NetApp

The Pirate

Twitter: @virtpirate

Blog: www.virtpirate.com


Highlighted

Re: How to create an own data source

Hi Jeremy

Still receive the same error which is a pity

However, thanks for the link – I am experiencing the same issue, so I have inserted a ‘search criteria’ field to narrow down the results and this works. The other alternative would be to have multiple queries based on region which would reduce the number of entries.

Still on the subject of Data Sources. Is it possible to run LDAP queries? For example, searching for user email addresses I’d like to run an LDAP query against Active directory – have you seen something similar done?

Regards

Bryce

Bryce Martin

GT Engineering

6/8 Bishopsgate, EC2N 4DA London, United Kingdom

Tel: +44 (0) 20 754-53566

Mob: +44 (0)7914 540882

Email: Bryce.Martin@db.com<mailto:Bryce.Martin@db.com>

Highlighted

Re: How to create an own data source

Remember, WFA Filters will only return the most relevant result and that is it.  The only time that this is not 100% the case is when you are using repeat rows.  The limitation is 9,999 rows which is hard set to provide the most relevant results while not causing a performance hit on collection.

If you are using these values as User Inputs, then it would theoretically take you forever to 'find the right value' if you even got back 9,999 values.  Leverage Filter Values in your queries.  For example:

SELECT username FROM ad.users

--------------------------------------------

Instead try

--------------------------------------------

SELECT username FROM ad.users WHERE username LIKE '%${filterQuery}%'

Now you have a new user input that acts as a filter point so you can provide any part of the name that you want to get the most relevant user inputs.

 

As far as building a Datasource based on AD or LDAP information, this is doable though nothing available to date based on what I have heard.  You could right a PoSH based script to gather the data as CSV and use the How-To video (referenced here) to create your own Datasource.

Highlighted

Re: How to create an own data source

Hi Jeremy

I managed to get the LDAP Data Source working via script. All seemed ok with small files but when I run the full query I receive a 'The transaction is not active!' error.

On WFA 2.0 it does this after 310 secs, on v2.1 it will get further but will still timeout with, 'ARJUNA016063: The transaction is not active!'

I found I a query of 26,000 lines would work, but 44,000 and 86,000 lines timed out.

The content is pretty simple as it's just email addresses...e.g.

\N     joe.bloggs@company.com

..........

This is in tab delimited ascii format. Smaller files work but still take a very long time considering their size. 20 lines takes 36 seconds. The 26,000 line file was taking 877 seconds to complete, which seems to be very long for a single field.

Is this something you have seen before - would you consider that a large input?

Bryce

Re: How to create an own data source

Hi Bryce,

      'ARJUNA016063: The transaction is not active!' indicates a time out by the Jboss transaction manager. Not sure if it will help or not but can you edit the following line in file.

  1. Open file standalone-full.xml located at WFA\jboss\standalone\configuration folder
  2. Find the line <coordinator-environment default-timeout="300"/> . The default timeout is set to 300 sec ( 5 Min )
  3. Modify this default-timeout to some larger value like 1000 sec.
  4. Restart NetApp WFA Server service.

Now try to acquire and see if it works.

warm regards,

sinhaa

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Highlighted

Re: How to create an own data source

Hi sinhaa

Thanks for the reply.

The WFA\jboss\standalone\configuration doesn't exist on my WFA v2.0 install - is variable in another file in WFA v2.0? Or any log files which would highlight the issue?

Regards

Bryce

Highlighted

Re: How to create an own data source

Bryce,

    Send me a mail at the below id. I'll take this fwd via email.

My mail id : sinhaa at netapp dot com

warm regards,

Abhishek

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Try the NEW Knowledgebase!
NetApp KB Site
Forums