Can I use "XP1-Distributed.ps1" to distributed installation for 3 server
It fails when create app pool in IIS
The error is:
I want confirm the "XP1-Distributed.ps1" install one role in one server.
because in script json file use "DnsName" to create binding website
I change DnsName to SiteName it work for me
Related
I just installed WSO2 3.2.0 and Analytics 4.4.0 on the same machine using repositories on Debian 9.
Everything looks fine except the analytics Dashboard that I can't access for. According to the documentation here, I have to go on this url https://check.mydomain.com:9643/analytics-dashboard but all I got is this error :
Problem accessing: /analytics-dashboard. Reason: Not Found
I followed these steps to set up my domain name and enable analytics :
nano /usr/lib/wso2/wso2am/3.2.0/repository/conf/deployment.toml
[server]
hostname = "check.mydomain.com"
[apim.analytics]
enable = true
And I replaced every "localhost" string by ${server.hostname}
I followed these steps to start Analytics, API Manager and Dashboard :
service wso2sp-4.4.0-worker start
service wso2am-3.2.0 start
service wso2sp-4.4.0-dashboard start
Every service is fine regarding
service wso2sp-4.4.0-worker status
service wso2am-3.2.0 status
service wso2sp-4.4.0-dashboard status
Every other urls are working :
https://check.mydomain.com:9443/admin
https://check.mydomain.com:9443/carbon
https://check.mydomain.com:9443/devportal
https://check.mydomain.com:9443/publisher
Analytics is enabled and I can see subscription options on Publisher settings
Nothing happends on logs when I wisit https://check.mydomain.com:9643/analytics-dashboard
tail -f /usr/lib/wso2/wso2am/3.2.0/repository/logs/http_access_.2020-11-18.log
tail -f /usr/lib/wso2/wso2am/3.2.0/repository/logs/wso2carbon.log
tail -f /usr/lib/wso2/wso2sp/4.4.0/wso2/worker/logs/carbon.log
tail -f /usr/lib/wso2/wso2sp/4.4.0/wso2/dashboard/logs/carbon.log
Any help would be very appreciated, thanks.
You need to use wso2am analytics setup to configure analytics with the API manager. But I think now you are trying to use wso2 stream processor to configure the analytics and it's not supported with wso2am 3.2.
Follow the [1]documentation to download and set up the analytics.
You need to manually download the wso2am-analytics-3.2.0.zip.
if you follow the quick setup make sure wso2am-analytics-3.2.0 and wso2am folders locate in the same place. (since you installed apim via the apt installer you need to manually put anlytics setup in /usr/lib/wso2/wso2am/ folder and correctly set the path to API manager am_db in wso2am-analytics-3.2.0/conf/dashboard/deployment.yaml---> AM_DB -> jdbcUrl)
If you follow the standard setup no need to worry about the locations of wso2am pack and wso2am-analytics pack.
[1] https://apim.docs.wso2.com/en/latest/learn/analytics/configuring-apim-analytics/
New Windows server 2012 R2 installation, added ASP.Net and .Net 3.5
Getting following error when trying to browse web service file svc:
Could not load type '%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll'.
Any thoughts?
Open command prompt as administrator
Navigate to C:\Windows\Microsoft.Net\Framework\v3.0\Windows Communication Foundation
and execute the command:
ServiceModelReg.exe /i
Navigate to c:\windows\Microsoft.NET\Framework\v4.0.30319
and execute the command:
aspnet_regiis -iru
Some roles and features are required on the server
enable server role "Internet Information Services", all underlaying services will be included
enable feature "HTTP Activation", this both under .NET framework 3.5 and .NET framework 4.5
In IIS make sure there is a "handler mappings" configured for the "*.svc" files
That error message turned out to be a bit of a red herring when I encountered it. I simply didn't have a HEAD route setup in WebApiConfig and was getting hundreds of HEAD requests per day. So, if you've verified that you have all the necessary Windows Features installed, then next check that you have default routes setup for each HTTP request method.
I'm trying to deploy a parse application according to this document https://aws.amazon.com/it/blogs/mobile/how-to-set-up-parse-server-on-aws-using-aws-elastic-beanstalk/ .
I deployed the application in aws, created a mongolab cluster, copied the connection string in the environment panel and started the application.
If I try to test using curl according the aws tutorial I receive an interval server error.
How can I understand what's the problem?
I have added this question on ServerFault but no one replied.
I have a .net application which calls a webservice deployed on my local windows server 2012 on IIS, and the sql server database resides on that server too. All employees connect to the same service and DB since we're all on the same domain, and I publish the app and webservice to the server through visual studio (2012).
Now I need to make employees access this application when they are outside the company's network, so I deployed the webservice on IIS on one of our remote windows 2012 servers, I created a public shared folder in my remote server and added to app webservice files to it and in visual studio I changed the publish method to web deploy and filled in the information as below:
Server: https://x.x.x.x/
Site Name: https://x.x.x.x/PublicFolder
Destication URL: https://x.x.x.x/PublicFolder/Application
When I click Validate Connection, it fails with the following message:
Could not connect to the remote computer ("x.x.x.x"). on the remote
computer make sure that Web Deploy is installed and that the required
process ("Web Management Service") is started. Learn more at:
http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE.
Unable to connect to the remote server
Note that I tried to replace https with http and I got another error:
Could not connect to the remote computer ("x.x.x.x"). on the remote
computer make sure that Web Deploy is installed and that the required
process ("Web Management Service") is started. Learn more at:
http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_USER_NOT_ADMIN.
the remote server returned an error: (401)Unauthorized
I went to the previous link and I did what they suggested:
Create a separate user group MSDepSvcUsers on remote computer.
Create an local account A on both local & remote computer.
Add A to MSDepSvcUsers on remote computer.
Use account A to publish, this will allow you to publish without
needing to use built-in admin account.
but the same error (NOT_ADMIN) remained
UPDATE: I found another possible solution:
Add/modify windows registery key
“HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\”
and set it “1”.
After I added this registry key, the error changed to:
site 'http:' does not exist ... #ERROR_SITE_DOES_NOT_EXIST
So now if I put wrong credentials, I get the unauthorized error, if I use correct credentials I get side does not exist error.
What should I do?
It worked!!
I mean the connection, it's now validated, all I had to do is change site name from "http://x.x.x.x/PublicFolder" to "Default Web Site\SiteName" !!
This was really confusing, finally got it!
I have developed a play 1.2.5 application and implemented secure module module for authentication.Its working fine. Now I have developed another play 1.2.5 application which is running on a separate server. I have maintained a href tag in my first play application which has the link to second application.On loging in through my first application, I want the username to be passed to the second application because i am using the logged username. As soon as I log out from the first application, The session (username) should be removed from the second application too.
How can i achieve this ...Plz help!
If you run both of servers on 1 domain (such as www.example.com), and using load balancer (like nginx) to transfer requests to 2 server. You just make sure the config application.secret is the same for both.
If you run on different sub-domain (Recommend), you MUST do like that:
Server should use sub-domain, for example login server is login.example.com and application server is app.example.com
Use config application.defaultCookieDomain=.example.com for both server, then they can use the cookie each others
Make sure both servers have same config application.secret
If you really want to put 2 difference domain, like example.com and example.net. You should implement OAuth on login server and provide API to call from application server.