Testing Aderant
Verify that Timekeeper ID for ping01 user is the same Timekeeper (EMPLOYEE_NUMBER) in the SQL database
Open a web browser on the client VM
In the
Ping Aderant Endpointsguide linked above we have the endpoints that TBP will communicate with
Browse to each of these endpoints → click on
Read SingleThere should be a search bar labeled
uno→ enter1into this search bar and click onsearchYou should receive an XML response
If you get a permissions error the firm will need to contact Aderant support to have the necessary endpoints permission’s adjusted
Note: Please test this with SOAP UI, if you have to use the authentication endpoint or log in before performing any operations this means that Auth Service is in use. Please had the firm disable this method for the TBP svc account.
SOAP UI testing
Authentication Service should not be used. If for some reason you need to log in prior to connecting to one of these endpoints you will run into issues. Auth service endpoint http://ADERANTROOT/Tools/ToolsWS/AuthenticationService.asmx
In SOAP UI Navigate to →
New SOAP ProjectCreate a SOAP project per endpoint
Click on
New SOAP Project
Project name can be anything
Refer to Link below for
Initial WSDL
http://ADERANTROOT/Time/TimeWS/TimeEntryService.asmx?WSDLto test TimeEntry service (Time entry and releasing time)
Note: Refer to Required Aderant Endpoints (Click)
Note: Refer to Required Aderant Endpoints (Click)
Verify Access ASAP - this can become a blocker.
Launch Chrome/browser via shift rt-click Run As Different User -> try both the Windows service account (live access) -> eg. svc_TBPprod
Windows service account (test access) -> eg. svc_TBPtest
Then, go to http://ADERANTROOT/Time/TimeWS/TimeEntryService.asmx
> ReadSingle > invoke = 1
IF YOU GET A PERMISSIONS ERROR, THEN AN AUTH SERVICE IS BEING USED. Please “Grant All” for these Win Service Accounts (live & test access) for these endpoints.
TimeWS
TimeEntryService (http://ADERANTROOT/Time/TimeWS/TimeEntryService.asmx):
TimeEntryService.Create
Creates a time entry in Aderant
TimeEntryService.Release
Marks time entries as released in Aderant
ActionService (http://ADERANTROOT/Time/TimeWS/ActionService.asmx):
ActionService.Read
Grabs all the action codes from Aderant
ExpensesWS <-- Not needed
PhaseTaskService (http://ADERANTROOT/Expenses/ExpensesWS/PhaseTaskService.asmx):
PhaseTaskService.Read
Grabs all the phase/task codes from Aderant
PhaseTaskPlanService (http://ADERANTROOT/Expenses/ExpensesWS/PhaseTaskPlanService.asmx):
PhaseTaskPlanService.Read
Tells Ping which phase/task codes can be used for each matter plan
FileOpeningWS
MatterService (http://ADERANTROOT/FileOpening/FileOpeningWS/MatterService.asmx):
MatterService.Read
Allows users to search for matters
ClientService (http://ADERANTROOT/FileOpening/FileOpeningWS/ClientService.asmx):
ClientService.Read
Allows users to search for clients
ToolsWS (Only required for certain Aderant setups - normally bypassed)
AuthenticationService (http://ADERANTROOT/Tools/ToolsWS/AuthenticationService.asmx):
AuthenticationService.Login
Generates a cookie for the service account to be used to authenticate subsequent requests
AuthenticationService.LoggedIn
Checks whether the user is logged in or if the cookie has expired.
Aderant Troubleshooting
Principal permissions error
This is generally caused by our service account not having the proper access to API endpoint operations
Solution 1: Customer have not given our user access level 1 - this will need to be adjusted within their security manager
Solution 2: Customer have not set our users endpoint access correcting in security manager. Please see:
Solution 3: Customer has not set up Login manager
