Integrations and APIs for Service

Get Involved. Join the Conversation.

Topic

    Ryan Young
    How to actually deploy/upload Add-InAnswered
    Topic posted September 3, 2010 by Ryan YoungGold Medal: 3,500+ Points, last edited October 29, 2011 
    4830 Views, 24 Comments
    Title:
    How to actually deploy/upload Add-In
    Content:

    I'm using RN Feb '10, and have developed an Add-In.  It works great in Developer Mode; however, when I use the Add-In Manager to add the Add-In, it is not usable in other Account Profiles.  It is not even showing up as Active OR Inactive.  I am supposed to demo this in a little over 2 hours, but can not get it to work correctly.

    I have followed all of the steps I could find for deployment in the Getting Started, User Guide, and the Advanced Tutorials PDFs.  Please help!  I did notice something about "uploading the Add-In to the server", but could not find specific steps for that (unless it is referring to using the Add-In Manager >> New Add-In, which I have already done).

    The Add-In is showing up in the Add-In Manager, but not in the lists of Active / Inactive Add-Ins, so I am very confused.  Thank you in advance for your help!  :)

    Sincerely,

    Ryan Young

    Best Comment

    Kevin Noreus

    Hi Ryan,

    If your using the MSI installer then add-in deployment becomes a manual process.  I'm not an expert on this but there some info about it here:

    http://crm.rightnow.com/app/answers/detail/a_id/2778

    You basically need to recreate the AddIns directory structure yourself.  So you should just be able to create the AddIns directory under SiteFiles/<site name> and then copy your add-in from a working dev client of yours into it.

    So you would have:

    SiteFiles/<site name>/AddIns/YourAddIn/YourAddIn.dll

    Once you've done this the RN console should recognize the add-in next time its started up and load it assuming the logged in user's profile has access to it.

    Comment

    • Ryan Young

      I have 2 Account Profiles set up.  One is for Add-In Dev, the other for deployed Add-Ins.  When I log in to the non-dev profile with nothing in the RightNowDev directory, the CX Console loads, but I do not have access to the deployed Add-In.  When I log in to the DEV profile with the correct folder/DLL under RightNowDev, the console crashes when trying to load and tells me that "An item with the same key has already been added."  The deployed Add-In is disabled for the Dev profile and enabled for the non-dev profile.  Please help!

    • Kevin Noreus

      Hi Ryan,

      I'm not sure why your non-dev profile add-in is not loading but the second issue sounds familiar.

      If you haven't done so already try unchecking the "developer access" checkbox for the DEV profile you have set up.  That error you are seeing occurs when the console attempts to load both a dev mode add-in and its matching production  add-in.  This was fixed in 10.5. 

      Hope this helps.

      -Kevin 

    • Ryan Young

      Thanks Kevin.

      Unfortunately, all that does is not allow me access to the Add-In.  I'm going to try copying the Add-In to a different name so that I can at least demo it.

    • Ryan Young

      I'm still having the same problem.  The "deployed" Add-In (uploaded to the server according to the Add-In log) is not showing up where it should.  I have set a profile to use this Add-In; however, it still won't show up in the Active/Inactive Add-Ins list, nor will it show up in the workspace for which it was designed.  I copied the Add-In to use in Dev mode for my demo.  It works great in Dev mode, but we can't use that to pseudo-deploy it to all of the agents who need to use it.  Any advice on deploying a seemingly non-deployable Add-In?  Thanks!

    • Kevin Noreus

      Do you see anything in the Add-In log indicating an activation failure?  There should be a "*** Failed to Activate ..." or "Failed to Initialize ..." message if the activation was not successful.

      Or it is possible that the Add-in is not even getting downloaded to the client.  Can you verify the add-in is getting downloaded to the client?  The file and its container directory should live under:

      SiteFiles\<site name>\AddIns

      -Kevin

    • Ryan Young

      Kevin,

      Thank you again for your help!

      I do not see any activation failure message in the log.

      I think that the add-in is not getting downloaded to the client (though I'm not 100% sure it was uploaded to the server).  I did not see the AddIns folder, so I created it and put the container folder in SiteFiles\<site name>\AddIns; however, it is still not showing up.  I originally deployed the add-in using the Add-In Manager.  That should have uploaded the add-in to the server, correct?

    • Kevin Noreus

      It's definitely not getting downloaded if that folder is not getting created.  To see if it was uploaded you can look in the following location on the server.

      <sitename>.db/components/addin

      There should be an entry (by ID) for each uploaded add-in.

      If this is empty you can check to make sure the db entries look correct.  

      The master record is stored in the addin_files table.

      select * from addin_files.

      Then there should be an entry in the profile2addin_file table for each profile you've given this add-in access to.

    • Ryan Young

      Thanks, Kevin!

      I'm not sure I know where to access the server.  Am I supposed to use a browser, the CX Console, or something entirely different?

    • Kevin Noreus

      Well I'm not sure if you have access to that directory on a hosted site.  Sorry didn't think of that.  Maybe someone else knows if this is possible?

      Were you able to verify the proper record(s) were inserted into the profile2addin_file table?

    • Ryan Young

      I have gone through the Data Dictionary, but can not find the profile2addin_file table (or Profile to AddIn File).  Since the add-in was working in dev mode, I thought that add-ins have been enabled for our site.  Could this not be the case?  Are add-ins automatically enabled in the Feb '10 version?

      I opened an incident on Friday, but have not heard back yet.  I will keep checking here to see if a solution presents itself.  Also, when I finally figure this out, I'll make sure to post the exact solution in case anyone else runs up against this.

      Thanks, Kevin!

    • Dietrik

      Upload the add-in using the add-in manager

      Don't use dev mode, delete your local dev directorie, make sure it works without dev mode for your own profile

      Make sure your profiles are configured for add-in (per interface) through the add-in manager, or at the profile administration

      Don't test with two righnow instances running at the same time

      There's different setup options when using the msi installer

    • Ryan Young

      Thanks, DS!

      I did upload the add-in using the add-in manager.  I have deleted my dev directory and am using a non-dev profile.  The profile has been set up to use the add-in which is still listed in the add-in manager and on the Add-In tab in the profile editor.  Also, I have never used 2 RN instances at the same time.

      The add-in is still not working.  It is supposed to go into production tomorrow (I have tested it in Dev Mode and it works fine), so I may have to create a temporary RN profile with dev access until I can get this figured out.  I will check to see if the MSI installer was not set up correctly for this; however, if that's the case, we would have to reinstall RN on all of our agents' computers which would take quite a while.

      I will continue to keep y'all posted until this issue is resolved.  Thank you again for your support!

      Sincerely,

      Ryan Young

    • Ryan Young

      I am trying to reinstall the RN CX Console using the MSI installer; however, I don't see a place to change any settings.  How can I access them?

    • Ryan Young

      Well, I was unable to pseudo-deploy the add-in in dev mode on a select few agents' computers.  It's supposed to go into production tomorrow, but no luck yet.

    • Kevin Noreus

      Hi Ryan,

      If your using the MSI installer then add-in deployment becomes a manual process.  I'm not an expert on this but there some info about it here:

      http://crm.rightnow.com/app/answers/detail/a_id/2778

      You basically need to recreate the AddIns directory structure yourself.  So you should just be able to create the AddIns directory under SiteFiles/<site name> and then copy your add-in from a working dev client of yours into it.

      So you would have:

      SiteFiles/<site name>/AddIns/YourAddIn/YourAddIn.dll

      Once you've done this the RN console should recognize the add-in next time its started up and load it assuming the logged in user's profile has access to it.