I integrated activiti-explorer and OpenLDAP. After integrating activiti and LDAP, i am not able to deploy processes in activiti-explorer. How i can deploy a process after integration of activiti-explorer and OpenLDAP. Please help. Any help is appreciated.
Related
Problem Statement is - I have one EC2 linux instance on which ASP.NET core web application is deployed. I want to do the windows authentication for that application.
I am a fresher with not much experience in the field of development. I have tried searching on the Google but could not find any relevant document that can help in achieving the objective.
Can anyone from the community provide information on how to do the windows authentication for the app running on EC2 ?
I have a .Net Core IdentityServer4 application which was hosted on a different server before and was working perfectly unti we decided to moved everything on AWS.
The problem now is we can't find a guided on how to deploy it on AWS, as a new comer in AWS things can get very confusing with their too many services.
Hope someone can help provide a documentation or instruction on how to deploy it on AWS.
NOTE: This question is for a .net core console application, not ASP.NET Core.
I am confused on the proper use of a Profile on AWS. What I understand is that AWS would prefer that a profile name is used instead of a file containing AWS credentials (aws_access_key_id, aws_secret_access_key) values.
With .net core, how will I know how to navigate to the users home directory where the credentials file should be stored? (According to this reference: http://docs.aws.amazon.com/sdk-for-net/v3/developer-guide/net-dg-config-creds.html#using-a-credentials-file
I am creating a .net Core application to connect to Amazon Kinesis and will be deploying it in a Docker container. I want to be able to deploy and have the application find the credentials on its own using .CreateServiceClient<IAmazonKinesis>(). From what I understand, this approach allows AWSOptions to lookup/find the credentials under the covers by locating the credentials file.
Please help me understand how to approach this.
Is the docker container you will be deploying to hosted in ECS? If so, using the IAM Roles for Tasks feature in ECS will be the simplest solution to your question.
Essentially, you can configure an IAM role that the task/container will run under, and configure it's permissions by assigning an IAM policy to that role. ECS manages the process of providing credentials for that role to the docker container. The SDKs will all pick up the credentials ECS provides by default, unless you explicitly override them by providing credentials while creating a client or change your credential provider chain.
We published a blog post about ECS IAM roles for tasks when we launched the feature:
https://aws.amazon.com/about-aws/whats-new/2016/07/amazon-ec2-container-service-now-supports-iam-roles-for-tasks/
i need some advice about continuous deployment within Visual Studio Team Service. To be honest, i am quite new in this area, so forgive this silly question because i can't find any reference for AWS but only Azure.
My idea is i can deploy asp.net application to AWS EC2 which is built from VSTS source control.
My current scenario is:
I had source control which contain asp.net application code inside VSTS.
I created build definition which build the source code and produce artifact.
I created release definition, which copy artifact to remote AWS EC2 instance.
....
I don't have any idea to continue the next step, could you give advice what i should do next ? Or any better scenario ?
Thank You.
Currently I don't see any tasks which can directly deploy to AWS, so the only way this seems possible if you create your own task or use powershell or bash along with AWS cli to deploy your artifact. The process would be something like this
Download the artifact in a release. This is default if you link the artifact.
Make sure the agent machine that you are using has AWS CLI for Powershell or AWS Shell if you are using bash.
You can then write a powershell or bash script which will utilize aws cli to deploy your artifact to AWS.
For anyone else wondering about this in the future, AWS just released the AWS Tools for VSTS to the Visual Studio Marketplace. These tools contain a number of tasks you can use to work with AWS services such as S3, CodeDeploy, Elastic Beanstalk, Lambda and CloudFormation from within a VSTS or TFS environmemt.
We also just published a blog post about using the tools to publish ASP.NET and ASP.NET Core applications to AWS from within VSTS.
There are couple of options for you. A tutorial to explain how to get this running is given below.
How to Build a CI/CD Pipeline Using AWS CodeDeploy and Microsoft Team Foundation Server (TFS)
(For hybrid/complex deployments, you can use this. You can deploy IIS websites, MSI packages, services, exe). The beauty of this is that with a single deployment you can deploy to both on premises and cloud environment.
https://www.youtube.com/watch?v=MIE0P3m9eEY
How to Integrate AWS Elastic Beanstalk with Microsoft Team Foundation Server (TFS) or (VSTS)
(for IIS websites/batch jobs you can use this)
https://www.youtube.com/watch?v=nRLZZefLDqU
How to Integrate AWS Cloudformation with Microsoft Team Foundation Server (TFS)
(fully infrastructure automation and manage infrastructure as code)
https://www.youtube.com/watch?v=WU93NJT0_3s
I am looking for automatic Ear deployment for WAS6 application. Is there any default scripts provided by WAS6? If Yes, Please provide me script names and please explain me, how to use that. It would be great help for me.
If there is no default scripts available to deploy ear, How to proceed to write script.
Please do needful.
Thanks in Advance
WebSphere Application Server provides a scripting tool, wsadmin, that may be used for automating the deployment of applications. See this Info Center document for more details.
AdminApp.install('/ears/application1.ear', '[-cluster cluster1]')
Also, for more general help in writing scripts using wsadmin, here are some other helpful resources:
WebSphere Application Server V6.1: System Management and Configuration: Administration with Scripting (Chapter 5)
WebSphere Application Server V6.1 InfoCenter: Wsadmin tool