C:Program FilesAzure Cosmos DB Emulator
by default. You can also start and stop the emulator from the command-line. For more information, see the command-line tool reference.https://localhost:8081/_explorer/index.html
. If you close the explorer and would like to reopen it later, you can either open the URL in your browser or launch it from the Azure Cosmos Emulator in the Windows Tray Icon as shown below.C2y6yDjf5/R+ob0N8A7Cgv30VRDJIWEHLM+4QDU5DE2nQ9nDuVTqobD4b8mGGyPMbIZnqyMsEcaGQy67XIw/Jw
. For more information about /Key option, see Command-line tool reference./AllowNetworkAccess
option at the command-line, which also requires that you specify /Key=key_string
or /KeyFile=file_name
. You can use /GenKeyFile=file_name
to generate a file with a random key upfront. Then you can pass that to /KeyFile=file_name
or /Key=contents_of_file
.AZURE_COSMOS_EMULATOR_CASSANDRA_ENDPOINT=true
.AZURE_COSMOS_EMULATOR_GREMLIN_ENDPOINT=true
CosmosDB.Emulator.exe /?
at the command prompt.Option | Description | Command | Arguments |
---|---|---|---|
[No arguments] | Starts up the Azure Cosmos Emulator with default settings. | CosmosDB.Emulator.exe | |
[Help] | Displays the list of supported command-line arguments. | CosmosDB.Emulator.exe /? | |
GetStatus | Gets the status of the Azure Cosmos Emulator. The status is indicated by the exit code: 1 = Starting, 2 = Running, 3 = Stopped. A negative exit code indicates that an error occurred. No other output is produced. | CosmosDB.Emulator.exe /GetStatus | |
Shutdown | Shuts down the Azure Cosmos Emulator. | CosmosDB.Emulator.exe /Shutdown | |
DataPath | Specifies the path in which to store data files. Default value is %LocalAppdata%CosmosDBEmulator. | CosmosDB.Emulator.exe /DataPath=<datapath> | <datapath>: An accessible path |
Port | Specifies the port number to use for the emulator. Default value is 8081. | CosmosDB.Emulator.exe /Port=<port> | <port>: Single port number |
ComputePort | Specified the port number to use for the Compute Interop Gateway service. The Gateway's HTTP endpoint probe port is calculated as ComputePort + 79. Hence, ComputePort and ComputePort + 79 must be open and available. The default values are 8900, 8979. | CosmosDB.Emulator.exe /ComputePort = <computeport> | <computeport>: Single port number |
EnableMongoDbEndpoint | Enables MongoDB API | CosmosDB.Emulator.exe /EnableMongoDbEndpoint | |
MongoPort | Specifies the port number to use for MongoDB compatibility API. Default value is 10255. | CosmosDB.Emulator.exe /MongoPort= <mongoport> | <mongoport>: Single port number |
EnableCassandraEndpoint | Enables Cassandra API | CosmosDB.Emulator.exe /EnableCassandraEndpoint | |
CassandraPort | Specifies the port number to use for the Cassandra endpoint. Default value is 10350. | CosmosDB.Emulator.exe /CassandraPort = <cassandraport> | <cassandraport>: Single port number |
EnableGremlinEndpoint | Enables Gremlin API | CosmosDB.Emulator.exe /EnableGremlinEndpoint | |
GremlinPort | Port number to use for the Gremlin Endpoint. Default value is 8901. | CosmosDB.Emulator.exe /GremlinPort=<port> | <port>: Single port number |
EnableTableEndpoint | Enables Azure Table API | CosmosDB.Emulator.exe /EnableTableEndpoint | |
TablePort | Port number to use for the Azure Table Endpoint. Default value is 8902. | CosmosDB.Emulator.exe /TablePort=<port> | <port>: Single port number |
KeyFile | Read authorization key from the specified file. Use the /GenKeyFile option to generate a keyfile | CosmosDB.Emulator.exe /KeyFile=<file_name> | <file_name>: Path to the file |
ResetDataPath | Recursively removes all the files in the specified path. If you don't specify a path, it defaults to %LOCALAPPDATA%CosmosDbEmulator | CosmosDB.Emulator.exe /ResetDataPath=<path> | <path>: File path |
StartTraces | Start collecting debug trace logs. | CosmosDB.Emulator.exe /StartTraces | |
StopTraces | Stop collecting debug trace logs. | CosmosDB.Emulator.exe /StopTraces | |
FailOnSslCertificateNameMismatch | By default the Emulator regenerates its self-signed SSL certificate, if the certificate's SAN does not include the Emulator host's domain name, local IPv4 address, 'localhost', and '127.0.0.1'. With this option, the emulator will fail at startup instead. You should then use the /GenCert option to create and install a new self-signed SSL certificate. | CosmosDB.Emulator.exe /FailOnSslCertificateNameMismatch | |
GenCert | Generate and install a new self-signed SSL certificate. optionally including a comma-separated list of additional DNS names for accessing the Emulator over the network. | CosmosDB.Emulator.exe /GenCert=<dns-names> | <dns-names>: Optional comma-separated list of additional dns names |
DirectPorts | Specifies the ports to use for direct connectivity. Defaults are 10251,10252,10253,10254. | CosmosDB.Emulator.exe /DirectPorts:<directports> | <directports>: Comma-delimited list of 4 ports |
Key | Authorization key for the emulator. Key must be the base-64 encoding of a 64-byte vector. | CosmosDB.Emulator.exe /Key:<key> | <key>: Key must be the base-64 encoding of a 64-byte vector |
EnableRateLimiting | Specifies that request rate limiting behavior is enabled. | CosmosDB.Emulator.exe /EnableRateLimiting | |
DisableRateLimiting | Specifies that request rate limiting behavior is disabled. | CosmosDB.Emulator.exe /DisableRateLimiting | |
NoUI | Do not show the emulator user interface. | CosmosDB.Emulator.exe /NoUI | |
NoExplorer | Don't show data explorer on startup. | CosmosDB.Emulator.exe /NoExplorer | |
PartitionCount | Specifies the maximum number of partitioned containers. See Change the number of containers for more information. | CosmosDB.Emulator.exe /PartitionCount=<partitioncount> | <partitioncount>: Maximum number of allowed single partition containers. Default value is 25. Maximum allowed is 250. |
DefaultPartitionCount | Specifies the default number of partitions for a partitioned container. | CosmosDB.Emulator.exe /DefaultPartitionCount=<defaultpartitioncount> | <defaultpartitioncount> Default value is 25. |
AllowNetworkAccess | Enables access to the emulator over a network. You must also pass /Key=<key_string> or /KeyFile=<file_name> to enable network access. | CosmosDB.Emulator.exe /AllowNetworkAccess /Key=<key_string> or CosmosDB.Emulator.exe /AllowNetworkAccess /KeyFile=<file_name> | |
NoFirewall | Don't adjust firewall rules when /AllowNetworkAccess option is used. | CosmosDB.Emulator.exe /NoFirewall | |
GenKeyFile | Generate a new authorization key and save to the specified file. The generated key can be used with the /Key or /KeyFile options. | CosmosDB.Emulator.exe /GenKeyFile=<path to key file> | |
Consistency | Set the default consistency level for the account. | CosmosDB.Emulator.exe /Consistency=<consistency> | <consistency>: Value must be one of the following consistency levels: Session, Strong, Eventual, or BoundedStaleness. The default value is Session. |
? | Show the help message. |
%LOCALAPPDATA%CosmosDBEmulator
.C:Program FilesAzure Cosmos DB Emulator> CosmosDB.Emulator.exe /PartitionCount=100
.PSModules
directory on your PSModulesPath
and import it as shown in the following command:Get-CosmosDbEmulatorStatus
Get-CosmosDbEmulatorStatus
Start-CosmosDbEmulator
Start-CosmosDbEmulator [-DataPath <string>] [-DefaultPartitionCount <uint16>] [-DirectPort <uint16[]>] [-MongoPort <uint16>] [-NoUI] [-NoWait] [-PartitionCount <uint16>] [-Port <uint16>] [<CommonParameters>]
Stop-CosmosDbEmulator
Stop-CosmosDbEmulator [-NoWait]
Uninstall-CosmosDbEmulator
Uninstall-CosmosDbEmulator [-RemoveData]
HttpClientHandler
instance as shown in the following .Net code sample. This workaround is only applicable if you are using the Microsoft.Azure.DocumentDB
Nuget package, it isn't supported with the Microsoft.Azure.Cosmos
Nuget package:/allownetworkaccess
option and the emulator’s endpoint is accessible from the host IP address rather than host.docker.internal
DNS.ipconfig.exe
. The next step is to work around the CA validation when constructing the DocumentClient object. For this you will need to provide an HttpClientHandler to the DocumentClient constructor, which has it's own implementation for ServerCertificateCustomValidationCallback.Microsoft.Azure.Cosmos.ComputeServiceStartupEntryPoint.exe
, this might be a symptom where the Performance Counters are in a corrupted state. Usually running the following command from an admin command prompt fixes the issue:cd /d '%ProgramFiles%Azure Cosmos DB Emulator'
CosmosDB.Emulator.exe /shutdown
. Watch the system tray to make sure the program has shut down, it may take a minute. You can also just click Exit in the Azure Cosmos Emulator user interface.CosmosDB.Emulator.exe /starttraces
CosmosDB.Emulator.exe
CosmosDB.Emulator.exe /stoptraces
%ProgramFiles%Azure Cosmos DB Emulator
and find the docdbemulator_000001.etl file.%LOCALAPPDATA%CosmosDBEmulator
and delete the folder.What is QEMU for Windows - PPC emulator, runs Mac OS 9.1, 9.2 + OSX 10.0 to 10.5? QEMU is a very versatile and extremely broadly supported open source virtual machine emulator. In 2016, QEMU could finally achieve what has never been possible before: emulating Mac OS 9.0.4, 9.1 and 9.2.2 (albeit still it's quite slow and the sound support is kind of buggy at the moment). Note that QEMU can also emulate Mac OS X 10.0 up to 10.5. At some point in the near future hopefully, QEMU will fully replace SheepShaver, but at the moment, SheepShaver still runs faster in most situations. Advantages of using QEMU vs SheepShaver:
These bundles were put together by 'that-ben' and are intended to be the easiest possible for beginners. Just launch the 'QEMU - Mac OS 9.2.2.bat' (or 'QEMU - Mac OS X Tiger 10.4.11.bat') file and wait 30 seconds for Mac OS to boot up. Nevermind the yellow screen with a VRAM partition not found error, it will go past this without any problem. The Mac OS 9 package contains a 1GB disk image on which Mac OS 9.2.2 is already fully installed. The Mac OS X package contains Mac OS X 10.4.11. BTW, if you need a larger disk image, you can grab one instantly from here: Blank hard drive disk images (3GB HFS up to 30GB HFS+) Networking is fully functional thanks to the sungem driver that's already pre-configured in these downloads. Right out of the box, it will network through your host machine but on its own subnet branch. The virtual machine's IP will be like 10.0.x.x. Your Windows host IP would likely be something like 192.168.x.x but what's nice is that the virtual machine can still tunnel back to your host machine's subnet branch. So, for instance, you could perfectly well make a server/client environment between Mac OS 9 in QEMU and your Windows host machine. Pre-installed software in the Mac OS 9.2.2 package includes:
Pre-installed software in the Mac OS X 10.4.11 package includes:
See also:Basilisk II - a 68K emulator with floppy support Qemu_(20171224)_-_PPC_-_Mac_OS_X_10.4.11.rar(1197.59 MiB / 1255.76 MB) QEMU (2017/12/15 build) for Windows w/ Mac OS X 10.4.11 pre-installed, RAR'ed / RAR archive 112 / 2018-01-28 / 63bc2a712f342b55ae25eb4397e1f3ad097e71be / / Qemu (20190212) - PPC - Mac OS 9.2.2.rar(125.04 MiB / 131.11 MB) QEMU (2019/02/12 build) for Windows w/ Mac OS 9.2.2 pre-installed / RAR archive 584 / 2019-03-19 / 16daa6ef096db9391dd15e8a486e6c2648011b22 / / Architecture Intel x86-64 This program is for Windows. USEFUL TIPS WHEN USING QEMU:
|