Nexus 5k Upgrade Guide
Milba Vanpatten
Upgrading Sonatype Nexus Repository presents a necessary step to gain access to new features, bug fixes, performance improvements and other advantages. Regular updates to the latest release are recommended as a general best practice. Version 3 upgrades will only work from version 3.0.0 milestone 7 and later.
Extract the newest downloaded distribution archive using the standard approach. The archive distribution offers the familiar process of downloading and simply extracting the install archive in place. There is no graphical or automated process and all commands are done inside a terminal console.
Become familiar with the basic directory structure of a Sonatype Nexus Repository installation. You are encouraged to stick with the standard installation layout to make future upgrades as simple as possible.
Re-start replication once you've upgraded both instances to the same version. Content replication will pick up from the last successful replication timestamp and begin replicating any changes since that stored timestamp.
If you do not pause replication, the instances will temporarily be on different versions; this will cause replication to fail as both instances must be using the same version. Once both instances are on the same version again, content replication will pick back up from the last successful replication timestamp, which is stored in the repository configuration. Content replication will then replicate an content added since that timestamp.
Upgrades from a version older than 3.26.0 - Is your jetty-https.xml file outside of the install directory? If so, you will need to make some changes to it as we updated the Jetty version in 3.26.0 and older jetty-https.xml files will not work.
If you changed the default location of the temporary directory, then edit ./bin/nexus.vmoptions and replace the line -Djava.io.tmpdir=../sonatype-work/nexus3/tmp to point to your preferred temporary directory.
If you have enabled jetty HTTPS access, make sure your etc/jetty/jetty-https.xml SSL keystore location is still available to the new install and configured according to our recommendations.
If you manually adjusted any other install files under ./etcyou will need to manually perform a diff between the old files and the new files and apply your changes if applicable to the new version.
Ensure you have taken recent backups of the existing Data Directory and any custom blobstore locations according to our recommended practices. Because of involved Upgrade steps, downgrading a Nexus Repository version is not supported and will almost always result in failures. If you have issues, restore from this backup instead.
If you are using an H2 or PostgreSQL database and upgrading from a pre-3.48.0 release to 3.48.0 or later, you will need to run a task to rebuild metadata for each existing Apt, Helm, and Yum repository after upgrading:
Note: This guide is not fully up-to-date as it currently uses the deprecated version of the nexus-plugin-prisma. While this is still functional, it is recommended to use the new nexus-prisma library or an alternative code-first GraphQL library like Pothos going forward. If you have any questions, feel free to share them on our Discord.
The nexus-plugin-prisma dependency bundles all required Prisma ORM dependencies. You should therefore remove the dependencies that you added installed when you upgraded the Prisma ORM layer of your app:
Next you need to adjust the code where you currently create your GraphQLSchema, most likely this is currently happening via the makePrismaSchema function in your code. Since this function was imported from the removed nexus-prisma package, you'll need to replace it with the makeSchema function from the @nexus/schema package. The way how the Prisma ORM plugin for Nexus is used also changes in the latest version.
Note that t.model looks at the name attribute in the object that's passed as an argument to the objectType function and matches it against the models in your Prisma schema. In this case, it's matched against the User model. Therefore, t.model exposes functions that are named after the fields of the User model.
Note that t.model looks at the name attribute and matches it against the models in your Prisma schema. In this case, it's matched against the Post model. Therefore, t.model exposes functions that are named after the fields of the Post model.
Note that t.model looks at the name attribute and matches it against the models in your Prisma schema. In this case, it's matched against the Profile model. Therefore, t.model exposes functions that are named after the fields of the Profile model.
Note that t.model looks at the name attribute and matches it against the models in your Prisma schema. In this case, it's matched against the Category model. Therefore, t.model exposes functions that are named after the fields of the Category model.
Notice that the db object is automatically attached to the context by the nexus-plugin-prisma. It represents an instance of your PrismaClient which enables you to send queries to your database inside your resolvers.
To get the same behavior with the latest versions of @nexus/schema and the nexus-plugin-prisma, you need to call the createOneUser function on t.crud and pass an alias in order to rename the field in your GraphQL schema to createUser (otherwise it would be called createOneUser, after the function that's used):
In many states certain products are either exempted from sales tax, taxed at a lower rate, or even exempted below certain prices and within only certain jurisdictions. To help you make an accurate determination about how an individual item should be taxed, the TaxJar API allows you to submit a product_tax_code parameter with each line_item in an order.
If no product_tax_code is submitted with a line_item, then that item is deemed to be fully taxable. You do not need to send any information to tell TaxJar that something is taxable. It assumes that, unless told otherwise through the existence of a product_tax_code.
The very first bit of logic used when calculating sales tax is the notion of nexus. In short, whether or not your business has sufficient presence within a taxing jurisdiction to require you to remit sales tax.
If you are calculating tax just for your own business, you can store all of your nexus information within your TaxJar account. Just use the State Settings page to enter all of your business locations. When you make a call to the TaxJar API with your API token, we will look at your nexus information on file and calculate sales tax when appropriate. Of course, our ability to calculate properly will depend on your maintaining an accurate list of nexus locations. To add states and nexus locations, just go to the State Settings page and click the Add State with Nexus button.
If you would rather not load your locations into your TaxJar account or if you are trying to perform calculations for other merchants, you may pass in nexus information with each call to the TaxJar API. At minimum, if you pass in valid values for nexus_country and nexus_state, we can make a proper nexus determination.
In general, we recommend always passing in the address information from which an order ships. This gives us what we need to make sourcing determinations in both origin and destination states. If you know that you are shipping within/to a destination state, you may elect not to send from_ address information. In addition, in the absence of from_address parameters, we will look to your State Settings in your TaxJar account, using the address information there. However, we recommend a best practice of always sending from_ address information.
First, if you are the merchant of record, then you are responsible for collecting and remitting sales tax for all of those sales. In such a case, you would use the TaxJar API to calculate the proper amount of tax to collect, then, if you wish to use TaxJar for reporting and filing, send completed orders to TaxJar using the same API token that is tied to your account.
While the TaxJar API was originally created as a way for eCommerce marketplaces to provide compliance help for merchants, our transaction endpoints also make it possible to build an integration from any shopping cart, invoicing tool or accounting platform to TaxJar.
If you already provide customers with a reporting interface that allows them to select a date range to view orders within that range, simply add a button that uses the same date range to query and send those orders/refunds.
Want a simple way to reduce the number of TaxJar API calls you need to make? Compare the delivery address of an order or invoice to the list of nexus_addresses for your business or merchant. If the delivery address falls in a different state than those in which your business (or merchant of sale) has nexus, no sales tax need be collected. Note, this only works for US-based sales.
Furthermore, many carts estimate taxes in the cart or preview pages prior to checkout. You could consider eliminating this estimate or at least delaying it until the shopper is closer to completing the purchase. During checkout make sure you wait to make a request to calculate tax until the shipping address is complete. Many customers use an address validation service to ensure a valid shipping address prior to calling the TaxJar API with the final order totals and shipping from and to addresses.
At TaxJar, we provide official integrations for popular eCommerce platforms such as WooCommerce and Magento. All of our official integrations are built and maintained in-house by eCommerce experts.
Dozens of certified integrations are available for other popular marketplaces and eCommerce, ERP, POS, accounting, inventory management, and order management platforms as well. These integrations are built and maintained by third-party developers and tested and certified by the TaxJar team. See the full list of integrations built by our partners.
93ddb68554