Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
13 replies
Subscribers
9 subscribers
Views
7277 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Deployment of first solution on-premise
sudhak
over 8 years ago
Hello,
Could someone throw some light on best practices for deployment of a first solution on an on-premise installation? I saw the link on Application Deployment Guidelines here:
ppdtpoc.appiancloud.com/.../Application_Deployment_Guidelines.html
but these are only for 16.1 or are applicable for all versions? We run 7.9 on-premise.
Thanks,
Sudha
OriginalPostID-232684
Discussion posts and replies are publicly visible
0
phanibabuk
over 8 years ago
Hi,
Could you please check the following link:
forum.appian.com/.../Application_Deployment_Guidelines.html
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Ashvin Kapur
over 8 years ago
Sudhak, the deployment guidelines should be similar, but this is the corresponding link from the documentation for Appian 7.9. Please be more specific with any questions you may have on deployment or regarding what you see in the documentation.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Ashvin Kapur
over 8 years ago
forum.appian.com/.../Application_Deployment_Guidelines.html
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
sudhak
over 8 years ago
thank you. Specifically looking for common pitfalls to be aware of and if there are guildelines on how to resolve them.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Ashvin Kapur
over 8 years ago
Some off the cuff thoughts:
- Ensure that security and data management settings are configured for all objects
- Verify that no security is set to an individual user account so that it will not cause issues in migration
- Run a healthcheck on the app prior to migration
- Verify that custom properties files match in both environments (not including any intentional configuration differences)
- Make SQL mods prior to app import
- Always inspect app before import
- Modify any environment specific objects
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
sudhak
over 8 years ago
Great! Thanks!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
phanibabuk
over 8 years ago
1. Create a separate package for CDTs and data store.
2. Create other artifacts in a different package.
3. Import the CDT package first and then the other one.
4. Do not add users in your package until and unless the user is already present in the target system. It is a good practice to use groups.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
sudhak
over 8 years ago
ah good point. Now does this impact any of the dynamic group creations? I suppose no... we are creating dynamic groups and users (already visible to appian). That should still work fine.. correct? after the import/export..
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
phanibabuk
over 8 years ago
Could you give more details on this?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
sudhak
over 8 years ago
we have used a smart service the created groups at the time the process runs (as per some conditions and data it sees at run time)... I suppose we don't have to worry about those as long as the users are available and visible inside the appian tool..
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
>